Public report of rerun-io/rerun, published 14 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 14 November 2026, 16:34 UTC · Survey ID cd_640b47e44d654a84a148d92ce8452d2d
rerun-io/rerun
Measured 14 November 2026, 16:32 UTC, at code version 330fe94
CAI scoreAt riskNo change 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 very large codebase: 591,051 lines of product code in 126 projects, tests not counted · Estimated rebuild effort: about 5.4 person-years · Weakest lens: Production Readiness, 54
Findings by how serious they are
149 critical3405 serious218 minor
23 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
14 November 2026, 16:32 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 ▸
72of 72 dimensions measured by tools.
3584of 3772 findings point to an exact file and line, so you can open each one in the code. The other 188 concern the repository as a whole, such as missing documentation.
72dimensions across 8 lenses, read from 591,051 lines of product code in 126 projects.
rerun-io/rerun is rated At risk because critical security findings are open, most of them in the build pipeline. It scores 61 out of 100, which the At risk rating leaves unchanged. We judged it as a preview release, against a lower bar.
Production Readiness, at 54, is the weakest lens and counts most in the score. The best first steps are adding tests for the code no test reaches and protecting outgoing calls with timeouts, each worth about 4 points. Raising Production Readiness to 62 would lift the score to about 65.
Ninety-one secrets can leak from the build pipeline. Forty pipeline steps put outside input straight into a shell command, so an attacker can run commands in the build pipeline. Limiting each secret to its own step and passing outside input through environment variables would close both risks. Fixing the weaknesses the scanner points to would fix the five security weaknesses in the code, and the three unsafe settings in infrastructure or container files need changing to safe values. The page that blocks zooming needs the zoom block removed.
The product code is 591,051 lines, about €780,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 Production Readiness rose from 54 to 62, the lowest score rated Strong, the score would rise from 61 to about 65.
Code composition: what the lines of code are
Product code 83%Tests 17%
New since the last survey: 1100 findings
These 1100 critical or serious findings weren't in the previous survey, on 27 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.
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: 752 findings
These 752 critical or serious findings were in the previous survey, on 27 October 2026, and are gone from this one. The first 100 are listed here.
€260,000 to €1,300,000, for 4,322 to 13,710 hours of work, about 5.4 person-years for 3 to 11 engineers
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.8 at a score of 61. 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
Very large: 591,051 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 tests that import the unreached modules (directly or through their public entry).
Raises the score by about 4 points · Medium effort · Test Coverage
2
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.
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 €780,000 to build again, about 5.4 person-years of work. Its weakest lens is Production Readiness, at 54 (Adequate). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Add tests that import the unreached modules (directly or through their public entry). Of all the actions in this report, it raises the score most for the work it takes: about 4 points for medium effort. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 7.4 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 2% to 5% on every change. The history of the code shows how much it changes: about 398,564 lines over the last 90 days, which is about 1,616,398 lines a year. At that pace, the extra work comes to an estimated 80.8 to 538.8 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
2620 modules, with 7094 dependencies between them. 47 loops run through 257 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 2580 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.
1 pair of types, where a type in re_analytics.event uses a type in re_byte_size.
The types involved
re_analytics.event.Id → re_byte_size.SizeBytes
Direction
re_analytics.event uses re_byte_size, so a change to re_byte_size can break re_analytics.event, while a change to re_analytics.event can't break re_byte_size.
Position
Below the diagonal: re_analytics.event uses a module listed above it, which is the healthy direction.
re_log_types.index.absolute_time_range uses re_log_types.index.time_int, so a change to re_log_types.index.time_int can break re_log_types.index.absolute_time_range, while a change to re_log_types.index.absolute_time_range can't break re_log_types.index.time_int.
Position
Below the diagonal: re_log_types.index.absolute_time_range uses a module listed above it, which is the healthy direction.
re_renderer.wgpu_buffer_types uses re_byte_size, so a change to re_byte_size can break re_renderer.wgpu_buffer_types, while a change to re_renderer.wgpu_buffer_types can't break re_byte_size.
Position
Below the diagonal: re_renderer.wgpu_buffer_types uses a module listed above it, which is the healthy direction.
re_types_core.chunk_id uses re_types_core.component_descriptor, so a change to re_types_core.component_descriptor can break re_types_core.chunk_id, while a change to re_types_core.chunk_id can't break re_types_core.component_descriptor.
Position
Below the diagonal: re_types_core.chunk_id uses a module listed above it, which is the healthy direction.
re_types_core.row_id uses re_types_core.component_descriptor, so a change to re_types_core.component_descriptor can break re_types_core.row_id, while a change to re_types_core.row_id can't break re_types_core.component_descriptor.
Position
Below the diagonal: re_types_core.row_id uses a module listed above it, which is the healthy direction.
re_chunk.latest_at uses re_log_types.index.time_int, so a change to re_log_types.index.time_int can break re_chunk.latest_at, while a change to re_chunk.latest_at can't break re_log_types.index.time_int.
Position
Below the diagonal: re_chunk.latest_at uses a module listed above it, which is the healthy direction.
re_chunk.latest_at uses re_types_core.chunk_id, so a change to re_types_core.chunk_id can break re_chunk.latest_at, while a change to re_chunk.latest_at can't break re_types_core.chunk_id.
Position
Below the diagonal: re_chunk.latest_at uses a module listed above it, which is the healthy direction.
re_log_types.index.time_type uses re_log_types.index.time_int, so a change to re_log_types.index.time_int can break re_log_types.index.time_type, while a change to re_log_types.index.time_type can't break re_log_types.index.time_int.
Position
Below the diagonal: re_log_types.index.time_type uses a module listed above it, which is the healthy direction.
re_log_types.index.time_type uses re_log_types.index.absolute_time_range, so a change to re_log_types.index.absolute_time_range can break re_log_types.index.time_type, while a change to re_log_types.index.time_type can't break re_log_types.index.absolute_time_range.
Position
Below the diagonal: re_log_types.index.time_type uses a module listed above it, which is the healthy direction.
re_chunk.chunk uses re_log_types.index.time_int, so a change to re_log_types.index.time_int can break re_chunk.chunk, while a change to re_chunk.chunk can't break re_log_types.index.time_int.
Position
Below the diagonal: re_chunk.chunk uses a module listed above it, which is the healthy direction.
re_chunk.chunk uses re_log_types.path.entity_path, so a change to re_log_types.path.entity_path can break re_chunk.chunk, while a change to re_chunk.chunk can't break re_log_types.path.entity_path.
Position
Below the diagonal: re_chunk.chunk uses a module listed above it, which is the healthy direction.
re_chunk.chunk uses re_types_core.component_descriptor, so a change to re_types_core.component_descriptor can break re_chunk.chunk, while a change to re_chunk.chunk can't break re_types_core.component_descriptor.
Position
Below the diagonal: re_chunk.chunk uses a module listed above it, which is the healthy direction.
re_chunk.chunk uses re_log_types.index.absolute_time_range, so a change to re_log_types.index.absolute_time_range can break re_chunk.chunk, while a change to re_chunk.chunk can't break re_log_types.index.absolute_time_range.
Position
Below the diagonal: re_chunk.chunk uses a module listed above it, which is the healthy direction.
re_chunk.chunk uses re_types_core.chunk_id, so a change to re_types_core.chunk_id can break re_chunk.chunk, while a change to re_chunk.chunk can't break re_types_core.chunk_id.
Position
Below the diagonal: re_chunk.chunk uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in re_chunk.chunk uses a type in re_types_core.row_id.
The types involved
re_chunk.chunk.Chunk → re_types_core.row_id.RowId
Direction
re_chunk.chunk uses re_types_core.row_id, so a change to re_types_core.row_id can break re_chunk.chunk, while a change to re_chunk.chunk can't break re_types_core.row_id.
Position
Below the diagonal: re_chunk.chunk uses a module listed above it, which is the healthy direction.
re_chunk.chunk uses re_chunk.latest_at, so a change to re_chunk.latest_at can break re_chunk.chunk, while a change to re_chunk.chunk can't break re_chunk.latest_at.
Position
Below the diagonal: re_chunk.chunk uses a module listed above it, which is the healthy direction.
re_entity_db.entity_db uses re_byte_size, so a change to re_byte_size can break re_entity_db.entity_db, while a change to re_entity_db.entity_db can't break re_byte_size.
Position
Below the diagonal: re_entity_db.entity_db uses a module listed above it, which is the healthy direction.
re_entity_db.entity_db uses re_byte_size.mem_usage_tree, so a change to re_byte_size.mem_usage_tree can break re_entity_db.entity_db, while a change to re_entity_db.entity_db can't break re_byte_size.mem_usage_tree.
Position
Below the diagonal: re_entity_db.entity_db uses a module listed above it, which is the healthy direction.
re_entity_db.entity_db uses re_log_types.index.time_int, so a change to re_log_types.index.time_int can break re_entity_db.entity_db, while a change to re_entity_db.entity_db can't break re_log_types.index.time_int.
Position
Below the diagonal: re_entity_db.entity_db uses a module listed above it, which is the healthy direction.
re_entity_db.entity_db uses re_log_types.path.entity_path, so a change to re_log_types.path.entity_path can break re_entity_db.entity_db, while a change to re_entity_db.entity_db can't break re_log_types.path.entity_path.
Position
Below the diagonal: re_entity_db.entity_db uses a module listed above it, which is the healthy direction.
re_entity_db.entity_db uses re_types_core.component_descriptor, so a change to re_types_core.component_descriptor can break re_entity_db.entity_db, while a change to re_entity_db.entity_db can't break re_types_core.component_descriptor.
Position
Below the diagonal: re_entity_db.entity_db uses a module listed above it, which is the healthy direction.
re_entity_db.entity_db uses re_log_types.index.absolute_time_range, so a change to re_log_types.index.absolute_time_range can break re_entity_db.entity_db, while a change to re_entity_db.entity_db can't break re_log_types.index.absolute_time_range.
Position
Below the diagonal: re_entity_db.entity_db uses a module listed above it, which is the healthy direction.
re_entity_db.entity_db uses re_types_core.row_id, so a change to re_types_core.row_id can break re_entity_db.entity_db, while a change to re_entity_db.entity_db can't break re_types_core.row_id.
Position
Below the diagonal: re_entity_db.entity_db uses a module listed above it, which is the healthy direction.
re_entity_db.entity_db uses re_chunk.latest_at, so a change to re_chunk.latest_at can break re_entity_db.entity_db, while a change to re_entity_db.entity_db can't break re_chunk.latest_at.
Position
Below the diagonal: re_entity_db.entity_db uses a module listed above it, which is the healthy direction.
re_entity_db.entity_db uses re_log_types.index.time_type, so a change to re_log_types.index.time_type can break re_entity_db.entity_db, while a change to re_entity_db.entity_db can't break re_log_types.index.time_type.
Position
Below the diagonal: re_entity_db.entity_db uses a module listed above it, which is the healthy direction.
re_entity_db.entity_db uses re_chunk.chunk, so a change to re_chunk.chunk can break re_entity_db.entity_db, while a change to re_entity_db.entity_db can't break re_chunk.chunk.
Position
Below the diagonal: re_entity_db.entity_db uses a module listed above it, which is the healthy direction.
26→36 re_entity_db.entity_db uses re_viewer_context.app_contextpart of a loop✕
Connections
1 pair of types, where a type in re_entity_db.entity_db uses a type in re_viewer_context.app_context.
re_entity_db.entity_db uses re_viewer_context.app_context, so a change to re_viewer_context.app_context can break re_entity_db.entity_db, while a change to re_entity_db.entity_db can't break re_viewer_context.app_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.
26→37 re_entity_db.entity_db uses re_log_types.store_idpart of a loop✕
Connections
3 pairs of types, where a type in re_entity_db.entity_db uses a type in re_log_types.store_id.
re_entity_db.entity_db uses re_log_types.store_id, so a change to re_log_types.store_id can break re_entity_db.entity_db, while a change to re_entity_db.entity_db can't break re_log_types.store_id.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
26→38 re_entity_db.entity_db uses re_chunk_store.storepart of a loop✕
Connections
2 pairs of types, where a type in re_entity_db.entity_db uses a type in re_chunk_store.store.
re_entity_db.entity_db uses re_chunk_store.store, so a change to re_chunk_store.store can break re_entity_db.entity_db, while a change to re_entity_db.entity_db can't break re_chunk_store.store.
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.
re_viewer_context.item uses re_log_types.entry_id, so a change to re_log_types.entry_id can break re_viewer_context.item, while a change to re_viewer_context.item can't break re_log_types.entry_id.
Position
Below the diagonal: re_viewer_context.item uses a module listed above it, which is the healthy direction.
re_viewer_context.item uses re_log_types.path.entity_path, so a change to re_log_types.path.entity_path can break re_viewer_context.item, while a change to re_viewer_context.item can't break re_log_types.path.entity_path.
Position
Below the diagonal: re_viewer_context.item uses a module listed above it, which is the healthy direction.
re_viewer_context.item uses re_uri.origin, so a change to re_uri.origin can break re_viewer_context.item, while a change to re_viewer_context.item can't break re_uri.origin.
Position
Below the diagonal: re_viewer_context.item uses a module listed above it, which is the healthy direction.
re_viewer_context.item uses re_chunk.latest_at, so a change to re_chunk.latest_at can break re_viewer_context.item, while a change to re_viewer_context.item can't break re_chunk.latest_at.
Position
Below the diagonal: re_viewer_context.item uses a module listed above it, which is the healthy direction.
re_viewer_context.item uses re_entity_db.entity_db, so a change to re_entity_db.entity_db can break re_viewer_context.item, while a change to re_viewer_context.item can't break re_entity_db.entity_db.
Position
Below the diagonal: re_viewer_context.item uses a module listed above it, which is the healthy direction.
re_viewer_context.store_view_context uses re_renderer.context, so a change to re_renderer.context can break re_viewer_context.store_view_context, while a change to re_viewer_context.store_view_context can't break re_renderer.context.
Position
Below the diagonal: re_viewer_context.store_view_context uses a module listed above it, which is the healthy direction.
re_viewer_context.store_view_context uses re_viewer_context.app_options, so a change to re_viewer_context.app_options can break re_viewer_context.store_view_context, while a change to re_viewer_context.store_view_context can't break re_viewer_context.app_options.
Position
Below the diagonal: re_viewer_context.store_view_context uses a module listed above it, which is the healthy direction.
re_viewer_context.store_view_context uses re_chunk.latest_at, so a change to re_chunk.latest_at can break re_viewer_context.store_view_context, while a change to re_viewer_context.store_view_context can't break re_chunk.latest_at.
Position
Below the diagonal: re_viewer_context.store_view_context uses a module listed above it, which is the healthy direction.
re_viewer_context.store_view_context uses re_entity_db.entity_db, so a change to re_entity_db.entity_db can break re_viewer_context.store_view_context, while a change to re_viewer_context.store_view_context can't break re_entity_db.entity_db.
Position
Below the diagonal: re_viewer_context.store_view_context uses a module listed above it, which is the healthy direction.
28→36 re_viewer_context.store_view_context uses re_viewer_context.app_contextpart of a loop✕
Connections
1 pair of types, where a type in re_viewer_context.store_view_context uses a type in re_viewer_context.app_context.
re_viewer_context.store_view_context uses re_viewer_context.app_context, so a change to re_viewer_context.app_context can break re_viewer_context.store_view_context, while a change to re_viewer_context.store_view_context can't break re_viewer_context.app_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.
re_viewer_context.viewer_context uses re_log_types.entry_id, so a change to re_log_types.entry_id can break re_viewer_context.viewer_context, while a change to re_viewer_context.viewer_context can't break re_log_types.entry_id.
Position
Below the diagonal: re_viewer_context.viewer_context uses a module listed above it, which is the healthy direction.
re_viewer_context.viewer_context uses re_log_types.path.entity_path, so a change to re_log_types.path.entity_path can break re_viewer_context.viewer_context, while a change to re_viewer_context.viewer_context can't break re_log_types.path.entity_path.
Position
Below the diagonal: re_viewer_context.viewer_context uses a module listed above it, which is the healthy direction.
re_viewer_context.viewer_context uses re_renderer.context, so a change to re_renderer.context can break re_viewer_context.viewer_context, while a change to re_viewer_context.viewer_context can't break re_renderer.context.
Position
Below the diagonal: re_viewer_context.viewer_context uses a module listed above it, which is the healthy direction.
re_viewer_context.viewer_context uses re_types_core.view, so a change to re_types_core.view can break re_viewer_context.viewer_context, while a change to re_viewer_context.viewer_context can't break re_types_core.view.
Position
Below the diagonal: re_viewer_context.viewer_context uses a module listed above it, which is the healthy direction.
re_viewer_context.viewer_context uses re_viewer_context.app_options, so a change to re_viewer_context.app_options can break re_viewer_context.viewer_context, while a change to re_viewer_context.viewer_context can't break re_viewer_context.app_options.
Position
Below the diagonal: re_viewer_context.viewer_context uses a module listed above it, which is the healthy direction.
re_viewer_context.viewer_context uses re_chunk.latest_at, so a change to re_chunk.latest_at can break re_viewer_context.viewer_context, while a change to re_viewer_context.viewer_context can't break re_chunk.latest_at.
Position
Below the diagonal: re_viewer_context.viewer_context uses a module listed above it, which is the healthy direction.
re_viewer_context.viewer_context uses re_entity_db.entity_db, so a change to re_entity_db.entity_db can break re_viewer_context.viewer_context, while a change to re_viewer_context.viewer_context can't break re_entity_db.entity_db.
Position
Below the diagonal: re_viewer_context.viewer_context uses a module listed above it, which is the healthy direction.
re_viewer_context.viewer_context uses re_viewer_context.item, so a change to re_viewer_context.item can break re_viewer_context.viewer_context, while a change to re_viewer_context.viewer_context can't break re_viewer_context.item.
Position
Below the diagonal: re_viewer_context.viewer_context uses a module listed above it, which is the healthy direction.
re_viewer_context.viewer_context uses re_viewer_context.store_view_context, so a change to re_viewer_context.store_view_context can break re_viewer_context.viewer_context, while a change to re_viewer_context.viewer_context can't break re_viewer_context.store_view_context.
Position
Below the diagonal: re_viewer_context.viewer_context uses a module listed above it, which is the healthy direction.
29→31 re_viewer_context.viewer_context uses re_viewer_context.query_contextpart of a loop✕
Connections
1 pair of types, where a type in re_viewer_context.viewer_context uses a type in re_viewer_context.query_context.
re_viewer_context.viewer_context uses re_viewer_context.query_context, so a change to re_viewer_context.query_context can break re_viewer_context.viewer_context, while a change to re_viewer_context.viewer_context can't break re_viewer_context.query_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.
29→35 re_viewer_context.viewer_context uses re_viewer_context.view.view_class_registrypart of a loop✕
Connections
1 pair of types, where a type in re_viewer_context.viewer_context uses a type in re_viewer_context.view.view_class_registry.
re_viewer_context.viewer_context uses re_viewer_context.view.view_class_registry, so a change to re_viewer_context.view.view_class_registry can break re_viewer_context.viewer_context, while a change to re_viewer_context.viewer_context can't break re_viewer_context.view.view_class_registry.
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.
29→36 re_viewer_context.viewer_context uses re_viewer_context.app_contextpart of a loop✕
Connections
1 pair of types, where a type in re_viewer_context.viewer_context uses a type in re_viewer_context.app_context.
re_viewer_context.viewer_context uses re_viewer_context.app_context, so a change to re_viewer_context.app_context can break re_viewer_context.viewer_context, while a change to re_viewer_context.viewer_context can't break re_viewer_context.app_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.
29→37 re_viewer_context.viewer_context uses re_log_types.store_idpart of a loop✕
Connections
1 pair of types, where a type in re_viewer_context.viewer_context uses a type in re_log_types.store_id.
re_viewer_context.viewer_context uses re_log_types.store_id, so a change to re_log_types.store_id can break re_viewer_context.viewer_context, while a change to re_viewer_context.viewer_context can't break re_log_types.store_id.
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.
re_viewer_context.view.view_query uses re_log_types.index.time_int, so a change to re_log_types.index.time_int can break re_viewer_context.view.view_query, while a change to re_viewer_context.view.view_query can't break re_log_types.index.time_int.
Position
Below the diagonal: re_viewer_context.view.view_query uses a module listed above it, which is the healthy direction.
re_viewer_context.view.view_query uses re_log_types.path.entity_path, so a change to re_log_types.path.entity_path can break re_viewer_context.view.view_query, while a change to re_viewer_context.view.view_query can't break re_log_types.path.entity_path.
Position
Below the diagonal: re_viewer_context.view.view_query uses a module listed above it, which is the healthy direction.
re_viewer_context.view.view_query uses re_types_core.component_descriptor, so a change to re_types_core.component_descriptor can break re_viewer_context.view.view_query, while a change to re_viewer_context.view.view_query can't break re_types_core.component_descriptor.
Position
Below the diagonal: re_viewer_context.view.view_query uses a module listed above it, which is the healthy direction.
re_viewer_context.view.view_query uses re_viewer_context.view.named_system, so a change to re_viewer_context.view.named_system can break re_viewer_context.view.view_query, while a change to re_viewer_context.view.view_query can't break re_viewer_context.view.named_system.
Position
Below the diagonal: re_viewer_context.view.view_query uses a module listed above it, which is the healthy direction.
re_viewer_context.view.view_query uses re_chunk.latest_at, so a change to re_chunk.latest_at can break re_viewer_context.view.view_query, while a change to re_viewer_context.view.view_query can't break re_chunk.latest_at.
Position
Below the diagonal: re_viewer_context.view.view_query uses a module listed above it, which is the healthy direction.
re_viewer_context.view.view_query uses re_viewer_context.viewer_context, so a change to re_viewer_context.viewer_context can break re_viewer_context.view.view_query, while a change to re_viewer_context.view.view_query can't break re_viewer_context.viewer_context.
Position
Below the diagonal: re_viewer_context.view.view_query uses a module listed above it, which is the healthy direction.
30→31 re_viewer_context.view.view_query uses re_viewer_context.query_contextpart of a loop✕
Connections
1 pair of types, where a type in re_viewer_context.view.view_query uses a type in re_viewer_context.query_context.
re_viewer_context.view.view_query uses re_viewer_context.query_context, so a change to re_viewer_context.query_context can break re_viewer_context.view.view_query, while a change to re_viewer_context.view.view_query can't break re_viewer_context.query_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.
30→33 re_viewer_context.view.view_query uses re_viewer_context.view.view_contextpart of a loop✕
Connections
1 pair of types, where a type in re_viewer_context.view.view_query uses a type in re_viewer_context.view.view_context.
re_viewer_context.view.view_query uses re_viewer_context.view.view_context, so a change to re_viewer_context.view.view_context can break re_viewer_context.view.view_query, while a change to re_viewer_context.view.view_query can't break re_viewer_context.view.view_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.
re_viewer_context.query_context uses re_log_types.path.entity_path, so a change to re_log_types.path.entity_path can break re_viewer_context.query_context, while a change to re_viewer_context.query_context can't break re_log_types.path.entity_path.
Position
Below the diagonal: re_viewer_context.query_context uses a module listed above it, which is the healthy direction.
re_viewer_context.query_context uses re_renderer.context, so a change to re_renderer.context can break re_viewer_context.query_context, while a change to re_viewer_context.query_context can't break re_renderer.context.
Position
Below the diagonal: re_viewer_context.query_context uses a module listed above it, which is the healthy direction.
re_viewer_context.query_context uses re_chunk.latest_at, so a change to re_chunk.latest_at can break re_viewer_context.query_context, while a change to re_viewer_context.query_context can't break re_chunk.latest_at.
Position
Below the diagonal: re_viewer_context.query_context uses a module listed above it, which is the healthy direction.
re_viewer_context.query_context uses re_entity_db.entity_db, so a change to re_entity_db.entity_db can break re_viewer_context.query_context, while a change to re_viewer_context.query_context can't break re_entity_db.entity_db.
Position
Below the diagonal: re_viewer_context.query_context uses a module listed above it, which is the healthy direction.
re_viewer_context.query_context uses re_viewer_context.viewer_context, so a change to re_viewer_context.viewer_context can break re_viewer_context.query_context, while a change to re_viewer_context.query_context can't break re_viewer_context.viewer_context.
Position
Below the diagonal: re_viewer_context.query_context uses a module listed above it, which is the healthy direction.
re_viewer_context.query_context uses re_viewer_context.view.view_query, so a change to re_viewer_context.view.view_query can break re_viewer_context.query_context, while a change to re_viewer_context.query_context can't break re_viewer_context.view.view_query.
Position
Below the diagonal: re_viewer_context.query_context uses a module listed above it, which is the healthy direction.
31→33 re_viewer_context.query_context uses re_viewer_context.view.view_contextpart of a loop✕
Connections
1 pair of types, where a type in re_viewer_context.query_context uses a type in re_viewer_context.view.view_context.
re_viewer_context.query_context uses re_viewer_context.view.view_context, so a change to re_viewer_context.view.view_context can break re_viewer_context.query_context, while a change to re_viewer_context.query_context can't break re_viewer_context.view.view_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.
31→36 re_viewer_context.query_context uses re_viewer_context.app_contextpart of a loop✕
Connections
1 pair of types, where a type in re_viewer_context.query_context uses a type in re_viewer_context.app_context.
re_viewer_context.query_context uses re_viewer_context.app_context, so a change to re_viewer_context.app_context can break re_viewer_context.query_context, while a change to re_viewer_context.query_context can't break re_viewer_context.app_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.
re_viewer_context.view.visualizer_system uses re_types_core.component_descriptor, so a change to re_types_core.component_descriptor can break re_viewer_context.view.visualizer_system, while a change to re_viewer_context.view.visualizer_system can't break re_types_core.component_descriptor.
Position
Below the diagonal: re_viewer_context.view.visualizer_system uses a module listed above it, which is the healthy direction.
re_viewer_context.view.visualizer_system uses re_types_core.view, so a change to re_types_core.view can break re_viewer_context.view.visualizer_system, while a change to re_viewer_context.view.visualizer_system can't break re_types_core.view.
Position
Below the diagonal: re_viewer_context.view.visualizer_system uses a module listed above it, which is the healthy direction.
re_viewer_context.view.visualizer_system uses re_viewer_context.app_options, so a change to re_viewer_context.app_options can break re_viewer_context.view.visualizer_system, while a change to re_viewer_context.view.visualizer_system can't break re_viewer_context.app_options.
Position
Below the diagonal: re_viewer_context.view.visualizer_system uses a module listed above it, which is the healthy direction.
re_viewer_context.view.visualizer_system uses re_viewer_context.view.named_system, so a change to re_viewer_context.view.named_system can break re_viewer_context.view.visualizer_system, while a change to re_viewer_context.view.visualizer_system can't break re_viewer_context.view.named_system.
Position
Below the diagonal: re_viewer_context.view.visualizer_system uses a module listed above it, which is the healthy direction.
re_viewer_context.view.visualizer_system uses re_viewer_context.view.view_query, so a change to re_viewer_context.view.view_query can break re_viewer_context.view.visualizer_system, while a change to re_viewer_context.view.visualizer_system can't break re_viewer_context.view.view_query.
Position
Below the diagonal: re_viewer_context.view.visualizer_system uses a module listed above it, which is the healthy direction.
32→33 re_viewer_context.view.visualizer_system uses re_viewer_context.view.view_contextpart of a loop✕
Connections
1 pair of types, where a type in re_viewer_context.view.visualizer_system uses a type in re_viewer_context.view.view_context.
re_viewer_context.view.visualizer_system uses re_viewer_context.view.view_context, so a change to re_viewer_context.view.view_context can break re_viewer_context.view.visualizer_system, while a change to re_viewer_context.view.visualizer_system can't break re_viewer_context.view.view_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.
32→34 re_viewer_context.view.visualizer_system uses re_viewer_context.view.view_context_systempart of a loop✕
Connections
1 pair of types, where a type in re_viewer_context.view.visualizer_system uses a type in re_viewer_context.view.view_context_system.
re_viewer_context.view.visualizer_system uses re_viewer_context.view.view_context_system, so a change to re_viewer_context.view.view_context_system can break re_viewer_context.view.visualizer_system, while a change to re_viewer_context.view.visualizer_system can't break re_viewer_context.view.view_context_system.
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.
re_viewer_context.view.view_context uses re_log_types.path.entity_path, so a change to re_log_types.path.entity_path can break re_viewer_context.view.view_context, while a change to re_viewer_context.view.view_context can't break re_log_types.path.entity_path.
Position
Below the diagonal: re_viewer_context.view.view_context uses a module listed above it, which is the healthy direction.
re_viewer_context.view.view_context uses re_renderer.context, so a change to re_renderer.context can break re_viewer_context.view.view_context, while a change to re_viewer_context.view.view_context can't break re_renderer.context.
Position
Below the diagonal: re_viewer_context.view.view_context uses a module listed above it, which is the healthy direction.
re_viewer_context.view.view_context uses re_types_core.component_descriptor, so a change to re_types_core.component_descriptor can break re_viewer_context.view.view_context, while a change to re_viewer_context.view.view_context can't break re_types_core.component_descriptor.
Position
Below the diagonal: re_viewer_context.view.view_context uses a module listed above it, which is the healthy direction.
re_viewer_context.view.view_context uses re_types_core.view, so a change to re_types_core.view can break re_viewer_context.view.view_context, while a change to re_viewer_context.view.view_context can't break re_types_core.view.
Position
Below the diagonal: re_viewer_context.view.view_context uses a module listed above it, which is the healthy direction.
re_viewer_context.view.view_context uses re_chunk.latest_at, so a change to re_chunk.latest_at can break re_viewer_context.view.view_context, while a change to re_viewer_context.view.view_context can't break re_chunk.latest_at.
Position
Below the diagonal: re_viewer_context.view.view_context uses a module listed above it, which is the healthy direction.
re_viewer_context.view.view_context uses re_entity_db.entity_db, so a change to re_entity_db.entity_db can break re_viewer_context.view.view_context, while a change to re_viewer_context.view.view_context can't break re_entity_db.entity_db.
Position
Below the diagonal: re_viewer_context.view.view_context uses a module listed above it, which is the healthy direction.
re_viewer_context.view.view_context uses re_viewer_context.viewer_context, so a change to re_viewer_context.viewer_context can break re_viewer_context.view.view_context, while a change to re_viewer_context.view.view_context can't break re_viewer_context.viewer_context.
Position
Below the diagonal: re_viewer_context.view.view_context uses a module listed above it, which is the healthy direction.
re_viewer_context.view.view_context uses re_viewer_context.view.view_query, so a change to re_viewer_context.view.view_query can break re_viewer_context.view.view_context, while a change to re_viewer_context.view.view_context can't break re_viewer_context.view.view_query.
Position
Below the diagonal: re_viewer_context.view.view_context uses a module listed above it, which is the healthy direction.
re_viewer_context.view.view_context uses re_viewer_context.query_context, so a change to re_viewer_context.query_context can break re_viewer_context.view.view_context, while a change to re_viewer_context.view.view_context can't break re_viewer_context.query_context.
Position
Below the diagonal: re_viewer_context.view.view_context uses a module listed above it, which is the healthy direction.
re_viewer_context.view.view_context uses re_viewer_context.view.visualizer_system, so a change to re_viewer_context.view.visualizer_system can break re_viewer_context.view.view_context, while a change to re_viewer_context.view.view_context can't break re_viewer_context.view.visualizer_system.
Position
Below the diagonal: re_viewer_context.view.view_context uses a module listed above it, which is the healthy direction.
33→35 re_viewer_context.view.view_context uses re_viewer_context.view.view_class_registrypart of a loop✕
Connections
1 pair of types, where a type in re_viewer_context.view.view_context uses a type in re_viewer_context.view.view_class_registry.
re_viewer_context.view.view_context uses re_viewer_context.view.view_class_registry, so a change to re_viewer_context.view.view_class_registry can break re_viewer_context.view.view_context, while a change to re_viewer_context.view.view_context can't break re_viewer_context.view.view_class_registry.
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.
33→37 re_viewer_context.view.view_context uses re_log_types.store_idpart of a loop✕
Connections
1 pair of types, where a type in re_viewer_context.view.view_context uses a type in re_log_types.store_id.
re_viewer_context.view.view_context uses re_log_types.store_id, so a change to re_log_types.store_id can break re_viewer_context.view.view_context, while a change to re_viewer_context.view.view_context can't break re_log_types.store_id.
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.
re_viewer_context.view.view_context_system uses re_types_core.view, so a change to re_types_core.view can break re_viewer_context.view.view_context_system, while a change to re_viewer_context.view.view_context_system can't break re_types_core.view.
Position
Below the diagonal: re_viewer_context.view.view_context_system uses a module listed above it, which is the healthy direction.
re_viewer_context.view.view_context_system uses re_viewer_context.viewer_context, so a change to re_viewer_context.viewer_context can break re_viewer_context.view.view_context_system, while a change to re_viewer_context.view.view_context_system can't break re_viewer_context.viewer_context.
Position
Below the diagonal: re_viewer_context.view.view_context_system uses a module listed above it, which is the healthy direction.
re_viewer_context.view.view_context_system uses re_viewer_context.view.view_query, so a change to re_viewer_context.view.view_query can break re_viewer_context.view.view_context_system, while a change to re_viewer_context.view.view_context_system can't break re_viewer_context.view.view_query.
Position
Below the diagonal: re_viewer_context.view.view_context_system uses a module listed above it, which is the healthy direction.
re_viewer_context.view.view_context_system uses re_viewer_context.view.visualizer_system, so a change to re_viewer_context.view.visualizer_system can break re_viewer_context.view.view_context_system, while a change to re_viewer_context.view.view_context_system can't break re_viewer_context.view.visualizer_system.
Position
Below the diagonal: re_viewer_context.view.view_context_system uses a module listed above it, which is the healthy direction.
re_viewer_context.view.view_context_system uses re_viewer_context.view.view_context, so a change to re_viewer_context.view.view_context can break re_viewer_context.view.view_context_system, while a change to re_viewer_context.view.view_context_system can't break re_viewer_context.view.view_context.
Position
Below the diagonal: re_viewer_context.view.view_context_system uses a module listed above it, which is the healthy direction.
re_viewer_context.view.view_class_registry uses re_types_core.view, so a change to re_types_core.view can break re_viewer_context.view.view_class_registry, while a change to re_viewer_context.view.view_class_registry can't break re_types_core.view.
Position
Below the diagonal: re_viewer_context.view.view_class_registry uses a module listed above it, which is the healthy direction.
re_viewer_context.view.view_class_registry uses re_viewer_context.app_options, so a change to re_viewer_context.app_options can break re_viewer_context.view.view_class_registry, while a change to re_viewer_context.view.view_class_registry can't break re_viewer_context.app_options.
Position
Below the diagonal: re_viewer_context.view.view_class_registry uses a module listed above it, which is the healthy direction.
re_viewer_context.view.view_class_registry uses re_viewer_context.view.named_system, so a change to re_viewer_context.view.named_system can break re_viewer_context.view.view_class_registry, while a change to re_viewer_context.view.view_class_registry can't break re_viewer_context.view.named_system.
Position
Below the diagonal: re_viewer_context.view.view_class_registry uses a module listed above it, which is the healthy direction.
re_viewer_context.view.view_class_registry uses re_viewer_context.viewer_context, so a change to re_viewer_context.viewer_context can break re_viewer_context.view.view_class_registry, while a change to re_viewer_context.view.view_class_registry can't break re_viewer_context.viewer_context.
Position
Below the diagonal: re_viewer_context.view.view_class_registry uses a module listed above it, which is the healthy direction.
re_viewer_context.view.view_class_registry uses re_viewer_context.view.visualizer_system, so a change to re_viewer_context.view.visualizer_system can break re_viewer_context.view.view_class_registry, while a change to re_viewer_context.view.view_class_registry can't break re_viewer_context.view.visualizer_system.
Position
Below the diagonal: re_viewer_context.view.view_class_registry uses a module listed above it, which is the healthy direction.
re_viewer_context.view.view_class_registry uses re_viewer_context.view.view_context_system, so a change to re_viewer_context.view.view_context_system can break re_viewer_context.view.view_class_registry, while a change to re_viewer_context.view.view_class_registry can't break re_viewer_context.view.view_context_system.
Position
Below the diagonal: re_viewer_context.view.view_class_registry uses a module listed above it, which is the healthy direction.
re_viewer_context.app_context uses re_log_types.entry_id, so a change to re_log_types.entry_id can break re_viewer_context.app_context, while a change to re_viewer_context.app_context can't break re_log_types.entry_id.
Position
Below the diagonal: re_viewer_context.app_context uses a module listed above it, which is the healthy direction.
re_viewer_context.app_context uses re_log_types.path.entity_path, so a change to re_log_types.path.entity_path can break re_viewer_context.app_context, while a change to re_viewer_context.app_context can't break re_log_types.path.entity_path.
Position
Below the diagonal: re_viewer_context.app_context uses a module listed above it, which is the healthy direction.
re_viewer_context.app_context uses re_renderer.context, so a change to re_renderer.context can break re_viewer_context.app_context, while a change to re_viewer_context.app_context can't break re_renderer.context.
Position
Below the diagonal: re_viewer_context.app_context uses a module listed above it, which is the healthy direction.
re_viewer_context.app_context uses re_types_core.component_descriptor, so a change to re_types_core.component_descriptor can break re_viewer_context.app_context, while a change to re_viewer_context.app_context can't break re_types_core.component_descriptor.
Position
Below the diagonal: re_viewer_context.app_context uses a module listed above it, which is the healthy direction.
re_viewer_context.app_context uses re_viewer_context.app_options, so a change to re_viewer_context.app_options can break re_viewer_context.app_context, while a change to re_viewer_context.app_context can't break re_viewer_context.app_options.
Position
Below the diagonal: re_viewer_context.app_context uses a module listed above it, which is the healthy direction.
re_viewer_context.app_context uses re_entity_db.entity_db, so a change to re_entity_db.entity_db can break re_viewer_context.app_context, while a change to re_viewer_context.app_context can't break re_entity_db.entity_db.
Position
Below the diagonal: re_viewer_context.app_context uses a module listed above it, which is the healthy direction.
re_viewer_context.app_context uses re_viewer_context.item, so a change to re_viewer_context.item can break re_viewer_context.app_context, while a change to re_viewer_context.app_context can't break re_viewer_context.item.
Position
Below the diagonal: re_viewer_context.app_context uses a module listed above it, which is the healthy direction.
re_viewer_context.app_context uses re_viewer_context.view.view_class_registry, so a change to re_viewer_context.view.view_class_registry can break re_viewer_context.app_context, while a change to re_viewer_context.app_context can't break re_viewer_context.view.view_class_registry.
Position
Below the diagonal: re_viewer_context.app_context uses a module listed above it, which is the healthy direction.
36→37 re_viewer_context.app_context uses re_log_types.store_idpart of a loop✕
Connections
1 pair of types, where a type in re_viewer_context.app_context uses a type in re_log_types.store_id.
re_viewer_context.app_context uses re_log_types.store_id, so a change to re_log_types.store_id can break re_viewer_context.app_context, while a change to re_viewer_context.app_context can't break re_log_types.store_id.
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.
re_log_types.store_id uses re_byte_size, so a change to re_byte_size can break re_log_types.store_id, while a change to re_log_types.store_id can't break re_byte_size.
Position
Below the diagonal: re_log_types.store_id uses a module listed above it, which is the healthy direction.
re_log_types.store_id uses re_types_core.segment_id, so a change to re_types_core.segment_id can break re_log_types.store_id, while a change to re_log_types.store_id can't break re_types_core.segment_id.
Position
Below the diagonal: re_log_types.store_id uses a module listed above it, which is the healthy direction.
re_log_types.store_id uses re_viewer_context.app_context, so a change to re_viewer_context.app_context can break re_log_types.store_id, while a change to re_log_types.store_id can't break re_viewer_context.app_context.
Position
Below the diagonal: re_log_types.store_id uses a module listed above it, which is the healthy direction.
re_chunk_store.store uses re_byte_size, so a change to re_byte_size can break re_chunk_store.store, while a change to re_chunk_store.store can't break re_byte_size.
Position
Below the diagonal: re_chunk_store.store uses a module listed above it, which is the healthy direction.
re_chunk_store.store uses re_byte_size.mem_usage_tree, so a change to re_byte_size.mem_usage_tree can break re_chunk_store.store, while a change to re_chunk_store.store can't break re_byte_size.mem_usage_tree.
Position
Below the diagonal: re_chunk_store.store uses a module listed above it, which is the healthy direction.
re_chunk_store.store uses re_log_types.index.time_int, so a change to re_log_types.index.time_int can break re_chunk_store.store, while a change to re_chunk_store.store can't break re_log_types.index.time_int.
Position
Below the diagonal: re_chunk_store.store uses a module listed above it, which is the healthy direction.
re_chunk_store.store uses re_log_types.path.entity_path, so a change to re_log_types.path.entity_path can break re_chunk_store.store, while a change to re_chunk_store.store can't break re_log_types.path.entity_path.
Position
Below the diagonal: re_chunk_store.store uses a module listed above it, which is the healthy direction.
re_chunk_store.store uses re_log_types.index.absolute_time_range, so a change to re_log_types.index.absolute_time_range can break re_chunk_store.store, while a change to re_chunk_store.store can't break re_log_types.index.absolute_time_range.
Position
Below the diagonal: re_chunk_store.store uses a module listed above it, which is the healthy direction.
re_chunk_store.store uses re_types_core.chunk_id, so a change to re_types_core.chunk_id can break re_chunk_store.store, while a change to re_chunk_store.store can't break re_types_core.chunk_id.
Position
Below the diagonal: re_chunk_store.store uses a module listed above it, which is the healthy direction.
re_chunk_store.store uses re_chunk.latest_at, so a change to re_chunk.latest_at can break re_chunk_store.store, while a change to re_chunk_store.store can't break re_chunk.latest_at.
Position
Below the diagonal: re_chunk_store.store uses a module listed above it, which is the healthy direction.
re_chunk_store.store uses re_chunk.chunk, so a change to re_chunk.chunk can break re_chunk_store.store, while a change to re_chunk_store.store can't break re_chunk.chunk.
Position
Below the diagonal: re_chunk_store.store uses a module listed above it, which is the healthy direction.
re_chunk_store.store uses re_log_types.store_id, so a change to re_log_types.store_id can break re_chunk_store.store, while a change to re_chunk_store.store can't break re_log_types.store_id.
Position
Below the diagonal: re_chunk_store.store uses a module listed above it, which is the healthy direction.
re_protos.v1alpha1.rerun.cloud.v1alpha1.ext uses re_log_types.entry_id, so a change to re_log_types.entry_id can break re_protos.v1alpha1.rerun.cloud.v1alpha1.ext, while a change to re_protos.v1alpha1.rerun.cloud.v1alpha1.ext can't break re_log_types.entry_id.
Position
Below the diagonal: re_protos.v1alpha1.rerun.cloud.v1alpha1.ext uses a module listed above it, which is the healthy direction.
re_protos.v1alpha1.rerun.cloud.v1alpha1.ext uses re_log_types.index.time_int, so a change to re_log_types.index.time_int can break re_protos.v1alpha1.rerun.cloud.v1alpha1.ext, while a change to re_protos.v1alpha1.rerun.cloud.v1alpha1.ext can't break re_log_types.index.time_int.
Position
Below the diagonal: re_protos.v1alpha1.rerun.cloud.v1alpha1.ext uses a module listed above it, which is the healthy direction.
re_protos.v1alpha1.rerun.cloud.v1alpha1.ext uses re_types_core.segment_id, so a change to re_types_core.segment_id can break re_protos.v1alpha1.rerun.cloud.v1alpha1.ext, while a change to re_protos.v1alpha1.rerun.cloud.v1alpha1.ext can't break re_types_core.segment_id.
Position
Below the diagonal: re_protos.v1alpha1.rerun.cloud.v1alpha1.ext uses a module listed above it, which is the healthy direction.
re_protos.v1alpha1.rerun.cloud.v1alpha1.ext uses re_log_types.index.absolute_time_range, so a change to re_log_types.index.absolute_time_range can break re_protos.v1alpha1.rerun.cloud.v1alpha1.ext, while a change to re_protos.v1alpha1.rerun.cloud.v1alpha1.ext can't break re_log_types.index.absolute_time_range.
Position
Below the diagonal: re_protos.v1alpha1.rerun.cloud.v1alpha1.ext uses a module listed above it, which is the healthy direction.
re_protos.v1alpha1.rerun.cloud.v1alpha1.ext uses re_log_types.store_id, so a change to re_log_types.store_id can break re_protos.v1alpha1.rerun.cloud.v1alpha1.ext, while a change to re_protos.v1alpha1.rerun.cloud.v1alpha1.ext can't break re_log_types.store_id.
Position
Below the diagonal: re_protos.v1alpha1.rerun.cloud.v1alpha1.ext uses a module listed above it, which is the healthy direction.
re_viewer.app uses re_byte_size.mem_usage_tree, so a change to re_byte_size.mem_usage_tree can break re_viewer.app, while a change to re_viewer.app can't break re_byte_size.mem_usage_tree.
Position
Below the diagonal: re_viewer.app uses a module listed above it, which is the healthy direction.
re_viewer.app uses re_log_types.entry_id, so a change to re_log_types.entry_id can break re_viewer.app, while a change to re_viewer.app can't break re_log_types.entry_id.
Position
Below the diagonal: re_viewer.app uses a module listed above it, which is the healthy direction.
re_viewer.app uses re_quota_channel.async_broadcast_channel, so a change to re_quota_channel.async_broadcast_channel can break re_viewer.app, while a change to re_viewer.app can't break re_quota_channel.async_broadcast_channel.
Position
Below the diagonal: re_viewer.app uses a module listed above it, which is the healthy direction.
re_viewer.app uses re_types_core.segment_id, so a change to re_types_core.segment_id can break re_viewer.app, while a change to re_viewer.app can't break re_types_core.segment_id.
Position
Below the diagonal: re_viewer.app uses a module listed above it, which is the healthy direction.
re_viewer.app uses re_types_core.view, so a change to re_types_core.view can break re_viewer.app, while a change to re_viewer.app can't break re_types_core.view.
Position
Below the diagonal: re_viewer.app uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in re_viewer.app uses a type in re_analytics.event.
The types involved
re_viewer.app.app$module → re_analytics.event.Id
Direction
re_viewer.app uses re_analytics.event, so a change to re_analytics.event can break re_viewer.app, while a change to re_viewer.app can't break re_analytics.event.
Position
Below the diagonal: re_viewer.app uses a module listed above it, which is the healthy direction.
re_viewer.app uses re_chunk.latest_at, so a change to re_chunk.latest_at can break re_viewer.app, while a change to re_viewer.app can't break re_chunk.latest_at.
Position
Below the diagonal: re_viewer.app uses a module listed above it, which is the healthy direction.
re_viewer.app uses re_entity_db.entity_db, so a change to re_entity_db.entity_db can break re_viewer.app, while a change to re_viewer.app can't break re_entity_db.entity_db.
Position
Below the diagonal: re_viewer.app uses a module listed above it, which is the healthy direction.
re_viewer.app uses re_viewer_context.item, so a change to re_viewer_context.item can break re_viewer.app, while a change to re_viewer.app can't break re_viewer_context.item.
Position
Below the diagonal: re_viewer.app uses a module listed above it, which is the healthy direction.
re_viewer.app uses re_log_types.store_id, so a change to re_log_types.store_id can break re_viewer.app, while a change to re_viewer.app can't break re_log_types.store_id.
Position
Below the diagonal: re_viewer.app uses a module listed above it, which is the healthy direction.
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A05:2025 — Injection
146
High / Critical
A03:2025 — Software Supply Chain Failures
30
High / Critical
A02:2025 — Security Misconfiguration
5
High / Critical
Roadmap
Top priorities: Add tests that import the unreached modules (directly or through their public entry); 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; Enable Dependabot/Renovate or a dependency-review gate.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Add tests that import the unreached modules (directly or through their public entry).
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.
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.
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 — 149
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 — 3405
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 — 218
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 23
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 72 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 — 72 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, 3584 of 3772 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: this repository's production source spans .ts, .rs, and our analyzer cannot run the .rs test suite(s) — so no coverage was collected for the repository as a whole. The JavaScript/TypeScript half did build and run, and its own line coverage came back at 82.9% — but that is a figure for one half of the product, and we do not publish a partial one as if it were complete. This is OUR limitation, not a defect in the repo — coverage is excluded from the score rather than counted as a near-zero.
D10 Test Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 36 test(s) behind this row are the ones the JavaScript/TypeScript census could read, and this repository also carries at least 695 test source file(s) (.py, .rs) that it cannot: it reads JavaScript/TypeScript test declarations off disk, so a JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability NOT SCORED: this repository's production source includes .rs, and the rust executor ran against the .rs half and never executed — so reliability was not measured for the repository as a whole. The JavaScript/TypeScript (node:test via `npm ci --ignore-scripts` in rerun_js/web-viewer/ (5 tests)): measured (0 flaky) suite(s) did re-run, and came back with 0 flaky across 1 measured tier(s) — but that is a figure for one half of the product, and we do not publish a partial one as if it were complete. This is OUR limitation, not a defect in the repo — test reliability is excluded from the score rather than counted. The half was driven by a runner we ship, so this is not a missing-runner gap.
D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Python REDACTED/requirements.txt (pip/uv/Poetry), but the licence verdict published here was taken over its crate dependencies. Nothing was read about its Python dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its 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. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
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 — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `rerun_py/rerun_sdk/rerun/catalog/_entry.py` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
AX1 Captive dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository defines its own container in rerun_py/rerun_sdk/rerun/any_batch_value.py, whose lifetimes are not modelled 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.
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.
AXB2 Runtime readiness — 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. `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. (rule: no-root-manifest). The renderer reported: the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
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 DevServer (dev). the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
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, c, cpp 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, c, cpp 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.
M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
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.
X17 Uncapped recursion over a caller-supplied document — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check'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.
X19 Unrestored process-global state — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check'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.
X25 Inert configuration knob — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X3 Exception handling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
Repo exclusion declarations: 1743 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.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 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.
D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned REDACTED, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
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.
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.
M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
192 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was AppCore::run_system_command at 97. A further 23 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 UICommand::kb_shortcuts at 45 — they are counted neither in the figure above nor in this dimension's score. 15 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/ui_tools/re_ui/src/command/ui_command.rs (UICommand::kb_shortcuts at 45), crates/ui_tools/re_ui/src/color_table.rs (Scale::from_str at 42), rerun_py/src/chunk_stream/hdf5_reader.rs (PyHdf5ReaderInternal::attributes at 25), crates/ui_tools/re_arrow_ui/src/datatype_ui.rs (DataTypeHighlighter::data_type at 24), crates/viewer_support/re_viewer_context/src/command/recording_command.rs (RecordingCommandKind::text_and_tooltip at 24), and 10 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.
+ 116 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 Cyclomatic Complexity — start with AppCore::run_system_command (cyclomatic 97), AppCore::run_ui_command (cyclomatic 61). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cyclomatic Complexity from 6.0 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: 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.
+ 262 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 18 bodies over 60 down to 60 or less in Cognitive Complexity — start with AppCore::run_system_command (cognitive 123), ChunkStore::insert_chunk_impl (cognitive 106), re_types_builder::codegen::rust::serializer::quote_arrow_field_serializer (cognitive 105). — 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 18 together lifts Cognitive Complexity from 5.5 to about 6.4/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes8.3 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 103 FileTooLong finding(s) in God Classes — start with mod.rs (18), view_class.rs (3), query.rs (3). — One of this dimension's main actionable groups (103 warning-level).
Resolve the 102 MethodTooLong finding(s) in God Classes — start with mod.rs (12), query.rs (4), command_handling.rs (3). — One of this dimension's main actionable groups (102 warning-level).
Resolve the 59 FunctionTooLong finding(s) in God Classes — start with mod.rs (6), entrypoint.rs (3), visualizer_ui.rs (2). — One of this dimension's main actionable groups (59 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.
470 duplicated block group(s) detected. 4.1 % of the production lines (24,177 of 591,051) are in a reported copy. A further 389 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 76 of the 859 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
+ 220 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 41 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with mod.rs (4), draw.rs (2), voxel_grid.rs. — One of this dimension's main actionable groups (41 warning-level).
Resolve the 30 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with outlines.rs (2), lines.rs (2), importer_rrd.rs. — One of this dimension's main actionable groups (30 warning-level).
Resolve the 27 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with unit_chunk.rs (2), dataset_entry.rs (2), data_source.rs. — One of this dimension's main actionable groups (27 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling5.7 / 10Adequate✓ 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.
126 production modules (Cargo+npm+Python), 0 dependency cycle(s), 37 unstable depended-on module(s). Read from the build's own module declarations; 22 module(s) off the main sequence, with abstractness counted on 114 of the 126 (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: re_build_tools · ×22
Unstable project re_agent_panel
Unstable project re_agent_ui
Unstable project re_arrow_json
Unstable project re_blueprint_tree
+ 33 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 22 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (22 warning-level).
Resolve the 1 Unstable project re_agent_panel finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Unstable project re_agent_ui 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.
Resolve the 9 Low cohesion finding(s) in Cohesion (LCOM4) — start with view_coordinates.def.rs, tensor_data.def.rs, viewport_ui.rs. — One of this dimension's main actionable groups (9 warning-level).
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D10 · Test Quality10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 36 tests. Measured on the JavaScript/TypeScript suite only — at least 695 test source file(s) (.py, .rs) went unread, so its test quality is unmeasured and is not in these counts.
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.
102 outdated, 0 yanked direct Cargo dependencies. 341 of 359 direct crates were graded against crates.io (0 not published there, 18 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: accesskit · ×102
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 1150 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. This repository publishes itself under MIT OR Apache-2.0, which is its own choice and is not judged here. ★ COVERAGE OF THIS VERDICT: it grades this repository's crate dependencies and nothing else. The repository also declares a Python REDACTED/requirements.txt (pip/uv/Poetry) and package.json, and the licences of those dependency graphs were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
Top hotspots: crates/top/re_viewer/src/app/command_handling.rs (46×97=4462); crates/top/re_viewer/src/app/mod.rs (64×36=2304); crates/top/re_viewer/src/app/viewer_control/mod.rs (50×36=1800) Repeated repair below the complexity floor: crates/utils/re_video/src/decode/mod.rs (3 of 4 changes were fixes); crates/utils/re_video/src/player/sample_decoder.rs (3 of 3 changes were fixes)
Resolve the 82 Hotspot finding(s) in Churn × Complexity Hotspots — start with mod.rs (10), view_class.rs (4), command_handling.rs. — One of this dimension's main actionable groups (82 warning-level).
Resolve the 2 Repeated repair finding(s) in Churn × Complexity Hotspots — start with mod.rs, sample_decoder.rs. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D16 · Bus Factor9.5 / 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.
71 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is crates/store/re_chunk_optimizer/src/plan.rs. Counted over 1457 of the 2063 production source files in this repository: 604 are under the ~2,400-byte size floor this dimension measures over, and the remaining 2 have no attributable history left to measure.
Off-boarding risk: anonymized user #1 · ×9
Further sole-owners (lower concentration)
✓ On the Gold path — maintain.
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
1292 deducted task-comment markers across 591051 LoC (0.2/KLoC) → score 9.6. 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 1287 TodoComment finding(s) in Explicit Debt — start with mod.rs (82), lib.rs (44), query.rs (19). — One of this dimension's main actionable groups (1287 warning-level).
Resolve the 5 HackComment finding(s) in Explicit Debt — start with __main__.py, lib.rs, command_handling.rs. — One of this dimension's main actionable groups (5 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.
2 of 2 documentation facets pass in full. 323 document(s) read across 5 unit(s).
✓ On the Gold path — maintain.
Detailed fixes: d19_recommendation.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).
Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.
10 of 124 build units (Cargo, Python, 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).
146 finding(s): 0 critical, 140 high, 6 medium, 0 low. 1 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 11 file(s) — `crates/data_flow/re_data_source/src/data_source.rs` (line 275, line 277), `crates/data_flow/re_lerobot/src/language.rs` (lines 312–362, lines 424–427, lines 437–439, …), `crates/store_app/re_tf/src/transform_resolution_cache/tree_transforms_for_child_frame.rs` (line 65, lines 67–70, line 71, …), `crates/top/re_viewer/src/app/add_data_source.rs` (lines 112–113, line 115, line 117, …), `crates/top/rerun_c/src/lib.rs` (line 1332), … (+6 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 27 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
+ 9 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 85 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (26), REDACTED (15), REDACTED (12). — One of this dimension's main actionable groups (85 issue-level).
Resolve the 40 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4), REDACTED (4), REDACTED (4). — One of this dimension's main actionable groups (40 issue-level).
Resolve the 6 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (6 issue-level).
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 2 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
Resolve the 3 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 2 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
Resolve the 2 High IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 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 2 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 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.
29 of 1459 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is crates/store/re_log_types/src/vec_deque_ext.rs. Counted over 1459 of the 2063 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 33 Change coupling finding(s) in Change Coupling — start with widget.ts (2), grpc_server.rs (2), selection_panel.rs (2). — One of this dimension's main actionable groups (33 warning-level).
Resolve the 2 Change-coupling hub finding(s) in Change Coupling — start with app_state.rs, view_class.rs. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
+ 7 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — 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).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.
Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.
What it measures: Whether 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 4 platform declaration(s) and 10 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 alternatives10.0 / 10Exemplary○ Nothing flagged
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.
Do you agree with this assessment?
AC2 · Forms & labels10.0 / 10Exemplary○ Nothing flagged
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.
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.
The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). — REDACTED:3
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — REDACTED:3
user-scalable=no/0 or a maximum-scale below 2 stops low-vision users zooming to 200%. Remove the zoom restriction from the viewport meta. — REDACTED:7
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 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.
<div> moves — its inline style sets `transition: width 0.2s` — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:. — rerun_js/web-viewer/index.ts:1670
`.sm-dox ul a:hover, .sm-dox ul a:active, .sm-dox ul a:focus` sets color: #1C1D1F on background-color: #1982d2 — 4.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — rerun_cpp/docs/doxygen-awesome/doxygen-awesome.css:493
`.sm-dox a:hover, .sm-dox a:active, .tablist li a:hover` sets color: #1C1D1F on background-color: #1982d2 — 4.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — rerun_cpp/docs/doxygen-awesome/doxygen-awesome.css:515
`#MSearchSelectWindow a.SelectItem:hover` sets color: #1C1D1F on background-color: #1982d2 — 4.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — rerun_cpp/docs/doxygen-awesome/doxygen-awesome.css:713
`.rerun-notebook-loading__spinner` moves (`animation: rerun-notebook-spin 0.8s linear infinite`) 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. — rerun_py/rerun_sdk/rerun/_loading_widget.css:23
`.sm-dox ul` moves (`animation: ease-out 150ms slideInMenu`) 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. — rerun_cpp/docs/doxygen-awesome/doxygen-awesome.css:464
`#MSearchResultsWindow` moves (`animation: ease-out 280ms slideInSearchResults`) 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. — rerun_cpp/docs/doxygen-awesome/doxygen-awesome.css:664
`#MSearchResultsWindow` moves (`animation: ease-out 280ms slideInSearchResultsMobile`) 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. — rerun_cpp/docs/doxygen-awesome/doxygen-awesome.css:750
`div.contents .toc.interactive > h3::before` moves (`transition: transform 0.25s ease-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. — rerun_cpp/docs/doxygen-awesome/doxygen-awesome.css:1177
`div.contents .toc.interactive.open` moves (`transition: max-height 0.2s 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. — rerun_cpp/docs/doxygen-awesome/doxygen-awesome.css:1187
`table.memberdecls img[src="closed.png"]` moves (`transition: transform 0.25s ease-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. — rerun_cpp/docs/doxygen-awesome/doxygen-awesome.css:1869
`table.memberdecls tr[style="display: table-row "]` moves (`animation: fade .5s`) 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. — rerun_cpp/docs/doxygen-awesome/doxygen-awesome.css:1948
`doxygen-awesome-dark-mode-toggle > svg` moves (`transition: transform .1s 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. — rerun_cpp/docs/doxygen-awesome/doxygen-awesome.css:2347
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.
Do you agree with this assessment?
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified
Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.
Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.
Other · Architecture — Whether read (query) handlers stay side-effect-free — a query that writes persistent state or raises events breaks CQS and makes reads unsafe to retry, cache, or route to a read replica.
Method: Roslyn scan: CQRS handlers classified query-vs-command by interface (IQueryHandler/ICommandHandler/IRequestHandler<TQuery,TResult>) and name convention (*Query/Get*/Find* vs *Command); each query handler's body checked for persistent-state writes (SaveChanges/repository Add-Update) or event publishes by resolved invocation. Deterministic, type-level, exhaustive over the detected handlers.
Coverage: Population: CQRS handlers identified by IQueryHandler/ICommandHandler/IRequestHandler interface + *Query/Get*/Find*/*Command NAME convention; query purity then checked exhaustively within that set — a query handler using neither convention is invisible, and mutation is a resolved persistence/publish CALL, not full dataflow.
`StoreHub.load_blueprint_store` is a read-named query yet it performs a durable write on the read path (a persist to a store/repository). A query must stay side-effect-free so reads are safe to retry, cache, and route to a read replica; move the write into a command. — crates/viewer_support/re_viewer_context/src/store_hub/mod.rs:515
What to do
Keep query handlers read-only — move the writes/event-publishes into a command handler so reads stay safe to retry, cache, and route to a read replica.
Other · Event Sourcing — Whether the recovery-replay fold is deterministic — state derived purely from each event's own fields, no clock/random/IO on the replay path.
Method: Roslyn syntax scan (event-sourcing gated): Apply/When folds checked for forbidden tokens (DateTime.Now, Guid.NewGuid, Random, IO), stripped of comments/strings. Deterministic, hard fact per fold.
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.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
Do you agree with this assessment?
P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
Only 66/70 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `crates/build/re_dev_tools`, `crates/store_app/re_query`, `crates/top/rerun-cli`, `rerun_pixi_env`.
What to do
Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
Add a health-check endpoint (a /health route on your axum/actix router) so orchestrators and load balancers can probe liveness/readiness.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
`examples/js/viewer_control/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`. — examples/js/viewer_control/package.json:10
What to do
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
Readiness · 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::Client::builder(` 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. (×2) — crates/utils/re_agent/src/model_api_backend.rs:454, crates/utils/re_agent/src/model_api_backend.rs:461
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 · Performance — Whether the code protects its performance with benchmarks — a benchmark suite, allocation/memory measurement, and (ideally) a CI gate. Presence is credited as a bonus, never a deduction.
Method: Repo + source scan: BenchmarkDotNet referenced (csproj/source), [Benchmark]/[MemoryDiagnoser] attribute counts, and a benchmark step in CI; off .NET, the same ladder over Go testing.B, Rust criterion/#[bench]/divan, JMH/kotlinx-benchmark, pytest-benchmark/asv/pyperf, tinybench/mitata/vitest bench/benchmark.js and Swift package-benchmark — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
`login` is async and calls thread::sleep — a blocking call inside async code stalls the executor thread, and every task scheduled on it for as long as it runs. — crates/utils/re_auth/src/cli.rs:51
What to do
Rust: `.await` the future instead of `block_on` (on a Tokio runtime thread it panics outright) and use `tokio::time::sleep(..).await` instead of `std::thread::sleep`; where synchronous code must run, move it to `tokio::task::spawn_blocking` or `block_in_place`.
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.
rerun_js/web-viewer/index.ts:2036 · rerun_js/web-viewer/index.ts:2051 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — rerun_js/web-viewer/index.ts:2036
rerun_js/web-viewer/index.ts:1831 · rerun_js/web-viewer/index.ts:1850 — 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. — rerun_js/web-viewer/index.ts:1831
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 · 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.
collectTargets has cyclomatic complexity 17 and cognitive complexity 20; 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. — rerun_js/web-viewer/typedoc-used-by.mjs:97
start has cyclomatic complexity 14 and cognitive complexity 13; 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. — rerun_js/web-viewer/index.ts:1644
closeTargetOf has cyclomatic complexity 13 and cognitive complexity 9; 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. — rerun_js/web-viewer/index.ts:842
(top-level) has cyclomatic complexity 12 and cognitive complexity 24; 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. — rerun_js/scripts/version.mjs:4
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.
rerun_js/web-viewer/index.ts has 2719 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — rerun_js/web-viewer/index.ts: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?
R4 · Test Coverage2.9 / 10Weak✓ Tool-verified
React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.
Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.
No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×10) — rerun_notebook/src/js/widget.ts:1, rerun_js/web-viewer-react/index.js:1, rerun_js/web-viewer/typedoc-used-by.mjs:1, …
What to do
Add tests that import the unreached modules (directly or through their public entry).
React / JS · Readiness — How outdated the npm dependencies are (a maturity signal). JS/npm CVEs are scored separately in D30 (JS/npm Dependency Vulnerabilities).
Method: npm dependency staleness from manifest/registry metadata (a maturity signal; JS/npm CVEs are scored separately in D30, which answers dependency vulnerabilities for every ecosystem). Deterministic.
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.9 / 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.
9 file(s) (~3850 LoC) were excluded from dead-code analysis. This package's entry point(s) resolved, but the walk stopped one hop in: rerun_js/web-viewer/index.ts imports './proto/rerun/v1alpha1/viewer_control_pb.js', which is not in the scanned tree. That is usually a generated or build-output module, so reachability cannot see past it and no dead-code claim is made about this package. Nothing is necessarily wrong here. — rerun_js/web-viewer
Nothing imports this binding — it is safe to review for removal. (×2) — rerun_js/web-viewer/exact_json.ts:51, rerun_js/web-viewer/exact_json.ts:55
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 rerun_js/web-viewer/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×2)
Declared in rerun_js/web-viewer-react/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.
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.
Other · Security — Only what this repository's own non-C# files could be read for was assessed — markup this repository SHIPS is scored for third-party script integrity whether or not the repository serves it itself, since a page handed to a consumer runs in that consumer’s origin. Nothing else in this dimension was assessed: the transport, cookie, input-validation and crypto controls are read from a source model that was not loaded for this repository’s language, so their absence here is not a finding about this repository.
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.
`https://cdn.jsdelivr.net/npm/chart.js@4.4.0/dist/chart.umd.min.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. — scripts/ci/templates/benchmark.html:111
What to do
Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
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.
This `async` body is polled on an executor's worker thread, and `std::thread::sleep` blocks that thread: for the whole delay no other task scheduled on it makes progress — the Rust form of blocking on a task. Use `tokio::time::sleep(…).await` (or the runtime's own timer), which suspends only this task. Where the blocking work is not a sleep but a synchronous call that cannot be made async, move it off the executor with `tokio::task::spawn_blocking(…).await`. — crates/utils/re_auth/src/cli.rs:92
Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.
Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether async functions that make a cancellable request accept or pass on an AbortSignal (adoption curve).
Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.
Only 0/3 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
`urlExists` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — rerun_notebook/src/rerun_notebook/error_widget.js:18
`fetchViewerWasm` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — rerun_js/web-viewer/index.ts:1086
`isPublished` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — rerun_js/scripts/common.mjs:84
What to do
Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.
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?
X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a `for` loop leaves the `RefCell` it is walking alone — safe Rust rejects a body that changes the collection its loop borrows at compile time, except through interior mutability: a `RefCell` borrowed in the loop's header stays borrowed until the loop ends, so a `borrow_mut()` of it inside the body panics with `already borrowed: BorrowMutError` and the remaining elements are never seen. Whether a `for` loop leaves the `dict`, `set` or `deque` it is walking alone — CPython's iterators over those check that the collection has not changed size since the loop began, so a body that removes from (or empties) the very collection the loop is walking makes the next step raise `RuntimeError: dictionary changed size during iteration` and the remaining items are never seen.
Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.
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.
`warning` at line 181 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.warning("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.warning("order moved", order_id=order_id, status=status)` with structlog. — rerun_py/rerun_sdk/rerun/catalog/_catalog_client.py:181
`warning` at line 272 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.warning("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.warning("order moved", order_id=order_id, status=status)` with structlog. — rerun_notebook/src/rerun_notebook/__init__.py:272
`debug!` at line 149 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`. — rerun_py/src/trace_context.rs:149
`debug!` at line 160 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`. — rerun_py/src/trace_context.rs:160
`info!` at line 136 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`. — rerun_py/src/tracing_session.rs:136
`warn!` at line 404 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`. — rerun_py/src/catalog/connection_handle.rs:404
`error!` at line 49 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/utils/re_perf_telemetry/src/metrics_server.rs:49
`info!` at line 53 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `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/utils/re_perf_telemetry/src/metrics_server.rs:53
`error!` at line 78 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/utils/re_perf_telemetry/src/metrics_server.rs:78
`error!` at line 98 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/utils/re_perf_telemetry/src/metrics_server.rs:98
`warn!` at line 186 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/utils/re_perf_telemetry/src/telemetry.rs:186
`warn!` at line 310 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/utils/re_perf_telemetry/src/telemetry.rs:310
`debug!` at line 139 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/utils/re_perf_telemetry/src/tracestate.rs:139
`info!` at line 329 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `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/utils/re_perf_telemetry/src/tracing_session.rs:329
`error!` at line 101 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/store_app/re_server/src/server.rs:101
`info!` at line 112 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/store_app/re_server/src/server.rs:112
`error!` at line 127 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/store_app/re_server/src/server.rs:127
`error!` at line 175 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/store_app/re_server/src/server.rs:175
`error!` at line 324 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/store_app/re_server/src/server.rs:324
`debug!` at line 342 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/store_app/re_datafusion/src/dataframe_query_provider/fetch_plan.rs:342
`debug!` at line 403 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/store_app/re_datafusion/src/dataframe_query_provider/fetch_plan.rs:403
`trace!` at line 329 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(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/data_flow/re_redap_client/src/lib.rs:329
`trace!` at line 340 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: `trace!(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/data_flow/re_redap_client/src/lib.rs:340
`trace!` at line 348 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: `trace!(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/data_flow/re_redap_client/src/lib.rs:348
`trace!` at line 357 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: `trace!(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/data_flow/re_redap_client/src/lib.rs:357
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.7 `!` null assertions per 1k TypeScript source lines — 6 assertion(s) across the 3616 source line(s) of the 5 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: rerun_js/web-viewer/index.ts (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 — 3 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
X10 Duplicated predicate — 18 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 7 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X9 Subsumed condition operand — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 51 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.
AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
AX1 Captive dependencies — 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
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 1% of this repository's production lines — rust (525,554 lines), python (62,180 lines), cpp (12,812 lines), c (162 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered. 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 — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
D11 Test Reliability — Test reliability not scored — polyglot repository, one half's runner produced no measurement
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 — Naming consistency does not read html yet; not measured.
D22 Internal API Consistency — API consistency is measured on C# only; the exposed JavaScript, Rust, TypeScript 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"]`.
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) — 1 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
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 — polyglot repository, one half has no runner
DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 549 value object(s); 2 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
GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — coverage data present for 2 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
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 (525,554 lines), cpp (12,812 lines), c (162 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
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X16 Unfloored truncation loop — X16 reached only 1% of this repository's production lines — rust (525,554 lines), python (62,180 lines), cpp (12,812 lines), c (162 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 — X17 reached only 11% of this repository's production lines — rust (525,554 lines), cpp (12,812 lines), c (162 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
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 — X19 reached only 11% of this repository's production lines — rust (525,554 lines), cpp (12,812 lines), c (162 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
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 (525,554 lines), cpp (12,812 lines), c (162 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 — X25 reached only 11% of this repository's production lines — rust (525,554 lines), cpp (12,812 lines), c (162 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
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
X3 Exception handling — X3 reached only 11% of this repository's production lines — rust (525,554 lines), cpp (12,812 lines), c (162 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.
X6 Hand-rolled structured-format parsing — 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.
Viewport restricts zoom REDACTED:7— user-scalable=no/0 or a maximum-scale below 2 stops low-vision users zooming to 200%. Remove the zoom restriction from the viewport meta.
AX9 · CQS / query purity· Query writes persistent state on the read path · ×1
Query writes persistent state on the read path: StoreHub.load_blueprint_store crates/viewer_support/re_viewer_context/src/store_hub/mod.rs:515— `StoreHub.load_blueprint_store` is a read-named query yet it performs a durable write on the read path (a persist to a store/repository). A query must stay side-effect-free so reads are safe to retry, cache, and route to a read replica; move the write into a command.
TodoComment tests/rust/re_integration_test/tests/integration/blueprint_import_test.rs:110— // TODO(RR-5258): Removing the flag will break this test since it implies a change in behavior.
TodoComment tests/rust/re_integration_test/tests/integration/rrd_bw_compat_test.rs:276— // TODO(RR-5258): Removing the flag will break this test since it implies a change in behavior.
TodoComment tests/rust/re_integration_test/tests/integration/internal_catalog.rs:32— // TODO(RR-4929): We should properly show the application id,
TodoComment tests/rust/re_integration_test/tests/integration/internal_catalog.rs:140— // TODO(RR-4929): Remove this mask once the catalog app id matches recording app id.
TodoComment tests/rust/re_integration_test/tests/integration/multi_container_test.rs:252— // TODO(aedm): count the labels in the selection panel only — 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 tests/rust/re_integration_test/tests/integration/preview_table.rs:332— /// TODO(andreas): Should use a higher level rust blueprint api. — 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 tests/rust/re_integration_test/tests/inspection/datasets.rs:126— // TODO(RR-6358): in the browser, the segment never downloads its chunks.
TodoComment tests/rust/plot_dashboard_stress/src/main.rs:32— // TODO(cmc): could have flags to add attributes (color, radius...) to put some more stress — 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 tests/rust/log_benchmark/src/image.rs:65— // TODO(andreas): We have to copy the image every time since the tensor buffer wants to — 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 tests/python/plot_dashboard_stress/main.py:91— # TODO(cmc): could have flags to add attributes (color, radius...) to put some more stress — 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 tests/python/chunk_zoo/chunk_zoo.py:140— # TODO(ab): add variants (unordered, overlapping timestamps, etc.) — 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 scripts/fast_lint.py:164— # TODO(jleibs): implement lint-cpp-files — 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 scripts/generate_changelog.py:583— # NOTE: we intentionally add TODO:s with names below, which the CI will not be happy about. Hence the # NOLINT suffixes — 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 scripts/generate_view_coordinate_defs.py:7— # TODO(#2388): This script can potentially go away or be significantly reduced.
TodoComment scripts/lint.py:105— # TODO(RR-3355): Use a shared utility for this
TodoComment scripts/roundtrip_utils.py:14— # TODO(RR-3355): Use a shared utility for this
TodoComment scripts/lint.py:188— # TODO(#6077): figure out how we best link to our own code from our docs
TodoComment scripts/lint.py:2149— # zombie TODO hunting job — 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 scripts/lint.py:2190— # TODO(#6730): parse all .gitignore files, not just top-level
TodoComment scripts/nbstripout.py:34— # TODO(#6730): parse all .gitignore files, not just top-level
TodoComment scripts/run_all.py:45— # TODO(ab): remove when mediapipe is 3.12 compatible — 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 scripts/run_all.py:46— # TODO(ab): remove when mediapipe is 3.12 compatible — 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 scripts/run_all.py:47— # TODO(ab): remove when torch is umap-learn/numba is 3.12 compatible — 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: v1alpha1/rerun.cloud.v1alpha1.ext.rs crates/store/re_protos/src/v1alpha1/rerun.cloud.v1alpha1.ext.rs— FileTooLong — 2103 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 1603 over it, 4.21× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/python_bridge.rs rerun_py/src/python_bridge.rs— FileTooLong — 1712 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 78 free functions. The bar is 500 significant lines; this is 1212 over it, 3.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: rerun_cloud/mod.rs crates/store_app/re_server/src/rerun_cloud/mod.rs— FileTooLong — 1600 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 80% of them inside a single declaration: RerunCloudHandler (5 blocks, 274-2308). The bar is 500 significant lines; this is 1100 over it, 3.20× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: viewer_control/mod.rs crates/top/re_viewer/src/app/viewer_control/mod.rs— FileTooLong — 1547 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 76% of them inside a single declaration: AppCore (2 blocks, 209-2028). The bar is 500 significant lines; this is 1047 over it, 3.09× 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: web-viewer/index.ts rerun_js/web-viewer/index.ts— FileTooLong — 1413 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 913 over it, 2.83× 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/datafusion_table_widget.rs crates/viewer_support/re_dataframe_ui/src/datafusion_table_widget.rs— FileTooLong — 1402 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 902 over it, 2.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: src/view_class.rs crates/views/re_view_time_series/src/view_class.rs— FileTooLong — 1393 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 893 over it, 2.79× 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: video_stream_cache/mod.rs crates/viewer_support/re_viewer_context/src/cache/video_stream_cache/mod.rs— FileTooLong — 1377 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 877 over it, 2.75× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: commands/entrypoint.rs crates/top/rerun/src/commands/entrypoint.rs— FileTooLong — 1347 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 847 over it, 2.69× 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/query.rs crates/store_app/re_dataframe/src/query.rs— FileTooLong — 1338 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: QueryHandle (4 blocks, 242-2522). The bar is 500 significant lines; this is 838 over it, 2.68× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/time_panel.rs crates/panels/re_time_panel/src/time_panel.rs— FileTooLong — 1307 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 81% of them inside a single declaration: TimePanel (4 blocks, 101-2063). The bar is 500 significant lines; this is 807 over it, 2.61× 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/recording_stream.rs crates/top/re_sdk/src/recording_stream.rs— FileTooLong — 1290 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 790 over it, 2.58× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: app/command_handling.rs crates/top/re_viewer/src/app/command_handling.rs— FileTooLong — 1256 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 88% of them inside a single declaration: AppCore (41-1828). The bar is 500 significant lines; this is 756 over it, 2.51× 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: app/mod.rs crates/top/re_viewer/src/app/mod.rs— FileTooLong — 1197 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 697 over it, 2.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/chunk.rs crates/store/re_chunk/src/chunk.rs— FileTooLong — 1152 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 62% of them inside a single declaration: Chunk (13 blocks, 242-1962). The bar is 500 significant lines; this is 652 over it, 2.30× 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: servers/mod.rs crates/panels/re_redap_browser/src/servers/mod.rs— FileTooLong — 1055 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 555 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/selection_panel.rs crates/panels/re_selection_panel/src/selection_panel.rs— FileTooLong — 1023 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 523 over it, 2.05× 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/design_tokens.rs crates/ui_tools/re_ui/src/design_tokens.rs— FileTooLong — 994 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 66% of them inside a single declaration: DesignTokens (2 blocks, 262-1402). The bar is 500 significant lines; this is 494 over it, 1.99× 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: dataloader/_utils.py rerun_py/rerun_sdk/rerun/experimental/dataloader/_utils.py— FileTooLong — 986 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 486 over it, 1.97× 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: servers/dataset.rs crates/panels/re_redap_browser/src/servers/dataset.rs— FileTooLong — 986 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 486 over it, 1.97× 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/raw_rrd_manifest.rs crates/store/re_chunk_index/src/raw_rrd_manifest.rs— FileTooLong — 976 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 83% of them inside a single declaration: RawRrdManifest (8 blocks, 145-1824). The bar is 500 significant lines; this is 476 over it, 1.95× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: ui/chat_ui.rs crates/ui_tools/re_agent_ui/src/ui/chat_ui.rs— FileTooLong — 960 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 33 free functions. The bar is 500 significant lines; this is 460 over it, 1.92× 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/top/rerun_c/src/lib.rs— FileTooLong — 939 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 44 free functions. The bar is 500 significant lines; this is 439 over it, 1.88× 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: catalog/_entry.py rerun_py/rerun_sdk/rerun/catalog/_entry.py— FileTooLong — 929 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 429 over it, 1.86× 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/ui_ext.rs crates/ui_tools/re_ui/src/ui_ext.rs— FileTooLong — 916 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 89% of them inside a single declaration: UiExt (43-1489). The bar is 500 significant lines; this is 416 over it, 1.83× 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.
MethodTooLong: AppCore.route_ui crates/top/re_viewer/src/app/route_ui.rs:35— MethodTooLong — route_ui runs 500 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 400 over it, 5.00× 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: AppCore.run_system_command crates/top/re_viewer/src/app/command_handling.rs:120— MethodTooLong — run_system_command runs 430 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 330 over it, 4.30× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: TimeSeriesView.ui crates/views/re_view_time_series/src/view_class.rs:412— MethodTooLong — ui runs 380 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 280 over it, 3.80× 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: DataFusionTableWidget.table_ui crates/viewer_support/re_dataframe_ui/src/datafusion_table_widget.rs:937— MethodTooLong — table_ui runs 322 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 222 over it, 3.22× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: StatsCommand.run crates/top/rerun/src/commands/rrd/stats.rs:38— MethodTooLong — run runs 315 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 215 over it, 3.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: ChunkStore.insert_chunk_impl crates/store/re_chunk_store/src/writes.rs:113— MethodTooLong — insert_chunk_impl runs 293 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 193 over it, 2.93× 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: Telemetry.init crates/utils/re_perf_telemetry/src/telemetry.rs:513— MethodTooLong — init runs 285 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 185 over it, 2.85× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: AppCore.frame_ui crates/top/re_viewer/src/app/mod.rs:1534— MethodTooLong — frame_ui runs 261 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 161 over it, 2.61× 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: AppCore.run_ui_command crates/top/re_viewer/src/app/command_handling.rs:883— MethodTooLong — run_ui_command runs 252 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 152 over it, 2.52× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: App.with_commands crates/top/re_viewer/src/app/mod.rs:332— MethodTooLong — with_commands runs 235 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 135 over it, 2.35× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: AppCore.serve_viewer_control crates/top/re_viewer/src/app/viewer_control/mod.rs:333— MethodTooLong — serve_viewer_control runs 234 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 134 over it, 2.34× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: StateTimelineView.ui crates/views/re_view_state_timeline/src/view_class.rs:250— MethodTooLong — ui runs 232 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 132 over it, 2.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.
MethodTooLong: SpatialView3D.view_3d crates/views/re_view_spatial/src/ui_3d.rs:126— MethodTooLong — view_3d runs 228 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 128 over it, 2.28× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: QueryHandle.next_n_rows_in_store crates/store_app/re_dataframe/src/query.rs:1788— MethodTooLong — next_n_rows_in_store runs 223 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 123 over it, 2.23× 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: TimeControl.handle_time_command crates/viewer_support/re_viewer_context/src/time_control/command.rs:214— MethodTooLong — handle_time_command runs 212 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 112 over it, 2.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: DataframeQueryTableProvider.scan crates/store_app/re_datafusion/src/dataframe_query_common/mod.rs:753— MethodTooLong — scan runs 208 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 108 over it, 2.08× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: DesignTokens.load_with_color_table crates/ui_tools/re_ui/src/design_tokens.rs:645— MethodTooLong — load_with_color_table runs 201 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 101 over it, 2.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: GaussianSplatDrawData.new crates/ui_tools/re_renderer/src/renderer/gaussian_splat.rs:337— MethodTooLong — new runs 195 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 95 over it, 1.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.
MethodTooLong: ViewBuilder.new crates/ui_tools/re_renderer/src/view_builder.rs:445— MethodTooLong — new runs 195 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 95 over it, 1.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.
MethodTooLong: SegmentPreviewRenderer.show_preview crates/viewer_support/re_dataframe_ui/src/preview_renderer.rs:330— MethodTooLong — show_preview runs 195 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 95 over it, 1.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.
MethodTooLong: PointCloudDrawData.new crates/ui_tools/re_renderer/src/renderer/point_cloud.rs:336— MethodTooLong — new runs 194 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 94 over it, 1.94× 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: BarChartView.ui crates/views/re_view_bar_chart/src/view_class.rs:135— MethodTooLong — ui runs 189 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 89 over it, 1.89× 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: SeriesPointsSystem.load_series crates/views/re_view_time_series/src/point_visualizer_system.rs:189— MethodTooLong — load_series runs 186 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 86 over it, 1.86× 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: RedapServers.handle_command crates/panels/re_redap_browser/src/servers/mod.rs:1114— MethodTooLong — handle_command runs 182 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 82 over it, 1.82× 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: QueryHandle.try_bulk_emit_run crates/store_app/re_dataframe/src/query.rs:2132— MethodTooLong — try_bulk_emit_run runs 181 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 81 over it, 1.81× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
Hotspot: crates/top/re_viewer/src/app/command_handling.rs crates/top/re_viewer/src/app/command_handling.rs:120— crates/top/re_viewer/src/app/command_handling.rs changed 46 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 97 in AppCore::run_system_command at line 120. 4 of those changes were fix/bug commits, and the other 42 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 23:06:51 +00:00' --until='2026-11-13 23:06:51 +00:00' --full-history --no-merges -- crates/top/re_viewer/src/app/command_handling.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/top/re_viewer/src/app/mod.rs crates/top/re_viewer/src/app/mod.rs:1534— crates/top/re_viewer/src/app/mod.rs changed 64 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 36 in AppCore::frame_ui at line 1534. 6 of those changes were fix/bug commits, and the other 58 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 23:06:51 +00:00' --until='2026-11-13 23:06:51 +00:00' --full-history --no-merges -- crates/top/re_viewer/src/app/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/top/re_viewer/src/app/viewer_control/mod.rs crates/top/re_viewer/src/app/viewer_control/mod.rs:333— crates/top/re_viewer/src/app/viewer_control/mod.rs changed 50 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 36 in AppCore::serve_viewer_control at line 333. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 23:06:51 +00:00' --until='2026-11-13 23:06:51 +00:00' --full-history --no-merges -- crates/top/re_viewer/src/app/viewer_control/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/utils/re_agent/src/session.rs crates/utils/re_agent/src/session.rs:1079— crates/utils/re_agent/src/session.rs changed 31 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 37 in AgentSession::handle_event at line 1079. 1 of those changes was a fix/bug commit, and the other 30 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 23:06:51 +00:00' --until='2026-11-13 23:06:51 +00:00' --full-history --no-merges -- crates/utils/re_agent/src/session.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/ui_tools/re_agent_ui/src/ui/chat_ui.rs crates/ui_tools/re_agent_ui/src/ui/chat_ui.rs:564— crates/ui_tools/re_agent_ui/src/ui/chat_ui.rs changed 43 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 26 in re_agent_ui::ui::chat_ui::config_menu_ui at line 564. 3 of those changes were fix/bug commits, and the other 40 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 23:06:51 +00:00' --until='2026-11-13 23:06:51 +00:00' --full-history --no-merges -- crates/ui_tools/re_agent_ui/src/ui/chat_ui.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/top/rerun/src/commands/entrypoint.rs crates/top/rerun/src/commands/entrypoint.rs:2102— crates/top/rerun/src/commands/entrypoint.rs changed 28 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 32 in rerun::commands::entrypoint::record_cli_command_analytics at line 2102. 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 23:06:51 +00:00' --until='2026-11-13 23:06:51 +00:00' --full-history --no-merges -- crates/top/rerun/src/commands/entrypoint.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/viewer_support/re_dataframe_ui/src/datafusion_table_widget.rs crates/viewer_support/re_dataframe_ui/src/datafusion_table_widget.rs:937— crates/viewer_support/re_dataframe_ui/src/datafusion_table_widget.rs changed 30 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 28 in DataFusionTableWidget::table_ui at line 937. 2 of those changes were fix/bug commits, and the other 28 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 23:06:51 +00:00' --until='2026-11-13 23:06:51 +00:00' --full-history --no-merges -- crates/viewer_support/re_dataframe_ui/src/datafusion_table_widget.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: scripts/lint.py scripts/lint.py:1803— scripts/lint.py changed 17 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 45 in lint.lint_file at line 1803. 1 of those changes was a fix/bug commit, and the other 16 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 23:06:51 +00:00' --until='2026-11-13 23:06:51 +00:00' --full-history --no-merges -- scripts/lint.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/panels/re_redap_browser/src/servers/mod.rs crates/panels/re_redap_browser/src/servers/mod.rs:1114— crates/panels/re_redap_browser/src/servers/mod.rs changed 23 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 33 in RedapServers::handle_command at line 1114. 2 of those changes were fix/bug commits, and the other 21 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 23:06:51 +00:00' --until='2026-11-13 23:06:51 +00:00' --full-history --no-merges -- crates/panels/re_redap_browser/src/servers/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/views/re_view_time_series/src/view_class.rs crates/views/re_view_time_series/src/view_class.rs:412— crates/views/re_view_time_series/src/view_class.rs changed 18 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 41 in TimeSeriesView::ui at line 412. 1 of those changes was a fix/bug commit, and the other 17 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 23:06:51 +00:00' --until='2026-11-13 23:06:51 +00:00' --full-history --no-merges -- crates/views/re_view_time_series/src/view_class.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/top/re_viewer/src/app/logic.rs crates/top/re_viewer/src/app/logic.rs:159— crates/top/re_viewer/src/app/logic.rs changed 33 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in AppCore::receive_messages at line 159. 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 23:06:51 +00:00' --until='2026-11-13 23:06:51 +00:00' --full-history --no-merges -- crates/top/re_viewer/src/app/logic.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/top/re_viewer/src/app/add_data_source.rs crates/top/re_viewer/src/app/add_data_source.rs:72— crates/top/re_viewer/src/app/add_data_source.rs changed 24 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in AppCore::load_data_source at line 72. 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 23:06:51 +00:00' --until='2026-11-13 23:06:51 +00:00' --full-history --no-merges -- crates/top/re_viewer/src/app/add_data_source.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/panels/re_agent_panel/src/lib.rs crates/panels/re_agent_panel/src/lib.rs:214— crates/panels/re_agent_panel/src/lib.rs changed 31 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in ViewerAgentPanel::show at line 214. 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 23:06:51 +00:00' --until='2026-11-13 23:06:51 +00:00' --full-history --no-merges -- crates/panels/re_agent_panel/src/lib.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/views/re_view_state_timeline/src/view_class.rs crates/views/re_view_state_timeline/src/view_class.rs:250— crates/views/re_view_state_timeline/src/view_class.rs changed 15 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 30 in StateTimelineView::ui at line 250. 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 23:06:51 +00:00' --until='2026-11-13 23:06:51 +00:00' --full-history --no-merges -- crates/views/re_view_state_timeline/src/view_class.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/viewer_support/re_dataframe_ui/src/filters/column_filter_ui.rs crates/viewer_support/re_dataframe_ui/src/filters/column_filter_ui.rs:89— crates/viewer_support/re_dataframe_ui/src/filters/column_filter_ui.rs changed 13 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 31 in re_dataframe_ui::filters::column_filter_ui::column_picker_ui at line 89. 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 23:06:51 +00:00' --until='2026-11-13 23:06:51 +00:00' --full-history --no-merges -- crates/viewer_support/re_dataframe_ui/src/filters/column_filter_ui.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/top/re_viewer/src/ui/top_panel.rs crates/top/re_viewer/src/ui/top_panel.rs:132— crates/top/re_viewer/src/ui/top_panel.rs changed 23 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in re_viewer::ui::top_panel::top_bar_ui at line 132. 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 23:06:51 +00:00' --until='2026-11-13 23:06:51 +00:00' --full-history --no-merges -- crates/top/re_viewer/src/ui/top_panel.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/top/re_viewer/src/web.rs crates/top/re_viewer/src/web.rs:648— crates/top/re_viewer/src/web.rs changed 21 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in re_viewer::web::create_app at line 648. 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 23:06:51 +00:00' --until='2026-11-13 23:06:51 +00:00' --full-history --no-merges -- crates/top/re_viewer/src/web.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/store_app/re_datafusion/src/dataframe_query_common/mod.rs crates/store_app/re_datafusion/src/dataframe_query_common/mod.rs:753— crates/store_app/re_datafusion/src/dataframe_query_common/mod.rs changed 16 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in DataframeQueryTableProvider::scan at line 753. 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 23:06:51 +00:00' --until='2026-11-13 23:06:51 +00:00' --full-history --no-merges -- crates/store_app/re_datafusion/src/dataframe_query_common/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/ui_tools/re_ui/src/notifications.rs crates/ui_tools/re_ui/src/notifications.rs:947— crates/ui_tools/re_ui/src/notifications.rs changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 28 in re_ui::notifications::show_notification at line 947. 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 23:06:51 +00:00' --until='2026-11-13 23:06:51 +00:00' --full-history --no-merges -- crates/ui_tools/re_ui/src/notifications.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/panels/re_viewport/src/viewport_ui.rs crates/panels/re_viewport/src/viewport_ui.rs:55— crates/panels/re_viewport/src/viewport_ui.rs changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 31 in ViewportUi::viewport_ui at line 55. 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 23:06:51 +00:00' --until='2026-11-13 23:06:51 +00:00' --full-history --no-merges -- crates/panels/re_viewport/src/viewport_ui.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/utils/re_agent/src/transcript.rs crates/utils/re_agent/src/transcript.rs:487— crates/utils/re_agent/src/transcript.rs changed 18 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in Transcript::to_markdown at line 487. 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 23:06:51 +00:00' --until='2026-11-13 23:06:51 +00:00' --full-history --no-merges -- crates/utils/re_agent/src/transcript.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/viewer_support/re_dataframe_ui/src/preview_renderer.rs crates/viewer_support/re_dataframe_ui/src/preview_renderer.rs:644— crates/viewer_support/re_dataframe_ui/src/preview_renderer.rs changed 16 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in re_dataframe_ui::preview_renderer::preview_playback_ui at line 644. 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 23:06:51 +00:00' --until='2026-11-13 23:06:51 +00:00' --full-history --no-merges -- crates/viewer_support/re_dataframe_ui/src/preview_renderer.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: rerun_py/rerun_sdk/rerun/experimental/dataloader/decoders/_video.py rerun_py/rerun_sdk/rerun/experimental/dataloader/decoders/_video.py:386— rerun_py/rerun_sdk/rerun/experimental/dataloader/decoders/_video.py changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 31 in VideoFrameDecoder._decode_run at line 386. 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 23:06:51 +00:00' --until='2026-11-13 23:06:51 +00:00' --full-history --no-merges -- rerun_py/rerun_sdk/rerun/experimental/dataloader/decoders/_video.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: rerun_py/rerun_sdk/rerun/experimental/dataloader/_utils.py rerun_py/rerun_sdk/rerun/experimental/dataloader/_utils.py:1234— rerun_py/rerun_sdk/rerun/experimental/dataloader/_utils.py changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 25 in _utils._discover_prior_keyframes at line 1234. 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 23:06:51 +00:00' --until='2026-11-13 23:06:51 +00:00' --full-history --no-merges -- rerun_py/rerun_sdk/rerun/experimental/dataloader/_utils.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/store_app/re_dataframe/src/query.rs crates/store_app/re_dataframe/src/query.rs:1788— crates/store_app/re_dataframe/src/query.rs changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 34 in QueryHandle::next_n_rows_in_store at line 1788. 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 23:06:51 +00:00' --until='2026-11-13 23:06:51 +00:00' --full-history --no-merges -- crates/store_app/re_dataframe/src/query.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.
FunctionTooLong: re_component_fallbacks::component_fallbacks::archetype_field_fallbacks crates/viewer_support/re_component_fallbacks/src/component_fallbacks.rs:30— FunctionTooLong — re_component_fallbacks::component_fallbacks::archetype_field_fallbacks runs 346 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 246 over it, 3.46× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: re_view_spatial::visualizers::video::execute_video_stream_like crates/views/re_view_spatial/src/visualizers/video/mod.rs:166— FunctionTooLong — re_view_spatial::visualizers::video::execute_video_stream_like runs 236 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 136 over it, 2.36× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: re_datafusion::dataframe_query_provider::io_loop::chunk_stream_io_loop crates/store_app/re_datafusion/src/dataframe_query_provider/io_loop.rs:694— FunctionTooLong — re_datafusion::dataframe_query_provider::io_loop::chunk_stream_io_loop runs 215 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 115 over it, 2.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.
FunctionTooLong: re_datafusion::analytics::build_query_span crates/store_app/re_datafusion/src/analytics/mod.rs:891— FunctionTooLong — re_datafusion::analytics::build_query_span runs 198 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 98 over it, 1.98× 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: re_datafusion::dataframe_query_provider::cpu_worker::chunk_store_cpu_worker_thread crates/store_app/re_datafusion/src/dataframe_query_provider/cpu_worker.rs:304— FunctionTooLong — re_datafusion::dataframe_query_provider::cpu_worker::chunk_store_cpu_worker_thread runs 195 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 95 over it, 1.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: re_view_time_series::line_series_loader::load_line_series_with_styling crates/views/re_view_time_series/src/line_series_loader.rs:103— FunctionTooLong — re_view_time_series::line_series_loader::load_line_series_with_styling runs 185 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 85 over it, 1.85× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: re_data_ui::entity_db_ui::grid_content_ui crates/viewer_support/re_data_ui/src/entity_db_ui.rs:102— FunctionTooLong — re_data_ui::entity_db_ui::grid_content_ui runs 178 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 78 over it, 1.78× 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: re_dataframe_ui::filters::column_filter_ui::column_picker_ui crates/viewer_support/re_dataframe_ui/src/filters/column_filter_ui.rs:89— FunctionTooLong — re_dataframe_ui::filters::column_filter_ui::column_picker_ui runs 170 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 70 over it, 1.70× 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: rerun::commands::rrd::route::process_messages crates/top/rerun/src/commands/rrd/route.rs:104— FunctionTooLong — rerun::commands::rrd::route::process_messages runs 163 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 63 over it, 1.63× 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: re_view_spatial::visualizers::video::show_video_frame crates/views/re_view_spatial/src/visualizers/video/mod.rs:586— FunctionTooLong — re_view_spatial::visualizers::video::show_video_frame runs 163 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 63 over it, 1.63× 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: re_protos::v1alpha1::rerun::cloud::v1alpha1::ext::legacy_adapter::adapt_legacy crates/store/re_protos/src/v1alpha1/rerun.cloud.v1alpha1.ext.legacy_adapter.rs:53— FunctionTooLong — re_protos::v1alpha1::rerun::cloud::v1alpha1::ext::legacy_adapter::adapt_legacy runs 160 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 60 over it, 1.60× 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: re_datafusion::chunk_fetcher::fetch_batch_via_direct_urls crates/store_app/re_datafusion/src/chunk_fetcher/mod.rs:703— FunctionTooLong — re_datafusion::chunk_fetcher::fetch_batch_via_direct_urls runs 159 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 59 over it, 1.59× 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: re_viewer::blueprint::references::reference_problems crates/top/re_viewer/src/blueprint/references.rs:174— FunctionTooLong — re_viewer::blueprint::references::reference_problems runs 157 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 57 over it, 1.57× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: re_redap_client::connection_client::rrd_manifest::fetch_rrd_manifest_via_key crates/data_flow/re_redap_client/src/connection_client/rrd_manifest.rs:39— FunctionTooLong — re_redap_client::connection_client::rrd_manifest::fetch_rrd_manifest_via_key runs 153 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 53 over it, 1.53× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: rerun::commands::entrypoint::start_native_viewer crates/top/rerun/src/commands/entrypoint.rs:1228— FunctionTooLong — rerun::commands::entrypoint::start_native_viewer runs 153 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 53 over it, 1.53× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: re_selection_panel::visualizer_ui::visualizer_components crates/panels/re_selection_panel/src/visualizer_ui.rs:216— FunctionTooLong — re_selection_panel::visualizer_ui::visualizer_components runs 151 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 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: re_sdk::spawn::spawn crates/top/re_sdk/src/spawn.rs:205— FunctionTooLong — re_sdk::spawn::spawn runs 151 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 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: re_dataframe_ui::cards_view::card_content_ui crates/viewer_support/re_dataframe_ui/src/cards_view.rs:207— FunctionTooLong — re_dataframe_ui::cards_view::card_content_ui runs 151 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 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: re_view_spatial::picking_ui::picking crates/views/re_view_spatial/src/picking_ui.rs:28— FunctionTooLong — re_view_spatial::picking_ui::picking runs 151 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 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: re_time_panel::time_selection_ui::loop_selection_ui crates/panels/re_time_panel/src/time_selection_ui.rs:56— FunctionTooLong — re_time_panel::time_selection_ui::loop_selection_ui runs 143 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 43 over it, 1.43× 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: re_view_spatial::shared_fallbacks::register_fallbacks crates/views/re_view_spatial/src/shared_fallbacks.rs:27— FunctionTooLong — re_view_spatial::shared_fallbacks::register_fallbacks 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.
FunctionTooLong: rerun_py" # name of the rust crate::python_bridge::rerun_bindings rerun_py/src/python_bridge.rs:186— FunctionTooLong — rerun_py" # name of the rust crate::python_bridge::rerun_bindings runs 140 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 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: re_viewport_blueprint::viewport_blueprint::apply_viewport_command crates/viewer_support/re_viewport_blueprint/src/viewport_blueprint.rs:974— FunctionTooLong — re_viewport_blueprint::viewport_blueprint::apply_viewport_command runs 139 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 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: rerun::commands::entrypoint::run_impl crates/top/rerun/src/commands/entrypoint.rs:1044— FunctionTooLong — rerun::commands::entrypoint::run_impl runs 137 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 37 over it, 1.37× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: re_viewer::ui::settings_screen::settings_screen_ui_impl crates/top/re_viewer/src/ui/settings_screen.rs:44— FunctionTooLong — re_viewer::ui::settings_screen::settings_screen_ui_impl runs 134 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 34 over it, 1.34× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
Duplicated block (9 lines × 2) crates/data_flow/re_lenses/src/semantic/ros2msg/voxel_grid.rs:150— crates/data_flow/re_lenses/src/semantic/ros2msg/voxel_grid.rs:150-158 | crates/data_flow/re_lenses/src/semantic/ros2msg/voxel_grid.rs:174-182 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/data_flow/re_lenses/src/semantic/ros2msg/voxel_grid.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 (9 lines × 2) crates/panels/re_chunk_store_ui/src/chunk_store_ui.rs:476— crates/panels/re_chunk_store_ui/src/chunk_store_ui.rs:476-484 | crates/panels/re_chunk_store_ui/src/chunk_ui.rs:196-204 — 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/panels/re_chunk_store_ui/src/chunk_store_ui.rs:476` it does not close everything it opens, so those exact lines 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/store/re_chunk/src/earliest_at.rs:99— crates/store/re_chunk/src/earliest_at.rs:99-107 | crates/store/re_chunk/src/latest_at.rs:124-132 — 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/store/re_chunk/src/earliest_at.rs:99` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `query` to `&EarliestAtQuery` in one and `&LatestAtQuery` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (9 lines × 2) crates/store/re_lenses_core/src/selector/eval.rs:498— crates/store/re_lenses_core/src/selector/eval.rs:498-506 | crates/store/re_lenses_core/src/selector/eval.rs:582-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. Read the line range as the matched WINDOW rather than a finished unit: at `crates/store/re_lenses_core/src/selector/eval.rs:498` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) crates/store/re_lenses_core/src/selector/lexer.rs:122— crates/store/re_lenses_core/src/selector/lexer.rs:122-130 | crates/store/re_lenses_core/src/selector/lexer.rs:209-217 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/store/re_lenses_core/src/selector/lexer.rs:122` it does not close everything it opens, so those exact lines 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/store_app/re_catalog_client/src/segment.rs:148— crates/store_app/re_catalog_client/src/segment.rs:148-156 | crates/store_app/re_catalog_client/src/segment.rs:200-208 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/store_app/re_catalog_client/src/segment.rs:148` 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/store_app/re_dataframe/src/query.rs:1242— crates/store_app/re_dataframe/src/query.rs:1242-1250 | crates/store_app/re_dataframe/src/query.rs:1722-1730 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) crates/store_app/re_entity_db/src/entity_db.rs:1211— crates/store_app/re_entity_db/src/entity_db.rs:1211-1219 | crates/store_app/re_entity_db/src/entity_db.rs:1234-1242 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/store_app/re_entity_db/src/entity_db.rs:1211` it does not close everything it opens, so those exact lines 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/store_app/re_server/src/rerun_cloud/mod.rs:1453— crates/store_app/re_server/src/rerun_cloud/mod.rs:1453-1461 | crates/store_app/re_server/src/rerun_cloud/mod.rs:1517-1525 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/store_app/re_server/src/rerun_cloud/mod.rs:1453` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `request` to `tonic::Request<re_protos::cloud::v1alpha1::ScanSegmentTableRequest>` in one and `Request<ScanDatasetManifestRequest>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `crates/store_app/re_server/src/rerun_cloud/mod.rs:1514` calls `apply_layer_name_filter`, `as_ref` and `crates/store_app/re_server/src/rerun_cloud/mod.rs:1450` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 2) crates/utils/re_arrow_util/src/format.rs:298— crates/utils/re_arrow_util/src/format.rs:298-306 | crates/utils/re_arrow_util/src/format.rs:353-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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `crates/utils/re_arrow_util/src/format.rs:295` calls `format_dataframe_without_metadata`, `is_empty` and `crates/utils/re_arrow_util/src/format.rs:351` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 2) crates/utils/re_auth/src/callback_server.rs:27— crates/utils/re_auth/src/callback_server.rs:27-35 | crates/utils/re_auth/src/callback_server.rs:70-78 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `crates/utils/re_auth/src/callback_server.rs:80` calls `new_v4`, `to_string` and `crates/utils/re_auth/src/callback_server.rs:37` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 2) crates/utils/re_auth/src/oauth/api.rs:76— crates/utils/re_auth/src/oauth/api.rs:76-84 | crates/utils/re_auth/src/oauth/api.rs:101-109 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/utils/re_auth/src/oauth/api.rs:76` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) crates/utils/re_video/src/demux/mod.rs:367— crates/utils/re_video/src/demux/mod.rs:367-375 | crates/utils/re_video/src/demux/mod.rs:390-398 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) crates/viewer_support/re_dataframe_ui/src/filters/filter.rs:145— crates/viewer_support/re_dataframe_ui/src/filters/filter.rs:145-153 | crates/viewer_support/re_dataframe_ui/src/filters/filter.rs:156-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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (9 lines × 2) crates/viewer_support/re_viewer_context/src/item.rs:164— crates/viewer_support/re_viewer_context/src/item.rs:164-172 | crates/viewer_support/re_viewer_context/src/item.rs:205-213 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/viewer_support/re_viewer_context/src/item.rs:164` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) crates/views/re_view_graph/src/ui/draw.rs:144— crates/views/re_view_graph/src/ui/draw.rs:144-152 | crates/views/re_view_graph/src/ui/draw.rs:172-180 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `crates/views/re_view_graph/src/ui/draw.rs:184` calls `unwrap_or_else`, `text_color`, `gamma_multiply` and `crates/views/re_view_graph/src/ui/draw.rs:154` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 2) crates/views/re_view_graph/src/ui/draw.rs:365— crates/views/re_view_graph/src/ui/draw.rs:365-373 | crates/views/re_view_map/src/map_view.rs:472-480 — 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/views/re_view_graph/src/ui/draw.rs:365` 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/views/re_view_time_series/src/line_visualizer_system.rs:287— crates/views/re_view_time_series/src/line_visualizer_system.rs:287-295 | crates/views/re_view_time_series/src/line_visualizer_system.rs:353-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/views/re_view_time_series/src/line_visualizer_system.rs:287` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (9 lines × 2) docs/snippets/all/archetypes/line_strips3d_segments_simple.rs:6— docs/snippets/all/archetypes/line_strips3d_segments_simple.rs:6-14 | docs/snippets/all/archetypes/line_strips3d_simple.rs:5-13 — 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 `docs/snippets/all/archetypes/line_strips3d_segments_simple.rs:6` 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) docs/snippets/all/tutorials/dna.rs:68— docs/snippets/all/tutorials/dna.rs:68-76 | docs/snippets/all/tutorials/dna.rs:92-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 `docs/snippets/all/tutorials/dna.rs:68` 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/utils/re_video/src/demux/mod.rs:256— crates/utils/re_video/src/demux/mod.rs:256-264 | crates/utils/re_video/src/demux/mp4.rs:74-82 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `crates/utils/re_video/src/demux/mod.rs:256` it does not close everything it opens, so those exact lines 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/store/re_sdk_types/src/archetypes/points2d_ext.rs:42— crates/store/re_sdk_types/src/archetypes/points2d_ext.rs:42-50 | crates/store/re_sdk_types/src/archetypes/points3d_ext.rs:47-55 — before extracting anything, compare `crates/store/re_sdk_types/src/archetypes/points2d_ext.rs` and `crates/store/re_sdk_types/src/archetypes/points3d_ext.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 65 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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/store/re_sdk_types/src/archetypes/points2d_ext.rs:42` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `crates/store/re_sdk_types/src/archetypes/points3d_ext.rs:44` calls `set_required_f32` and `crates/store/re_sdk_types/src/archetypes/points2d_ext.rs:39` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 2) rerun_py/src/trace_context.rs:65— rerun_py/src/trace_context.rs:65-73 | rerun_py/src/tracing_session.rs:42-50 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9 lines × 2) rerun_py/src/catalog/segment_url_udf.rs:215— rerun_py/src/catalog/segment_url_udf.rs:215-223 | rerun_py/src/catalog/segment_url_udf.rs:232-243 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `rerun_py/src/catalog/segment_url_udf.rs:215` 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/ui_tools/re_renderer/src/renderer/rectangles.rs:770— crates/ui_tools/re_renderer/src/renderer/rectangles.rs:770-778 | crates/ui_tools/re_renderer/src/renderer/rectangles.rs:781-790 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/ui_tools/re_renderer/src/renderer/rectangles.rs:770` 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.
Change coupling: viewport_ui.rs ↔ auto_layout.rs crates/panels/re_viewport/src/viewport_ui.rs:1— `crates/panels/re_viewport/src/viewport_ui.rs` and `crates/viewer_support/re_viewport_blueprint/src/auto_layout.rs` change together 86% of the time (19 of the 22 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — 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 19 shared commits counted here, the most recent 3 are `3deb7af3` Move the blueprint saving logic to `re_viewer_blueprint` (#8717) (at that commit the files were still `crates/viewer/re_viewport/src/viewport_ui.rs` and `crates/viewer/re_viewport_blueprint/src/auto_layout.rs`); `cd494cc4` Move SpaceViewBlueprint -> re_space_view (#5047) (at that commit the files were still `crates/re_viewport/src/viewport.rs` and `crates/re_viewport/src/auto_layout.rs`); `4c9753e7` Improve viewport tile behavior (#3295) (at that commit the files were still `crates/re_viewport/src/viewport.rs` and `crates/re_viewport/src/auto_layout.rs`) — run `git show` on any of them.
Change coupling: gltf.rs ↔ obj.rs crates/ui_tools/re_renderer/src/importer/gltf.rs:1— `crates/ui_tools/re_renderer/src/importer/gltf.rs` and `crates/ui_tools/re_renderer/src/importer/obj.rs` change together 85% of the time (11 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 11 shared commits counted here, the most recent 3 are `7df80219` Compute `Asset3D` normals when they are missing (at that commit the files were still `crates/viewer_support/re_renderer/src/importer/gltf.rs` and `crates/viewer_support/re_renderer/src/importer/obj.rs`); `3e26be7f` Ignore NaN/Inf values for bounding box calculations used in 3d eye ca… (at that commit the files were still `crates/viewer/re_renderer/src/importer/gltf.rs` and `crates/viewer/re_renderer/src/importer/obj.rs`); `8382f149` Fix bounding box calculation for GLB/GLTF & DAE meshes (at that commit the files were still `crates/viewer/re_renderer/src/importer/gltf.rs` and `crates/viewer/re_renderer/src/importer/obj.rs`) — run `git show` on any of them.
Change coupling: widget.ts ↔ __init__.py rerun_notebook/src/js/widget.ts:1— `rerun_notebook/src/js/widget.ts` and `rerun_notebook/src/rerun_notebook/__init__.py` change together 84% of the time (16 of the 19 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) and are written in DIFFERENT LANGUAGES, so no import can join them and they cannot be co-located into one unit — they compile and ship as separate artifacts. What binds them is a CONTRACT across that boundary — an event or message name, a route, a serialised shape — that each side currently spells out on its own, which is exactly why a change to one drags the other. Declare that contract once where both sides read it (a shared schema, a generated constants file, an interface-definition file) so a change on one side fails the other's build instead of drifting silently; where the surface is too small to be worth that, name the counterpart in a comment on both sides so the next reader finds it. There is nothing here to merge. You can check this without leaving the row: of the 16 shared commits counted here, the most recent 3 are `e5fc7f08` Move the WebViewer time and recording methods onto the Viewer Control…; `45c11358` Fix theme warning for embedded viewers in Python notebooks; `beaee9c6` Expose theme setting on web-viewer notebook — run `git show` on any of them.
Change coupling: depth_offsets.rs ↔ transform_tree_context.rs crates/views/re_view_spatial/src/contexts/depth_offsets.rs:1— `crates/views/re_view_spatial/src/contexts/depth_offsets.rs` and `crates/views/re_view_spatial/src/contexts/transform_tree_context.rs` change together 82% of the time (9 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `f622d5ef` Minor blueprint resolved query refactors (at that commit the files were still `crates/viewer/re_view_spatial/src/contexts/depth_offsets.rs` and `crates/viewer/re_view_spatial/src/contexts/transform_tree_context.rs`); `624160e0` Move `QueryContext` into `BlueprintResolvedLatestAtResult` (at that commit the files were still `crates/viewer/re_view_spatial/src/contexts/depth_offsets.rs` and `crates/viewer/re_view_spatial/src/contexts/transform_tree_context.rs`); `d899007d` Add `VisualizerInstructionId` to `QueryContext` if available (at that commit the files were still `crates/viewer/re_view_spatial/src/contexts/depth_offsets.rs` and `crates/viewer/re_view_spatial/src/contexts/transform_tree_context.rs`) — run `git show` on any of them.
Change coupling: line_visualizer_system.rs ↔ point_visualizer_system.rs crates/views/re_view_time_series/src/line_visualizer_system.rs:1— `crates/views/re_view_time_series/src/line_visualizer_system.rs` and `crates/views/re_view_time_series/src/point_visualizer_system.rs` change together 78% of the time (36 of the 46 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 36 shared commits counted here, the most recent 3 are `8c8e96b6` Time series: warn when scalar series count changes (#12802) (at that commit the files were still `crates/viewer/re_view_time_series/src/line_visualizer_system.rs` and `crates/viewer/re_view_time_series/src/point_visualizer_system.rs`); `7d6aeef7` Skip empty visualizers (at that commit the files were still `crates/viewer/re_view_time_series/src/line_visualizer_system.rs` and `crates/viewer/re_view_time_series/src/point_visualizer_system.rs`); `f9ca4953` Fix spamming errors when trying to show static scalars in the time se… (at that commit the files were still `crates/viewer/re_view_time_series/src/line_visualizer_system.rs` and `crates/viewer/re_view_time_series/src/point_visualizer_system.rs`) — run `git show` on any of them.
Change coupling: history.rs ↔ web.rs crates/top/re_viewer/src/history.rs:1— `crates/top/re_viewer/src/history.rs` and `crates/top/re_viewer/src/web.rs` change together 77% of the time (10 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `9bac4784` Rename `ViewerOpenUrl` to `ViewerUrl`; `436ea5ca` Show loading screen when opening link (#11270) (at that commit the files were still `crates/viewer/re_viewer/src/history.rs` and `crates/viewer/re_viewer/src/web.rs`); `1470937c` Add share link button to time panel context menu (#11186) (at that commit the files were still `crates/viewer/re_viewer/src/history.rs` and `crates/viewer/re_viewer/src/web.rs`) — run `git show` on any of them.
Change coupling: points2d.rs ↔ points3d.rs crates/views/re_view_spatial/src/visualizers/points2d.rs:1— `crates/views/re_view_spatial/src/visualizers/points2d.rs` and `crates/views/re_view_spatial/src/visualizers/points3d.rs` change together 71% of the time (17 of the 24 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 17 shared commits counted here, the most recent 3 are `d96b077b` Refactor spatial visualizer bounds into a single `SpatialViewBounds` (at that commit the files were still `crates/viewer/re_view_spatial/src/visualizers/points2d.rs` and `crates/viewer/re_view_spatial/src/visualizers/points3d.rs`); `3e26be7f` Ignore NaN/Inf values for bounding box calculations used in 3d eye ca… (at that commit the files were still `crates/viewer/re_view_spatial/src/visualizers/points2d.rs` and `crates/viewer/re_view_spatial/src/visualizers/points3d.rs`); `9056ec92` Chunkified, deserialization-free Point Cloud visualizers (#7011) (at that commit the files were still `crates/viewer/re_space_view_spatial/src/visualizers/points2d.rs` and `crates/viewer/re_space_view_spatial/src/visualizers/points3d.rs`) — run `git show` on any of them.
Change coupling: view_class.rs ↔ view_class.rs crates/views/re_view_bar_chart/src/view_class.rs:1— `crates/views/re_view_bar_chart/src/view_class.rs` and `crates/views/re_view_time_series/src/view_class.rs` change together 70% of the time (30 of the 43 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — 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 30 shared commits counted here, the most recent 3 are `7d6aeef7` Skip empty visualizers (at that commit the files were still `crates/viewer/re_view_bar_chart/src/view_class.rs` and `crates/viewer/re_view_time_series/src/view_class.rs`); `2503bddf` Don't use ahash from egui since it's deprecated (at that commit the files were still `crates/viewer/re_view_bar_chart/src/view_class.rs` and `crates/viewer/re_view_time_series/src/view_class.rs`); `b1a9d828` New tooltip redesign (at that commit the files were still `crates/viewer/re_view_bar_chart/src/view_class.rs` and `crates/viewer/re_view_time_series/src/view_class.rs`) — run `git show` on any of them.
Change coupling: obj.rs ↔ mesh_renderer.rs crates/ui_tools/re_renderer/src/importer/obj.rs:1— `crates/ui_tools/re_renderer/src/importer/obj.rs` and `crates/ui_tools/re_renderer/src/renderer/mesh_renderer.rs` change together 69% of the time (9 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `3e26be7f` Ignore NaN/Inf values for bounding box calculations used in 3d eye ca… (at that commit the files were still `crates/viewer/re_renderer/src/importer/obj.rs` and `crates/viewer/re_renderer/src/renderer/mesh_renderer.rs`); `1c02564c` Don't keep around additional cpu copy of loaded mesh files (#7824) (at that commit the files were still `crates/viewer/re_renderer/src/importer/obj.rs` and `crates/viewer/re_renderer/src/renderer/mesh_renderer.rs`); `514ed624` Remove old `MeshManager` (#7531) (at that commit the files were still `crates/viewer/re_renderer/src/importer/obj.rs` and `crates/viewer/re_renderer/src/renderer/mesh_renderer.rs`) — run `git show` on any of them.
Change coupling: defaults_ui.rs ↔ visualizer_ui.rs crates/panels/re_selection_panel/src/defaults_ui.rs:1— `crates/panels/re_selection_panel/src/defaults_ui.rs` and `crates/panels/re_selection_panel/src/visualizer_ui.rs` change together 68% of the time (15 of the 22 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 15 shared commits counted here, the most recent 3 are `3e404788` More powerful AppContext (at that commit the files were still `crates/viewer/re_selection_panel/src/defaults_ui.rs` and `crates/viewer/re_selection_panel/src/visualizer_ui.rs`); `0221dcdb` Query fallbacks via descriptor (at that commit the files were still `crates/viewer/re_selection_panel/src/defaults_ui.rs` and `crates/viewer/re_selection_panel/src/visualizer_ui.rs`); `b3fa1fc5` Only allow ui edits of visualizer components where they actually have… (at that commit the files were still `crates/viewer/re_selection_panel/src/defaults_ui.rs` and `crates/viewer/re_selection_panel/src/visualizer_ui.rs`) — run `git show` on any of them.
Change coupling: __init__.py ↔ mod.rs rerun_py/rerun_sdk/rerun/catalog/__init__.py:1— `rerun_py/rerun_sdk/rerun/catalog/__init__.py` and `rerun_py/src/catalog/mod.rs` change together 67% of the time (16 of the 24 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) and are written in DIFFERENT LANGUAGES, so no import can join them and they cannot be co-located into one unit — they compile and ship as separate artifacts. What binds them is a CONTRACT across that boundary — an event or message name, a route, a serialised shape — that each side currently spells out on its own, which is exactly why a change to one drags the other. Declare that contract once where both sides read it (a shared schema, a generated constants file, an interface-definition file) so a change on one side fails the other's build instead of drifting silently; where the surface is too small to be worth that, name the counterpart in a comment on both sides so the next reader finds it. There is nothing here to merge. You can check this without leaving the row: of the 16 shared commits counted here, the most recent 3 are `142f7883` Name property for blueprints; `12e530e5` Implement initial version of `CatalogClient._write_segment()`; `04390521` Rename `DatasetView` to `DatasetSelection` — run `git show` on any of them.
Change coupling: assets3d.rs ↔ meshes.rs crates/views/re_view_spatial/src/visualizers/assets3d.rs:1— `crates/views/re_view_spatial/src/visualizers/assets3d.rs` and `crates/views/re_view_spatial/src/visualizers/meshes.rs` change together 67% of the time (10 of the 15 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `d995b273` Lazily convert to string (at that commit the files were still `crates/viewer/re_view_spatial/src/visualizers/assets3d.rs` and `crates/viewer/re_view_spatial/src/visualizers/meshes.rs`); `a830fa0a` Always access `caches` through `store_context` (#9030) (at that commit the files were still `crates/viewer/re_view_spatial/src/visualizers/assets3d.rs` and `crates/viewer/re_view_spatial/src/visualizers/meshes.rs`); `1c02564c` Don't keep around additional cpu copy of loaded mesh files (#7824) (at that commit the files were still `crates/viewer/re_space_view_spatial/src/visualizers/assets3d.rs` and `crates/viewer/re_space_view_spatial/src/visualizers/meshes.rs`) — run `git show` on any of them.
Change coupling: grpc_server.rs ↔ web_viewer.rs crates/top/re_sdk/src/grpc_server.rs:1— `crates/top/re_sdk/src/grpc_server.rs` and `crates/top/re_sdk/src/web_viewer.rs` change together 64% of the time (7 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `e6d4f0f0` Use owned listeners for `re_grpc_server`; `2f5943f0` Revert "Listen on both ipv4+ipv6 rather than ipv4 only by default (#97)"; `9e4cd586` Unify LogMsg and TableMsg handling in re_grpc_server and viewer (#11963) — run `git show` on any of them.
Change coupling: widget.ts ↔ notebook.py rerun_notebook/src/js/widget.ts:1— `rerun_notebook/src/js/widget.ts` and `rerun_py/rerun_sdk/rerun/notebook.py` change together 63% of the time (12 of the 19 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) and are written in DIFFERENT LANGUAGES, so no import can join them and they cannot be co-located into one unit — they compile and ship as separate artifacts. What binds them is a CONTRACT across that boundary — an event or message name, a route, a serialised shape — that each side currently spells out on its own, which is exactly why a change to one drags the other. Declare that contract once where both sides read it (a shared schema, a generated constants file, an interface-definition file) so a change on one side fails the other's build instead of drifting silently; where the surface is too small to be worth that, name the counterpart in a comment on both sides so the next reader finds it. There is nothing here to merge. You can check this without leaving the row: of the 12 shared commits counted here, the most recent 3 are `e5fc7f08` Move the WebViewer time and recording methods onto the Viewer Control…; `beaee9c6` Expose theme setting on web-viewer notebook; `99ffdbe8` Auth for Jupyter Notebooks (#11855) — run `git show` on any of them.
Change coupling: view_2d.rs ↔ view_3d.rs crates/views/re_view_spatial/src/view_2d.rs:1— `crates/views/re_view_spatial/src/view_2d.rs` and `crates/views/re_view_spatial/src/view_3d.rs` change together 60% of the time (27 of the 45 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 27 shared commits counted here, the most recent 3 are `093a677e` Skip heuristic exclusions if transform frame ids have been logged (#1… (at that commit the files were still `crates/viewer/re_view_spatial/src/view_2d.rs` and `crates/viewer/re_view_spatial/src/view_3d.rs`); `2e71c003` Add exclusions for 2d visualizables in 3d and vice-versa (#12087) (at that commit the files were still `crates/viewer/re_view_spatial/src/view_2d.rs` and `crates/viewer/re_view_spatial/src/view_3d.rs`); `e27bf80e` Fix: don't always pick `/` as the origin when creating new views (#10… (at that commit the files were still `crates/viewer/re_view_spatial/src/view_2d.rs` and `crates/viewer/re_view_spatial/src/view_3d.rs`) — run `git show` on any of them.
Change coupling: loading.rs ↔ mod.rs crates/top/re_viewer/src/loading.rs:1— `crates/top/re_viewer/src/loading.rs` and `crates/viewer_support/re_viewer_context/src/store_hub/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, and counted over this repository's 10,000 most recent commits rather than its whole history — 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 `f26336ef` Removing all calls to `StoreBundle::entry` apart from `entity_db_entry` (at that commit the files were still `crates/viewer/re_viewer/src/loading.rs` and `crates/viewer/re_viewer_context/src/store_hub.rs`); `f5f80f98` Move `StoreBundle` from `re_viewer_context` to `re_entity_db` (#9971) (at that commit the files were still `crates/viewer/re_viewer/src/loading.rs` and `crates/viewer/re_viewer_context/src/store_hub.rs`); `ef0a3e8b` Move `store_bundle` to `re_viewer_context` (#9407) (at that commit the files were still `crates/viewer/re_viewer/src/loading.rs` and `crates/viewer/re_viewer_context/src/store_hub.rs`) — run `git show` on any of them.
Change coupling: navigation.rs ↔ viewer_context.rs crates/top/re_viewer/src/navigation.rs:1— `crates/top/re_viewer/src/navigation.rs` and `crates/viewer_support/re_viewer_context/src/viewer_context.rs` change together 58% of the time (7 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `f30766b1` Failure to load will now stay in loading screen (with error) for all … (at that commit the files were still `crates/viewer/re_viewer/src/navigation.rs` and `crates/viewer/re_viewer_context/src/viewer_context.rs`); `e62fda09` Rename `DisplayMode` -> `Route` (at that commit the files were still `crates/viewer/re_viewer/src/navigation.rs` and `crates/viewer/re_viewer_context/src/viewer_context.rs`); `b06cc217` Refactor: Remove state from `StoreHub` (at that commit the files were still `crates/viewer/re_viewer/src/navigation.rs` and `crates/viewer/re_viewer_context/src/viewer_context.rs`) — run `git show` on any of them.
Change coupling: selection_panel.rs ↔ view_highlights.rs crates/panels/re_selection_panel/src/selection_panel.rs:1— `crates/panels/re_selection_panel/src/selection_panel.rs` and `crates/viewer_support/re_view/src/view_highlights.rs` change together 58% of the time (7 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `9f04b354` Add an explicit `DataResult` variant to `re_viewport_context::Item` (… (at that commit the files were still `crates/re_viewer/src/ui/selection_panel.rs` and `crates/re_viewport/src/space_view_highlights.rs`); `4dc09f1f` Remove groups from blueprint (#5326) (at that commit the files were still `crates/re_viewer/src/ui/selection_panel.rs` and `crates/re_viewport/src/space_view_highlights.rs`); `48f64a73` Click a recording to select it (#4761) (at that commit the files were still `crates/re_viewer/src/ui/selection_panel.rs` and `crates/re_viewport/src/space_view_highlights.rs`) — run `git show` on any of them.
Change coupling: depth_images.rs ↔ images.rs crates/views/re_view_spatial/src/visualizers/depth_images.rs:1— `crates/views/re_view_spatial/src/visualizers/depth_images.rs` and `crates/views/re_view_spatial/src/visualizers/images.rs` change together 58% of the time (7 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `19b2c79a` Make more visualizer errors point to specific components that are in … (at that commit the files were still `crates/viewer/re_view_spatial/src/visualizers/depth_images.rs` and `crates/viewer/re_view_spatial/src/visualizers/images.rs`); `c8d169b2` Fix missing error when drawing depth image for point cloud without pi… (at that commit the files were still `crates/viewer/re_view_spatial/src/visualizers/depth_images.rs` and `crates/viewer/re_view_spatial/src/visualizers/images.rs`); `1d1eb78b` Prepare video visualizer for upcoming stream visualizer (#10125) (at that commit the files were still `crates/viewer/re_view_spatial/src/visualizers/depth_images.rs` and `crates/viewer/re_view_spatial/src/visualizers/images.rs`) — run `git show` on any of them.
Change coupling: lib.rs ↔ lib.rs crates/utils/re_analytics/src/lib.rs:1— `crates/utils/re_analytics/src/lib.rs` and `crates/utils/re_build_info/src/lib.rs` change together 58% of the time (7 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `553a767f` dont hardcode build mode into `BuildInfo` (#11386) (at that commit the file was still `crates/build/re_build_info/src/lib.rs`); `762fa4cf` Implement gRPC versioning APIs (#10039) (at that commit the file was still `crates/build/re_build_info/src/lib.rs`); `d0b60f9c` Show list of enabled feature with `rerun --version` (#7885) (at that commit the file was still `crates/build/re_build_info/src/lib.rs`) — run `git show` on any of them.
Change coupling: selection_history_ui.rs ↔ view_highlights.rs crates/panels/re_selection_panel/src/selection_history_ui.rs:1— `crates/panels/re_selection_panel/src/selection_history_ui.rs` and `crates/viewer_support/re_view/src/view_highlights.rs` change together 58% of the time (7 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `493bc5ba` Rename some structures and APIs around selection (#5597) (at that commit the files were still `crates/re_viewer/src/ui/selection_history_ui.rs` and `crates/re_viewport/src/space_view_highlights.rs`); `9f04b354` Add an explicit `DataResult` variant to `re_viewport_context::Item` (… (at that commit the files were still `crates/re_viewer/src/ui/selection_history_ui.rs` and `crates/re_viewport/src/space_view_highlights.rs`); `4dc09f1f` Remove groups from blueprint (#5326) (at that commit the files were still `crates/re_viewer/src/ui/selection_history_ui.rs` and `crates/re_viewport/src/space_view_highlights.rs`) — run `git show` on any of them.
Change coupling: image_decode_cache.rs ↔ video_asset_cache.rs crates/viewer_support/re_viewer_context/src/cache/image_decode_cache.rs:1— `crates/viewer_support/re_viewer_context/src/cache/image_decode_cache.rs` and `crates/viewer_support/re_viewer_context/src/cache/video_asset_cache.rs` change together 58% of the time (7 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `056c5d65` Use `IntMap` for caches keyed by hashes; `3149d364` Add `pixi run rerun-fast` for faster compile times using cranelift (at that commit the files were still `crates/viewer/re_viewer_context/src/cache/image_decode_cache.rs` and `crates/viewer/re_viewer_context/src/cache/video_asset_cache.rs`); `95a4b5ea` Help out `+nightly` type checker by specifying trait bounds (#12432) (at that commit the files were still `crates/viewer/re_viewer_context/src/cache/image_decode_cache.rs` and `crates/viewer/re_viewer_context/src/cache/video_asset_cache.rs`) — run `git show` on any of them.
Change coupling: grpc_server.rs ↔ entrypoint.rs crates/top/re_sdk/src/grpc_server.rs:1— `crates/top/re_sdk/src/grpc_server.rs` and `crates/top/rerun/src/commands/entrypoint.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, and counted over this repository's 10,000 most recent commits rather than its whole history — 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 `e6d4f0f0` Use owned listeners for `re_grpc_server`; `2f5943f0` Revert "Listen on both ipv4+ipv6 rather than ipv4 only by default (#97)"; `9e4cd586` Unify LogMsg and TableMsg handling in re_grpc_server and viewer (#11963) — run `git show` on any of them.
Change coupling: frame_id_registry.rs ↔ transform_tree_context.rs crates/store_app/re_tf/src/frame_id_registry.rs:1— `crates/store_app/re_tf/src/frame_id_registry.rs` and `crates/views/re_view_spatial/src/contexts/transform_tree_context.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, and counted over this repository's 10,000 most recent commits rather than its whole history — 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 `5bf9c4a6` Clearer behavior for `CoordinateFrame("")` (at that commit the files were still `crates/store/re_tf/src/frame_id_registry.rs` and `crates/viewer/re_view_spatial/src/contexts/transform_tree_context.rs`); `6589388d` Use full recording schema in manifest ingestion (at that commit the files were still `crates/store/re_tf/src/frame_id_registry.rs` and `crates/viewer/re_view_spatial/src/contexts/transform_tree_context.rs`); `5072951e` Show `TransformAxes3D` for out-of-hierarchy `Transform`s (#12262) (at that commit the files were still `crates/store/re_tf/src/frame_id_registry.rs` and `crates/viewer/re_view_spatial/src/contexts/transform_tree_context.rs`) — run `git show` on any of them.
Change coupling: mod.rs ↔ source.rs crates/store_app/re_server/src/rerun_cloud/mod.rs:1— `crates/store_app/re_server/src/rerun_cloud/mod.rs` and `crates/store_app/re_server/src/store/source.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, and counted over this repository's 10,000 most recent commits rather than its whole history — 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 `f27aa8f6` Replace `[u8; 32]` schema hashes with a `SchemaId` newtype; `143dfa96` Introduce `/GetSchemas`; `1cbb1fd9` Send correct source for OSS server (at that commit the files were still `crates/store/re_server/src/rerun_cloud/mod.rs` and `crates/store/re_server/src/store/source.rs`) — run `git show` on any of them.
re_types_builder::codegen::rust::serializer::quote_arrow_field_serializer (cognitive 105) crates/build/re_types_builder/src/codegen/rust/serializer.rs:568— re_types_builder::codegen::rust::serializer::quote_arrow_field_serializer has cognitive complexity 105 (threshold 15). Drivers by points: if/else 53 (93 pts), match/switch 5 (10 pts), boolean chains 2 (nesting depth added 45). 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.
re_types_builder::codegen::python::code_for_struct (cognitive 75) crates/build/re_types_builder/src/codegen/python/mod.rs:735— re_types_builder::codegen::python::code_for_struct has cognitive complexity 75 (threshold 15). Drivers by points: if/else 40 (61 pts), loops 3 (9 pts), match/switch 2 (3 pts), boolean chains 2 (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.
re_types_builder::codegen::python::check_ext_consistency (cognitive 61) crates/build/re_types_builder/src/codegen/python/mod.rs:309— re_types_builder::codegen::python::check_ext_consistency has cognitive complexity 61 (threshold 15). Drivers by points: if/else 18 (43 pts), loops 5 (15 pts), boolean chains 3 (nesting depth added 35). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
re_types_builder::codegen::python::quote_arrow_serialization (cognitive 60) crates/build/re_types_builder/src/codegen/python/mod.rs:2343— re_types_builder::codegen::python::quote_arrow_serialization has cognitive complexity 60 (threshold 15). Drivers by points: if/else 23 (43 pts), loops 3 (8 pts), match/switch 3 (7 pts), boolean chains 2 (nesting depth added 29). 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.
re_types_builder::codegen::rust::serializer::quote_arrow_serializer (cognitive 43) crates/build/re_types_builder/src/codegen/rust/serializer.rs:54— re_types_builder::codegen::rust::serializer::quote_arrow_serializer has cognitive complexity 43 (threshold 15). Drivers by points: if/else 23 (38 pts), match/switch 2 (4 pts), boolean chains 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.
re_types_builder::codegen::cpp::quote_fill_arrow_array_builder (cognitive 42) crates/build/re_types_builder/src/codegen/cpp/mod.rs:1823— re_types_builder::codegen::cpp::quote_fill_arrow_array_builder has cognitive complexity 42 (threshold 15). Drivers by points: if/else 17 (34 pts), match/switch 2 (8 pts) (nesting depth added 23). 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.
re_types_builder::codegen::common::remove_orphaned_files (cognitive 36) crates/build/re_types_builder/src/codegen/common.rs:444— re_types_builder::codegen::common::remove_orphaned_files has cognitive complexity 36 (threshold 15). Drivers by points: if/else 10 (33 pts), loops 2 (3 pts) (nesting depth added 24). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_types_builder::codegen::cpp::quote_append_field_to_builder (cognitive 34) crates/build/re_types_builder/src/codegen/cpp/mod.rs:2028— re_types_builder::codegen::cpp::quote_append_field_to_builder has cognitive complexity 34 (threshold 15). Drivers by points: if/else 16 (29 pts), match/switch 1 (3 pts), boolean chains 2 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_types_builder::codegen::rust::deserializer::quote_arrow_deserializer (cognitive 34) crates/build/re_types_builder/src/codegen/rust/deserializer.rs:61— re_types_builder::codegen::rust::deserializer::quote_arrow_deserializer has cognitive complexity 34 (threshold 15). Drivers by points: if/else 17 (29 pts), match/switch 2 (4 pts), boolean chains 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_types_builder::codegen::rust::util::string_from_quoted (cognitive 34) crates/build/re_types_builder/src/codegen/rust/util.rs:62— re_types_builder::codegen::rust::util::string_from_quoted has cognitive complexity 34 (threshold 15). Drivers by points: if/else 9 (28 pts), boolean chains 4, loops 1, match/switch 1 (nesting depth added 19). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
re_types_builder::codegen::rust::api::quote_from_impl_from_obj (cognitive 33) crates/build/re_types_builder/src/codegen/rust/api.rs:1324— re_types_builder::codegen::rust::api::quote_from_impl_from_obj has cognitive complexity 33 (threshold 15). Drivers by points: if/else 20 (33 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.
re_types_builder::codegen::docs::website::write_fields (cognitive 31) crates/build/re_types_builder/src/codegen/docs/website.rs:413— re_types_builder::codegen::docs::website::write_fields has cognitive complexity 31 (threshold 15). Drivers by points: if/else 12 (22 pts), loops 3 (5 pts), match/switch 2 (3 pts), boolean chains 1 (nesting depth added 13). Of this number, 30 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_types_builder::docs::doclink_translation::try_translate_doclink (cognitive 28) crates/build/re_types_builder/src/docs.rs:317— re_types_builder::docs::doclink_translation::try_translate_doclink has cognitive complexity 28 (threshold 15). Drivers by points: if/else 17 (24 pts), boolean chains 3, match/switch 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_types_builder::codegen::docs::snippets_ref::collect_snippets_recursively (cognitive 25) crates/build/re_types_builder/src/codegen/docs/snippets_ref.rs:370— re_types_builder::codegen::docs::snippets_ref::collect_snippets_recursively has cognitive complexity 25 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 6 (12 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.
re_types_builder::codegen::python::quote_field_converter_from_field (cognitive 25) crates/build/re_types_builder/src/codegen/python/mod.rs:1923— re_types_builder::codegen::python::quote_field_converter_from_field has cognitive complexity 25 (threshold 15). Drivers by points: if/else 14 (22 pts), boolean chains 2, match/switch 1 (nesting depth added 8). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
re_types_builder::codegen::python::quote_arrow_support_from_obj (cognitive 25) crates/build/re_types_builder/src/codegen/python/mod.rs:2171— re_types_builder::codegen::python::quote_arrow_support_from_obj has cognitive complexity 25 (threshold 15). Drivers by points: if/else 16 (21 pts), match/switch 3 (4 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.
re_types_builder::codegen::rust::deserializer::quote_arrow_field_deserializer (cognitive 24) crates/build/re_types_builder/src/codegen/rust/deserializer.rs:536— re_types_builder::codegen::rust::deserializer::quote_arrow_field_deserializer has cognitive complexity 24 (threshold 15). Drivers by points: if/else 12 (18 pts), match/switch 4 (6 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_types_builder::codegen::rust::util::doc_as_lines (cognitive 24) crates/build/re_types_builder/src/codegen/rust/util.rs:306— re_types_builder::codegen::rust::util::doc_as_lines has cognitive complexity 24 (threshold 15). Drivers by points: if/else 12 (21 pts), loops 1 (2 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.
re_types_builder::codegen::cpp::lines_from_docs (cognitive 23) crates/build/re_types_builder/src/codegen/cpp/mod.rs:2615— re_types_builder::codegen::cpp::lines_from_docs has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (14 pts), loops 2 (5 pts), match/switch 1 (4 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.
re_types_builder::codegen::rust::reflection::generate_component_reflection (cognitive 23) crates/build/re_types_builder/src/codegen/rust/reflection.rs:130— re_types_builder::codegen::rust::reflection::generate_component_reflection has cognitive complexity 23 (threshold 15). Drivers by points: if/else 12 (18 pts), boolean chains 4, 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.
re_types_builder::codegen::python::code_for_union (cognitive 20) crates/build/re_types_builder/src/codegen/python/mod.rs:1207— re_types_builder::codegen::python::code_for_union has cognitive complexity 20 (threshold 15). Drivers by points: if/else 19, match/switch 1. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
re_types_builder::codegen::docs::website::write_archetype_fields (cognitive 19) crates/build/re_types_builder/src/codegen/docs/website.rs:570— re_types_builder::codegen::docs::website::write_archetype_fields has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 4 (6 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.
re_types_builder::codegen::rust::util::replace_doc_attrb_with_doc_comment (cognitive 19) crates/build/re_types_builder/src/codegen/rust/util.rs:188— re_types_builder::codegen::rust::util::replace_doc_attrb_with_doc_comment has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (14 pts), loops 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.
re_types_builder::codegen::common::collect_snippets_for_api_docs (cognitive 18) crates/build/re_types_builder/src/codegen/common.rs:341— re_types_builder::codegen::common::collect_snippets_for_api_docs has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (9 pts), loops 3 (5 pts), boolean chains 2, match/switch 1 (2 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_types_builder::codegen::docs::website::index_page (cognitive 18) crates/build/re_types_builder/src/codegen/docs/website.rs:145— re_types_builder::codegen::docs::website::index_page has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (15 pts), loops 2 (3 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Duplicated block (11 lines × 2) crates/data_flow/re_importer/src/importer_rrd.rs:55— crates/data_flow/re_importer/src/importer_rrd.rs:55-65 | crates/data_flow/re_importer/src/importer_rrd.rs:85-95 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/data_flow/re_importer/src/importer_rrd.rs:55` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `crates/data_flow/re_importer/src/importer_rrd.rs:66` calls `clone` and `crates/data_flow/re_importer/src/importer_rrd.rs:96` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (11 lines × 2) crates/data_flow/re_lerobot/src/parse_v2.rs:245— crates/data_flow/re_lerobot/src/parse_v2.rs:245-255 | crates/data_flow/re_lerobot/src/parse_v3.rs:996-1006 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 2) crates/store/re_chunk_store/src/insert_rrd_manifest.rs:143— crates/store/re_chunk_store/src/insert_rrd_manifest.rs:143-153 | crates/store/re_chunk_store/src/insert_rrd_manifest.rs:165-175 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/store/re_chunk_store/src/insert_rrd_manifest.rs:143` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) crates/top/re_sdk/src/recording_stream.rs:1906— crates/top/re_sdk/src/recording_stream.rs:1906-1916 | crates/top/re_sdk/src/recording_stream.rs:1929-1939 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/top/re_sdk/src/recording_stream.rs:1906` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) crates/top/re_viewer/src/app/logic.rs:89— crates/top/re_viewer/src/app/logic.rs:89-99 | crates/top/re_viewer/src/app/mod.rs:1758-1768 — before extracting anything, compare `crates/top/re_viewer/src/app/logic.rs` and `crates/top/re_viewer/src/app/mod.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 46 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 (11 lines × 2) crates/top/rerun/src/commands/mcap/check.rs:49— crates/top/rerun/src/commands/mcap/check.rs:49-59 | crates/top/rerun/src/commands/mcap/info.rs:25-35 — 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 (11 lines × 2) crates/ui_tools/re_renderer/src/allocator/cpu_write_gpu_read_belt.rs:298— crates/ui_tools/re_renderer/src/allocator/cpu_write_gpu_read_belt.rs:298-308 | crates/ui_tools/re_renderer/src/allocator/cpu_write_gpu_read_belt.rs:341-351 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/ui_tools/re_renderer/src/allocator/cpu_write_gpu_read_belt.rs:298` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) crates/ui_tools/re_renderer/src/device_caps.rs:409— crates/ui_tools/re_renderer/src/device_caps.rs:409-419 | crates/ui_tools/re_renderer/src/device_caps.rs:476-486 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/ui_tools/re_renderer/src/device_caps.rs:409` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) crates/ui_tools/re_renderer/src/draw_phases/depth_resolve.rs:154— crates/ui_tools/re_renderer/src/draw_phases/depth_resolve.rs:154-164 | crates/ui_tools/re_renderer/src/draw_phases/picking_layer.rs:583-593 — 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/ui_tools/re_renderer/src/draw_phases/depth_resolve.rs:154` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) crates/ui_tools/re_renderer/src/draw_phases/outlines.rs:307— crates/ui_tools/re_renderer/src/draw_phases/outlines.rs:307-317 | crates/ui_tools/re_renderer/src/renderer/compositor.rs:190-202 — 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/ui_tools/re_renderer/src/draw_phases/outlines.rs:307` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (11 lines × 2) crates/ui_tools/re_renderer/src/renderer/lines.rs:747— crates/ui_tools/re_renderer/src/renderer/lines.rs:747-757 | crates/ui_tools/re_renderer/src/renderer/point_cloud.rs:804-814 — before extracting anything, compare `crates/ui_tools/re_renderer/src/renderer/lines.rs` and `crates/ui_tools/re_renderer/src/renderer/point_cloud.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 103 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/ui_tools/re_renderer/src/renderer/lines.rs:747` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) crates/viewer_support/re_data_ui/src/video_ui.rs:858— crates/viewer_support/re_data_ui/src/video_ui.rs:858-868 | crates/viewer_support/re_data_ui/src/video_ui.rs:890-900 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/viewer_support/re_data_ui/src/video_ui.rs:858` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (11 lines × 2) crates/viewer_support/re_view/src/blueprint_resolved_results.rs:149— crates/viewer_support/re_view/src/blueprint_resolved_results.rs:149-159 | crates/viewer_support/re_view/src/blueprint_resolved_results.rs:319-329 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/viewer_support/re_view/src/blueprint_resolved_results.rs:149` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) crates/viewer_support/re_viewer_context/src/image_info.rs:75— crates/viewer_support/re_viewer_context/src/image_info.rs:75-85 | crates/viewer_support/re_viewer_context/src/image_info.rs:114-124 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/viewer_support/re_viewer_context/src/image_info.rs:75` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) crates/views/re_view_time_series/src/aggregation.rs:46— crates/views/re_view_time_series/src/aggregation.rs:46-56 | crates/views/re_view_time_series/src/aggregation.rs:131-141 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/views/re_view_time_series/src/aggregation.rs:46` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) crates/views/re_view_time_series/src/series_query.rs:263— crates/views/re_view_time_series/src/series_query.rs:263-273 | crates/views/re_view_time_series/src/series_query.rs:407-417 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/views/re_view_time_series/src/series_query.rs:263` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) docs/snippets/all/archetypes/capsules3d_batch.rs:29— docs/snippets/all/archetypes/capsules3d_batch.rs:29-39 | docs/snippets/all/archetypes/cylinders3d_batch.rs:29-39 — 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 `docs/snippets/all/archetypes/capsules3d_batch.rs:29` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) docs/snippets/all/descriptors/descr_builtin_component.rs:62— docs/snippets/all/descriptors/descr_builtin_component.rs:62-72 | docs/snippets/all/descriptors/descr_custom_component.rs:57-67 — 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 `docs/snippets/all/descriptors/descr_builtin_component.rs:62` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) crates/viewer_support/re_dataframe_ui/src/datafusion_table_widget.rs:1112— crates/viewer_support/re_dataframe_ui/src/datafusion_table_widget.rs:1112-1122 | crates/viewer_support/re_dataframe_ui/src/datafusion_table_widget.rs:1126-1136 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/viewer_support/re_dataframe_ui/src/datafusion_table_widget.rs:1112` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) crates/views/re_view_spatial/src/visualizers/points2d.rs:296— crates/views/re_view_spatial/src/visualizers/points2d.rs:296-306 | crates/views/re_view_spatial/src/visualizers/points3d.rs:474-484 — before extracting anything, compare `crates/views/re_view_spatial/src/visualizers/points2d.rs` and `crates/views/re_view_spatial/src/visualizers/points3d.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 66 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 (11 lines × 2) crates/store_app/re_catalog_client/src/dataset.rs:54— crates/store_app/re_catalog_client/src/dataset.rs:54-65 | crates/store_app/re_catalog_client/src/segment.rs:161-171 — 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/store_app/re_catalog_client/src/dataset.rs:54` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) crates/store_app/re_server/src/rerun_cloud/mod.rs:608— crates/store_app/re_server/src/rerun_cloud/mod.rs:608-618 | crates/store_app/re_server/src/rerun_cloud/mod.rs:666-676 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/store_app/re_server/src/rerun_cloud/mod.rs:608` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (11 lines × 2) crates/store/re_sorbet/src/migrations/v0_1_1__to__v0_1_2.rs:112— crates/store/re_sorbet/src/migrations/v0_1_1__to__v0_1_2.rs:112-122 | crates/store/re_sorbet/src/migrations/v0_1_1__to__v0_1_2.rs:164-174 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/store/re_sorbet/src/migrations/v0_1_1__to__v0_1_2.rs:112` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) crates/data_flow/re_redap_client/src/connection_client/datasets.rs:230— crates/data_flow/re_redap_client/src/connection_client/datasets.rs:230-240 | crates/data_flow/re_redap_client/src/connection_client/datasets.rs:393-403 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/data_flow/re_redap_client/src/connection_client/datasets.rs:230` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) docs/snippets/all/archetypes/transform3d_hierarchy_frames.rs:26— docs/snippets/all/archetypes/transform3d_hierarchy_frames.rs:26-36 | docs/snippets/all/archetypes/transform3d_hierarchy_frames.rs:40-50 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `docs/snippets/all/archetypes/transform3d_hierarchy_frames.rs:26` 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.
ClassTooLong: RerunCloudHandler crates/store_app/re_server/src/rerun_cloud/mod.rs:274— ClassTooLong — 1272 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 9 methods, 5 blocks, lines 274-2308. The bar is 400 significant lines; this is 872 over it, 3.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: QueryHandle crates/store_app/re_dataframe/src/query.rs:242— ClassTooLong — 1122 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 30 methods, 4 blocks, lines 242-2522. The bar is 400 significant lines; this is 722 over it, 2.81× 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: TimePanel crates/panels/re_time_panel/src/time_panel.rs:101— ClassTooLong — 1060 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, 4 blocks, lines 101-2063. The bar is 400 significant lines; this is 660 over it, 2.65× 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: UiExt crates/ui_tools/re_ui/src/ui_ext.rs:43— ClassTooLong — 816 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 72 methods. The bar is 400 significant lines; this is 416 over it, 2.04× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: RawRrdManifest crates/store/re_chunk_index/src/raw_rrd_manifest.rs:145— ClassTooLong — 811 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 58 methods, 8 blocks, lines 145-1824. The bar is 400 significant lines; this is 411 over it, 2.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: BlueprintTree crates/panels/re_blueprint_tree/src/blueprint_tree.rs:27— ClassTooLong — 773 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 21 methods, 2 blocks, lines 27-1241. The bar is 400 significant lines; this is 373 over it, 1.93× 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: DataFusionTableWidget crates/viewer_support/re_dataframe_ui/src/datafusion_table_widget.rs:375— ClassTooLong — 748 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 22 methods, 2 blocks, lines 375-1446. The bar is 400 significant lines; this is 348 over it, 1.87× 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: EntityDb crates/store_app/re_entity_db/src/entity_db.rs:127— ClassTooLong — 731 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 75 methods, 6 blocks, lines 127-1444. The bar is 400 significant lines; this is 331 over it, 1.83× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Chunk crates/store/re_chunk/src/chunk.rs:242— ClassTooLong — 718 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 122 methods, 13 blocks, lines 242-1962. The bar is 400 significant lines; this is 318 over it, 1.80× 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: AppCore crates/top/re_viewer/src/app/mod.rs:197— ClassTooLong — 683 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 139 methods, 3 blocks, lines 197-1938. The bar is 400 significant lines; this is 283 over it, 1.71× 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: DesignTokens crates/ui_tools/re_ui/src/design_tokens.rs:262— ClassTooLong — 655 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 52 methods, 2 blocks, lines 262-1402. The bar is 400 significant lines; this is 255 over it, 1.64× 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: RecordingStream crates/top/re_sdk/src/recording_stream.rs:783— ClassTooLong — 651 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 74 methods, 10 blocks, lines 783-2979. The bar is 400 significant lines; this is 251 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: PyDatasetEntryInternal rerun_py/src/catalog/dataset_entry.rs:44— ClassTooLong — 644 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 45 methods, 4 blocks, lines 44-1140. The bar is 400 significant lines; this is 244 over it, 1.61× 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: WebViewer rerun_js/web-viewer/index.ts:1615— ClassTooLong — 617 significant lines (blank, comment-only and punctuation-only lines excluded), 83 methods. The bar is 400 significant lines; this is 217 over it, 1.54× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: AgentSession crates/utils/re_agent/src/session.rs:302— ClassTooLong — 598 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 51 methods, 3 blocks, lines 302-1270. The bar is 400 significant lines; this is 198 over it, 1.50× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: TimeSeriesView crates/views/re_view_time_series/src/view_class.rs:126— ClassTooLong — 565 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 0 methods. The bar is 400 significant lines; this is 165 over it, 1.41× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: ComponentUiRegistry crates/viewer_support/re_viewer_context/src/component_ui_registry.rs:116— ClassTooLong — 552 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 22 methods, 2 blocks, lines 116-1002. The bar is 400 significant lines; this is 152 over it, 1.38× 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: RedapServers crates/panels/re_redap_browser/src/servers/mod.rs:607— ClassTooLong — 540 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 25 methods, 5 blocks, lines 607-1591. The bar is 400 significant lines; this is 140 over it, 1.35× 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: ViewportBlueprint crates/viewer_support/re_viewport_blueprint/src/viewport_blueprint.rs:36— ClassTooLong — 508 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 39 methods, 2 blocks, lines 36-960. The bar is 400 significant lines; this is 108 over it, 1.27× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: DatastoreUi crates/panels/re_chunk_store_ui/src/chunk_store_ui.rs:117— ClassTooLong — 484 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 10 methods, 3 blocks, lines 117-866. The bar is 400 significant lines; this is 84 over it, 1.21× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: DataframeQueryTableProvider crates/store_app/re_datafusion/src/dataframe_query_common/mod.rs:129— ClassTooLong — 483 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 10 methods, 4 blocks, lines 129-1155. The bar is 400 significant lines; this is 83 over it, 1.21× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: ViewerUrl crates/viewer_support/re_viewer_context/src/viewer_url.rs:51— ClassTooLong — 482 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, 6 blocks, lines 51-920. The bar is 400 significant lines; this is 82 over it, 1.21× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: InMemoryStore crates/store_app/re_server/src/store/in_memory_store.rs:39— ClassTooLong — 465 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 32 methods, 4 blocks, lines 39-746. The bar is 400 significant lines; this is 65 over it, 1.16× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: StoreHub crates/viewer_support/re_viewer_context/src/store_hub/mod.rs:126— ClassTooLong — 462 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 78 methods, 3 blocks, lines 126-1040. The bar is 400 significant lines; this is 62 over it, 1.16× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: RrdManifest crates/store/re_chunk_index/src/rrd_manifest.rs:58— ClassTooLong — 451 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 32 methods, 6 blocks, lines 58-846. The bar is 400 significant lines; this is 51 over it, 1.13× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: AppCore crates/top/re_viewer/src/app/mod.rs:197— TooManyMethods — 139 methods, declared across 14 files: app/mod.rs (41), viewer_control/mod.rs (33), app/command_handling.rs (20), app/logic.rs (17), +10 more file(s). The bar is 30 methods; this is 109 over it, 4.63× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ChunkStore crates/store/re_chunk_store/src/store.rs:527— TooManyMethods — 126 methods, declared across 15 files: src/query.rs (36), src/store.rs (31), src/lineage.rs (12), src/subscribers.rs (11), +11 more file(s). The bar is 30 methods; this is 96 over it, 4.20× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Chunk crates/store/re_chunk/src/chunk.rs:242— TooManyMethods — 122 methods, declared across 13 files: src/chunk.rs (51), src/slice.rs (18), src/iter.rs (10), src/shuffle.rs (10), +9 more file(s). The bar is 30 methods; this is 92 over it, 4.07× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: WebViewer rerun_js/web-viewer/index.ts:1615— TooManyMethods — 83 methods. The bar is 30 methods; this is 53 over it, 2.77× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: StoreHub crates/viewer_support/re_viewer_context/src/store_hub/mod.rs:126— TooManyMethods — 78 methods, declared across 3 files: store_hub/mod.rs (41), store_hub/blueprint_persistence.rs (19), store_hub/blueprints.rs (18). The bar is 30 methods; this is 48 over it, 2.60× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: CatalogClient crates/store_app/re_catalog_client/src/lib.rs:47— TooManyMethods — 77 methods, declared across 13 files: src/blueprint.rs (14), src/asset.rs (10), src/write.rs (10), src/entry.rs (8), +9 more file(s). The bar is 30 methods; this is 47 over it, 2.57× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: EntityDb crates/store_app/re_entity_db/src/entity_db.rs:127— TooManyMethods — 75 methods. The bar is 30 methods; this is 45 over it, 2.50× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: RecordingStream crates/top/re_sdk/src/recording_stream.rs:783— TooManyMethods — 74 methods, declared across 2 files: src/recording_stream.rs (63), src/global.rs (11). The bar is 30 methods; this is 44 over it, 2.47× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: RedapClient crates/data_flow/re_redap_client/src/connection_client/mod.rs:42— TooManyMethods — 62 methods, declared across 14 files: connection_client/datasets.rs (11), connection_client/segments_schema.rs (6), connection_client/server_info.rs (6), connection_client/tables.rs (6), +10 more file(s). The bar is 30 methods; this is 32 over it, 2.07× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: RawRrdManifest crates/store/re_chunk_index/src/raw_rrd_manifest.rs:145— TooManyMethods — 58 methods. The bar is 30 methods; this is 28 over it, 1.93× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: DesignTokens crates/ui_tools/re_ui/src/design_tokens.rs:262— TooManyMethods — 52 methods. The bar is 30 methods; this is 22 over it, 1.73× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: AgentSession crates/utils/re_agent/src/session.rs:302— TooManyMethods — 51 methods. The bar is 30 methods; this is 21 over it, 1.70× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: DatasetEntry rerun_py/rerun_sdk/rerun/catalog/_entry.py:268— TooManyMethods — 49 methods. The bar is 30 methods; this is 19 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.
TooManyMethods: TimeControl crates/viewer_support/re_viewer_context/src/time_control/mod.rs:183— TooManyMethods — 46 methods, declared across 2 files: time_control/mod.rs (36), time_control/command.rs (10). The bar is 30 methods; this is 16 over it, 1.53× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: PyDatasetEntryInternal rerun_py/src/catalog/dataset_entry.rs:44— TooManyMethods — 45 methods. The bar is 30 methods; this is 15 over it, 1.50× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: AgentPanel crates/ui_tools/re_agent_ui/src/ui/agent_panel.rs:167— TooManyMethods — 44 methods. The bar is 30 methods; this is 14 over it, 1.47× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ViewerClient rerun_py/rerun_sdk/rerun/experimental/_viewer_client.py:633— TooManyMethods — 40 methods. The bar is 30 methods; this is 10 over it, 1.33× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ViewportBlueprint crates/viewer_support/re_viewport_blueprint/src/viewport_blueprint.rs:36— TooManyMethods — 39 methods. The bar is 30 methods; this is 9 over it, 1.30× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: _ValueFilters rerun_py/rerun_sdk/rerun/blueprint/_table_filters.py:106— TooManyMethods — 37 methods. The bar is 30 methods; this is 7 over it, 1.23× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: RecordingStream rerun_py/rerun_sdk/rerun/recording_stream.py:153— TooManyMethods — 37 methods. The bar is 30 methods; this is 7 over it, 1.23× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ViewerContext crates/viewer_support/re_viewer_context/src/viewer_context.rs:22— TooManyMethods — 37 methods, declared across 2 files: src/viewer_context.rs (36), src/query_context.rs (1). The bar is 30 methods; this is 7 over it, 1.23× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: TimeColumn crates/store/re_chunk/src/chunk.rs:913— TooManyMethods — 32 methods, declared across 5 files: src/chunk.rs (23), src/slice.rs (5), src/shuffle.rs (2), src/builder.rs (1), +1 more file(s). The bar is 30 methods; this is 2 over it, 1.07× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: RrdManifest crates/store/re_chunk_index/src/rrd_manifest.rs:58— TooManyMethods — 32 methods. The bar is 30 methods; this is 2 over it, 1.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: RrdManifestIndex crates/store_app/re_entity_db/src/rrd_manifest_index/mod.rs:130— TooManyMethods — 32 methods. The bar is 30 methods; this is 2 over it, 1.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: InMemoryStore crates/store_app/re_server/src/store/in_memory_store.rs:39— TooManyMethods — 32 methods. The bar is 30 methods; this is 2 over it, 1.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Duplicated block (10 lines × 2) crates/data_flow/re_data_source/src/data_source.rs:148— crates/data_flow/re_data_source/src/data_source.rs:148-157 | crates/data_flow/re_data_source/src/data_source.rs:202-211 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/data_flow/re_data_source/src/data_source.rs:148` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) crates/data_flow/re_redap_client/src/connection_client/rrd_manifest.rs:93— crates/data_flow/re_redap_client/src/connection_client/rrd_manifest.rs:93-102 | crates/store_app/re_catalog_client/src/staging/mod.rs:192-201 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (10 lines × 2) crates/panels/re_blueprint_tree/src/data.rs:422— crates/panels/re_blueprint_tree/src/data.rs:422-431 | crates/panels/re_blueprint_tree/src/data.rs:446-456 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/panels/re_blueprint_tree/src/data.rs:422` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (10 lines × 2) crates/store/re_chunk/src/unit_chunk.rs:85— crates/store/re_chunk/src/unit_chunk.rs:85-94 | crates/store/re_chunk/src/unit_chunk.rs:380-389 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/store/re_chunk/src/unit_chunk.rs:85` 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/store/re_chunk/src/unit_chunk.rs:139— crates/store/re_chunk/src/unit_chunk.rs:139-148 | crates/store/re_chunk/src/unit_chunk.rs:425-434 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/store/re_chunk/src/unit_chunk.rs:139` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) crates/store/re_chunk_index/src/raw_rrd_manifest.rs:461— crates/store/re_chunk_index/src/raw_rrd_manifest.rs:461-470 | crates/store/re_chunk_index/src/raw_rrd_manifest.rs:911-920 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/store/re_chunk_index/src/raw_rrd_manifest.rs:461` 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/store/re_chunk_store/src/events.rs:52— crates/store/re_chunk_store/src/events.rs:52-61 | crates/store/re_chunk_store/src/events.rs:402-411 — both copies are in the same file, so extract the 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/store_app/re_datafusion/src/table_entry_provider.rs:211— crates/store_app/re_datafusion/src/table_entry_provider.rs:211-220 | crates/store_app/re_datafusion/src/table_entry_provider.rs:258-267 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/store_app/re_datafusion/src/table_entry_provider.rs:211` 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/store_app/re_tf/src/transform_resolution_cache/cache.rs:314— crates/store_app/re_tf/src/transform_resolution_cache/cache.rs:314-323 | crates/store_app/re_tf/src/transform_resolution_cache/cache.rs:379-390 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/store_app/re_tf/src/transform_resolution_cache/cache.rs:314` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) crates/store_app/re_tf/src/transform_resolution_cache/cached_transforms_for_timeline.rs:179— crates/store_app/re_tf/src/transform_resolution_cache/cached_transforms_for_timeline.rs:179-188 | crates/store_app/re_tf/src/transform_resolution_cache/cached_transforms_for_timeline.rs:214-223 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/store_app/re_tf/src/transform_resolution_cache/cached_transforms_for_timeline.rs:179` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) crates/top/rerun/src/commands/entrypoint.rs:1719— crates/top/rerun/src/commands/entrypoint.rs:1719-1728 | crates/top/rerun/src/commands/entrypoint.rs:1734-1743 — both copies are in the same file, so extract the 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/top/rerun/src/demo_util.rs:119— crates/top/rerun/src/demo_util.rs:119-128 | crates/ui_tools/re_renderer/src/colormap.rs:251-260 — 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/top/rerun/src/demo_util.rs:119` 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/ui_tools/re_renderer/src/renderer/volume.rs:311— crates/ui_tools/re_renderer/src/renderer/volume.rs:311-320 | crates/ui_tools/re_renderer/src/renderer/voxel_grid.rs:389-398 — before extracting anything, compare `crates/ui_tools/re_renderer/src/renderer/volume.rs` and `crates/ui_tools/re_renderer/src/renderer/voxel_grid.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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/ui_tools/re_renderer/src/renderer/volume.rs:311` 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/viewer_support/re_context_menu/src/actions/show_hide.rs:18— crates/viewer_support/re_context_menu/src/actions/show_hide.rs:18-27 | crates/viewer_support/re_context_menu/src/actions/show_hide.rs:77-87 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/viewer_support/re_context_menu/src/actions/show_hide.rs:18` 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/viewer_support/re_view/src/blueprint_resolved_results.rs:132— crates/viewer_support/re_view/src/blueprint_resolved_results.rs:132-141 | crates/viewer_support/re_view/src/blueprint_resolved_results.rs:302-311 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/viewer_support/re_view/src/blueprint_resolved_results.rs:132` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) crates/views/re_view_time_series/src/line_visualizer_system.rs:121— crates/views/re_view_time_series/src/line_visualizer_system.rs:121-130 | crates/views/re_view_time_series/src/point_visualizer_system.rs:117-126 — before extracting anything, compare `crates/views/re_view_time_series/src/line_visualizer_system.rs` and `crates/views/re_view_time_series/src/point_visualizer_system.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 73 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) docs/snippets/all/archetypes/graph_directed.rs:6— docs/snippets/all/archetypes/graph_directed.rs:6-15 | docs/snippets/all/archetypes/graph_undirected.rs:6-15 — 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 `docs/snippets/all/archetypes/graph_directed.rs:6` 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) rerun_py/src/catalog/dataset_entry.rs:266— rerun_py/src/catalog/dataset_entry.rs:266-275 | rerun_py/src/catalog/dataset_entry.rs:281-290 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `rerun_py/src/catalog/dataset_entry.rs:266` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) rerun_py/src/python_bridge.rs:1587— rerun_py/src/python_bridge.rs:1587-1596 | rerun_py/src/python_bridge.rs:1618-1627 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `rerun_py/src/python_bridge.rs:1587` 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/store/re_log_types/src/example_components.rs:211— crates/store/re_log_types/src/example_components.rs:211-220 | crates/store/re_log_types/src/example_components.rs:316-325 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/store/re_log_types/src/example_components.rs:211` 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/viewer_support/re_viewport_blueprint/src/container.rs:364— crates/viewer_support/re_viewport_blueprint/src/container.rs:364-373 | crates/viewer_support/re_viewport_blueprint/src/view.rs:387-396 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (10 lines × 2) crates/top/re_viewer/src/ui/share_modal.rs:280— crates/top/re_viewer/src/ui/share_modal.rs:280-289 | crates/top/re_viewer/src/ui/share_modal.rs:309-318 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/top/re_viewer/src/ui/share_modal.rs:280` it does not close everything it opens, so those exact lines 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/utils/re_video/src/decode/av1.rs:266— crates/utils/re_video/src/decode/av1.rs:266-275 | crates/utils/re_video/src/decode/av1.rs:279-288 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/utils/re_video/src/decode/av1.rs:266` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) rerun_py/src/catalog/dataset_entry.rs:776— rerun_py/src/catalog/dataset_entry.rs:776-785 | rerun_py/src/catalog/dataset_entry.rs:823-832 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `rerun_py/src/catalog/dataset_entry.rs:776` it does not close everything it opens, so those 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, `rerun_py/src/catalog/dataset_entry.rs:786` calls `from` and `rerun_py/src/catalog/dataset_entry.rs:833` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10 lines × 2) examples/python/detect_and_track_objects/detect_and_track_objects.py:443— examples/python/detect_and_track_objects/detect_and_track_objects.py:443-452 | examples/python/human_pose_tracking/human_pose_tracking.py:165-174 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) crates/data_flow/re_importer/src/importer_parquet.rs:47— crates/data_flow/re_importer/src/importer_parquet.rs:47-54 | crates/data_flow/re_importer/src/importer_parquet.rs:81-88 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/data_flow/re_importer/src/importer_parquet.rs:47` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) crates/panels/re_redap_browser/src/source_field.rs:386— crates/panels/re_redap_browser/src/source_field.rs:386-393 | crates/ui_tools/re_ui/src/filter_widget.rs:231-238 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) crates/store/re_chunk/src/chunk.rs:1254— crates/store/re_chunk/src/chunk.rs:1254-1261 | crates/store/re_chunk/src/chunk.rs:1280-1287 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/store/re_chunk/src/chunk.rs:1254` it does not close everything it opens, so those exact lines 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/store/re_log_types/src/example_components.rs:197— crates/store/re_log_types/src/example_components.rs:197-204 | crates/store/re_log_types/src/example_components.rs:302-309 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) crates/store/re_sorbet/src/migrations/v0_0_1__to__v0_0_2.rs:90— crates/store/re_sorbet/src/migrations/v0_0_1__to__v0_0_2.rs:90-97 | crates/store/re_sorbet/src/migrations/v0_0_1__to__v0_0_2.rs:215-222 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/store/re_sorbet/src/migrations/v0_0_1__to__v0_0_2.rs:90` 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/viewer_support/re_data_ui/src/item_ui.rs:424— crates/viewer_support/re_data_ui/src/item_ui.rs:424-431 | crates/viewer_support/re_data_ui/src/item_ui.rs:440-447 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/viewer_support/re_data_ui/src/item_ui.rs:424` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) crates/viewer_support/re_view/src/query.rs:306— crates/viewer_support/re_view/src/query.rs:306-313 | crates/viewer_support/re_view/src/query.rs:491-498 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) crates/viewer_support/re_viewer_context/src/tensor/image_stats.rs:46— crates/viewer_support/re_viewer_context/src/tensor/image_stats.rs:46-53 | crates/viewer_support/re_viewer_context/src/tensor/tensor_stats.rs:42-49 — before extracting anything, compare `crates/viewer_support/re_viewer_context/src/tensor/image_stats.rs` and `crates/viewer_support/re_viewer_context/src/tensor/tensor_stats.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 31 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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/viewer_support/re_viewer_context/src/tensor/image_stats.rs:46` 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/views/re_view_spatial/src/picking_ui_pixel.rs:250— crates/views/re_view_spatial/src/picking_ui_pixel.rs:250-257 | crates/views/re_view_spatial/src/picking_ui_pixel.rs:304-311 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/views/re_view_spatial/src/picking_ui_pixel.rs:250` it does not close everything it opens, so those exact lines 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/views/re_view_time_series/src/series_query.rs:277— crates/views/re_view_time_series/src/series_query.rs:277-284 | crates/views/re_view_time_series/src/series_query.rs:421-428 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/views/re_view_time_series/src/series_query.rs:277` 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) docs/snippets/all/archetypes/mesh3d_indexed.rs:6— docs/snippets/all/archetypes/mesh3d_indexed.rs:6-15 | docs/snippets/all/archetypes/mesh3d_simple.rs:7-14 — 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 `docs/snippets/all/archetypes/mesh3d_indexed.rs:6` 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) docs/snippets/all/archetypes/transform3d_hierarchy.rs:20— docs/snippets/all/archetypes/transform3d_hierarchy.rs:20-27 | docs/snippets/all/archetypes/transform3d_hierarchy.rs:30-37 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `docs/snippets/all/archetypes/transform3d_hierarchy.rs:20` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (8 lines × 2) crates/viewer_support/re_component_ui/src/line_strip.rs:54— crates/viewer_support/re_component_ui/src/line_strip.rs:54-61 | crates/viewer_support/re_component_ui/src/line_strip.rs:116-123 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/viewer_support/re_component_ui/src/line_strip.rs:54` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `value` to `&mut MaybeMutRef<'_, LineStrip3D>` in one and `&mut MaybeMutRef<'_, LineStrip2D>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `crates/viewer_support/re_component_ui/src/line_strip.rs:62` calls `col`, `label`, `format_f32` and `crates/viewer_support/re_component_ui/src/line_strip.rs:124` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 2) crates/data_flow/re_hdf5/src/config.rs:105— crates/data_flow/re_hdf5/src/config.rs:105-112 | crates/data_flow/re_parquet/src/config.rs:133-140 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) crates/viewer_support/re_context_menu/src/actions/add_container.rs:29— crates/viewer_support/re_context_menu/src/actions/add_container.rs:29-36 | crates/viewer_support/re_context_menu/src/actions/move_contents_to_new_container.rs:41-48 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (8 lines × 2) crates/store/re_uri/src/fragment.rs:135— crates/store/re_uri/src/fragment.rs:135-144 | crates/viewer_support/re_viewer_context/src/command_sender.rs:356-363 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) crates/ui_tools/re_renderer/src/gaussian_splat_builder.rs:85— crates/ui_tools/re_renderer/src/gaussian_splat_builder.rs:85-92 | crates/ui_tools/re_renderer/src/line_drawable_builder.rs:81-88 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (8 lines × 2) crates/viewer_support/re_viewer_context/src/command/recording_command.rs:98— crates/viewer_support/re_viewer_context/src/command/recording_command.rs:98-105 | crates/viewer_support/re_viewer_context/src/command/redap_server_command.rs:48-55 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (8 lines × 2) crates/views/re_view_spatial/src/view_2d.rs:270— crates/views/re_view_spatial/src/view_2d.rs:270-277 | crates/views/re_view_spatial/src/view_3d.rs:536-543 — 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/views/re_view_spatial/src/view_2d.rs:270` 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/views/re_view_spatial/src/visualizers/gaussian_splats3d.rs:199— crates/views/re_view_spatial/src/visualizers/gaussian_splats3d.rs:199-209 | crates/views/re_view_spatial/src/visualizers/points3d.rs:163-170 — before extracting anything, compare `crates/views/re_view_spatial/src/visualizers/gaussian_splats3d.rs` and `crates/views/re_view_spatial/src/visualizers/points3d.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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/views/re_view_spatial/src/visualizers/gaussian_splats3d.rs:199` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `compute` to `impl FnOnce() -> GaussianSplats3DCpu` in one and `impl FnOnce() -> Points3DCpu` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (8 lines × 2) docs/snippets/all/concepts/transform3d_hierarchy_simple.rs:10— docs/snippets/all/concepts/transform3d_hierarchy_simple.rs:10-17 | docs/snippets/all/concepts/transform3d_hierarchy_simple.rs:24-32 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `docs/snippets/all/concepts/transform3d_hierarchy_simple.rs:10` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) crates/store_app/re_datafusion/src/dataframe_query_provider/fetch_plan.rs:246— crates/store_app/re_datafusion/src/dataframe_query_provider/fetch_plan.rs:246-253 | crates/store_app/re_datafusion/src/dataframe_query_provider/fetch_plan.rs:291-298 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/store_app/re_datafusion/src/dataframe_query_provider/fetch_plan.rs:246` it does not close everything it opens, so those exact lines 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/ui_tools/re_renderer/src/view_builder.rs:465— crates/ui_tools/re_renderer/src/view_builder.rs:465-472 | crates/ui_tools/re_renderer/src/view_builder.rs:505-512 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/ui_tools/re_renderer/src/view_builder.rs:465` it does not close everything it opens, so those exact lines 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) scripts/zombie_todos.py:439— scripts/zombie_todos.py:439-446 | scripts/zombie_todos.py:460-467 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (8 lines × 2) scripts/ci/compare.py:53— scripts/ci/compare.py:53-60 | scripts/ci/count_bytes.py:58-65 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (6 lines × 2) crates/store_app/re_server/src/rerun_cloud/chunk_selection.rs:232— crates/store_app/re_server/src/rerun_cloud/chunk_selection.rs:232-237 | crates/store_app/re_server/src/store/dataset.rs:422-427 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) crates/store_app/re_server/src/store/dataset.rs:326— crates/store_app/re_server/src/store/dataset.rs:326-331 | crates/store_app/re_server/src/store/dataset.rs:431-436 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) crates/top/re_viewer/src/app/viewer_control/mod.rs:1721— crates/top/re_viewer/src/app/viewer_control/mod.rs:1721-1726 | crates/top/re_viewer/src/app/viewer_control/transform_graph.rs:63-68 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `crates/top/re_viewer/src/app/viewer_control/mod.rs:1721` 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/utils/re_analytics/src/native/pipeline.rs:74— crates/utils/re_analytics/src/native/pipeline.rs:74-80 | crates/utils/re_analytics/src/native/pipeline.rs:92-97 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/utils/re_analytics/src/native/pipeline.rs:74` 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/viewer_support/re_viewer_context/src/command/redap_server_command.rs:86— crates/viewer_support/re_viewer_context/src/command/redap_server_command.rs:86-91 | crates/viewer_support/re_viewer_context/src/command/table_command.rs:44-49 — 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/viewer_support/re_viewer_context/src/command/redap_server_command.rs:86` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) crates/views/re_view_spatial/src/ui_2d.rs:274— crates/views/re_view_spatial/src/ui_2d.rs:274-279 | crates/views/re_view_spatial/src/ui_3d.rs:420-425 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `crates/views/re_view_spatial/src/ui_2d.rs:273` calls `view_context` and `crates/views/re_view_spatial/src/ui_3d.rs:418` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6 lines × 2) crates/views/re_view_time_series/src/point_visualizer_system.rs:393— crates/views/re_view_time_series/src/point_visualizer_system.rs:393-400 | crates/views/re_view_time_series/src/series_query.rs:412-417 — 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/views/re_view_time_series/src/point_visualizer_system.rs:393` 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 (6 lines × 2) docs/snippets/all/archetypes/points2d_random.rs:20— docs/snippets/all/archetypes/points2d_random.rs:20-27 | docs/snippets/all/archetypes/points3d_random.rs:22-27 — 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 `docs/snippets/all/archetypes/points2d_random.rs:20` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) crates/data_flow/re_lenses/src/semantic/helpers.rs:35— crates/data_flow/re_lenses/src/semantic/helpers.rs:35-40 | crates/data_flow/re_lenses/src/semantic/helpers.rs:47-52 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) crates/data_flow/re_lerobot/src/parse_v2.rs:199— crates/data_flow/re_lerobot/src/parse_v2.rs:199-204 | crates/data_flow/re_lerobot/src/parse_v3.rs:960-965 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (6 lines × 2) crates/store/re_chunk_store/src/query.rs:74— crates/store/re_chunk_store/src/query.rs:74-79 | crates/store/re_chunk_store/src/query.rs:101-106 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/store/re_chunk_store/src/query.rs:74` 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/store/re_lenses_core/src/combinators/reshape.rs:294— crates/store/re_lenses_core/src/combinators/reshape.rs:294-299 | crates/store/re_lenses_core/src/combinators/reshape.rs:307-312 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) crates/top/rerun/src/commands/rrd/filter.rs:75— crates/top/rerun/src/commands/rrd/filter.rs:75-80 | crates/top/rerun/src/commands/rrd/merge_optimize.rs:507-512 — 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/top/rerun/src/commands/rrd/filter.rs:75` 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 (6 lines × 2) rerun_py/src/selector.rs:75— rerun_py/src/selector.rs:75-80 | rerun_py/src/selector.rs:96-101 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `rerun_py/src/selector.rs:75` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) crates/data_flow/re_hdf5/src/config.rs:85— crates/data_flow/re_hdf5/src/config.rs:85-90 | crates/data_flow/re_parquet/src/config.rs:113-118 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) crates/store/re_sorbet/src/column_descriptor.rs:60— crates/store/re_sorbet/src/column_descriptor.rs:60-65 | crates/store/re_sorbet/src/column_descriptor_ref.rs:49-54 — 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/viewer_support/re_viewport_blueprint/src/container.rs:333— crates/viewer_support/re_viewport_blueprint/src/container.rs:333-338 | crates/viewer_support/re_viewport_blueprint/src/view.rs:153-158 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (6 lines × 2) crates/viewer_support/re_component_ui/src/encoding_uis/view_uuid.rs:9— crates/viewer_support/re_component_ui/src/encoding_uis/view_uuid.rs:9-14 | crates/viewer_support/re_component_ui/src/image_format.rs:9-15 — 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/viewer_support/re_component_ui/src/encoding_uis/view_uuid.rs:9` 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/viewer_support/re_context_menu/src/actions/lock_unlock.rs:23— crates/viewer_support/re_context_menu/src/actions/lock_unlock.rs:23-28 | crates/viewer_support/re_context_menu/src/visibility_actions.rs:27-32 — 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/viewer_support/re_context_menu/src/actions/lock_unlock.rs:23` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `ctx` to `&re_viewer_context::ViewerContext<'_>` in one and `&ViewerContext<'_>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (6 lines × 2) crates/ui_tools/re_renderer/src/view_builder.rs:782— crates/ui_tools/re_renderer/src/view_builder.rs:782-787 | crates/ui_tools/re_renderer/src/view_builder.rs:856-861 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/ui_tools/re_renderer/src/view_builder.rs:782` it does not close everything it opens, so those exact lines 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) docs/snippets/all/archetypes/transform3d_hierarchy.rs:48— docs/snippets/all/archetypes/transform3d_hierarchy.rs:48-53 | docs/snippets/all/archetypes/transform3d_hierarchy_frames.rs:62-67 — 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 `docs/snippets/all/archetypes/transform3d_hierarchy.rs:48` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) scripts/ci/python_check_signatures.py:132— scripts/ci/python_check_signatures.py:132-137 | scripts/ci/python_check_signatures.py:162-167 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) examples/python/structure_from_motion/structure_from_motion/read_write_model.py:331— examples/python/structure_from_motion/structure_from_motion/read_write_model.py:331-336 | examples/python/structure_from_motion/structure_from_motion/read_write_model.py:356-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. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (6 lines × 2) scripts/ci/upload_docs.py:293— scripts/ci/upload_docs.py:293-298 | scripts/ci/upload_docs.py:396-401 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) crates/store/re_sdk_types/src/archetypes/points2d_ext.rs:78— crates/store/re_sdk_types/src/archetypes/points2d_ext.rs:78-82 | crates/store/re_sdk_types/src/archetypes/points3d_ext.rs:88-92 — before extracting anything, compare `crates/store/re_sdk_types/src/archetypes/points2d_ext.rs` and `crates/store/re_sdk_types/src/archetypes/points3d_ext.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 65 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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/store/re_sdk_types/src/archetypes/points3d_ext.rs:86` calls `unwrap_or` and `crates/store/re_sdk_types/src/archetypes/points2d_ext.rs:76` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (5 lines × 2) crates/store_app/re_server/src/rerun_cloud/mod.rs:112— crates/store_app/re_server/src/rerun_cloud/mod.rs:112-116 | crates/store_app/re_server/src/rerun_cloud/mod.rs:136-140 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/store_app/re_server/src/rerun_cloud/mod.rs:112` 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/top/re_viewer/data/quick_start_guides/quick_start_connect.rs:7— crates/top/re_viewer/data/quick_start_guides/quick_start_connect.rs:7-11 | docs/snippets/all/quick_start/quick_start_connect.rs:7-12 — before extracting anything, compare `crates/top/re_viewer/data/quick_start_guides/quick_start_connect.rs` and `docs/snippets/all/quick_start/quick_start_connect.rs` as WHOLE FILES: 94% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) crates/viewer_support/re_viewer_context/src/cache/video_stream_cache/mod.rs:1106— crates/viewer_support/re_viewer_context/src/cache/video_stream_cache/mod.rs:1106-1112 | crates/viewer_support/re_viewer_context/src/cache/video_stream_cache/mod.rs:1439-1443 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (5 lines × 2) crates/views/re_view_spatial/src/proc_mesh.rs:324— crates/views/re_view_spatial/src/proc_mesh.rs:324-328 | crates/views/re_view_spatial/src/proc_mesh.rs:336-340 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/views/re_view_spatial/src/proc_mesh.rs:324` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) crates/views/re_view_spatial/src/visualizers/gaussian_splats3d.rs:454— crates/views/re_view_spatial/src/visualizers/gaussian_splats3d.rs:454-459 | crates/views/re_view_spatial/src/visualizers/points3d.rs:472-476 — before extracting anything, compare `crates/views/re_view_spatial/src/visualizers/gaussian_splats3d.rs` and `crates/views/re_view_spatial/src/visualizers/points3d.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (5 lines × 2) crates/views/re_view_spatial/src/visualizers/lines2d.rs:223— crates/views/re_view_spatial/src/visualizers/lines2d.rs:223-227 | crates/views/re_view_spatial/src/visualizers/lines3d.rs:234-238 — before extracting anything, compare `crates/views/re_view_spatial/src/visualizers/lines2d.rs` and `crates/views/re_view_spatial/src/visualizers/lines3d.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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/views/re_view_spatial/src/visualizers/lines2d.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.
Duplicated block (5 lines × 2) docs/snippets/all/tutorials/dna.rs:62— docs/snippets/all/tutorials/dna.rs:62-66 | docs/snippets/all/tutorials/dna.rs:86-90 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) rerun_py/src/catalog/dataframe_rendering.rs:140— rerun_py/src/catalog/dataframe_rendering.rs:140-144 | rerun_py/src/catalog/dataframe_rendering.rs:179-183 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `rerun_py/src/catalog/dataframe_rendering.rs:140` 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/store/re_sdk_types/src/archetypes/points2d_ext.rs:113— crates/store/re_sdk_types/src/archetypes/points2d_ext.rs:113-117 | crates/store/re_sdk_types/src/archetypes/points3d_ext.rs:125-129 — before extracting anything, compare `crates/store/re_sdk_types/src/archetypes/points2d_ext.rs` and `crates/store/re_sdk_types/src/archetypes/points3d_ext.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 65 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) crates/ui_tools/re_ui/src/list_item/label_content.rs:107— crates/ui_tools/re_ui/src/list_item/label_content.rs:107-111 | crates/ui_tools/re_ui/src/list_item/property_content.rs:64-68 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) crates/views/re_view_spatial/src/visualizers/gaussian_splats3d.rs:172— crates/views/re_view_spatial/src/visualizers/gaussian_splats3d.rs:172-176 | crates/views/re_view_spatial/src/visualizers/points3d.rs:141-145 — before extracting anything, compare `crates/views/re_view_spatial/src/visualizers/gaussian_splats3d.rs` and `crates/views/re_view_spatial/src/visualizers/points3d.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) crates/top/rerun/src/commands/rrd/stats.rs:245— crates/top/rerun/src/commands/rrd/stats.rs:245-249 | crates/top/rerun/src/commands/rrd/stats.rs:261-268 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/top/rerun/src/commands/rrd/stats.rs:245` it does not close everything it opens, so those exact lines 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) docs/snippets/all/archetypes/transform3d_hierarchy_frames.rs:71— docs/snippets/all/archetypes/transform3d_hierarchy_frames.rs:71-77 | docs/snippets/all/archetypes/transform3d_hierarchy_frames.rs:82-86 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `docs/snippets/all/archetypes/transform3d_hierarchy_frames.rs:71` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) rerun_py/src/catalog/dataset_entry.rs:569— rerun_py/src/catalog/dataset_entry.rs:569-573 | rerun_py/src/catalog/dataset_entry.rs:593-597 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `rerun_py/src/catalog/dataset_entry.rs:569` it does not close everything it opens, so those exact lines 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) rerun_py/src/catalog/policy_handle.rs:34— rerun_py/src/catalog/policy_handle.rs:34-38 | rerun_py/src/catalog/unregistration_handle.rs:50-54 — 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 (5 lines × 2) crates/store/re_chunk/src/iter.rs:326— crates/store/re_chunk/src/iter.rs:326-330 | crates/store/re_chunk/src/iter.rs:417-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.
Duplicated block (5 lines × 2) crates/store_app/re_server/src/rerun_cloud/mod.rs:1412— crates/store_app/re_server/src/rerun_cloud/mod.rs:1412-1416 | crates/store_app/re_server/src/rerun_cloud/mod.rs:1442-1446 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note first that the copies are not typed on the same thing: the declarations holding them bind `request` to `tonic::Request<re_protos::cloud::v1alpha1::GetSegmentTableSchemaRequest>` in one and `tonic::Request<re_protos::cloud::v1alpha1::ScanSegmentTableRequest>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (5 lines × 2) crates/views/re_view_spatial/src/visualizers/mod.rs:77— crates/views/re_view_spatial/src/visualizers/mod.rs:77-81 | crates/views/re_view_spatial/src/visualizers/mod.rs:106-110 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) examples/notebook/notebook/cube_marimo.py:38— examples/notebook/notebook/cube_marimo.py:38-42 | examples/notebook/notebook/cube_marimo.py:90-94 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) scripts/ci/compare.py:69— scripts/ci/compare.py:69-73 | scripts/ci/count_bytes.py:74-78 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (5 lines × 2) scripts/ci/pixi_install_wheel.py:88— scripts/ci/pixi_install_wheel.py:88-92 | scripts/ci/uv_install_wheel.py:88-92 — before extracting anything, compare `scripts/ci/pixi_install_wheel.py` and `scripts/ci/uv_install_wheel.py` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) scripts/lint.py:1626— scripts/lint.py:1626-1630 | scripts/lint.py:1635-1639 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) scripts/ci/bundle_and_upload_rerun_cpp.py:23— scripts/ci/bundle_and_upload_rerun_cpp.py:23-27 | scripts/screenshot_compare/build_screenshot_compare.py:67-71 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (12 lines × 2) crates/data_flow/re_lenses/src/semantic/foxglove/packed_element_field.rs:183— crates/data_flow/re_lenses/src/semantic/foxglove/packed_element_field.rs:183-194 | crates/data_flow/re_lenses/src/semantic/foxglove/packed_element_field.rs:334-345 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/data_flow/re_lenses/src/semantic/foxglove/packed_element_field.rs:183` 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 (12 lines × 2) crates/store/re_chunk_store/src/query.rs:196— crates/store/re_chunk_store/src/query.rs:196-207 | crates/store/re_chunk_store/src/query.rs:245-256 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/store/re_chunk_store/src/query.rs:196` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) crates/store/re_log_types/src/index/time_real.rs:110— crates/store/re_log_types/src/index/time_real.rs:110-121 | crates/store/re_log_types/src/index/time_real.rs:128-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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. Note first that the copies are not typed on the same thing: the declarations holding them bind `value` to `f32` in one and `f64` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (12 lines × 2) crates/store_app/re_entity_db/src/rrd_manifest_index/time_range_merger.rs:407— crates/store_app/re_entity_db/src/rrd_manifest_index/time_range_merger.rs:407-418 | crates/store_app/re_entity_db/src/rrd_manifest_index/time_range_merger.rs:429-440 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/store_app/re_entity_db/src/rrd_manifest_index/time_range_merger.rs:407` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (12 lines × 2) crates/ui_tools/re_renderer/src/colormap.rs:114— crates/ui_tools/re_renderer/src/colormap.rs:114-125 | crates/ui_tools/re_renderer/src/colormap.rs:158-169 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/ui_tools/re_renderer/src/colormap.rs:114` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) crates/viewer_support/re_viewer_context/src/selection_state.rs:207— crates/viewer_support/re_viewer_context/src/selection_state.rs:207-218 | crates/viewer_support/re_viewer_context/src/selection_state.rs:228-239 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/viewer_support/re_viewer_context/src/selection_state.rs:207` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) crates/views/re_view_spatial/src/eye.rs:667— crates/views/re_view_spatial/src/eye.rs:667-678 | crates/views/re_view_spatial/src/eye.rs:717-728 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) crates/views/re_view_spatial/src/visualizers/arrows2d.rs:83— crates/views/re_view_spatial/src/visualizers/arrows2d.rs:83-95 | crates/views/re_view_spatial/src/visualizers/arrows3d.rs:83-94 — before extracting anything, compare `crates/views/re_view_spatial/src/visualizers/arrows2d.rs` and `crates/views/re_view_spatial/src/visualizers/arrows3d.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 85 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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/views/re_view_spatial/src/visualizers/arrows2d.rs:83` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (12 lines × 2) crates/views/re_view_spatial/src/visualizers/boxes2d.rs:62— crates/views/re_view_spatial/src/visualizers/boxes2d.rs:62-73 | crates/views/re_view_spatial/src/visualizers/ellipses2d.rs:169-180 — before extracting anything, compare `crates/views/re_view_spatial/src/visualizers/boxes2d.rs` and `crates/views/re_view_spatial/src/visualizers/ellipses2d.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 97 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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/views/re_view_spatial/src/visualizers/boxes2d.rs:62` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) crates/views/re_view_time_series/src/line_visualizer_system.rs:95— crates/views/re_view_time_series/src/line_visualizer_system.rs:95-108 | crates/views/re_view_time_series/src/measurements_visualizer_system.rs:97-108 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `crates/views/re_view_time_series/src/line_visualizer_system.rs:95` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (12 lines × 2) docs/snippets/all/tutorials/any_values.rs:22— docs/snippets/all/tutorials/any_values.rs:22-33 | docs/snippets/all/tutorials/dynamic_archetype.rs:23-34 — 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 `docs/snippets/all/tutorials/any_values.rs:22` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) crates/ui_tools/re_renderer/src/renderer/depth_cloud.rs:435— crates/ui_tools/re_renderer/src/renderer/depth_cloud.rs:435-447 | crates/ui_tools/re_renderer/src/renderer/mesh_renderer.rs:475-486 — before extracting anything, compare `crates/ui_tools/re_renderer/src/renderer/depth_cloud.rs` and `crates/ui_tools/re_renderer/src/renderer/mesh_renderer.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 35 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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/ui_tools/re_renderer/src/renderer/depth_cloud.rs:435` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) crates/store_app/re_datafusion/src/dataframe_query_provider/cpu_worker.rs:392— crates/store_app/re_datafusion/src/dataframe_query_provider/cpu_worker.rs:392-404 | crates/store_app/re_datafusion/src/dataframe_query_provider/cpu_worker.rs:465-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/store_app/re_datafusion/src/dataframe_query_provider/cpu_worker.rs:392` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (12 lines × 2) docs/snippets/all/archetypes/transform3d_hierarchy.rs:66— docs/snippets/all/archetypes/transform3d_hierarchy.rs:66-77 | docs/snippets/all/archetypes/transform3d_hierarchy_frames.rs:86-97 — 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 `docs/snippets/all/archetypes/transform3d_hierarchy.rs:66` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) rerun_py/src/catalog/segment_url_udf.rs:101— rerun_py/src/catalog/segment_url_udf.rs:101-112 | rerun_py/src/catalog/segment_url_udf.rs:118-129 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `rerun_py/src/catalog/segment_url_udf.rs:101` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (12 lines × 2) crates/views/re_view_time_series/src/line_visualizer_system.rs:332— crates/views/re_view_time_series/src/line_visualizer_system.rs:332-343 | crates/views/re_view_time_series/src/line_visualizer_system.rs:401-412 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/views/re_view_time_series/src/line_visualizer_system.rs:332` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) crates/data_flow/re_lenses/src/semantic/foxglove/point_cloud.rs:13— crates/data_flow/re_lenses/src/semantic/foxglove/point_cloud.rs:13-24 | crates/data_flow/re_lenses/src/semantic/foxglove/voxel_grid.rs:13-24 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (12 lines × 2) crates/data_flow/re_lenses/src/semantic/foxglove/pose_in_frame.rs:12— crates/data_flow/re_lenses/src/semantic/foxglove/pose_in_frame.rs:12-23 | crates/data_flow/re_lenses/src/semantic/foxglove/poses_in_frame.rs:12-23 — 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/data_flow/re_lenses/src/semantic/foxglove/pose_in_frame.rs:12` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) rerun_notebook/src/rerun_notebook/asset_server.py:49— rerun_notebook/src/rerun_notebook/asset_server.py:49-60 | rerun_notebook/src/rerun_notebook/asset_server.py:64-75 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (12 lines × 2) rerun_py/rerun_sdk/rerun/experimental/dataloader/_iterable_dataset.py:408— rerun_py/rerun_sdk/rerun/experimental/dataloader/_iterable_dataset.py:408-419 | rerun_py/rerun_sdk/rerun/experimental/dataloader/_iterable_dataset.py:498-509 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `rerun_py/rerun_sdk/rerun/experimental/dataloader/_iterable_dataset.py:408` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (12 lines × 2) crates/ui_tools/re_renderer_examples/picking.rs:132— crates/ui_tools/re_renderer_examples/picking.rs:132-143 | crates/ui_tools/re_renderer_examples/world_grid.rs:64-75 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `crates/ui_tools/re_renderer_examples/picking.rs:132` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) examples/python/face_tracking/face_tracking.py:374— examples/python/face_tracking/face_tracking.py:374-385 | examples/python/gesture_detection/gesture_detection.py:226-237 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `examples/python/face_tracking/face_tracking.py:387` calls `resize_image` and `examples/python/gesture_detection/gesture_detection.py:242` 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 (12 lines × 2) scripts/ci/pixi_install_wheel.py:33— scripts/ci/pixi_install_wheel.py:33-44 | scripts/ci/uv_install_wheel.py:32-43 — before extracting anything, compare `scripts/ci/pixi_install_wheel.py` and `scripts/ci/uv_install_wheel.py` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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.
Off the main sequence: re_build_tools — re_build_tools: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 13 project(s), so it's rigid to change.
Off the main sequence: re_dump_puffin — re_dump_puffin: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: re_error — re_error: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 33 project(s), so it's rigid to change.
Off the main sequence: re_rvl — re_rvl: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 5 project(s), so it's rigid to change.
Off the main sequence: re_span — re_span: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 27 project(s), so it's rigid to change.
Off the main sequence: re_tracing — re_tracing: abstractness 0.00, instability 0.01, distance 0.99 — zone of pain — concrete and depended on by 69 project(s), so it's rigid to change.
Off the main sequence: re_format — re_format: abstractness 0.00, instability 0.05, distance 0.95 — zone of pain — concrete and depended on by 42 project(s), so it's rigid to change.
Off the main sequence: re_build_info — re_build_info: abstractness 0.00, instability 0.07, distance 0.93 — zone of pain — concrete and depended on by 13 project(s), so it's rigid to change.
Off the main sequence: re_tuid — re_tuid: abstractness 0.00, instability 0.13, distance 0.88 — zone of pain — concrete and depended on by 14 project(s), so it's rigid to change.
Off the main sequence: re_quota_channel — re_quota_channel: abstractness 0.00, instability 0.14, distance 0.86 — zone of pain — concrete and depended on by 19 project(s), so it's rigid to change.
Off the main sequence: re_log — re_log: abstractness 0.13, instability 0.01, distance 0.86 — zone of pain — concrete and depended on by 84 project(s), so it's rigid to change.
Off the main sequence: re_mutex — re_mutex: abstractness 0.00, instability 0.14, distance 0.86 — zone of pain — concrete and depended on by 12 project(s), so it's rigid to change.
Off the main sequence: re_backoff — re_backoff: 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: re_web — re_web: abstractness 0.00, instability 0.17, distance 0.83 — zone of pain — concrete and depended on by 10 project(s), so it's rigid to change.
Off the main sequence: re_log_types — re_log_types: abstractness 0.07, instability 0.11, distance 0.82 — zone of pain — concrete and depended on by 63 project(s), so it's rigid to change.
Off the main sequence: re_uri — re_uri: abstractness 0.00, instability 0.19, distance 0.81 — zone of pain — concrete and depended on by 21 project(s), so it's rigid to change.
Off the main sequence: re_capabilities — re_capabilities: 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: re_string_interner — re_string_interner: 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: re_log_msg — re_log_msg: abstractness 0.00, instability 0.21, distance 0.79 — zone of pain — concrete and depended on by 19 project(s), so it's rigid to change.
Off the main sequence: @rerun-io/web-viewer — @rerun-io/web-viewer: abstractness 0.22, instability 0.00, distance 0.78 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: re_sorbet — re_sorbet: abstractness 0.07, instability 0.22, distance 0.71 — zone of pain — concrete and depended on by 25 project(s), so it's rigid to change.
Off the main sequence: re_chunk — re_chunk: abstractness 0.04, instability 0.26, distance 0.70 — zone of pain — concrete and depended on by 34 project(s), so it's rigid to change.
Duplicated block (7 lines × 2) crates/panels/re_selection_panel/src/selection_panel.rs:1350— crates/panels/re_selection_panel/src/selection_panel.rs:1350-1356 | crates/panels/re_selection_panel/src/selection_panel.rs:1391-1397 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/panels/re_selection_panel/src/selection_panel.rs:1350` it does not close everything it opens, so those exact lines 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/store/re_chunk/src/iter.rs:477— crates/store/re_chunk/src/iter.rs:477-483 | crates/store/re_chunk/src/iter.rs:554-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.
Duplicated block (7 lines × 2) crates/store_app/re_entity_db/src/rrd_manifest_index/time_range_merger.rs:171— crates/store_app/re_entity_db/src/rrd_manifest_index/time_range_merger.rs:171-177 | crates/store_app/re_entity_db/src/rrd_manifest_index/time_range_merger.rs:217-223 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/store_app/re_entity_db/src/rrd_manifest_index/time_range_merger.rs:171` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) crates/top/re_viewer/src/ui/dev_panel/transform_cache_ui/paint.rs:107— crates/top/re_viewer/src/ui/dev_panel/transform_cache_ui/paint.rs:107-113 | crates/top/re_viewer/src/ui/dev_panel/transform_cache_ui/paint.rs:154-160 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) crates/ui_tools/re_renderer/src/mesh.rs:114— crates/ui_tools/re_renderer/src/mesh.rs:114-120 | crates/ui_tools/re_renderer/src/mesh.rs:136-142 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/ui_tools/re_renderer/src/mesh.rs:114` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) crates/ui_tools/re_renderer/src/renderer/mesh_renderer.rs:513— crates/ui_tools/re_renderer/src/renderer/mesh_renderer.rs:513-519 | crates/ui_tools/re_renderer/src/renderer/voxel_grid.rs:360-368 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `crates/ui_tools/re_renderer/src/renderer/mesh_renderer.rs:513` 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/views/re_view_map/src/map_view.rs:591— crates/views/re_view_map/src/map_view.rs:591-597 | crates/views/re_view_spatial/src/picking.rs:206-212 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 2) rerun_py/src/catalog/dataset_entry.rs:405— rerun_py/src/catalog/dataset_entry.rs:405-411 | rerun_py/src/catalog/dataset_entry.rs:431-437 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `rerun_py/src/catalog/dataset_entry.rs:405` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) crates/store/re_sdk_types/src/archetypes/points2d_ext.rs:104— crates/store/re_sdk_types/src/archetypes/points2d_ext.rs:104-110 | crates/store/re_sdk_types/src/archetypes/points3d_ext.rs:116-122 — before extracting anything, compare `crates/store/re_sdk_types/src/archetypes/points2d_ext.rs` and `crates/store/re_sdk_types/src/archetypes/points3d_ext.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 65 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 × 2) crates/store/re_sorbet/src/column_descriptor.rs:113— crates/store/re_sorbet/src/column_descriptor.rs:113-119 | crates/store/re_sorbet/src/column_descriptor_ref.rs:27-33 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Note first that the copies are not typed on the same thing: the declarations holding them bind `batch_type` to `crate::BatchType` in one and `BatchType` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (7 lines × 2) crates/store/re_sorbet/src/column_kind.rs:29— crates/store/re_sorbet/src/column_kind.rs:29-35 | crates/store/re_sorbet/src/migrations/v0_0_1__to__v0_0_2.rs:54-60 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 2) crates/viewer_support/re_viewer_context/src/cache/encoded_depth_image_stats_cache.rs:125— crates/viewer_support/re_viewer_context/src/cache/encoded_depth_image_stats_cache.rs:125-131 | crates/viewer_support/re_viewer_context/src/cache/video_asset_cache.rs:136-142 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `crates/viewer_support/re_viewer_context/src/cache/encoded_depth_image_stats_cache.rs:122` calls `clear` and `crates/viewer_support/re_viewer_context/src/cache/video_asset_cache.rs:126` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7 lines × 2) crates/store/re_uri/src/endpoints/catalog.rs:24— crates/store/re_uri/src/endpoints/catalog.rs:24-30 | crates/store/re_uri/src/endpoints/proxy.rs:23-29 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (7 lines × 2) crates/store_app/re_query/src/cache.rs:219— crates/store_app/re_query/src/cache.rs:219-225 | crates/store_app/re_query/src/cache.rs:245-251 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/store_app/re_query/src/cache.rs:219` it does not close everything it opens, so those exact lines 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) rerun_py/src/catalog/dataset_entry.rs:499— rerun_py/src/catalog/dataset_entry.rs:499-505 | rerun_py/src/catalog/dataset_entry.rs:524-530 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `rerun_py/src/catalog/dataset_entry.rs:499` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) rerun_py/src/arrow.rs:27— rerun_py/src/arrow.rs:27-33 | rerun_py/src/arrow.rs:34-40 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) crates/data_flow/re_mcap/src/parsers/ros2msg/sensor_msgs/joy.rs:69— crates/data_flow/re_mcap/src/parsers/ros2msg/sensor_msgs/joy.rs:69-75 | crates/data_flow/re_mcap/src/parsers/ros2msg/sensor_msgs/joy.rs:76-82 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/data_flow/re_mcap/src/parsers/ros2msg/sensor_msgs/joy.rs:69` 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 × 2) crates/panels/re_recording_panel/src/recording_panel_ui.rs:629— crates/panels/re_recording_panel/src/recording_panel_ui.rs:629-635 | crates/panels/re_recording_panel/src/recording_panel_ui.rs:695-701 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/panels/re_recording_panel/src/recording_panel_ui.rs:629` 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/store_app/re_query/src/bin/clamped_zip.rs:200— crates/store_app/re_query/src/bin/clamped_zip.rs:200-206 | crates/store_app/re_query/src/bin/clamped_zip.rs:239-245 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) crates/top/rerun/src/demo_util.rs:109— crates/top/rerun/src/demo_util.rs:109-115 | crates/ui_tools/re_renderer/src/colormap.rs:241-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.
Duplicated block (7 lines × 2) crates/views/re_view_spatial/src/visualizers/mod.rs:82— crates/views/re_view_spatial/src/visualizers/mod.rs:82-88 | crates/views/re_view_spatial/src/visualizers/mod.rs:112-118 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) crates/panels/re_chunk_store_ui/src/chunk_store_ui.rs:486— crates/panels/re_chunk_store_ui/src/chunk_store_ui.rs:486-498 | crates/panels/re_chunk_store_ui/src/chunk_ui.rs:206-218 — 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/panels/re_chunk_store_ui/src/chunk_store_ui.rs:486` 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/panels/re_redap_browser/src/asset_coverage_modal.rs:849— crates/panels/re_redap_browser/src/asset_coverage_modal.rs:849-861 | crates/panels/re_redap_browser/src/servers/dataset.rs:1362-1374 — 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/panels/re_redap_browser/src/asset_coverage_modal.rs:849` 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/panels/re_selection_panel/src/selection_panel.rs:701— crates/panels/re_selection_panel/src/selection_panel.rs:701-713 | crates/panels/re_selection_panel/src/visualizer_ui.rs:561-573 — 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/panels/re_selection_panel/src/selection_panel.rs:701` it does not close everything it opens, so those exact lines 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/store/re_chunk/src/earliest_at.rs:124— crates/store/re_chunk/src/earliest_at.rs:124-136 | crates/store/re_chunk/src/latest_at.rs:150-162 — 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/store/re_chunk/src/earliest_at.rs:124` it does not close everything it opens, so those exact lines 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/store/re_chunk_store/src/writes.rs:712— crates/store/re_chunk_store/src/writes.rs:712-724 | crates/store/re_chunk_store/src/writes.rs:744-756 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/store/re_chunk_store/src/writes.rs:712` 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/store/re_log_channel/src/receiver_set.rs:126— crates/store/re_log_channel/src/receiver_set.rs:126-138 | crates/store/re_log_channel/src/receiver_set.rs:162-174 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) crates/store/re_sorbet/src/column_kind.rs:48— crates/store/re_sorbet/src/column_kind.rs:48-60 | crates/store/re_sorbet/src/migrations/v0_0_1__to__v0_0_2.rs:68-80 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `crates/store/re_sorbet/src/column_kind.rs:48` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) crates/store/re_sorbet/src/migrations/v0_1_3__to__v0_1_4.rs:82— crates/store/re_sorbet/src/migrations/v0_1_3__to__v0_1_4.rs:82-94 | crates/store/re_sorbet/src/migrations/v0_1_3__to__v0_1_4.rs:186-198 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/store/re_sorbet/src/migrations/v0_1_3__to__v0_1_4.rs:82` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) crates/store_app/re_dataframe/src/query.rs:1869— crates/store_app/re_dataframe/src/query.rs:1869-1881 | crates/store_app/re_dataframe/src/query.rs:2326-2338 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/store_app/re_dataframe/src/query.rs:1869` it does not close everything it opens, so those exact lines 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/ui_tools/re_renderer/src/renderer/depth_cloud.rs:515— crates/ui_tools/re_renderer/src/renderer/depth_cloud.rs:515-527 | crates/ui_tools/re_renderer/src/renderer/rectangles.rs:822-834 — 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/ui_tools/re_renderer/src/renderer/depth_cloud.rs:515` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (13 lines × 2) crates/ui_tools/re_ui/src/command/ui_command.rs:287— crates/ui_tools/re_ui/src/command/ui_command.rs:287-299 | crates/viewer_support/re_viewer_context/src/command/recording_command.rs:297-309 — before extracting anything, compare `crates/ui_tools/re_ui/src/command/ui_command.rs` and `crates/viewer_support/re_viewer_context/src/command/recording_command.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 43 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/ui_tools/re_ui/src/command/ui_command.rs:287` it does not close everything it opens, so those exact lines 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/viewer_support/re_view/src/clears.rs:39— crates/viewer_support/re_view/src/clears.rs:39-51 | crates/viewer_support/re_view/src/clears.rs:66-78 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/viewer_support/re_view/src/clears.rs:39` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `crates/viewer_support/re_view/src/clears.rs:65` calls `unwrap_or_default` and `crates/viewer_support/re_view/src/clears.rs:38` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (13 lines × 2) crates/viewer_support/re_view/src/view_property_ui.rs:109— crates/viewer_support/re_view/src/view_property_ui.rs:109-121 | crates/viewer_support/re_view/src/view_property_ui.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.
Duplicated block (13 lines × 2) crates/views/re_view_spatial/src/visualizers/cylinders3d.rs:85— crates/views/re_view_spatial/src/visualizers/cylinders3d.rs:85-97 | crates/views/re_view_spatial/src/visualizers/ellipsoids.rs:57-69 — 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/views/re_view_spatial/src/visualizers/cylinders3d.rs:85` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) docs/snippets/all/archetypes/transform3d_column_updates.rs:8— docs/snippets/all/archetypes/transform3d_column_updates.rs:8-20 | docs/snippets/all/archetypes/transform3d_row_updates.rs:8-20 — 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 `docs/snippets/all/archetypes/transform3d_column_updates.rs:8` 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) docs/snippets/all/archetypes/arrows3d_column_updates.rs:16— docs/snippets/all/archetypes/arrows3d_column_updates.rs:16-28 | docs/snippets/all/archetypes/arrows3d_row_updates.rs:15-27 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `docs/snippets/all/archetypes/arrows3d_column_updates.rs:12` calls `new_duration_secs` and `docs/snippets/all/archetypes/arrows3d_row_updates.rs:11` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (13 lines × 2) crates/viewer_support/re_viewer_context/src/blueprint_helpers.rs:147— crates/viewer_support/re_viewer_context/src/blueprint_helpers.rs:147-159 | crates/viewer_support/re_viewer_context/src/blueprint_helpers.rs:227-239 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/viewer_support/re_viewer_context/src/blueprint_helpers.rs:147` 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/views/re_view_bar_chart/src/view_class.rs:206— crates/views/re_view_bar_chart/src/view_class.rs:206-218 | crates/views/re_view_bar_chart/src/view_class.rs:220-232 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) skills/rerun-lerobot/scripts/fetch_lerobot_episodes.py:36— skills/rerun-lerobot/scripts/fetch_lerobot_episodes.py:36-50 | skills/rerun-lerobot/scripts/find_lerobot_dataset.py:45-57 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (13 lines × 2) examples/python/structure_from_motion/structure_from_motion/read_write_model.py:226— examples/python/structure_from_motion/structure_from_motion/read_write_model.py:226-238 | examples/python/structure_from_motion/structure_from_motion/read_write_model.py:340-352 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
AppCore::run_system_command (cognitive 123) crates/top/re_viewer/src/app/command_handling.rs:120— AppCore::run_system_command has cognitive complexity 123 (threshold 15). Drivers by points: if/else 41 (92 pts), match/switch 11 (23 pts), boolean chains 4, loops 2 (4 pts) (nesting depth added 65). 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.
AppCore::route_ui (cognitive 62) crates/top/re_viewer/src/app/route_ui.rs:35— AppCore::route_ui has cognitive complexity 62 (threshold 15). Drivers by points: if/else 35 (54 pts), boolean chains 4, loops 2 (3 pts), match/switch 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.
AppCore::run_recording_command (cognitive 51) crates/top/re_viewer/src/app/command_handling.rs:1296— AppCore::run_recording_command has cognitive complexity 51 (threshold 15). Drivers by points: if/else 19 (41 pts), loops 2 (6 pts), match/switch 2 (4 pts) (nesting depth added 28). 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.
AppCore::frame_ui (cognitive 46) crates/top/re_viewer/src/app/mod.rs:1534— AppCore::frame_ui has cognitive complexity 46 (threshold 15). Drivers by points: if/else 26 (37 pts), match/switch 2 (5 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AppCore::run_ui_command (cognitive 37) crates/top/re_viewer/src/app/command_handling.rs:883— AppCore::run_ui_command has cognitive complexity 37 (threshold 15). Drivers by points: if/else 12 (25 pts), match/switch 4 (7 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 18). 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.
AppCore::receive_log_msg (cognitive 36) crates/top/re_viewer/src/app/logic.rs:356— AppCore::receive_log_msg has cognitive complexity 36 (threshold 15). Drivers by points: if/else 11 (29 pts), match/switch 3 (4 pts), boolean chains 3 (nesting depth added 19). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
AppCore::load_data_source (cognitive 34) crates/top/re_viewer/src/app/add_data_source.rs:72— AppCore::load_data_source has cognitive complexity 34 (threshold 15). Drivers by points: if/else 16 (29 pts), match/switch 3 (5 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AppCore::serve_viewer_control (cognitive 27) crates/top/re_viewer/src/app/viewer_control/mod.rs:333— AppCore::serve_viewer_control has cognitive complexity 27 (threshold 15). Drivers by points: if/else 5 (14 pts), match/switch 6 (12 pts), boolean chains 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AppCore::answer_pending_viewer_control_replies (cognitive 26) crates/top/re_viewer/src/app/viewer_control/mod.rs:235— AppCore::answer_pending_viewer_control_replies has cognitive complexity 26 (threshold 15). Drivers by points: if/else 9 (17 pts), match/switch 2 (5 pts), boolean chains 3, 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.
AppCore::receive_fetched_chunks (cognitive 25) crates/top/re_viewer/src/app/logic.rs:735— AppCore::receive_fetched_chunks has cognitive complexity 25 (threshold 15). Drivers by points: if/else 5 (13 pts), loops 3 (7 pts), match/switch 1 (4 pts), boolean chains 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AppCore::receive_messages (cognitive 22) crates/top/re_viewer/src/app/logic.rs:159— AppCore::receive_messages has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (15 pts), match/switch 3 (6 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.
AppCore::validate_loaded_events (cognitive 21) crates/top/re_viewer/src/app/logic.rs:899— AppCore::validate_loaded_events has cognitive complexity 21 (threshold 15). Drivers by points: if/else 4 (14 pts), loops 3 (7 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AppCore::on_new_store (cognitive 20) crates/top/re_viewer/src/app/logic.rs:599— AppCore::on_new_store has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 3, match/switch 2 (3 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AppCore::ui_impl (cognitive 18) crates/top/re_viewer/src/app/ui.rs:20— AppCore::ui_impl has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 2 (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.
AppCore::prefetch_chunks (cognitive 17) crates/top/re_viewer/src/app/logic.rs:1057— AppCore::prefetch_chunks has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (14 pts), match/switch 1 (2 pts), loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AppCore::move_time (cognitive 17) crates/top/re_viewer/src/app/mod.rs:952— AppCore::move_time has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (16 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AppCore::purge_memory_if_needed (cognitive 16) crates/top/re_viewer/src/app/logic.rs:933— AppCore::purge_memory_if_needed has cognitive complexity 16 (threshold 15). Drivers by points: if/else 13 (14 pts), boolean chains 2 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D4 · Code Duplication· Edited copy of a member (12 corresponding lines) · ×16
Edited copy of a member (12 corresponding lines) rerun_py/src/catalog/connection_handle.rs:75— rerun_py/src/catalog/connection_handle.rs:75-91 | rerun_py/src/catalog/connection_handle.rs:100-111 — 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/data_flow/re_lenses/src/semantic/ros2msg/compressed_image.rs:80— crates/data_flow/re_lenses/src/semantic/ros2msg/compressed_image.rs:80-91 | crates/data_flow/re_lenses/src/semantic/ros2msg/compressed_image.rs:96-107 — 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/panels/re_time_panel/src/time_selection_ui.rs:431— crates/panels/re_time_panel/src/time_selection_ui.rs:431-442 | crates/panels/re_time_panel/src/time_selection_ui.rs:449-460 — 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/views/re_view_spatial/src/visualizers/gaussian_splats3d.rs:236— crates/views/re_view_spatial/src/visualizers/gaussian_splats3d.rs:236-247 | crates/views/re_view_spatial/src/visualizers/points3d.rs:197-210 — 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) rerun_py/src/lenses.rs:63— rerun_py/src/lenses.rs:63-74 | rerun_py/src/lenses.rs:82-97 — 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/store_app/re_datafusion/src/pipeline/config.rs:142— crates/store_app/re_datafusion/src/pipeline/config.rs:142-153 | crates/store_app/re_datafusion/src/pipeline_budget/mod.rs:835-851 — 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/store/re_chunk_store/src/subscribers.rs:330— crates/store/re_chunk_store/src/subscribers.rs:330-341 | crates/views/re_view_spatial/src/spatial_topology.rs:143-157 — 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/store/re_chunk/src/unit_chunk.rs:378— crates/store/re_chunk/src/unit_chunk.rs:378-389 | crates/store/re_chunk/src/unit_chunk.rs:423-434 — 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/store/re_chunk_store/src/query.rs:523— crates/store/re_chunk_store/src/query.rs:523-534 | crates/store/re_chunk_store/src/query.rs:655-667 — 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/store_app/re_datafusion/src/dataset_manifest.rs:67— crates/store_app/re_datafusion/src/dataset_manifest.rs:67-78 | crates/store_app/re_datafusion/src/segment_table.rs:66-77 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) crates/top/re_sdk/src/recording_stream.rs:2721— crates/top/re_sdk/src/recording_stream.rs:2721-2732 | crates/top/re_sdk/src/recording_stream.rs:2756-2771 — 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/ui_tools/re_ui/src/requested_object.rs:69— crates/ui_tools/re_ui/src/requested_object.rs:69-80 | crates/ui_tools/re_ui/src/requested_object.rs:176-189 — 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/viewer_support/re_component_ui/src/encoding_uis/float_drag.rs:104— crates/viewer_support/re_component_ui/src/encoding_uis/float_drag.rs:104-116 | crates/viewer_support/re_component_ui/src/encoding_uis/float_drag.rs:162-173 — 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/data_flow/re_redap_client/src/grpc.rs:663— crates/data_flow/re_redap_client/src/grpc.rs:663-674 | crates/panels/re_redap_browser/src/servers/mod.rs:707-718 — 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/store_app/re_entity_db/src/entity_db.rs:669— crates/store_app/re_entity_db/src/entity_db.rs:669-681 | crates/viewer_support/re_viewer_context/src/annotations.rs:281-292 — 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/ui_tools/re_renderer/src/draw_phases/screenshot.rs:106— crates/ui_tools/re_renderer/src/draw_phases/screenshot.rs:106-117 | crates/ui_tools/re_renderer/src/allocator/cpu_write_gpu_read_belt.rs:266-277 — 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 (15 lines × 2) crates/data_flow/re_grpc_client/src/lib.rs:50— crates/data_flow/re_grpc_client/src/lib.rs:50-64 | crates/data_flow/re_grpc_server/src/lib.rs:132-146 — 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 (15 lines × 2) crates/store/re_chunk_store/src/query.rs:122— crates/store/re_chunk_store/src/query.rs:122-136 | crates/store/re_chunk_store/src/query.rs:142-156 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (15 lines × 2) crates/store/re_log_channel/src/receiver_set.rs:141— crates/store/re_log_channel/src/receiver_set.rs:141-155 | crates/store/re_log_channel/src/receiver_set.rs:177-191 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/store/re_log_channel/src/receiver_set.rs:141` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) crates/store/re_log_encoding/src/transport_to_app.rs:305— crates/store/re_log_encoding/src/transport_to_app.rs:305-319 | crates/store/re_log_encoding/src/transport_to_app.rs:335-349 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/store/re_log_encoding/src/transport_to_app.rs:305` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) crates/ui_tools/re_renderer/src/renderer/gaussian_splat.rs:802— crates/ui_tools/re_renderer/src/renderer/gaussian_splat.rs:802-816 | crates/ui_tools/re_renderer/src/renderer/point_cloud.rs:831-846 — before extracting anything, compare `crates/ui_tools/re_renderer/src/renderer/gaussian_splat.rs` and `crates/ui_tools/re_renderer/src/renderer/point_cloud.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 207 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/ui_tools/re_renderer/src/renderer/gaussian_splat.rs:802` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (15 lines × 2) crates/ui_tools/re_renderer/src/renderer/volume.rs:323— crates/ui_tools/re_renderer/src/renderer/volume.rs:323-337 | crates/ui_tools/re_renderer/src/renderer/voxel_grid.rs:401-415 — before extracting anything, compare `crates/ui_tools/re_renderer/src/renderer/volume.rs` and `crates/ui_tools/re_renderer/src/renderer/voxel_grid.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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/ui_tools/re_renderer/src/renderer/volume.rs:323` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) crates/ui_tools/re_ui/src/command/ui_command.rs:492— crates/ui_tools/re_ui/src/command/ui_command.rs:492-506 | crates/viewer_support/re_viewer_context/src/command/recording_command.rs:394-408 — before extracting anything, compare `crates/ui_tools/re_ui/src/command/ui_command.rs` and `crates/viewer_support/re_viewer_context/src/command/recording_command.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 43 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/ui_tools/re_ui/src/command/ui_command.rs:492` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) crates/ui_tools/re_ui/src/command/ui_command.rs:508— crates/ui_tools/re_ui/src/command/ui_command.rs:508-522 | crates/viewer_support/re_viewer_context/src/command/recording_command.rs:410-424 — before extracting anything, compare `crates/ui_tools/re_ui/src/command/ui_command.rs` and `crates/viewer_support/re_viewer_context/src/command/recording_command.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 43 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/ui_tools/re_ui/src/command/ui_command.rs:508` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) crates/utils/re_perf_telemetry/src/prometheus.rs:216— crates/utils/re_perf_telemetry/src/prometheus.rs:216-230 | crates/utils/re_perf_telemetry/src/prometheus.rs:391-405 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/utils/re_perf_telemetry/src/prometheus.rs:216` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) crates/viewer_support/re_component_ui/src/time_range.rs:123— crates/viewer_support/re_component_ui/src/time_range.rs:123-137 | crates/viewer_support/re_component_ui/src/time_range.rs:167-181 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/viewer_support/re_component_ui/src/time_range.rs:123` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) crates/views/re_view_spatial/src/visualizers/video/encoded_depth_image.rs:72— crates/views/re_view_spatial/src/visualizers/video/encoded_depth_image.rs:72-86 | crates/views/re_view_spatial/src/visualizers/video/encoded_image.rs:53-67 — 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/views/re_view_spatial/src/visualizers/video/encoded_depth_image.rs:72` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) crates/views/re_view_time_series/src/line_series_loader.rs:182— crates/views/re_view_time_series/src/line_series_loader.rs:182-196 | crates/views/re_view_time_series/src/point_visualizer_system.rs:261-275 — before extracting anything, compare `crates/views/re_view_time_series/src/line_series_loader.rs` and `crates/views/re_view_time_series/src/point_visualizer_system.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 50 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (15 lines × 2) docs/snippets/all/howto/any_batch_value_column_updates.rs:10— docs/snippets/all/howto/any_batch_value_column_updates.rs:10-24 | docs/snippets/all/howto/any_values_column_updates.rs:12-26 — 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 `docs/snippets/all/howto/any_batch_value_column_updates.rs:10` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) crates/ui_tools/re_renderer/src/resource_managers/bayer_converter.rs:133— crates/ui_tools/re_renderer/src/resource_managers/bayer_converter.rs:133-147 | crates/ui_tools/re_renderer/src/resource_managers/yuv_converter.rs:435-449 — before extracting anything, compare `crates/ui_tools/re_renderer/src/resource_managers/bayer_converter.rs` and `crates/ui_tools/re_renderer/src/resource_managers/yuv_converter.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 99 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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/ui_tools/re_renderer/src/resource_managers/bayer_converter.rs:133` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) crates/ui_tools/re_renderer/src/renderer/mesh_renderer.rs:587— crates/ui_tools/re_renderer/src/renderer/mesh_renderer.rs:587-601 | crates/ui_tools/re_renderer/src/renderer/mesh_renderer.rs:619-633 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/ui_tools/re_renderer/src/renderer/mesh_renderer.rs:587` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) crates/store/re_chunk/src/chunk.rs:1310— crates/store/re_chunk/src/chunk.rs:1310-1324 | crates/store/re_chunk/src/chunk.rs:1339-1353 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/store/re_chunk/src/chunk.rs:1310` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication· Edited copy of a member (10 corresponding lines) · ×15
Edited copy of a member (10 corresponding lines) rerun_py/src/selector.rs:71— rerun_py/src/selector.rs:71-80 | rerun_py/src/selector.rs:89-101 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) rerun_py/src/python_bridge.rs:2161— rerun_py/src/python_bridge.rs:2161-2170 | rerun_py/src/python_bridge.rs:2174-2183 — 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/store/re_chunk/src/iter.rs:325— crates/store/re_chunk/src/iter.rs:325-334 | crates/store/re_chunk/src/iter.rs:416-429 — 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/top/rerun_c/src/lib.rs:310— crates/top/rerun_c/src/lib.rs:310-319 | crates/top/rerun_c/src/lib.rs:1071-1082 — 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) rerun_py/src/catalog/catalog_client.rs:438— rerun_py/src/catalog/catalog_client.rs:438-447 | rerun_py/src/catalog/catalog_client.rs:456-465 — 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/store/re_log_types/src/index/time_int.rs:262— crates/store/re_log_types/src/index/time_int.rs:262-271 | crates/store/re_log_types/src/index/time_int.rs:278-287 — 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/viewer_support/re_dataframe_ui/src/filters/numerical.rs:104— crates/viewer_support/re_dataframe_ui/src/filters/numerical.rs:104-113 | crates/viewer_support/re_dataframe_ui/src/filters/numerical.rs:195-204 — 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/utils/re_perf_telemetry/src/lib.rs:102— crates/utils/re_perf_telemetry/src/lib.rs:102-111 | crates/utils/re_perf_telemetry/src/trace_id_format.rs:31-43 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) crates/views/re_view_audio/src/audio_asset_cache.rs:181— crates/views/re_view_audio/src/audio_asset_cache.rs:181-190 | crates/views/re_view_audio/src/audio_asset_cache.rs:192-203 — 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/ui_tools/re_ui/src/list_item/custom_content.rs:125— crates/ui_tools/re_ui/src/list_item/custom_content.rs:125-134 | crates/ui_tools/re_ui/src/list_item/item_buttons.rs:216-226 — 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) rerun_py/src/chunk_stream/hdf5_reader.rs:54— rerun_py/src/chunk_stream/hdf5_reader.rs:54-63 | rerun_py/src/chunk_stream/parquet_reader.rs:28-37 — 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/top/re_sdk/src/grpc_server.rs:90— crates/top/re_sdk/src/grpc_server.rs:90-99 | crates/top/re_sdk/src/web_viewer.rs:112-121 — 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) docs/snippets/all/concepts/how-does-rerun-work/log-to-grpc.rs:1— docs/snippets/all/concepts/how-does-rerun-work/log-to-grpc.rs:1-11 | docs/snippets/all/concepts/how-does-rerun-work/log-to-rrd.rs:1-10 — 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) scripts/ci/compare.py:64— scripts/ci/compare.py:64-73 | scripts/ci/count_bytes.py:69-78 — 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) scripts/generate_view_coordinate_defs.py:120— scripts/generate_view_coordinate_defs.py:120-129 | scripts/generate_view_coordinate_defs.py:143-152 — 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 (13 corresponding lines) · ×14
Edited copy of a member (13 corresponding lines) crates/store/re_sdk_types/src/archetypes/points2d_ext.rs:38— crates/store/re_sdk_types/src/archetypes/points2d_ext.rs:38-50 | crates/store/re_sdk_types/src/archetypes/points3d_ext.rs:42-55 — 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) rerun_py/src/catalog/dataset_entry.rs:263— rerun_py/src/catalog/dataset_entry.rs:263-275 | rerun_py/src/catalog/dataset_entry.rs:278-290 — 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/store/re_chunk/src/chunk.rs:1695— crates/store/re_chunk/src/chunk.rs:1695-1707 | crates/store/re_chunk/src/chunk.rs:1710-1722 — 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/data_flow/re_importer/src/importer_urdf/joint_transform.rs:24— crates/data_flow/re_importer/src/importer_urdf/joint_transform.rs:24-36 | crates/data_flow/re_importer/src/importer_urdf/urdf_tree.rs:223-235 — 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/store_app/re_dataframe/src/query.rs:1240— crates/store_app/re_dataframe/src/query.rs:1240-1252 | crates/store_app/re_dataframe/src/query.rs:1720-1734 — 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/viewer_support/re_context_menu/src/collapse_expand.rs:59— crates/viewer_support/re_context_menu/src/collapse_expand.rs:59-73 | crates/viewer_support/re_context_menu/src/collapse_expand.rs:81-93 — 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/ui_tools/re_agent_ui/src/ui/agent_panel.rs:922— crates/ui_tools/re_agent_ui/src/ui/agent_panel.rs:922-938 | crates/ui_tools/re_agent_ui/src/ui/setup_ui/mod.rs:289-301 — 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/utils/re_crash_handler/src/lib.rs:235— crates/utils/re_crash_handler/src/lib.rs:235-247 | crates/utils/re_memory/src/backtrace_native.rs:39-58 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) crates/store/re_types_core/src/archetype.rs:164— crates/store/re_types_core/src/archetype.rs:164-176 | crates/store/re_types_core/src/loggable.rs:171-185 — 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/data_flow/re_hdf5/src/streaming.rs:223— crates/data_flow/re_hdf5/src/streaming.rs:223-237 | crates/data_flow/re_hdf5/src/streaming.rs:244-256 — 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/store/re_log_types/src/index/time_cell.rs:165— crates/store/re_log_types/src/index/time_cell.rs:165-178 | crates/store/re_log_types/src/index/time_cell.rs:180-192 — 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) scripts/ci/compare.py:48— scripts/ci/compare.py:48-60 | scripts/ci/count_bytes.py:53-65 — 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) scripts/ci/check_doc_order.py:17— scripts/ci/check_doc_order.py:17-29 | scripts/ci/check_skills.py:22-34 — 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/viewer_support/re_viewer_context/src/cache/video_stream_cache/test_player/encoded_depth_image.rs:23— crates/viewer_support/re_viewer_context/src/cache/video_stream_cache/test_player/encoded_depth_image.rs:23-35 | crates/viewer_support/re_viewer_context/src/cache/video_stream_cache/test_player/encoded_image.rs:27-39 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (14 lines × 2) crates/data_flow/re_mcap/src/parsers/ros2msg/std_msgs/float64_array.rs:33— crates/data_flow/re_mcap/src/parsers/ros2msg/std_msgs/float64_array.rs:33-46 | crates/data_flow/re_mcap/src/parsers/ros2msg/std_msgs/float64_multi_array.rs:33-46 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (14 lines × 2) crates/data_flow/re_redap_client/src/grpc.rs:780— crates/data_flow/re_redap_client/src/grpc.rs:780-793 | crates/data_flow/re_redap_client/src/grpc.rs:892-905 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/data_flow/re_redap_client/src/grpc.rs:780` it does not close everything it opens, so those exact lines 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/store/re_lenses_core/src/selector/parser.rs:529— crates/store/re_lenses_core/src/selector/parser.rs:529-542 | crates/store/re_lenses_core/src/selector/parser.rs:634-647 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/store/re_lenses_core/src/selector/parser.rs:529` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) crates/utils/re_perf_telemetry/src/prometheus.rs:273— crates/utils/re_perf_telemetry/src/prometheus.rs:273-286 | crates/utils/re_perf_telemetry/src/prometheus.rs:448-461 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/utils/re_perf_telemetry/src/prometheus.rs:273` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) crates/viewer_support/re_dataframe_ui/src/filters/string.rs:178— crates/viewer_support/re_dataframe_ui/src/filters/string.rs:178-191 | crates/viewer_support/re_dataframe_ui/src/filters/timestamp.rs:423-436 — 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/viewer_support/re_dataframe_ui/src/filters/string.rs:178` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) crates/viewer_support/re_viewer_context/src/blueprint_helpers.rs:305— crates/viewer_support/re_viewer_context/src/blueprint_helpers.rs:305-318 | crates/viewer_support/re_viewer_context/src/blueprint_helpers.rs:350-363 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (14 lines × 2) crates/viewer_support/re_viewer_context/src/tensor/image_stats.rs:84— crates/viewer_support/re_viewer_context/src/tensor/image_stats.rs:84-97 | crates/viewer_support/re_viewer_context/src/tensor/tensor_stats.rs:80-93 — before extracting anything, compare `crates/viewer_support/re_viewer_context/src/tensor/image_stats.rs` and `crates/viewer_support/re_viewer_context/src/tensor/tensor_stats.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 31 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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/viewer_support/re_viewer_context/src/tensor/image_stats.rs:84` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) crates/views/re_view_map/src/map_view.rs:598— crates/views/re_view_map/src/map_view.rs:598-611 | crates/views/re_view_spatial/src/picking.rs:214-227 — 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/views/re_view_map/src/map_view.rs:598` it does not close everything it opens, so those exact lines 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/views/re_view_spatial/src/visualizers/assets3d.rs:76— crates/views/re_view_spatial/src/visualizers/assets3d.rs:76-89 | crates/views/re_view_spatial/src/visualizers/meshes.rs:78-91 — 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/views/re_view_spatial/src/visualizers/assets3d.rs:76` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) rerun_py/src/catalog/dataset_entry.rs:575— rerun_py/src/catalog/dataset_entry.rs:575-588 | rerun_py/src/catalog/dataset_entry.rs:599-612 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `rerun_py/src/catalog/dataset_entry.rs:575` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) crates/store_app/re_server/src/rerun_cloud/mod.rs:213— crates/store_app/re_server/src/rerun_cloud/mod.rs:213-226 | crates/store_app/re_server/src/store/in_memory_store.rs:251-267 — 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/store_app/re_server/src/rerun_cloud/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 (14 lines × 2) crates/data_flow/re_mcap/src/parsers/ros2msg/sensor_msgs/joint_state.rs:81— crates/data_flow/re_mcap/src/parsers/ros2msg/sensor_msgs/joint_state.rs:81-94 | crates/data_flow/re_mcap/src/parsers/ros2msg/sensor_msgs/joint_state.rs:105-118 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/data_flow/re_mcap/src/parsers/ros2msg/sensor_msgs/joint_state.rs:81` it does not close everything it opens, so those exact lines 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/views/re_view_state_timeline/src/view_class.rs:235— crates/views/re_view_state_timeline/src/view_class.rs:235-248 | crates/views/re_view_time_series/src/view_class.rs:397-410 — 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/views/re_view_state_timeline/src/view_class.rs:235` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) examples/python/lidar/lidar/__main__.py:78— examples/python/lidar/lidar/__main__.py:78-91 | examples/python/nuscenes_dataset/nuscenes_dataset/__main__.py:290-303 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication· Edited copy of a member (14 corresponding lines) · ×13
Edited copy of a member (14 corresponding lines) docs/snippets/all/archetypes/pinhole_simple.rs:6— docs/snippets/all/archetypes/pinhole_simple.rs:6-27 | docs/snippets/all/archetypes/tensor_simple.rs:6-19 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) crates/viewer_support/re_view/src/blueprint_resolved_results.rs:128— crates/viewer_support/re_view/src/blueprint_resolved_results.rs:128-141 | crates/viewer_support/re_view/src/blueprint_resolved_results.rs:298-311 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) crates/store/re_chunk_store/src/store.rs:1170— crates/store/re_chunk_store/src/store.rs:1170-1183 | crates/store/re_chunk_store/src/store.rs:1194-1209 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) crates/store_app/re_catalog_client/src/dataset.rs:270— crates/store_app/re_catalog_client/src/dataset.rs:270-283 | crates/store_app/re_catalog_client/src/segment.rs:245-258 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) crates/viewer_support/re_viewer_context/src/command/redap_server_command.rs:82— crates/viewer_support/re_viewer_context/src/command/redap_server_command.rs:82-97 | crates/viewer_support/re_viewer_context/src/command/table_command.rs:42-55 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) crates/store/re_protos/src/v1alpha1/rerun.common.v1alpha1.ext.rs:826— crates/store/re_protos/src/v1alpha1/rerun.common.v1alpha1.ext.rs:826-844 | crates/store/re_protos/src/v1alpha1/rerun.common.v1alpha1.ext.rs:848-861 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) crates/data_flow/re_redap_client/src/grpc.rs:325— crates/data_flow/re_redap_client/src/grpc.rs:325-338 | crates/data_flow/re_redap_client/src/grpc.rs:421-437 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) crates/store/re_lenses_core/src/selector/lexer.rs:121— crates/store/re_lenses_core/src/selector/lexer.rs:121-134 | crates/store/re_lenses_core/src/selector/lexer.rs:208-221 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) crates/store/re_chunk_store/src/query.rs:440— crates/store/re_chunk_store/src/query.rs:440-453 | crates/store/re_chunk_store/src/query.rs:466-482 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) crates/top/re_viewer/src/app_blueprint.rs:175— crates/top/re_viewer/src/app_blueprint.rs:175-188 | crates/top/re_viewer/src/app_blueprint.rs:190-204 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) crates/utils/re_perf_telemetry/src/grpc.rs:369— crates/utils/re_perf_telemetry/src/grpc.rs:369-387 | crates/utils/re_perf_telemetry/src/grpc.rs:398-411 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) crates/viewer_support/re_viewer_context/src/cache/video_stream_cache/mod.rs:79— crates/viewer_support/re_viewer_context/src/cache/video_stream_cache/mod.rs:79-92 | crates/viewer_support/re_viewer_context/src/cache/video_stream_cache/mod.rs:94-107 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) crates/store_app/re_tf/src/transform_resolution_cache/transform_cache_snapshot.rs:263— crates/store_app/re_tf/src/transform_resolution_cache/transform_cache_snapshot.rs:263-276 | crates/store_app/re_tf/src/transform_resolution_cache/transform_cache_snapshot.rs:284-297 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (11 corresponding lines) · ×13
Edited copy of a member (11 corresponding lines) crates/viewer_support/re_data_ui/src/item_ui.rs:421— crates/viewer_support/re_data_ui/src/item_ui.rs:421-431 | crates/viewer_support/re_data_ui/src/item_ui.rs:437-447 — 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) rerun_py/src/catalog/datafusion_catalog.rs:44— rerun_py/src/catalog/datafusion_catalog.rs:44-54 | rerun_py/src/catalog/table_entry.rs:147-160 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) crates/viewer_support/re_component_ui/src/encoding_uis/singleline_string.rs:25— crates/viewer_support/re_component_ui/src/encoding_uis/singleline_string.rs:25-37 | crates/viewer_support/re_component_ui/src/encoding_uis/singleline_string.rs:56-66 — 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) docs/snippets/all/archetypes/line_strips2d_segments_simple.rs:3— docs/snippets/all/archetypes/line_strips2d_segments_simple.rs:3-14 | docs/snippets/all/archetypes/line_strips2d_simple.rs:3-13 — 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/utils/re_arrow_util/src/arrays.rs:661— crates/utils/re_arrow_util/src/arrays.rs:661-671 | crates/utils/re_arrow_util/src/arrays.rs:681-691 — 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/viewer_support/re_viewer_context/src/command/mod.rs:35— crates/viewer_support/re_viewer_context/src/command/mod.rs:35-45 | crates/viewer_support/re_viewer_context/src/command/mod.rs:54-67 — 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/viewer_support/re_viewer_context/src/drag_and_drop.rs:88— crates/viewer_support/re_viewer_context/src/drag_and_drop.rs:88-103 | crates/viewer_support/re_viewer_context/src/drag_and_drop.rs:105-115 — 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/store/re_sorbet/src/sorbet_batch.rs:134— crates/store/re_sorbet/src/sorbet_batch.rs:134-144 | crates/store/re_sorbet/src/sorbet_batch.rs:149-159 — 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/store/re_sorbet/src/chunk_batch.rs:54— crates/store/re_sorbet/src/chunk_batch.rs:54-67 | crates/store/re_sorbet/src/sorbet_batch.rs:35-45 — 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/ui_tools/re_ui/src/list_item/item_buttons.rs:189— crates/ui_tools/re_ui/src/list_item/item_buttons.rs:189-199 | crates/ui_tools/re_ui/src/list_item/custom_content.rs:101-111 — 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/data_flow/re_mcap/src/decoders/protobuf.rs:861— crates/data_flow/re_mcap/src/decoders/protobuf.rs:861-871 | crates/data_flow/re_mcap/src/decoders/ros2_reflection.rs:220-235 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) crates/utils/re_quota_channel/src/async_broadcast_channel.rs:377— crates/utils/re_quota_channel/src/async_broadcast_channel.rs:377-387 | crates/utils/re_quota_channel/src/sync/mod.rs:321-331 — 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/store/re_log_encoding/src/rrd/decoder/iterator.rs:38— crates/store/re_log_encoding/src/rrd/decoder/iterator.rs:38-48 | crates/store/re_log_encoding/src/rrd/decoder/stream.rs:25-35 — 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.
ChunkStore::insert_chunk_impl (cognitive 106) crates/store/re_chunk_store/src/writes.rs:113— ChunkStore::insert_chunk_impl has cognitive complexity 106 (threshold 15). Drivers by points: if/else 33 (73 pts), loops 11 (30 pts), boolean chains 3 (nesting depth added 59). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
ChunkStore::remove_chunk_from_virtual_indices (cognitive 51) crates/store/re_chunk_store/src/gc.rs:494— ChunkStore::remove_chunk_from_virtual_indices has cognitive complexity 51 (threshold 15). Drivers by points: if/else 13 (44 pts), loops 3 (7 pts) (nesting depth added 35). 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.
ChunkStore::find_and_elect_compaction_candidate (cognitive 36) crates/store/re_chunk_store/src/compaction_election.rs:22— ChunkStore::find_and_elect_compaction_candidate has cognitive complexity 36 (threshold 15). Drivers by points: if/else 13 (20 pts), loops 5 (14 pts), boolean chains 2 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ChunkStore::drop_time_range (cognitive 33) crates/store/re_chunk_store/src/drop_time_range.rs:47— ChunkStore::drop_time_range has cognitive complexity 33 (threshold 15). Drivers by points: if/else 12 (30 pts), loops 3 (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.
ChunkStore::gc_find_candidates (cognitive 20) crates/store/re_chunk_store/src/gc.rs:377— ChunkStore::gc_find_candidates has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (16 pts), loops 2 (4 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ChunkStore::drop_lineage_reference (cognitive 20) crates/store/re_chunk_store/src/lineage_dropping.rs:23— ChunkStore::drop_lineage_reference has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (16 pts), match/switch 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ChunkStore::extract_chunks_for_single_split (cognitive 19) crates/store/re_chunk_store/src/split.rs:293— ChunkStore::extract_chunks_for_single_split has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (15 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ChunkStore::finalize_compaction (cognitive 18) crates/store/re_chunk_store/src/compact.rs:98— ChunkStore::finalize_compaction has cognitive complexity 18 (threshold 15). Drivers by points: loops 5 (8 pts), if/else 4 (5 pts), match/switch 2 (4 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ChunkStore::format_lineage (cognitive 17) crates/store/re_chunk_store/src/lineage.rs:311— ChunkStore::format_lineage has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (14 pts), match/switch 2, loops 1 (nesting depth added 4). None of this is in the body itself: all 17 points belong to 2 function items inside it that branch (compute_staticness, recurse). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
ChunkStore::split_by_time_ranges (cognitive 17) crates/store/re_chunk_store/src/split.rs:27— ChunkStore::split_by_time_ranges has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 3, loops 2 (3 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ChunkStore::next_time_on_timeline (cognitive 16) crates/store/re_chunk_store/src/query.rs:552— ChunkStore::next_time_on_timeline has cognitive complexity 16 (threshold 15). Drivers by points: loops 5 (11 pts), if/else 2 (5 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. This shape REPEATS in the file: one other method here (ChunkStore::prev_time_on_timeline) 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.
ChunkStore::prev_time_on_timeline (cognitive 16) crates/store/re_chunk_store/src/query.rs:605— ChunkStore::prev_time_on_timeline has cognitive complexity 16 (threshold 15). Drivers by points: loops 5 (11 pts), if/else 2 (5 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. This shape REPEATS in the file: one other method here (ChunkStore::next_time_on_timeline) 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.
re_view_spatial::visualizers::video::execute_video_stream_like (cognitive 49) crates/views/re_view_spatial/src/visualizers/video/mod.rs:166— re_view_spatial::visualizers::video::execute_video_stream_like has cognitive complexity 49 (threshold 15). Drivers by points: if/else 21 (44 pts), boolean chains 2, match/switch 1 (2 pts), loops 1 (nesting depth added 24). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
re_view_spatial::picking_ui_pixel::format_pixel_value (cognitive 35) crates/views/re_view_spatial/src/picking_ui_pixel.rs:210— re_view_spatial::picking_ui_pixel::format_pixel_value has cognitive complexity 35 (threshold 15). Drivers by points: match/switch 6 (19 pts), if/else 8 (16 pts) (nesting depth added 21). 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.
re_view_spatial::picking_ui::picking (cognitive 33) crates/views/re_view_spatial/src/picking_ui.rs:28— re_view_spatial::picking_ui::picking has cognitive complexity 33 (threshold 15). Drivers by points: if/else 15 (27 pts), match/switch 2 (5 pts), loops 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_view_spatial::shared_fallbacks::register_fallbacks (cognitive 29) crates/views/re_view_spatial/src/shared_fallbacks.rs:27— re_view_spatial::shared_fallbacks::register_fallbacks has cognitive complexity 29 (threshold 15). Drivers by points: if/else 19 (21 pts), boolean chains 6, loops 2 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
re_view_spatial::visualizers::utilities::transform_retrieval::is_valid_space_for_content (cognitive 29) crates/views/re_view_spatial/src/visualizers/utilities/transform_retrieval.rs:251— re_view_spatial::visualizers::utilities::transform_retrieval::is_valid_space_for_content has cognitive complexity 29 (threshold 15). Drivers by points: if/else 12 (20 pts), match/switch 4 (8 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.
re_view_spatial::proc_mesh::capsule_wireframe_lines (cognitive 25) crates/views/re_view_spatial/src/proc_mesh.rs:383— re_view_spatial::proc_mesh::capsule_wireframe_lines has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (18 pts), loops 4 (5 pts), boolean chains 2 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_view_spatial::visualizers::video::show_video_frame (cognitive 25) crates/views/re_view_spatial/src/visualizers/video/mod.rs:586— re_view_spatial::visualizers::video::show_video_frame has cognitive complexity 25 (threshold 15). Drivers by points: if/else 16 (21 pts), boolean chains 2, match/switch 2 (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
re_view_spatial::picking::picking_gpu (cognitive 22) crates/views/re_view_spatial/src/picking.rs:189— re_view_spatial::picking::picking_gpu has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (17 pts), loops 2 (5 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.
re_view_spatial::ui::create_labels (cognitive 21) crates/views/re_view_spatial/src/ui.rs:214— re_view_spatial::ui::create_labels has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (17 pts), match/switch 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_view_spatial::visualizers::utilities::transform_retrieval::format_transform_info_result (cognitive 20) crates/views/re_view_spatial/src/visualizers/utilities/transform_retrieval.rs:167— re_view_spatial::visualizers::utilities::transform_retrieval::format_transform_info_result has cognitive complexity 20 (threshold 15). Drivers by points: if/else 12 (19 pts), match/switch 1 (nesting depth added 7). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
re_view_spatial::proc_mesh::generate_wireframe (cognitive 16) crates/views/re_view_spatial/src/proc_mesh.rs:216— re_view_spatial::proc_mesh::generate_wireframe has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (9 pts), loops 3 (6 pts), match/switch 1 (nesting depth added 7). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
re_view_spatial::ui::resolve_label_positions (cognitive 16) crates/views/re_view_spatial/src/ui.rs:379— re_view_spatial::ui::resolve_label_positions has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (13 pts), match/switch 1 (2 pts), loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_view_time_series::series_query::collect_colors (cognitive 36) crates/views/re_view_time_series/src/series_query.rs:196— re_view_time_series::series_query::collect_colors has cognitive complexity 36 (threshold 15). Drivers by points: loops 5 (18 pts), if/else 10 (17 pts), boolean chains 1 (nesting depth added 20). 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.
re_view_time_series::series_query::collect_radius_ui (cognitive 25) crates/views/re_view_time_series/src/series_query.rs:370— re_view_time_series::series_query::collect_radius_ui has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 3 (11 pts), boolean chains 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_view_time_series::fallbacks::register_fallbacks (cognitive 24) crates/views/re_view_time_series/src/fallbacks.rs:13— re_view_time_series::fallbacks::register_fallbacks has cognitive complexity 24 (threshold 15). Drivers by points: if/else 12 (18 pts), boolean chains 2, loops 2, match/switch 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_view_time_series::line_visualizer_system::build_line_draw_data (cognitive 24) crates/views/re_view_time_series/src/line_visualizer_system.rs:116— re_view_time_series::line_visualizer_system::build_line_draw_data has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (13 pts), match/switch 3 (8 pts), loops 2, 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.
re_view_time_series::view_class::update_series_visibility_from_legend (cognitive 23) crates/views/re_view_time_series/src/view_class.rs:1782— re_view_time_series::view_class::update_series_visibility_from_legend has cognitive complexity 23 (threshold 15). Drivers by points: if/else 12 (21 pts), loops 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_view_time_series::error_bands::build_band_draw_data (cognitive 22) crates/views/re_view_time_series/src/error_bands.rs:20— re_view_time_series::error_bands::build_band_draw_data has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (11 pts), match/switch 4 (7 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_view_time_series::line_visualizer_system::build_nan_island_marker_draw_data (cognitive 21) crates/views/re_view_time_series/src/line_visualizer_system.rs:345— re_view_time_series::line_visualizer_system::build_nan_island_marker_draw_data has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (13 pts), boolean chains 4, loops 2 (3 pts), match/switch 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_view_time_series::visualizer_ui::visualizer_ui_element (cognitive 21) crates/views/re_view_time_series/src/visualizer_ui.rs:25— re_view_time_series::visualizer_ui::visualizer_ui_element has cognitive complexity 21 (threshold 15). Drivers by points: if/else 16 (18 pts), boolean chains 3 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
re_view_time_series::view_class::nearest_data_point_tooltip (cognitive 18) crates/views/re_view_time_series/src/view_class.rs:1284— re_view_time_series::view_class::nearest_data_point_tooltip has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (10 pts), boolean chains 4, loops 2 (3 pts), match/switch 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_view_time_series::series_query::collect_scalars (cognitive 17) crates/views/re_view_time_series/src/series_query.rs:146— re_view_time_series::series_query::collect_scalars has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (10 pts), loops 3 (7 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.
re_view_time_series::view_class::all_scalar_mappings (cognitive 17) crates/views/re_view_time_series/src/view_class.rs:1115— re_view_time_series::view_class::all_scalar_mappings has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 3, match/switch 2 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_view_time_series::view_class::all_series_tooltip (cognitive 17) crates/views/re_view_time_series/src/view_class.rs:1559— re_view_time_series::view_class::all_series_tooltip has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 1, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D4 · Code Duplication· Edited copy of a member (18 corresponding lines) · ×12
Edited copy of a member (18 corresponding lines) crates/data_flow/re_lenses/src/semantic/foxglove/packed_element_field.rs:70— crates/data_flow/re_lenses/src/semantic/foxglove/packed_element_field.rs:70-87 | crates/data_flow/re_lenses/src/semantic/foxglove/packed_element_field.rs:90-115 — 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/store/re_log_types/src/example_components.rs:173— crates/store/re_log_types/src/example_components.rs:173-190 | crates/store/re_log_types/src/example_components.rs:278-295 — 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/utils/re_crash_handler/src/lib.rs:280— crates/utils/re_crash_handler/src/lib.rs:280-301 | crates/utils/re_memory/src/backtrace_native.rs:91-108 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (18 corresponding lines) docs/snippets/all/archetypes/line_strips3d_segments_simple.rs:3— docs/snippets/all/archetypes/line_strips3d_segments_simple.rs:3-21 | docs/snippets/all/archetypes/line_strips3d_simple.rs:3-20 — 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/top/re_viewer/src/web.rs:292— crates/top/re_viewer/src/web.rs:292-309 | crates/top/re_viewer/src/web.rs:313-331 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (18 corresponding lines) crates/store/re_chunk/src/unit_chunk.rs:77— crates/store/re_chunk/src/unit_chunk.rs:77-94 | crates/store/re_chunk/src/unit_chunk.rs:131-148 — 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/store_app/re_server/src/rerun_cloud/mod.rs:695— crates/store_app/re_server/src/rerun_cloud/mod.rs:695-713 | crates/store_app/re_server/src/rerun_cloud/mod.rs:719-736 — 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/data_flow/re_grpc_server/src/lib.rs:1283— crates/data_flow/re_grpc_server/src/lib.rs:1283-1300 | crates/data_flow/re_grpc_server/src/lib.rs:1302-1319 — 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/store_app/re_entity_db/src/entity_db.rs:1257— crates/store_app/re_entity_db/src/entity_db.rs:1257-1274 | crates/store_app/re_entity_db/src/entity_db.rs:1284-1301 — 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/store/re_log_encoding/src/rrd/encoder.rs:346— crates/store/re_log_encoding/src/rrd/encoder.rs:346-363 | crates/store/re_log_encoding/src/rrd/encoder.rs:373-391 — 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/store/re_chunk/src/chunk.rs:1743— crates/store/re_chunk/src/chunk.rs:1743-1762 | crates/store/re_protos/src/lib.rs:454-471 — 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) scripts/zombie_todos.py:429— scripts/zombie_todos.py:429-446 | scripts/zombie_todos.py:450-467 — 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 (8 corresponding lines) · ×12
Edited copy of a member (8 corresponding lines) crates/store_app/re_datafusion/src/pushdown_expressions.rs:25— crates/store_app/re_datafusion/src/pushdown_expressions.rs:25-32 | crates/store_app/re_datafusion/src/pushdown_expressions.rs:34-41 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) rerun_py/src/python_bridge.rs:2625— rerun_py/src/python_bridge.rs:2625-2634 | rerun_py/src/python_bridge.rs:2640-2647 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) crates/store/re_lenses_core/src/selector/eval.rs:71— crates/store/re_lenses_core/src/selector/eval.rs:71-78 | crates/store/re_lenses_core/src/selector/eval.rs:137-146 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) crates/store/re_log_types/src/index/time_cell.rs:136— crates/store/re_log_types/src/index/time_cell.rs:136-143 | crates/store/re_log_types/src/index/time_cell.rs:152-159 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) crates/store_app/re_datafusion/src/pipeline_budget/mod.rs:1020— crates/store_app/re_datafusion/src/pipeline_budget/mod.rs:1020-1031 | crates/store_app/re_datafusion/src/pipeline_budget/mod.rs:1067-1074 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) crates/views/re_view_map/src/visualizers/geo_line_strings.rs:137— crates/views/re_view_map/src/visualizers/geo_line_strings.rs:137-145 | crates/views/re_view_map/src/visualizers/geo_points.rs:150-157 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) crates/viewer_support/re_dataframe_ui/src/datafusion_table_widget.rs:1772— crates/viewer_support/re_dataframe_ui/src/datafusion_table_widget.rs:1772-1779 | crates/viewer_support/re_dataframe_ui/src/display_record_batch.rs:178-185 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) crates/store_app/re_query/src/latest_at.rs:314— crates/store_app/re_query/src/latest_at.rs:314-324 | crates/store_app/re_query/src/range.rs:128-135 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) crates/utils/re_video/src/h264.rs:191— crates/utils/re_video/src/h264.rs:191-204 | crates/utils/re_video/src/h265.rs:201-208 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) crates/data_flow/re_mcap/src/recover.rs:445— crates/data_flow/re_mcap/src/recover.rs:445-452 | rerun_py/src/chunk_stream/mcap_reader.rs:379-386 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) examples/python/minimal/minimal.py:15— examples/python/minimal/minimal.py:15-22 | examples/python/minimal_options/minimal_options.py:14-27 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) examples/python/ros_node/main.py:134— examples/python/ros_node/main.py:134-141 | examples/python/ros_node/main.py:144-151 — 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 (22 corresponding lines) · ×11
Edited copy of a member (22 corresponding lines) crates/store/re_protos/src/v1alpha1/rerun.cloud.v1alpha1.ext.asset_properties.rs:112— crates/store/re_protos/src/v1alpha1/rerun.cloud.v1alpha1.ext.asset_properties.rs:112-136 | crates/store/re_protos/src/v1alpha1/rerun.cloud.v1alpha1.ext.properties.rs:45-66 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (22 corresponding lines) rerun_py/src/catalog/dataset_entry.rs:567— rerun_py/src/catalog/dataset_entry.rs:567-588 | rerun_py/src/catalog/dataset_entry.rs:591-612 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (22 corresponding lines) rerun_py/rerun_sdk/rerun/encodings/mat3x3_ext.py:19— rerun_py/rerun_sdk/rerun/encodings/mat3x3_ext.py:19-40 | rerun_py/rerun_sdk/rerun/encodings/mat4x4_ext.py:18-39 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (22 corresponding lines) crates/views/re_view_graph/src/ui/draw.rs:140— crates/views/re_view_graph/src/ui/draw.rs:140-161 | crates/views/re_view_graph/src/ui/draw.rs:164-196 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (22 corresponding lines) crates/viewer_support/re_context_menu/src/actions/show_hide.rs:11— crates/viewer_support/re_context_menu/src/actions/show_hide.rs:11-32 | crates/viewer_support/re_context_menu/src/actions/show_hide.rs:71-92 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (22 corresponding lines) rerun_py/src/catalog/dataset_entry.rs:744— rerun_py/src/catalog/dataset_entry.rs:744-765 | rerun_py/src/catalog/dataset_entry.rs:889-913 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (22 corresponding lines) crates/viewer_support/re_data_ui/src/item_title.rs:202— crates/viewer_support/re_data_ui/src/item_title.rs:202-226 | crates/viewer_support/re_data_ui/src/item_title.rs:232-253 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (22 corresponding lines) crates/data_flow/re_lenses/src/semantic/foxglove/camera_calibration.rs:13— crates/data_flow/re_lenses/src/semantic/foxglove/camera_calibration.rs:13-38 | crates/data_flow/re_lenses/src/semantic/ros2msg/camera_info.rs:10-31 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (22 corresponding lines) crates/viewer_support/re_viewer_context/src/view/view_class_registry.rs:462— crates/viewer_support/re_viewer_context/src/view/view_class_registry.rs:462-485 | crates/viewer_support/re_viewer_context/src/view/view_class_registry.rs:490-511 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (22 corresponding lines) rerun_py/src/python_bridge.rs:2307— rerun_py/src/python_bridge.rs:2307-2328 | rerun_py/src/python_bridge.rs:2353-2377 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (22 corresponding lines) examples/python/structure_from_motion/structure_from_motion/read_write_model.py:226— examples/python/structure_from_motion/structure_from_motion/read_write_model.py:226-258 | examples/python/structure_from_motion/structure_from_motion/read_write_model.py:340-361 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (19 corresponding lines) · ×11
Edited copy of a member (19 corresponding lines) crates/ui_tools/re_renderer/src/colormap.rs:107— crates/ui_tools/re_renderer/src/colormap.rs:107-125 | crates/ui_tools/re_renderer/src/colormap.rs:142-169 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (19 corresponding lines) crates/viewer_support/re_viewer_context/src/cache/memoizers.rs:75— crates/viewer_support/re_viewer_context/src/cache/memoizers.rs:75-94 | crates/viewer_support/re_viewer_context/src/cache/memoizers.rs:237-255 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (19 corresponding lines) crates/top/re_sdk/src/recording_stream.rs:634— crates/top/re_sdk/src/recording_stream.rs:634-655 | crates/top/re_sdk/src/recording_stream.rs:2338-2356 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (19 corresponding lines) crates/panels/re_time_panel/src/recursive_chunks_per_timeline_subscriber.rs:177— crates/panels/re_time_panel/src/recursive_chunks_per_timeline_subscriber.rs:177-204 | crates/viewer_support/re_viewer_context/src/annotations.rs:358-376 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (19 corresponding lines) crates/store/re_lenses_core/src/selector/parser.rs:285— crates/store/re_lenses_core/src/selector/parser.rs:285-303 | crates/store/re_lenses_core/src/selector/parser.rs:423-441 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (19 corresponding lines) docs/snippets/all/archetypes/graph_directed.rs:3— docs/snippets/all/archetypes/graph_directed.rs:3-21 | docs/snippets/all/archetypes/graph_undirected.rs:3-22 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (19 corresponding lines) crates/store_app/re_tf/src/transform_resolution_cache/cached_transforms_for_timeline.rs:384— crates/store_app/re_tf/src/transform_resolution_cache/cached_transforms_for_timeline.rs:384-402 | crates/store_app/re_tf/src/transform_resolution_cache/cached_transforms_for_timeline.rs:408-433 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (19 corresponding lines) crates/store_app/re_datafusion/src/dataframe_query_provider/segment_store.rs:364— crates/store_app/re_datafusion/src/dataframe_query_provider/segment_store.rs:364-384 | crates/store_app/re_datafusion/src/pipeline/emitter.rs:104-122 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (19 corresponding lines) crates/store/re_log_types/src/path/entity_path_filter.rs:436— crates/store/re_log_types/src/path/entity_path_filter.rs:436-457 | crates/store/re_log_types/src/path/entity_path_filter.rs:463-481 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (19 corresponding lines) crates/top/re_sdk/src/global.rs:116— crates/top/re_sdk/src/global.rs:116-134 | crates/top/re_sdk/src/global.rs:140-158 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (19 corresponding lines) rerun_py/rerun_sdk/rerun/experimental/_viewer_client.py:1080— rerun_py/rerun_sdk/rerun/experimental/_viewer_client.py:1080-1104 | rerun_py/rerun_sdk/rerun/experimental/_viewer_client.py:1284-1302 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (7 corresponding lines) · ×11
Edited copy of a member (7 corresponding lines) crates/data_flow/re_lerobot/src/parse_v2.rs:198— crates/data_flow/re_lerobot/src/parse_v2.rs:198-204 | crates/data_flow/re_lerobot/src/parse_v3.rs:959-965 — 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) skills/rerun-lerobot/scripts/fetch_lerobot_episodes.py:54— skills/rerun-lerobot/scripts/fetch_lerobot_episodes.py:54-68 | skills/rerun-lerobot/scripts/find_lerobot_dataset.py:61-67 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) crates/data_flow/re_mcap/src/parsers/ros2msg/std_msgs/float64_multi_array.rs:24— crates/data_flow/re_mcap/src/parsers/ros2msg/std_msgs/float64_multi_array.rs:24-30 | crates/data_flow/re_mcap/src/parsers/ros2msg/std_msgs/float64_array.rs:24-30 — 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) rerun_py/src/catalog/dataset_selection.rs:160— rerun_py/src/catalog/dataset_selection.rs:160-172 | rerun_py/src/catalog/dataset_entry.rs:551-557 — 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/store/re_sorbet/src/column_descriptor.rs:77— crates/store/re_sorbet/src/column_descriptor.rs:77-83 | crates/store/re_sorbet/src/column_descriptor_ref.rs:19-25 — 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/ui_tools/re_renderer/src/allocator/cpu_write_gpu_read_belt.rs:762— crates/ui_tools/re_renderer/src/allocator/cpu_write_gpu_read_belt.rs:762-769 | crates/ui_tools/re_renderer/src/allocator/gpu_readback_belt.rs:515-521 — 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) rerun_py/rerun_sdk/rerun/archetypes/depth_image_ext.py:151— rerun_py/rerun_sdk/rerun/archetypes/depth_image_ext.py:151-157 | rerun_py/rerun_sdk/rerun/archetypes/image_ext.py:276-285 — 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/store_app/re_query/src/bin/clamped_zip.rs:49— crates/store_app/re_query/src/bin/clamped_zip.rs:49-55 | crates/store_app/re_query/src/bin/range_zip.rs:50-56 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) crates/store_app/re_query/src/bin/clamped_zip.rs:80— crates/store_app/re_query/src/bin/clamped_zip.rs:80-86 | crates/store_app/re_query/src/bin/range_zip.rs:88-94 — 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/viewer_support/re_context_menu/src/actions/move_contents_to_new_container.rs:33— crates/viewer_support/re_context_menu/src/actions/move_contents_to_new_container.rs:33-39 | crates/viewer_support/re_context_menu/src/actions/remove.rs:14-21 — 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/store/re_types_core/src/layer_name.rs:46— crates/store/re_types_core/src/layer_name.rs:46-56 | crates/store_app/re_catalog_client/src/blueprint.rs:28-34 — 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 (16 lines × 2) crates/panels/re_viewport/src/viewport_ui.rs:1221— crates/panels/re_viewport/src/viewport_ui.rs:1221-1236 | crates/panels/re_viewport/src/viewport_ui.rs:1243-1258 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/panels/re_viewport/src/viewport_ui.rs:1221` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `crates/panels/re_viewport/src/viewport_ui.rs:1236` calls `Some` and `crates/panels/re_viewport/src/viewport_ui.rs:1258` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (16 lines × 2) crates/top/re_viewer/src/app/viewer_control/mod.rs:1429— crates/top/re_viewer/src/app/viewer_control/mod.rs:1429-1444 | crates/top/re_viewer/src/app/viewer_control/mod.rs:1504-1519 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/top/re_viewer/src/app/viewer_control/mod.rs:1429` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) crates/top/re_viewer/src/web.rs:359— crates/top/re_viewer/src/web.rs:359-374 | crates/top/re_viewer/src/web.rs:797-812 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/top/re_viewer/src/web.rs:359` 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/ui_tools/re_renderer/src/resource_managers/bayer_converter.rs:151— crates/ui_tools/re_renderer/src/resource_managers/bayer_converter.rs:151-166 | crates/ui_tools/re_renderer/src/resource_managers/yuv_converter.rs:457-472 — before extracting anything, compare `crates/ui_tools/re_renderer/src/resource_managers/bayer_converter.rs` and `crates/ui_tools/re_renderer/src/resource_managers/yuv_converter.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 99 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 (16 lines × 2) crates/utils/re_crash_handler/src/lib.rs:257— crates/utils/re_crash_handler/src/lib.rs:257-272 | crates/utils/re_memory/src/backtrace_native.rs:68-83 — 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/utils/re_crash_handler/src/lib.rs:257` 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/utils/re_video/src/decode/rvl_decoder.rs:39— crates/utils/re_video/src/decode/rvl_decoder.rs:39-54 | crates/utils/re_video/src/decode/tiff_decoder.rs:25-40 — 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/utils/re_video/src/decode/rvl_decoder.rs:39` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) crates/views/re_view_dataframe/src/view_query/ui.rs:97— crates/views/re_view_dataframe/src/view_query/ui.rs:97-112 | crates/views/re_view_dataframe/src/view_query/ui.rs:138-153 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/views/re_view_dataframe/src/view_query/ui.rs:97` 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/views/re_view_spatial/src/visualizers/images.rs:154— crates/views/re_view_spatial/src/visualizers/images.rs:154-169 | crates/views/re_view_spatial/src/visualizers/segmentation_images.rs:119-134 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `crates/views/re_view_spatial/src/visualizers/images.rs:154` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `crates/views/re_view_spatial/src/visualizers/segmentation_images.rs:117` calls `default` and `crates/views/re_view_spatial/src/visualizers/images.rs:152` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (16 lines × 2) crates/views/re_view_spatial/src/visualizers/points2d.rs:224— crates/views/re_view_spatial/src/visualizers/points2d.rs:224-239 | crates/views/re_view_spatial/src/visualizers/points3d.rs:389-404 — before extracting anything, compare `crates/views/re_view_spatial/src/visualizers/points2d.rs` and `crates/views/re_view_spatial/src/visualizers/points3d.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 66 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 (16 lines × 2) crates/store/re_sdk_types/src/ply.rs:78— crates/store/re_sdk_types/src/ply.rs:78-93 | crates/ui_tools/re_renderer/src/importer/ply.rs:55-70 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (16 lines × 2) crates/ui_tools/re_renderer/src/renderer/gaussian_splat.rs:746— crates/ui_tools/re_renderer/src/renderer/gaussian_splat.rs:746-763 | crates/ui_tools/re_renderer/src/renderer/point_cloud.rs:760-775 — before extracting anything, compare `crates/ui_tools/re_renderer/src/renderer/gaussian_splat.rs` and `crates/ui_tools/re_renderer/src/renderer/point_cloud.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 207 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/ui_tools/re_renderer/src/renderer/gaussian_splat.rs:746` 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.
AC6 · Visual & motion safety· Animation without a prefers-reduced-motion guard · ×10
Animation without a prefers-reduced-motion guard rerun_js/web-viewer/index.ts:1670— <div> moves — its inline style sets `transition: width 0.2s` — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
Animation without a prefers-reduced-motion guard rerun_py/rerun_sdk/rerun/_loading_widget.css:23— `.rerun-notebook-loading__spinner` moves (`animation: rerun-notebook-spin 0.8s linear infinite`) 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 rerun_cpp/docs/doxygen-awesome/doxygen-awesome.css:464— `.sm-dox ul` moves (`animation: ease-out 150ms slideInMenu`) 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 rerun_cpp/docs/doxygen-awesome/doxygen-awesome.css:664— `#MSearchResultsWindow` moves (`animation: ease-out 280ms slideInSearchResults`) 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 rerun_cpp/docs/doxygen-awesome/doxygen-awesome.css:750— `#MSearchResultsWindow` moves (`animation: ease-out 280ms slideInSearchResultsMobile`) 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 rerun_cpp/docs/doxygen-awesome/doxygen-awesome.css:1177— `div.contents .toc.interactive > h3::before` moves (`transition: transform 0.25s ease-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 rerun_cpp/docs/doxygen-awesome/doxygen-awesome.css:1187— `div.contents .toc.interactive.open` moves (`transition: max-height 0.2s 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 rerun_cpp/docs/doxygen-awesome/doxygen-awesome.css:1869— `table.memberdecls img[src="closed.png"]` moves (`transition: transform 0.25s ease-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 rerun_cpp/docs/doxygen-awesome/doxygen-awesome.css:1948— `table.memberdecls tr[style="display: table-row "]` moves (`animation: fade .5s`) 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 rerun_cpp/docs/doxygen-awesome/doxygen-awesome.css:2347— `doxygen-awesome-dark-mode-toggle > svg` moves (`transition: transform .1s 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.
AppCore::run_system_command (cyclomatic 97) crates/top/re_viewer/src/app/command_handling.rs:120— AppCore::run_system_command has cyclomatic complexity 97 (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.
AppCore::run_ui_command (cyclomatic 61) crates/top/re_viewer/src/app/command_handling.rs:883— AppCore::run_ui_command has cyclomatic complexity 61 (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.
AppCore::route_ui (cyclomatic 41) crates/top/re_viewer/src/app/route_ui.rs:35— AppCore::route_ui 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.
AppCore::frame_ui (cyclomatic 36) crates/top/re_viewer/src/app/mod.rs:1534— AppCore::frame_ui has cyclomatic complexity 36 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AppCore::serve_viewer_control (cyclomatic 36) crates/top/re_viewer/src/app/viewer_control/mod.rs:333— AppCore::serve_viewer_control has cyclomatic complexity 36 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
AppCore::run_recording_command (cyclomatic 35) crates/top/re_viewer/src/app/command_handling.rs:1296— AppCore::run_recording_command has cyclomatic complexity 35 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AppCore::load_data_source (cyclomatic 21) crates/top/re_viewer/src/app/add_data_source.rs:72— AppCore::load_data_source 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.
AppCore::is_back_destination_open (cyclomatic 20) crates/top/re_viewer/src/app/command_handling.rs:1684— AppCore::is_back_destination_open 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.
AppCore::receive_messages (cyclomatic 17) crates/top/re_viewer/src/app/logic.rs:159— AppCore::receive_messages 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.
AppCore::receive_log_msg (cyclomatic 17) crates/top/re_viewer/src/app/logic.rs:356— AppCore::receive_log_msg 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.
re_viewer_context::view::visualizer_entity_subscriber::process_entity_components (cognitive 50) crates/viewer_support/re_viewer_context/src/view/visualizer_entity_subscriber.rs:183— re_viewer_context::view::visualizer_entity_subscriber::process_entity_components has cognitive complexity 50 (threshold 15). Drivers by points: if/else 13 (37 pts), loops 3 (8 pts), boolean chains 4, match/switch 1 (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.
re_viewer_context::cache::video_stream_cache::handle_out_of_order_chunk (cognitive 28) crates/viewer_support/re_viewer_context/src/cache/video_stream_cache/mod.rs:2095— re_viewer_context::cache::video_stream_cache::handle_out_of_order_chunk has cognitive complexity 28 (threshold 15). Drivers by points: if/else 14 (22 pts), loops 4 (5 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_viewer_context::cache::video_stream_cache::handle_deletion (cognitive 26) crates/viewer_support/re_viewer_context/src/cache/video_stream_cache/mod.rs:521— re_viewer_context::cache::video_stream_cache::handle_deletion has cognitive complexity 26 (threshold 15). Drivers by points: if/else 18 (23 pts), loops 2 (3 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.
re_viewer_context::cache::video_stream_cache::update_sample_durations (cognitive 23) crates/viewer_support/re_viewer_context/src/cache/video_stream_cache/mod.rs:1263— re_viewer_context::cache::video_stream_cache::update_sample_durations has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (15 pts), boolean chains 3, loops 3, match/switch 1 (2 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_viewer_context::cache::video_stream_cache::find_affected_sample_range (cognitive 23) crates/viewer_support/re_viewer_context/src/cache/video_stream_cache/mod.rs:1981— re_viewer_context::cache::video_stream_cache::find_affected_sample_range has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (18 pts), boolean chains 4, 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.
re_viewer_context::relative_time_range::edit_boundary_ui (cognitive 23) crates/viewer_support/re_viewer_context/src/relative_time_range.rs:43— re_viewer_context::relative_time_range::edit_boundary_ui has cognitive complexity 23 (threshold 15). Drivers by points: if/else 13 (17 pts), match/switch 4 (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.
re_viewer_context::gpu_bridge::image_to_gpu::color_image_to_gpu (cognitive 21) crates/viewer_support/re_viewer_context/src/gpu_bridge/image_to_gpu.rs:72— re_viewer_context::gpu_bridge::image_to_gpu::color_image_to_gpu has cognitive complexity 21 (threshold 15). Drivers by points: if/else 15 (16 pts), match/switch 2 (3 pts), boolean chains 2 (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.
re_viewer_context::cache::video_stream_cache::handle_compacted_chunk_addition (cognitive 20) crates/viewer_support/re_viewer_context/src/cache/video_stream_cache/mod.rs:686— re_viewer_context::cache::video_stream_cache::handle_compacted_chunk_addition has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (12 pts), loops 5 (7 pts), boolean chains 1 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
re_viewer_context::gpu_bridge::image_to_gpu::texture_creation_desc_from_color_image (cognitive 19) crates/viewer_support/re_viewer_context/src/gpu_bridge/image_to_gpu.rs:253— re_viewer_context::gpu_bridge::image_to_gpu::texture_creation_desc_from_color_image has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (13 pts), match/switch 3 (6 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_viewer_context::cache::video_stream_cache::load_known_chunk_ranges (cognitive 16) crates/viewer_support/re_viewer_context/src/cache/video_stream_cache/mod.rs:1872— re_viewer_context::cache::video_stream_cache::load_known_chunk_ranges has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (10 pts), loops 2 (4 pts), boolean chains 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D4 · Code Duplication· Edited copy of a member (24 corresponding lines) · ×10
Edited copy of a member (24 corresponding lines) crates/utils/re_format/src/lib.rs:598— crates/utils/re_format/src/lib.rs:598-621 | crates/utils/re_format/src/lib.rs:649-672 — 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/utils/re_ros_msg/src/deserialize/mod.rs:197— crates/utils/re_ros_msg/src/deserialize/mod.rs:197-220 | crates/utils/re_ros_msg/src/deserialize/mod.rs:226-256 — 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/views/re_view_graph/src/layout/provider.rs:121— crates/views/re_view_graph/src/layout/provider.rs:121-144 | crates/views/re_view_graph/src/layout/provider.rs:150-183 — 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/views/re_view_spatial/src/view_2d.rs:236— crates/views/re_view_spatial/src/view_2d.rs:236-260 | crates/views/re_view_spatial/src/view_3d.rs:503-526 — 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) rerun_pixi_env/src/rerun_pixi_env/__init__.py:114— rerun_pixi_env/src/rerun_pixi_env/__init__.py:114-139 | rerun_pixi_env/src/rerun_pixi_env/__init__.py:143-166 — 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/views/re_view_audio/src/view_class.rs:113— crates/views/re_view_audio/src/view_class.rs:113-141 | crates/views/re_view_state_timeline/src/view_class.rs:94-117 — 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/store_app/re_datafusion/src/dataframe_query_common/projection.rs:26— crates/store_app/re_datafusion/src/dataframe_query_common/projection.rs:26-50 | crates/store_app/re_datafusion/src/dataframe_query_common/projection.rs:107-130 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (24 corresponding lines) examples/python/structure_from_motion/structure_from_motion/read_write_model.py:191— examples/python/structure_from_motion/structure_from_motion/read_write_model.py:191-222 | examples/python/structure_from_motion/structure_from_motion/read_write_model.py:313-336 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (24 corresponding lines) examples/python/structure_from_motion/structure_from_motion/read_write_model.py:262— examples/python/structure_from_motion/structure_from_motion/read_write_model.py:262-288 | examples/python/structure_from_motion/structure_from_motion/read_write_model.py:365-388 — 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) scripts/append_web_viewer.py:65— scripts/append_web_viewer.py:65-88 | scripts/create_web_viewer_zip.py:60-86 — 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) · ×10
Edited copy of a member (25 corresponding lines) crates/store/re_log_types/src/example_components.rs:196— crates/store/re_log_types/src/example_components.rs:196-220 | crates/store/re_log_types/src/example_components.rs:301-325 — 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/ui_tools/re_renderer/src/draw_phases/outlines.rs:356— crates/ui_tools/re_renderer/src/draw_phases/outlines.rs:356-380 | crates/ui_tools/re_renderer/src/draw_phases/picking_layer.rs:315-345 — 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) docs/snippets/all/archetypes/state_configuration.rs:3— docs/snippets/all/archetypes/state_configuration.rs:3-27 | docs/snippets/all/howto/state_timeline.rs:3-40 — 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/data_flow/re_lenses/src/semantic/ros2msg/compressed_image.rs:25— crates/data_flow/re_lenses/src/semantic/ros2msg/compressed_image.rs:25-58 | crates/data_flow/re_lenses/src/semantic/ros2msg/image.rs:12-36 — 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/viewer_support/re_view/src/visualizer_query.rs:76— crates/viewer_support/re_view/src/visualizer_query.rs:76-105 | crates/viewer_support/re_view/src/visualizer_query.rs:122-146 — 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/views/re_view_spatial/src/visualizers/grid_map.rs:83— crates/views/re_view_spatial/src/visualizers/grid_map.rs:83-107 | crates/views/re_view_spatial/src/visualizers/images.rs:56-80 — 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/views/re_view_raw_data/src/component_time_stepping.rs:14— crates/views/re_view_raw_data/src/component_time_stepping.rs:14-41 | crates/views/re_view_raw_data/src/component_time_stepping.rs:76-100 — 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/top/re_sdk/src/log_sink.rs:76— crates/top/re_sdk/src/log_sink.rs:76-100 | crates/top/re_sdk/src/recording_stream.rs:2523-2547 — 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/store/re_sorbet/src/index_column_descriptor.rs:100— crates/store/re_sorbet/src/index_column_descriptor.rs:100-124 | crates/store/re_sorbet/src/row_id_column_descriptor.rs:43-68 — 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) scripts/run_all.py:244— scripts/run_all.py:244-275 | scripts/run_all.py:319-343 — 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.
R4 · Test Coverage· No test reaches this file · ×10
No test reaches this file rerun_notebook/src/js/widget.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file rerun_js/web-viewer-react/index.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file rerun_js/web-viewer/typedoc-used-by.mjs:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file rerun_js/scripts/common.mjs:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file REDACTED:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file rerun_js/scripts/version.mjs:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file rerun_js/scripts/publish.mjs:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file rerun_notebook/src/rerun_notebook/error_widget.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file rerun_notebook/build.mjs:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file rerun_js/scripts/docs.mjs:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
re_types_builder::codegen::rust::serializer::quote_arrow_field_serializer (cyclomatic 42) crates/build/re_types_builder/src/codegen/rust/serializer.rs:568— re_types_builder::codegen::rust::serializer::quote_arrow_field_serializer has cyclomatic complexity 42 (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.
re_types_builder::codegen::python::code_for_struct (cyclomatic 40) crates/build/re_types_builder/src/codegen/python/mod.rs:735— re_types_builder::codegen::python::code_for_struct has cyclomatic complexity 40 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
re_types_builder::codegen::python::quote_arrow_serialization (cyclomatic 30) crates/build/re_types_builder/src/codegen/python/mod.rs:2343— re_types_builder::codegen::python::quote_arrow_serialization has cyclomatic complexity 30 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
re_types_builder::codegen::rust::serializer::quote_arrow_serializer (cyclomatic 22) crates/build/re_types_builder/src/codegen/rust/serializer.rs:54— re_types_builder::codegen::rust::serializer::quote_arrow_serializer has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
re_types_builder::codegen::python::check_ext_consistency (cyclomatic 21) crates/build/re_types_builder/src/codegen/python/mod.rs:309— re_types_builder::codegen::python::check_ext_consistency 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.
re_types_builder::codegen::rust::deserializer::quote_arrow_deserializer (cyclomatic 18) crates/build/re_types_builder/src/codegen/rust/deserializer.rs:61— re_types_builder::codegen::rust::deserializer::quote_arrow_deserializer has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
re_types_builder::codegen::rust::deserializer::quote_arrow_field_deserializer (cyclomatic 18) crates/build/re_types_builder/src/codegen/rust/deserializer.rs:536— re_types_builder::codegen::rust::deserializer::quote_arrow_field_deserializer has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
re_types_builder::docs::doclink_translation::try_translate_doclink (cyclomatic 17) crates/build/re_types_builder/src/docs.rs:317— re_types_builder::docs::doclink_translation::try_translate_doclink 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.
re_types_builder::codegen::python::code_for_union (cyclomatic 16) crates/build/re_types_builder/src/codegen/python/mod.rs:1207— re_types_builder::codegen::python::code_for_union has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This is NOT this file's highest cyclomatic complexity: re_types_builder::codegen::python::quote_arrow_datatype (cyclomatic 21) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded function is counted neither in this dimension's figures nor in its score.
re_datafusion::dataframe_query_provider::cpu_worker::chunk_store_cpu_worker_thread (cognitive 76) crates/store_app/re_datafusion/src/dataframe_query_provider/cpu_worker.rs:304— re_datafusion::dataframe_query_provider::cpu_worker::chunk_store_cpu_worker_thread has cognitive complexity 76 (threshold 15). Drivers by points: if/else 23 (61 pts), match/switch 4 (7 pts), loops 3 (5 pts), boolean chains 3 (nesting depth added 43). 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.
re_datafusion::dataframe_query_provider::io_loop::chunk_stream_io_loop (cognitive 32) crates/store_app/re_datafusion/src/dataframe_query_provider/io_loop.rs:694— re_datafusion::dataframe_query_provider::io_loop::chunk_stream_io_loop has cognitive complexity 32 (threshold 15). Drivers by points: if/else 9 (16 pts), match/switch 4 (10 pts), loops 3 (5 pts), boolean chains 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_datafusion::pushdown_expressions::merge_queries_and (cognitive 30) crates/store_app/re_datafusion/src/pushdown_expressions.rs:736— re_datafusion::pushdown_expressions::merge_queries_and has cognitive complexity 30 (threshold 15). Drivers by points: if/else 12 (25 pts), match/switch 1 (3 pts), boolean chains 2 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_datafusion::dataframe_query_provider::fetch_plan::create_request_batches_with_segment_limit (cognitive 28) crates/store_app/re_datafusion/src/dataframe_query_provider/fetch_plan.rs:214— re_datafusion::dataframe_query_provider::fetch_plan::create_request_batches_with_segment_limit has cognitive complexity 28 (threshold 15). Drivers by points: if/else 10 (20 pts), boolean chains 4, loops 2 (4 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.
re_datafusion::pipeline::plan::build_fetch_plan (cognitive 26) crates/store_app/re_datafusion/src/pipeline/plan.rs:207— re_datafusion::pipeline::plan::build_fetch_plan has cognitive complexity 26 (threshold 15). Drivers by points: if/else 8 (17 pts), loops 3 (4 pts), boolean chains 3, match/switch 1 (2 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.
re_datafusion::pipeline::driver::advance_head (cognitive 22) crates/store_app/re_datafusion/src/pipeline/driver.rs:347— re_datafusion::pipeline::driver::advance_head has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (20 pts), boolean chains 1, loops 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_datafusion::pushdown_expressions::apply_filter_expr_to_queries (cognitive 22) crates/store_app/re_datafusion/src/pushdown_expressions.rs:465— re_datafusion::pushdown_expressions::apply_filter_expr_to_queries has cognitive complexity 22 (threshold 15). Drivers by points: match/switch 5 (12 pts), if/else 5 (10 pts) (nesting depth added 12). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
re_datafusion::chunk_fetcher::fetch_batch_via_direct_urls (cognitive 21) crates/store_app/re_datafusion/src/chunk_fetcher/mod.rs:703— re_datafusion::chunk_fetcher::fetch_batch_via_direct_urls has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (14 pts), match/switch 2 (4 pts), loops 3 (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.
re_datafusion::pushdown_expressions::known_filter_column (cognitive 16) crates/store_app/re_datafusion/src/pushdown_expressions.rs:677— re_datafusion::pushdown_expressions::known_filter_column has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (9 pts), match/switch 2 (6 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
rerun::commands::rrd::route::process_messages (cognitive 45) crates/top/rerun/src/commands/rrd/route.rs:104— rerun::commands::rrd::route::process_messages has cognitive complexity 45 (threshold 15). Drivers by points: if/else 8 (25 pts), loops 6 (11 pts), match/switch 3 (8 pts), 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.
rerun::commands::entrypoint::assert_receive_into_entity_db (cognitive 32) crates/top/rerun/src/commands/entrypoint.rs:1697— rerun::commands::entrypoint::assert_receive_into_entity_db has cognitive complexity 32 (threshold 15). Drivers by points: match/switch 5 (18 pts), if/else 6 (13 pts), loops 1 (nesting depth added 20). 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.
rerun::commands::entrypoint::run_impl (cognitive 22) crates/top/rerun/src/commands/entrypoint.rs:1044— rerun::commands::entrypoint::run_impl has cognitive complexity 22 (threshold 15). Drivers by points: if/else 14 (16 pts), boolean chains 6 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
rerun::commands::rrd::merge_optimize::optimize_dir_mirror (cognitive 20) crates/top/rerun/src/commands/rrd/merge_optimize.rs:312— rerun::commands::rrd::merge_optimize::optimize_dir_mirror has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (15 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
rerun::commands::entrypoint::start_native_viewer (cognitive 18) crates/top/rerun/src/commands/entrypoint.rs:1228— rerun::commands::entrypoint::start_native_viewer has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (13 pts), loops 3, boolean chains 1, match/switch 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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.
rerun::commands::rrd::print::print_msg (cognitive 18) crates/top/rerun/src/commands/rrd/print.rs:203— rerun::commands::rrd::print::print_msg has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (9 pts), match/switch 3 (7 pts), boolean chains 2 (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.
rerun::commands::entrypoint::connect_to_existing_server (cognitive 16) crates/top/rerun/src/commands/entrypoint.rs:1490— rerun::commands::entrypoint::connect_to_existing_server has cognitive complexity 16 (threshold 15). Drivers by points: loops 3 (6 pts), if/else 2 (5 pts), match/switch 1 (5 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
rerun::commands::rrd::merge_optimize::merge_and_compact (cognitive 16) crates/top/rerun/src/commands/rrd/merge_optimize.rs:428— rerun::commands::rrd::merge_optimize::merge_and_compact has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (12 pts), match/switch 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
rerun::commands::rrd::stats::compute_stats (cognitive 16) crates/top/rerun/src/commands/rrd/stats.rs:671— rerun::commands::rrd::stats::compute_stats has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (10 pts), boolean chains 3, match/switch 1 (3 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D4 · Code Duplication· Edited copy of a member (17 corresponding lines) · ×9
Edited copy of a member (17 corresponding lines) crates/top/rerun/src/commands/mcap/mod.rs:131— crates/top/rerun/src/commands/mcap/mod.rs:131-147 | rerun_py/src/chunk_stream/mcap_reader.rs:540-563 — 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) rerun_py/rerun_sdk/rerun/encodings/class_description_map_elem_ext.py:34— rerun_py/rerun_sdk/rerun/encodings/class_description_map_elem_ext.py:34-50 | rerun_py/rerun_sdk/rerun/encodings/keypoint_pair_ext.py:31-47 — 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/data_flow/re_mcap/src/decoders/protobuf.rs:190— crates/data_flow/re_mcap/src/decoders/protobuf.rs:190-216 | crates/data_flow/re_mcap/src/decoders/raw.rs:36-52 — 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/store/re_chunk_store/src/events.rs:51— crates/store/re_chunk_store/src/events.rs:51-67 | crates/store/re_chunk_store/src/events.rs:398-417 — 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/top/rerun_c/src/lib.rs:1227— crates/top/rerun_c/src/lib.rs:1227-1243 | crates/top/rerun_c/src/lib.rs:1268-1290 — 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/store/re_types_core/src/chunk_id.rs:69— crates/store/re_types_core/src/chunk_id.rs:69-85 | crates/store/re_types_core/src/row_id.rs:82-98 — 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/store_app/re_entity_db/src/rrd_manifest_index/time_range_merger.rs:406— crates/store_app/re_entity_db/src/rrd_manifest_index/time_range_merger.rs:406-422 | crates/store_app/re_entity_db/src/rrd_manifest_index/time_range_merger.rs:428-444 — 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/panels/re_time_panel/src/time_panel.rs:1665— crates/panels/re_time_panel/src/time_panel.rs:1665-1681 | crates/viewer_support/re_data_ui/src/instance_path_ui.rs:526-543 — 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/store/re_chunk/src/chunk.rs:324— crates/store/re_chunk/src/chunk.rs:324-340 | crates/store/re_chunk/src/chunk.rs:469-486 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (16 corresponding lines) · ×9
Edited copy of a member (16 corresponding lines) crates/data_flow/re_lenses/src/semantic/ros2msg/ros_map_helpers.rs:22— crates/data_flow/re_lenses/src/semantic/ros2msg/ros_map_helpers.rs:22-37 | crates/data_flow/re_lenses/src/semantic/ros2msg/voxel_grid.rs:279-298 — 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/ui_tools/re_ui/src/fuzzy.rs:145— crates/ui_tools/re_ui/src/fuzzy.rs:145-160 | crates/ui_tools/re_ui/src/fuzzy.rs:172-198 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) crates/store/re_lenses_core/src/selector/parser.rs:362— crates/store/re_lenses_core/src/selector/parser.rs:362-377 | crates/store/re_lenses_core/src/selector/parser.rs:487-502 — 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/top/rerun_c/src/lib.rs:479— crates/top/rerun_c/src/lib.rs:479-494 | crates/top/rerun_c/src/lib.rs:992-1007 — 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/store/re_lenses_core/src/combinators/map.rs:246— crates/store/re_lenses_core/src/combinators/map.rs:246-261 | crates/store/re_lenses_core/src/combinators/map.rs:296-311 — 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/panels/re_redap_browser/src/asset_coverage_modal.rs:684— crates/panels/re_redap_browser/src/asset_coverage_modal.rs:684-701 | crates/panels/re_redap_browser/src/register_asset_modal.rs:146-161 — 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/store_app/re_tf/src/transform_queries.rs:570— crates/store_app/re_tf/src/transform_queries.rs:570-585 | crates/store_app/re_tf/src/transform_queries.rs:596-611 — 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) examples/python/structure_from_motion/structure_from_motion/read_write_model.py:292— examples/python/structure_from_motion/structure_from_motion/read_write_model.py:292-309 | examples/python/structure_from_motion/structure_from_motion/read_write_model.py:392-407 — 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/viewer_support/re_viewer_context/src/cache/video_stream_cache/test_player/encoded_depth_image.rs:37— crates/viewer_support/re_viewer_context/src/cache/video_stream_cache/test_player/encoded_depth_image.rs:37-52 | crates/viewer_support/re_viewer_context/src/cache/video_stream_cache/test_player/encoded_image.rs:41-56 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (15 corresponding lines) · ×9
Edited copy of a member (15 corresponding lines) crates/store/re_sorbet/src/column_kind.rs:41— crates/store/re_sorbet/src/column_kind.rs:41-60 | crates/store/re_sorbet/src/migrations/v0_0_1__to__v0_0_2.rs:66-80 — 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/viewer_support/re_viewer_context/src/app_context.rs:472— crates/viewer_support/re_viewer_context/src/app_context.rs:472-486 | crates/viewer_support/re_viewer_context/src/blueprint_helpers.rs:200-214 — 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/store_app/re_entity_db/src/entity_db.rs:1210— crates/store_app/re_entity_db/src/entity_db.rs:1210-1224 | crates/store_app/re_entity_db/src/entity_db.rs:1233-1247 — 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/ui_tools/re_arrow_ui/src/show_index.rs:317— crates/ui_tools/re_arrow_ui/src/show_index.rs:317-333 | crates/ui_tools/re_arrow_ui/src/show_index.rs:360-374 — 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/store/re_protos/src/v1alpha1/rerun.cloud.v1alpha1.ext.rs:91— crates/store/re_protos/src/v1alpha1/rerun.cloud.v1alpha1.ext.rs:91-105 | crates/store/re_protos/src/v1alpha1/rerun.cloud.v1alpha1.ext.rs:111-125 — 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/ui_tools/re_renderer/src/renderer/gaussian_splat.rs:307— crates/ui_tools/re_renderer/src/renderer/gaussian_splat.rs:307-321 | crates/ui_tools/re_renderer/src/renderer/point_cloud.rs:303-317 — 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) docs/snippets/all/archetypes/scalars_row_updates.rs:5— docs/snippets/all/archetypes/scalars_row_updates.rs:5-19 | docs/snippets/all/archetypes/scalars_simple.rs:3-17 — 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/viewer_support/re_context_menu/src/actions/lock_unlock.rs:34— crates/viewer_support/re_context_menu/src/actions/lock_unlock.rs:34-48 | crates/viewer_support/re_context_menu/src/actions/lock_unlock.rs:73-87 — 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) rerun_py/src/catalog/dataset_selection.rs:180— rerun_py/src/catalog/dataset_selection.rs:180-194 | rerun_py/src/catalog/dataset_selection.rs:202-216 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (5 corresponding lines) · ×9
Edited copy of a member (5 corresponding lines) crates/store_app/re_datafusion/src/dataframe_query_common/segment_stream_common.rs:124— crates/store_app/re_datafusion/src/dataframe_query_common/segment_stream_common.rs:124-128 | crates/store_app/re_datafusion/src/dataframe_query_provider_wasm.rs:288-292 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (5 corresponding lines) rerun_py/src/catalog/dataset_entry.rs:162— rerun_py/src/catalog/dataset_entry.rs:162-166 | rerun_py/src/catalog/table_entry.rs:53-57 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (5 corresponding lines) crates/store/re_log_types/src/app_id.rs:185— crates/store/re_log_types/src/app_id.rs:185-189 | crates/store/re_types_core/src/layer_name.rs:183-187 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (5 corresponding lines) crates/store_app/re_query/src/bin/clamped_zip.rs:42— crates/store_app/re_query/src/bin/clamped_zip.rs:42-46 | crates/store_app/re_query/src/bin/range_zip.rs:43-47 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (5 corresponding lines) crates/store_app/re_query/src/bin/clamped_zip.rs:73— crates/store_app/re_query/src/bin/clamped_zip.rs:73-77 | crates/store_app/re_query/src/bin/range_zip.rs:74-78 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (5 corresponding lines) crates/store_app/re_query/src/bin/clamped_zip.rs:110— crates/store_app/re_query/src/bin/clamped_zip.rs:110-114 | crates/store_app/re_query/src/bin/range_zip.rs:81-85 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (5 corresponding lines) crates/viewer_support/re_dataframe_ui/src/filters/boolean.rs:305— crates/viewer_support/re_dataframe_ui/src/filters/boolean.rs:305-309 | crates/viewer_support/re_dataframe_ui/src/filters/string.rs:42-46 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (5 corresponding lines) crates/top/re_sdk/src/grpc_server.rs:83— crates/top/re_sdk/src/grpc_server.rs:83-87 | crates/top/re_sdk/src/web_viewer.rs:105-109 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (5 corresponding lines) examples/python/objectron/objectron/download_dataset.py:32— examples/python/objectron/objectron/download_dataset.py:32-38 | examples/python/human_pose_tracking/human_pose_tracking.py:193-197 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Low cohesion: ViewCoordinates (LCOM4 5) crates/build/re_type_definitions/rerun/archetypes/view_coordinates.def.rs:25— ViewCoordinates's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: TensorData (LCOM4 5) crates/build/re_type_definitions/rerun/components/tensor_data.def.rs:16— TensorData's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: TilesDelegate (LCOM4 5) crates/panels/re_viewport/src/viewport_ui.rs:292— TilesDelegate's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: ImageFormat (LCOM4 4) crates/build/re_type_definitions/rerun/components/image_format.def.rs:9— ImageFormat's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: McapImporter (LCOM4 4) crates/data_flow/re_importer/src/importer_mcap/importer.rs:33— McapImporter's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Chunk (LCOM4 4) crates/store/re_chunk/src/chunk.rs:242— Chunk's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: UnitChunkShared (LCOM4 4) crates/store/re_chunk/src/unit_chunk.rs:181— UnitChunkShared's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: RerunCloudHandler (LCOM4 4) crates/store_app/re_server/src/rerun_cloud/mod.rs:274— RerunCloudHandler's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: History (LCOM4 4) crates/top/re_viewer/src/history.rs:11— History's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
re_data_ui::entity_db_ui::grid_content_ui (cognitive 35) crates/viewer_support/re_data_ui/src/entity_db_ui.rs:102— re_data_ui::entity_db_ui::grid_content_ui has cognitive complexity 35 (threshold 15). Drivers by points: if/else 20 (29 pts), boolean chains 4, loops 1 (2 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_data_ui::video_ui::video_data_ui (cognitive 35) crates/viewer_support/re_data_ui/src/video_ui.rs:93— re_data_ui::video_ui::video_data_ui has cognitive complexity 35 (threshold 15). Drivers by points: if/else 16 (28 pts), match/switch 1 (3 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_data_ui::video_ui::decoded_frame_ui (cognitive 33) crates/viewer_support/re_data_ui/src/video_ui.rs:390— re_data_ui::video_ui::decoded_frame_ui has cognitive complexity 33 (threshold 15). Drivers by points: if/else 14 (25 pts), match/switch 2 (6 pts), boolean chains 2 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_data_ui::item_ui::entity_db_button_ui (cognitive 26) crates/viewer_support/re_data_ui/src/item_ui.rs:472— re_data_ui::item_ui::entity_db_button_ui has cognitive complexity 26 (threshold 15). Drivers by points: if/else 17 (19 pts), match/switch 2 (4 pts), boolean chains 3 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
re_data_ui::item_ui::entity_tree_stats_ui (cognitive 22) crates/viewer_support/re_data_ui/src/item_ui.rs:172— re_data_ui::item_ui::entity_tree_stats_ui has cognitive complexity 22 (threshold 15). Drivers by points: if/else 14 (17 pts), match/switch 1 (4 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
re_data_ui::instance_path_ui::component_list_ui (cognitive 21) crates/viewer_support/re_data_ui/src/instance_path_ui.rs:292— re_data_ui::instance_path_ui::component_list_ui has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (14 pts), loops 3 (5 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.
re_data_ui::video_ui::frame_info_ui (cognitive 20) crates/viewer_support/re_data_ui/src/video_ui.rs:535— re_data_ui::video_ui::frame_info_ui has cognitive complexity 20 (threshold 15). Drivers by points: if/else 12 (15 pts), boolean chains 5 (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.
re_data_ui::instance_path_ui::component_ui (cognitive 17) crates/viewer_support/re_data_ui/src/instance_path_ui.rs:372— re_data_ui::instance_path_ui::component_ui has cognitive complexity 17 (threshold 15). Drivers by points: if/else 15 (16 pts), boolean chains 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D4 · Code Duplication· Edited copy of a member (21 corresponding lines) · ×8
Edited copy of a member (21 corresponding lines) crates/top/rerun/src/demo_util.rs:105— crates/top/rerun/src/demo_util.rs:105-128 | crates/ui_tools/re_renderer/src/colormap.rs:240-260 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (21 corresponding lines) crates/utils/re_crash_handler/src/lib.rs:252— crates/utils/re_crash_handler/src/lib.rs:252-272 | crates/utils/re_memory/src/backtrace_native.rs:63-83 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (21 corresponding lines) crates/utils/re_auth/src/oauth/api.rs:64— crates/utils/re_auth/src/oauth/api.rs:64-84 | crates/utils/re_auth/src/oauth/api.rs:89-109 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (21 corresponding lines) crates/store_app/re_tf/src/transform_resolution_cache/cached_transforms_for_timeline.rs:435— crates/store_app/re_tf/src/transform_resolution_cache/cached_transforms_for_timeline.rs:435-455 | crates/store_app/re_tf/src/transform_resolution_cache/cached_transforms_for_timeline.rs:461-488 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (21 corresponding lines) rerun_py/src/trace_context.rs:96— rerun_py/src/trace_context.rs:96-116 | rerun_py/src/tracing_session.rs:71-91 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (21 corresponding lines) crates/store/re_chunk_index/src/raw_rrd_manifest.rs:453— crates/store/re_chunk_index/src/raw_rrd_manifest.rs:453-473 | crates/store/re_chunk_index/src/raw_rrd_manifest.rs:900-923 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (21 corresponding lines) crates/store_app/re_query/src/latest_at.rs:648— crates/store_app/re_query/src/latest_at.rs:648-669 | crates/store_app/re_query/src/range.rs:228-248 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (21 corresponding lines) crates/store/re_chunk_store/src/stats.rs:251— crates/store/re_chunk_store/src/stats.rs:251-271 | crates/store/re_chunk_store/src/stats.rs:306-326 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
re_viewer::blueprint::references::reference_problems (cyclomatic 26) crates/top/re_viewer/src/blueprint/references.rs:174— re_viewer::blueprint::references::reference_problems 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.
re_viewer::viewer_analytics::event::open_recording (cyclomatic 23) crates/top/re_viewer/src/viewer_analytics/event.rs:64— re_viewer::viewer_analytics::event::open_recording has cyclomatic complexity 23 (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.
re_viewer::ui::dev_panel::transform_cache_ui::paint::draw_transform_cache_contents (cyclomatic 20) crates/top/re_viewer/src/ui/dev_panel/transform_cache_ui/paint.rs:211— re_viewer::ui::dev_panel::transform_cache_ui::paint::draw_transform_cache_contents has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
re_viewer::prefetch_chunks::prefetch_chunks_for_recordings (cyclomatic 18) crates/top/re_viewer/src/prefetch_chunks.rs:30— re_viewer::prefetch_chunks::prefetch_chunks_for_recordings has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
re_viewer::web::create_app (cyclomatic 18) crates/top/re_viewer/src/web.rs:648— re_viewer::web::create_app has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
re_viewer::ui::top_panel::top_bar_ui (cyclomatic 17) crates/top/re_viewer/src/ui/top_panel.rs:132— re_viewer::ui::top_panel::top_bar_ui 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.
re_viewer::ui::top_panel::panel_buttons_r2l (cyclomatic 16) crates/top/re_viewer/src/ui/top_panel.rs:657— re_viewer::ui::top_panel::panel_buttons_r2l 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.
re_selection_panel::view_entity_picker::add_entities_line_ui (cognitive 40) crates/panels/re_selection_panel/src/view_entity_picker.rs:177— re_selection_panel::view_entity_picker::add_entities_line_ui has cognitive complexity 40 (threshold 15). Drivers by points: if/else 22 (39 pts), boolean chains 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.
re_selection_panel::visualizer_ui::visualizer_components (cognitive 36) crates/panels/re_selection_panel/src/visualizer_ui.rs:216— re_selection_panel::visualizer_ui::visualizer_components has cognitive complexity 36 (threshold 15). Drivers by points: if/else 16 (29 pts), boolean chains 4, loops 2 (3 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_selection_panel::selection_history_ui::history_button_ui (cognitive 31) crates/panels/re_selection_panel/src/selection_history_ui.rs:53— re_selection_panel::selection_history_ui::history_button_ui has cognitive complexity 31 (threshold 15). Drivers by points: if/else 15 (20 pts), match/switch 6, boolean chains 3, loops 1 (2 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_selection_panel::item_heading_with_breadcrumbs::item_bread_crumbs_ui (cognitive 21) crates/panels/re_selection_panel/src/item_heading_with_breadcrumbs.rs:39— re_selection_panel::item_heading_with_breadcrumbs::item_bread_crumbs_ui has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (20 pts), match/switch 1 (nesting depth added 11). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
re_selection_panel::visible_time_range_ui::resolved_visible_history_boundary_ui (cognitive 20) crates/panels/re_selection_panel/src/visible_time_range_ui.rs:348— re_selection_panel::visible_time_range_ui::resolved_visible_history_boundary_ui has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (12 pts), match/switch 5 (8 pts) (nesting depth added 8). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
re_selection_panel::visible_time_range_ui::query_range_ui (cognitive 19) crates/panels/re_selection_panel/src/visible_time_range_ui.rs:165— re_selection_panel::visible_time_range_ui::query_range_ui has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11, match/switch 3 (7 pts), boolean chains 1 (nesting depth added 4). 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.
re_selection_panel::visualizer_ui::visualizer_ui_impl (cognitive 18) crates/panels/re_selection_panel/src/visualizer_ui.rs:104— re_selection_panel::visualizer_ui::visualizer_ui_impl has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (11 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.
D4 · Code Duplication· Edited copy of a member (35 corresponding lines) · ×7
Edited copy of a member (35 corresponding lines) docs/snippets/all/tutorials/dna.py:16— docs/snippets/all/tutorials/dna.py:16-97 | examples/python/dna/dna.py:26-60 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (35 corresponding lines) docs/snippets/all/howto/any_batch_value_column_updates.rs:7— docs/snippets/all/howto/any_batch_value_column_updates.rs:7-43 | docs/snippets/all/howto/any_values_column_updates.rs:9-43 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (35 corresponding lines) docs/snippets/all/archetypes/arrows3d_column_updates.rs:7— docs/snippets/all/archetypes/arrows3d_column_updates.rs:7-41 | docs/snippets/all/archetypes/arrows3d_row_updates.rs:7-42 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (35 corresponding lines) crates/top/re_viewer/src/app/command_handling.rs:1956— crates/top/re_viewer/src/app/command_handling.rs:1956-1991 | crates/viewer_support/re_viewer_context/src/file_dialog.rs:23-57 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (35 corresponding lines) docs/snippets/all/archetypes/capsules3d_batch.rs:5— docs/snippets/all/archetypes/capsules3d_batch.rs:5-39 | docs/snippets/all/archetypes/cylinders3d_batch.rs:5-39 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (35 corresponding lines) rerun_py/rerun_sdk/rerun/catalog/_entry.py:355— rerun_py/rerun_sdk/rerun/catalog/_entry.py:355-392 | rerun_py/rerun_sdk/rerun/catalog/_entry.py:2234-2268 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (35 corresponding lines) examples/python/graph_lattice/graph_lattice.py:25— examples/python/graph_lattice/graph_lattice.py:25-61 | examples/python/graphs/graphs.py:47-81 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (31 corresponding lines) · ×7
Edited copy of a member (31 corresponding lines) crates/store/re_chunk_store/src/rebatch_videos.rs:757— crates/store/re_chunk_store/src/rebatch_videos.rs:757-787 | crates/store/re_chunk_store/src/rebatch_videos.rs:794-828 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (31 corresponding lines) rerun_py/src/catalog/dataset_entry.rs:775— rerun_py/src/catalog/dataset_entry.rs:775-812 | rerun_py/src/catalog/dataset_entry.rs:822-852 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (31 corresponding lines) crates/store/re_log_channel/src/receiver_set.rs:125— crates/store/re_log_channel/src/receiver_set.rs:125-155 | crates/store/re_log_channel/src/receiver_set.rs:161-191 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (31 corresponding lines) docs/snippets/all/archetypes/clear_recursive.rs:5— docs/snippets/all/archetypes/clear_recursive.rs:5-35 | docs/snippets/all/archetypes/clear_simple.rs:5-36 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (31 corresponding lines) crates/ui_tools/re_renderer/src/draw_phases/depth_resolve.rs:67— crates/ui_tools/re_renderer/src/draw_phases/depth_resolve.rs:67-99 | crates/ui_tools/re_renderer/src/draw_phases/outlines.rs:444-474 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (31 corresponding lines) crates/data_flow/re_mp4_reader/src/lib.rs:44— crates/data_flow/re_mp4_reader/src/lib.rs:44-75 | crates/data_flow/re_mp4_reader/src/lib.rs:97-127 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (31 corresponding lines) crates/ui_tools/re_renderer/src/allocator/data_texture_source.rs:205— crates/ui_tools/re_renderer/src/allocator/data_texture_source.rs:205-235 | crates/ui_tools/re_renderer/src/allocator/data_texture_source.rs:264-294 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (8 lines × 3) crates/store/re_sorbet/src/migrations/v0_0_2__to__v0_1_0.rs:177— crates/store/re_sorbet/src/migrations/v0_0_2__to__v0_1_0.rs:177-184 | crates/store/re_sorbet/src/migrations/v0_1_1__to__v0_1_2.rs:90-100 | crates/store/re_sorbet/src/migrations/v0_1_2__to__v0_1_3.rs:63-72 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `crates/store/re_sorbet/src/migrations/v0_0_2__to__v0_1_0.rs:177` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 3) crates/utils/re_auth/src/oauth/api.rs:45— crates/utils/re_auth/src/oauth/api.rs:45-52 | crates/utils/re_auth/src/oauth/api.rs:74-81 | crates/utils/re_auth/src/oauth/api.rs:99-106 — 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/utils/re_auth/src/oauth/api.rs:45` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 3) crates/viewer_support/re_viewer_context/src/item.rs:384— crates/viewer_support/re_viewer_context/src/item.rs:384-391 | crates/viewer_support/re_viewer_context/src/selection_state.rs:207-214 | crates/viewer_support/re_viewer_context/src/selection_state.rs:228-235 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (8 lines × 3) docs/snippets/all/archetypes/line_strips3d_batch.rs:9— docs/snippets/all/archetypes/line_strips3d_batch.rs:9-16 | docs/snippets/all/archetypes/line_strips3d_segments_simple.rs:8-15 | docs/snippets/all/archetypes/line_strips3d_simple.rs:7-14 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `docs/snippets/all/archetypes/line_strips3d_batch.rs:9` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 3) docs/snippets/all/archetypes/transform3d_hierarchy_frames.rs:15— docs/snippets/all/archetypes/transform3d_hierarchy_frames.rs:15-22 | docs/snippets/all/archetypes/transform3d_hierarchy_frames.rs:27-36 | docs/snippets/all/archetypes/transform3d_hierarchy_frames.rs:41-50 — 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 `docs/snippets/all/archetypes/transform3d_hierarchy_frames.rs:15` it does not close everything it opens, so those exact lines 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/ui_tools/re_renderer/src/draw_phases/depth_resolve.rs:69— crates/ui_tools/re_renderer/src/draw_phases/depth_resolve.rs:69-76 | crates/ui_tools/re_renderer/src/draw_phases/outlines.rs:445-453 | crates/ui_tools/re_renderer/src/draw_phases/picking_layer.rs:504-511 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `crates/ui_tools/re_renderer/src/draw_phases/depth_resolve.rs:69` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 3) crates/ui_tools/re_renderer/src/renderer/gaussian_splat.rs:408— crates/ui_tools/re_renderer/src/renderer/gaussian_splat.rs:408-415 | crates/ui_tools/re_renderer/src/renderer/lines.rs:455-462 | crates/ui_tools/re_renderer/src/renderer/lines.rs:469-476 — before extracting anything, compare `crates/ui_tools/re_renderer/src/renderer/gaussian_splat.rs` and `crates/ui_tools/re_renderer/src/renderer/lines.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 56 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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/ui_tools/re_renderer/src/renderer/gaussian_splat.rs:408` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
TimeControl::handle_time_command (cognitive 105) crates/viewer_support/re_viewer_context/src/time_control/command.rs:214— TimeControl::handle_time_command has cognitive complexity 105 (threshold 15). Drivers by points: if/else 51 (99 pts), match/switch 2 (5 pts), boolean chains 1 (nesting depth added 51). 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.
TimeControl::update (cognitive 56) crates/viewer_support/re_viewer_context/src/time_control/mod.rs:451— TimeControl::update has cognitive complexity 56 (threshold 15). Drivers by points: if/else 16 (36 pts), match/switch 3 (12 pts), boolean chains 8 (nesting depth added 29). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
TimeControl::update_from_blueprint (cognitive 26) crates/viewer_support/re_viewer_context/src/time_control/mod.rs:357— TimeControl::update_from_blueprint has cognitive complexity 26 (threshold 15). Drivers by points: if/else 13 (19 pts), match/switch 2 (5 pts), boolean chains 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TimeControl::step_time_back_no_pause (cognitive 21) crates/viewer_support/re_viewer_context/src/time_control/command.rs:561— TimeControl::step_time_back_no_pause has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11 (20 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (TimeControl::step_time_fwd_no_pause) 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.
TimeControl::step_time_fwd_no_pause (cognitive 21) crates/viewer_support/re_viewer_context/src/time_control/command.rs:598— TimeControl::step_time_fwd_no_pause has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11 (20 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (TimeControl::step_time_back_no_pause) 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.
TimeControl::set_play_state (cognitive 20) crates/viewer_support/re_viewer_context/src/time_control/mod.rs:663— TimeControl::set_play_state has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 5, match/switch 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
QueryHandle::next_n_rows_in_store (cognitive 101) crates/store_app/re_dataframe/src/query.rs:1788— QueryHandle::next_n_rows_in_store has cognitive complexity 101 (threshold 15). Drivers by points: if/else 27 (73 pts), match/switch 6 (19 pts), loops 4 (8 pts), boolean chains 1 (nesting depth added 63). 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.
QueryHandle::try_bulk_emit_run (cognitive 78) crates/store_app/re_dataframe/src/query.rs:2132— QueryHandle::try_bulk_emit_run has cognitive complexity 78 (threshold 15). Drivers by points: if/else 31 (65 pts), match/switch 3 (7 pts), loops 4 (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.
QueryHandle::resolve_one_row (cognitive 70) crates/store_app/re_dataframe/src/query.rs:1427— QueryHandle::resolve_one_row has cognitive complexity 70 (threshold 15). Drivers by points: if/else 17 (49 pts), loops 6 (14 pts), match/switch 4 (6 pts), boolean chains 1 (nesting depth added 42). 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.
QueryHandle::init_ (cognitive 28) crates/store_app/re_dataframe/src/query.rs:564— QueryHandle::init_ has cognitive complexity 28 (threshold 15). Drivers by points: if/else 14 (21 pts), match/switch 2 (4 pts), loops 3 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
QueryHandle::fill_bulk_metadata (cognitive 19) crates/store_app/re_dataframe/src/query.rs:776— QueryHandle::fill_bulk_metadata has cognitive complexity 19 (threshold 15). Drivers by points: if/else 4 (12 pts), loops 3 (5 pts), boolean chains 2 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
QueryHandle::seek_to_index_value_impl (cognitive 17) crates/store_app/re_dataframe/src/query.rs:1144— QueryHandle::seek_to_index_value_impl has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (9 pts), loops 4 (8 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Chunk::earliest_at (cognitive 57) crates/store/re_chunk/src/earliest_at.rs:84— Chunk::earliest_at has cognitive complexity 57 (threshold 15). Drivers by points: if/else 13 (39 pts), match/switch 2 (9 pts), loops 2 (7 pts), boolean chains 2 (nesting depth added 38). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
Chunk::latest_at (cognitive 50) crates/store/re_chunk/src/latest_at.rs:109— Chunk::latest_at has cognitive complexity 50 (threshold 15). Drivers by points: if/else 12 (35 pts), loops 2 (7 pts), match/switch 1 (5 pts), boolean chains 3 (nesting depth added 32). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
Chunk::sanity_check (cognitive 26) crates/store/re_chunk/src/chunk.rs:1822— Chunk::sanity_check has cognitive complexity 26 (threshold 15). Drivers by points: if/else 12 (21 pts), boolean chains 3, loops 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Chunk::row_id_range_per_component (cognitive 24) crates/store/re_chunk/src/chunk.rs:859— Chunk::row_id_range_per_component has cognitive complexity 24 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 4 (8 pts), boolean chains 2 (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.
Chunk::range (cognitive 19) crates/store/re_chunk/src/range.rs:211— Chunk::range has cognitive complexity 19 (threshold 15). Drivers by points: if/else 14 (19 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Chunk::static_row_index (cognitive 16) crates/store/re_chunk/src/latest_at.rs:208— Chunk::static_row_index has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (8 pts), match/switch 3 (6 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.
re_agent_ui::ui::elicitation_ui::field_ui (cognitive 44) crates/ui_tools/re_agent_ui/src/ui/elicitation_ui.rs:229— re_agent_ui::ui::elicitation_ui::field_ui has cognitive complexity 44 (threshold 15). Drivers by points: if/else 13 (35 pts), loops 2 (6 pts), match/switch 2, boolean chains 1 (nesting depth added 26). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_agent_ui::ui::chat_ui::config_menu_ui (cognitive 43) crates/ui_tools/re_agent_ui/src/ui/chat_ui.rs:564— re_agent_ui::ui::chat_ui::config_menu_ui has cognitive complexity 43 (threshold 15). Drivers by points: if/else 16 (28 pts), loops 3 (7 pts), match/switch 4 (6 pts), boolean chains 2 (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.
re_agent_ui::ui::chat_ui::permissions_ui (cognitive 28) crates/ui_tools/re_agent_ui/src/ui/chat_ui.rs:1024— re_agent_ui::ui::chat_ui::permissions_ui has cognitive complexity 28 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 6, match/switch 2 (6 pts), loops 2 (3 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_agent_ui::ui::transcript_ui::transcript_ui (cognitive 21) crates/ui_tools/re_agent_ui/src/ui/transcript_ui.rs:26— re_agent_ui::ui::transcript_ui::transcript_ui has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 3, match/switch 1 (2 pts), loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_agent_ui::ui::chat_ui::settings_menu_ui (cognitive 18) crates/ui_tools/re_agent_ui/src/ui/chat_ui.rs:394— re_agent_ui::ui::chat_ui::settings_menu_ui has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 4, loops 2, match/switch 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_agent_ui::ui::chat_ui::auth_ui (cognitive 18) crates/ui_tools/re_agent_ui/src/ui/chat_ui.rs:969— re_agent_ui::ui::chat_ui::auth_ui has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (14 pts), match/switch 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_viewer::blueprint::references::reference_problems (cognitive 39) crates/top/re_viewer/src/blueprint/references.rs:174— re_viewer::blueprint::references::reference_problems has cognitive complexity 39 (threshold 15). Drivers by points: if/else 15 (23 pts), loops 10 (13 pts), boolean chains 3 (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.
re_viewer::ui::dev_panel::transform_cache_ui::paint::draw_transform_cache_contents (cognitive 32) crates/top/re_viewer/src/ui/dev_panel/transform_cache_ui/paint.rs:211— re_viewer::ui::dev_panel::transform_cache_ui::paint::draw_transform_cache_contents has cognitive complexity 32 (threshold 15). Drivers by points: if/else 15 (25 pts), loops 4, boolean chains 3 (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.
re_viewer::ui::top_panel::top_bar_ui (cognitive 30) crates/top/re_viewer/src/ui/top_panel.rs:132— re_viewer::ui::top_panel::top_bar_ui has cognitive complexity 30 (threshold 15). Drivers by points: if/else 14 (26 pts), boolean chains 4 (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.
re_viewer::web::create_app (cognitive 25) crates/top/re_viewer/src/web.rs:648— re_viewer::web::create_app has cognitive complexity 25 (threshold 15). Drivers by points: if/else 11 (13 pts), match/switch 5 (10 pts), loops 1 (2 pts) (nesting depth added 8). 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.
re_viewer::prefetch_chunks::prefetch_chunks_for_recordings (cognitive 23) crates/top/re_viewer/src/prefetch_chunks.rs:30— re_viewer::prefetch_chunks::prefetch_chunks_for_recordings has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (12 pts), match/switch 2 (5 pts), loops 4, 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.
re_viewer::ui::top_panel::panel_buttons_r2l (cognitive 22) crates/top/re_viewer/src/ui/top_panel.rs:657— re_viewer::ui::top_panel::panel_buttons_r2l has cognitive complexity 22 (threshold 15). Drivers by points: if/else 12 (18 pts), boolean chains 4 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D4 · Code Duplication· Edited copy of a member (38 corresponding lines) · ×6
Edited copy of a member (38 corresponding lines) crates/data_flow/re_importer/src/importer_urdf/mod.rs:70— crates/data_flow/re_importer/src/importer_urdf/mod.rs:70-107 | crates/data_flow/re_importer/src/importer_urdf/mod.rs:115-152 — These two members are one piece of code written twice and then edited apart: 38 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (38 corresponding lines) crates/store/re_chunk_store/src/query.rs:170— crates/store/re_chunk_store/src/query.rs:170-207 | crates/store/re_chunk_store/src/query.rs:219-256 — These two members are one piece of code written twice and then edited apart: 38 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (38 corresponding lines) crates/store/re_log_types/src/path/entity_path_part.rs:59— crates/store/re_log_types/src/path/entity_path_part.rs:59-118 | crates/store/re_log_types/src/path/entity_path_part.rs:121-158 — These two members are one piece of code written twice and then edited apart: 38 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (38 corresponding lines) crates/viewer_support/re_view/src/blueprint_resolved_results.rs:148— crates/viewer_support/re_view/src/blueprint_resolved_results.rs:148-185 | crates/viewer_support/re_view/src/blueprint_resolved_results.rs:318-362 — These two members are one piece of code written twice and then edited apart: 38 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (38 corresponding lines) crates/store_app/re_query/src/bin/clamped_zip.rs:317— crates/store_app/re_query/src/bin/clamped_zip.rs:317-354 | crates/store_app/re_query/src/bin/range_zip.rs:457-497 — These two members are one piece of code written twice and then edited apart: 38 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (38 corresponding lines) rerun_py/rerun_sdk/rerun/blueprint/api.py:744— rerun_py/rerun_sdk/rerun/blueprint/api.py:744-782 | rerun_py/rerun_sdk/rerun/notebook.py:290-327 — These two members are one piece of code written twice and then edited apart: 38 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (30 corresponding lines) · ×6
Edited copy of a member (30 corresponding lines) docs/snippets/all/archetypes/line_strips2d_ui_radius.rs:3— docs/snippets/all/archetypes/line_strips2d_ui_radius.rs:3-34 | docs/snippets/all/archetypes/line_strips3d_ui_radius.rs:3-32 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (30 corresponding lines) crates/viewer_support/re_component_ui/src/encoding_uis/vec.rs:57— crates/viewer_support/re_component_ui/src/encoding_uis/vec.rs:57-86 | crates/viewer_support/re_component_ui/src/encoding_uis/vec.rs:93-127 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (30 corresponding lines) crates/store_app/re_tf/src/transform_resolution_cache/cached_transforms_for_timeline.rs:284— crates/store_app/re_tf/src/transform_resolution_cache/cached_transforms_for_timeline.rs:284-320 | crates/store_app/re_tf/src/transform_resolution_cache/cached_transforms_for_timeline.rs:327-356 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (30 corresponding lines) docs/snippets/all/archetypes/points2d_ui_radius.rs:3— docs/snippets/all/archetypes/points2d_ui_radius.rs:3-34 | docs/snippets/all/archetypes/points3d_ui_radius.rs:3-32 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (30 corresponding lines) crates/ui_tools/re_renderer/src/allocator/cpu_write_gpu_read_belt.rs:291— crates/ui_tools/re_renderer/src/allocator/cpu_write_gpu_read_belt.rs:291-320 | crates/ui_tools/re_renderer/src/allocator/cpu_write_gpu_read_belt.rs:333-364 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (30 corresponding lines) crates/store_app/re_tf/src/transform_forest.rs:596— crates/store_app/re_tf/src/transform_forest.rs:596-625 | crates/store_app/re_tf/src/transform_forest.rs:632-671 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (29 corresponding lines) · ×6
Edited copy of a member (29 corresponding lines) rerun_py/rerun_sdk/rerun/archetypes/depth_image_ext.py:67— rerun_py/rerun_sdk/rerun/archetypes/depth_image_ext.py:67-148 | rerun_py/rerun_sdk/rerun/archetypes/segmentation_image_ext.py:49-77 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (29 corresponding lines) crates/viewer_support/re_viewer_context/src/view/view_class_registry.rs:55— crates/viewer_support/re_viewer_context/src/view/view_class_registry.rs:55-83 | crates/viewer_support/re_viewer_context/src/view/view_class_registry.rs:325-357 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (29 corresponding lines) crates/store/re_sdk_types/src/archetypes/points2d_ext.rs:62— crates/store/re_sdk_types/src/archetypes/points2d_ext.rs:62-90 | crates/store/re_sdk_types/src/archetypes/points3d_ext.rs:67-100 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (29 corresponding lines) crates/ui_tools/re_renderer/src/renderer/depth_cloud.rs:508— crates/ui_tools/re_renderer/src/renderer/depth_cloud.rs:508-541 | crates/ui_tools/re_renderer/src/renderer/rectangles.rs:813-841 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (29 corresponding lines) crates/viewer_support/re_data_ui/src/video_ui.rs:28— crates/viewer_support/re_data_ui/src/video_ui.rs:28-56 | crates/viewer_support/re_data_ui/src/video_ui.rs:63-91 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (29 corresponding lines) crates/ui_tools/re_renderer_examples/depth_cloud.rs:407— crates/ui_tools/re_renderer_examples/depth_cloud.rs:407-435 | crates/ui_tools/re_renderer_examples/depth_cloud.rs:448-476 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (9 corresponding lines) · ×6
Edited copy of a member (9 corresponding lines) rerun_py/rerun_sdk/rerun/experimental/dataloader/decoders/_image.py:37— rerun_py/rerun_sdk/rerun/experimental/dataloader/decoders/_image.py:37-50 | rerun_py/rerun_sdk/rerun/experimental/dataloader/decoders/_numeric.py:86-94 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) crates/data_flow/re_lenses/src/semantic/helpers.rs:34— crates/data_flow/re_lenses/src/semantic/helpers.rs:34-42 | crates/data_flow/re_lenses/src/semantic/image_helpers.rs:20-29 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) crates/store_app/re_server/src/store/table.rs:110— crates/store_app/re_server/src/store/table.rs:110-118 | crates/store_app/re_server/src/store/table.rs:120-132 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) crates/viewer_support/re_viewer_context/src/cache/video_stream_cache/test_player/encoded_depth_image.rs:13— crates/viewer_support/re_viewer_context/src/cache/video_stream_cache/test_player/encoded_depth_image.rs:13-21 | crates/viewer_support/re_viewer_context/src/cache/video_stream_cache/test_player/encoded_image.rs:17-25 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) examples/python/openstreetmap_data/openstreetmap_data.py:61— examples/python/openstreetmap_data/openstreetmap_data.py:61-69 | examples/python/openstreetmap_data/openstreetmap_data.py:73-83 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) crates/ui_tools/re_renderer_examples/multiview.rs:167— crates/ui_tools/re_renderer_examples/multiview.rs:167-175 | crates/ui_tools/re_renderer_examples/picking.rs:28-36 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (6 corresponding lines) · ×6
Edited copy of a member (6 corresponding lines) crates/data_flow/re_mcap/src/decoders/protobuf.rs:222— crates/data_flow/re_mcap/src/decoders/protobuf.rs:222-230 | crates/utils/re_ros_msg/src/reflection/cdr_to_arrow.rs:514-519 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) crates/top/re_viewer/src/loading_errors.rs:22— crates/top/re_viewer/src/loading_errors.rs:22-27 | crates/viewer_support/re_viewer_context/src/app_context.rs:138-143 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) rerun_py/src/chunk_stream/chunk_store.rs:69— rerun_py/src/chunk_stream/chunk_store.rs:69-79 | rerun_py/src/chunk_stream/lazy_store.rs:54-59 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) crates/utils/re_ros_msg/src/reflection/timestamp.rs:86— crates/utils/re_ros_msg/src/reflection/timestamp.rs:86-92 | crates/viewer_support/re_dataframe_ui/src/datafusion_table_widget.rs:161-166 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) examples/python/human_pose_tracking/human_pose_tracking.py:116— examples/python/human_pose_tracking/human_pose_tracking.py:116-121 | examples/python/human_pose_tracking/human_pose_tracking.py:127-132 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) examples/notebook/notebook/cube_marimo.py:38— examples/notebook/notebook/cube_marimo.py:38-46 | examples/notebook/notebook/cube_marimo.py:70-75 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (23 lines × 2) crates/panels/re_selection_panel/src/view_entity_picker.rs:334— crates/panels/re_selection_panel/src/view_entity_picker.rs:334-356 | crates/panels/re_time_panel/src/streams_tree_data.rs:110-132 — before extracting anything, compare `crates/panels/re_selection_panel/src/view_entity_picker.rs` and `crates/panels/re_time_panel/src/streams_tree_data.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 66 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/panels/re_selection_panel/src/view_entity_picker.rs:334` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (23 lines × 2) crates/panels/re_selection_panel/src/view_entity_picker.rs:404— crates/panels/re_selection_panel/src/view_entity_picker.rs:404-426 | crates/panels/re_time_panel/src/streams_tree_data.rs:180-202 — before extracting anything, compare `crates/panels/re_selection_panel/src/view_entity_picker.rs` and `crates/panels/re_time_panel/src/streams_tree_data.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 66 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/panels/re_selection_panel/src/view_entity_picker.rs:404` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (23 lines × 2) crates/store/re_chunk_store/src/gc.rs:528— crates/store/re_chunk_store/src/gc.rs:528-550 | crates/store/re_chunk_store/src/gc.rs:574-596 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/store/re_chunk_store/src/gc.rs:528` 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/store/re_chunk_store/src/gc.rs:566` calls `time_range` and `crates/store/re_chunk_store/src/gc.rs:520` 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 (23 lines × 2) crates/store_app/re_catalog_client/src/blueprint.rs:464— crates/store_app/re_catalog_client/src/blueprint.rs:464-486 | crates/store_app/re_catalog_client/src/blueprint.rs:509-531 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/store_app/re_catalog_client/src/blueprint.rs:464` 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 (23 lines × 2) crates/viewer_support/re_component_ui/src/line_strip.rs:24— crates/viewer_support/re_component_ui/src/line_strip.rs:24-46 | crates/viewer_support/re_component_ui/src/line_strip.rs:89-111 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/viewer_support/re_component_ui/src/line_strip.rs:24` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `value` to `&mut MaybeMutRef<'_, LineStrip3D>` in one and `&mut MaybeMutRef<'_, LineStrip2D>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `crates/viewer_support/re_component_ui/src/line_strip.rs:47` calls `col`, `label` and `crates/viewer_support/re_component_ui/src/line_strip.rs:112` 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 (23 lines × 2) rerun_py/src/chunk_stream/hdf5_reader.rs:85— rerun_py/src/chunk_stream/hdf5_reader.rs:85-107 | rerun_py/src/chunk_stream/parquet_reader.rs:107-129 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `rerun_py/src/chunk_stream/hdf5_reader.rs:85` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (20 lines × 2) crates/store/re_chunk_index/src/raw_rrd_manifest.rs:1644— crates/store/re_chunk_index/src/raw_rrd_manifest.rs:1644-1663 | crates/store/re_chunk_index/src/raw_rrd_manifest.rs:1691-1710 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/store/re_chunk_index/src/raw_rrd_manifest.rs:1644` 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/store_app/re_query/src/bin/range_zip.rs:130— crates/store_app/re_query/src/bin/range_zip.rs:130-149 | crates/store_app/re_query/src/bin/range_zip.rs:340-359 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (20 lines × 2) crates/viewer_support/re_viewer_context/src/component_ui_registry.rs:356— crates/viewer_support/re_viewer_context/src/component_ui_registry.rs:356-375 | crates/viewer_support/re_viewer_context/src/component_ui_registry.rs:402-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/viewer_support/re_viewer_context/src/component_ui_registry.rs:356` 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/views/re_view_spatial/src/visualizers/lines2d.rs:194— crates/views/re_view_spatial/src/visualizers/lines2d.rs:194-213 | crates/views/re_view_spatial/src/visualizers/lines3d.rs:205-224 — before extracting anything, compare `crates/views/re_view_spatial/src/visualizers/lines2d.rs` and `crates/views/re_view_spatial/src/visualizers/lines3d.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 (20 lines × 2) crates/ui_tools/re_renderer_examples/outlines.rs:122— crates/ui_tools/re_renderer_examples/outlines.rs:122-141 | crates/ui_tools/re_renderer_examples/picking.rs:187-206 — 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/ui_tools/re_renderer_examples/outlines.rs:122` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (20 lines × 2) examples/python/lidar/lidar/__main__.py:30— examples/python/lidar/lidar/__main__.py:30-49 | examples/python/nuscenes_dataset/nuscenes_dataset/__main__.py:41-60 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (17 lines × 2) crates/store/re_chunk_store/src/writes.rs:529— crates/store/re_chunk_store/src/writes.rs:529-545 | crates/store/re_chunk_store/src/writes.rs:564-580 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/store/re_chunk_store/src/writes.rs:529` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 2) crates/store/re_protos/src/v1alpha1/rerun.cloud.v1alpha1.ext.asset_properties.rs:118— crates/store/re_protos/src/v1alpha1/rerun.cloud.v1alpha1.ext.asset_properties.rs:118-134 | crates/store/re_protos/src/v1alpha1/rerun.cloud.v1alpha1.ext.properties.rs:48-64 — 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/store/re_protos/src/v1alpha1/rerun.cloud.v1alpha1.ext.asset_properties.rs:118` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (17 lines × 2) crates/store/re_sdk_types/src/archetypes/points2d_ext.rs:141— crates/store/re_sdk_types/src/archetypes/points2d_ext.rs:141-157 | crates/store/re_sdk_types/src/archetypes/points3d_ext.rs:146-162 — before extracting anything, compare `crates/store/re_sdk_types/src/archetypes/points2d_ext.rs` and `crates/store/re_sdk_types/src/archetypes/points3d_ext.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 65 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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/store/re_sdk_types/src/archetypes/points2d_ext.rs:141` 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/store_app/re_datafusion/src/dataframe_query_provider/mod.rs:920— crates/store_app/re_datafusion/src/dataframe_query_provider/mod.rs:920-936 | crates/store_app/re_datafusion/src/dataframe_query_provider_wasm.rs:527-543 — 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/store_app/re_datafusion/src/dataframe_query_provider/mod.rs:920` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 2) crates/viewer_support/re_component_ui/src/encoding_uis/float_drag.rs:72— crates/viewer_support/re_component_ui/src/encoding_uis/float_drag.rs:72-88 | crates/viewer_support/re_component_ui/src/encoding_uis/int_drag.rs:66-82 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (17 lines × 2) rerun_py/src/chunk_stream/stream.rs:195— rerun_py/src/chunk_stream/stream.rs:195-211 | rerun_py/src/chunk_stream/stream.rs:228-244 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `rerun_py/src/chunk_stream/stream.rs:195` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
rerun::commands::entrypoint::record_cli_command_analytics (cyclomatic 32) crates/top/rerun/src/commands/entrypoint.rs:2102— rerun::commands::entrypoint::record_cli_command_analytics 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.
rerun::commands::entrypoint::run_inner (cyclomatic 20) crates/top/rerun/src/commands/entrypoint.rs:745— rerun::commands::entrypoint::run_inner 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.
rerun::commands::rrd::route::process_messages (cyclomatic 20) crates/top/rerun/src/commands/rrd/route.rs:104— rerun::commands::rrd::route::process_messages has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
rerun::commands::entrypoint::run_impl (cyclomatic 18) crates/top/rerun/src/commands/entrypoint.rs:1044— rerun::commands::entrypoint::run_impl has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
rerun::commands::entrypoint::assert_receive_into_entity_db (cyclomatic 17) crates/top/rerun/src/commands/entrypoint.rs:1697— rerun::commands::entrypoint::assert_receive_into_entity_db 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.
HackComment examples/python/arkit_scenes/arkit_scenes/__main__.py:34— # hack for now since dataset does not provide orientation information, only known after initial visual inspection — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment crates/viewer_support/re_component_ui/src/lib.rs:161— // Hack to make this field never editable. — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment crates/top/re_viewer/src/app/command_handling.rs:833— // Hacky: Shrink so we don't accidentally include the border of the view. — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment crates/top/re_viewer/src/app/logic.rs:413— // Hack: we cannot go to a specific timeline or entity until we know about it. — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment crates/store/re_uri/src/redap_uri.rs:93— // Hacky, but I don't want to have to memorize ports. — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
re_dataframe_ui::preview_renderer::preview_timeline (cognitive 52) crates/viewer_support/re_dataframe_ui/src/preview_renderer.rs:843— re_dataframe_ui::preview_renderer::preview_timeline has cognitive complexity 52 (threshold 15). Drivers by points: if/else 12 (40 pts), boolean chains 7, loops 1 (5 pts) (nesting depth added 32). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
re_dataframe_ui::filters::column_filter_ui::column_picker_ui (cognitive 40) crates/viewer_support/re_dataframe_ui/src/filters/column_filter_ui.rs:89— re_dataframe_ui::filters::column_filter_ui::column_picker_ui has cognitive complexity 40 (threshold 15). Drivers by points: if/else 25 (30 pts), boolean chains 9, loops 1 (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
re_dataframe_ui::cards_view::card_content_ui (cognitive 28) crates/viewer_support/re_dataframe_ui/src/cards_view.rs:207— re_dataframe_ui::cards_view::card_content_ui has cognitive complexity 28 (threshold 15). Drivers by points: if/else 16 (21 pts), boolean chains 3, loops 2 (3 pts), match/switch 1 (nesting depth added 6). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
re_dataframe_ui::preview_renderer::preview_playback_ui (cognitive 25) crates/viewer_support/re_dataframe_ui/src/preview_renderer.rs:644— re_dataframe_ui::preview_renderer::preview_playback_ui has cognitive complexity 25 (threshold 15). Drivers by points: if/else 19 (22 pts), boolean chains 3 (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.
re_dataframe_ui::datafusion_table_widget::toolbar_controls_ui (cognitive 16) crates/viewer_support/re_dataframe_ui/src/datafusion_table_widget.rs:1582— re_dataframe_ui::datafusion_table_widget::toolbar_controls_ui has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (14 pts), loops 1 (2 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TimePanel::show_entity_contents (cognitive 47) crates/panels/re_time_panel/src/time_panel.rs:970— TimePanel::show_entity_contents has cognitive complexity 47 (threshold 15). Drivers by points: if/else 17 (42 pts), loops 3 (4 pts), boolean chains 1 (nesting depth added 26). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TimePanel::data_density_graph_ui (cognitive 20) crates/panels/re_time_panel/src/time_panel.rs:1202— TimePanel::data_density_graph_ui has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 2 (6 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.
TimePanel::collapsed_ui (cognitive 19) crates/panels/re_time_panel/src/time_panel.rs:362— TimePanel::collapsed_ui has cognitive complexity 19 (threshold 15). Drivers by points: if/else 12 (18 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TimePanel::expanded_ui (cognitive 19) crates/panels/re_time_panel/src/time_panel.rs:465— TimePanel::expanded_ui has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (15 pts), match/switch 1 (3 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TimePanel::current_time_ui (cognitive 16) crates/panels/re_time_panel/src/time_panel.rs:1591— TimePanel::current_time_ui has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 1 (nesting depth added 5). Of this number, 10 points are the body's own statements and 6 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_video::decode::av1::create_frame (cognitive 37) crates/utils/re_video/src/decode/av1.rs:197— re_video::decode::av1::create_frame has cognitive complexity 37 (threshold 15). Drivers by points: if/else 10 (16 pts), loops 3 (12 pts), match/switch 5 (7 pts), boolean chains 2 (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.
re_video::decode::ffmpeg_cli::ffmpeg::read_ffmpeg_output (cognitive 29) crates/utils/re_video/src/decode/ffmpeg_cli/ffmpeg.rs:691— re_video::decode::ffmpeg_cli::ffmpeg::read_ffmpeg_output has cognitive complexity 29 (threshold 15). Drivers by points: if/else 8 (19 pts), match/switch 3 (9 pts), loops 1 (nesting depth added 17). Of this number, 25 points are the body's own statements and 4 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_video::player::request_keyframe_before (cognitive 21) crates/utils/re_video/src/player/mod.rs:356— re_video::player::request_keyframe_before has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (15 pts), match/switch 2 (3 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_video::av1::detect_av1_keyframe_start (cognitive 19) crates/utils/re_video/src/av1.rs:25— re_video::av1::detect_av1_keyframe_start has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 2, match/switch 1 (2 pts), loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_video::demux::mp4::codec_details_from_stds (cognitive 18) crates/utils/re_video/src/demux/mp4.rs:233— re_video::demux::mp4::codec_details_from_stds has cognitive complexity 18 (threshold 15). Drivers by points: if/else 3 (10 pts), loops 2 (6 pts), boolean chains 1, match/switch 1 (nesting depth added 11). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
TooManyFields: DesignTokens crates/ui_tools/re_ui/src/design_tokens.rs:262— TooManyFields — 164 stored fields beside 52 methods. The bar is 30 stored fields; this is 134 over it, 5.47× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
TooManyFields: AppCore crates/top/re_viewer/src/app/mod.rs:197— TooManyFields — 39 stored fields beside 139 methods. The bar is 30 stored fields; this is 9 over it, 1.30× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
TooManyFields: QuerySnapshot crates/store_app/re_datafusion/src/metrics_capture.rs:240— TooManyFields — 39 stored fields. The bar is 30 stored fields; this is 9 over it, 1.30× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
TooManyFields: QueryMetrics crates/store_app/re_datafusion/src/metrics_capture.rs:102— TooManyFields — 36 stored fields beside 1 method. The bar is 30 stored fields; this is 6 over it, 1.20× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
TooManyFields: Args crates/top/rerun/src/commands/entrypoint.rs:137— TooManyFields — 31 stored fields beside 1 method. The bar is 30 stored fields; this is 1 over it, 1.03× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×5
Members sharing a duplicated core (4 members, 50+ identical tokens) crates/store/re_chunk/src/iter.rs:476— crates/store/re_chunk/src/iter.rs:476-501 | crates/store/re_chunk/src/iter.rs:553-590 | crates/store/re_chunk/src/iter.rs:637-668 | crates/store/re_chunk/src/iter.rs:778-825 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) crates/store/re_chunk/src/unit_chunk.rs:106— crates/store/re_chunk/src/unit_chunk.rs:106-118 | crates/store/re_chunk/src/unit_chunk.rs:159-171 | crates/store/re_chunk/src/unit_chunk.rs:400-412 | crates/store/re_chunk/src/unit_chunk.rs:443-455 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) crates/views/re_view_spatial/src/visualizers/boxes3d.rs:125— crates/views/re_view_spatial/src/visualizers/boxes3d.rs:125-232 | crates/views/re_view_spatial/src/visualizers/capsules3d.rs:165-257 | crates/views/re_view_spatial/src/visualizers/cylinders3d.rs:160-253 | crates/views/re_view_spatial/src/visualizers/ellipsoids.rs:133-239 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) docs/snippets/all/descriptors/descr_builtin_archetype.rs:30— docs/snippets/all/descriptors/descr_builtin_archetype.rs:30-78 | docs/snippets/all/descriptors/descr_builtin_component.rs:40-83 | docs/snippets/all/descriptors/descr_custom_archetype.rs:75-121 | docs/snippets/all/descriptors/descr_custom_component.rs:35-76 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) rerun_py/src/catalog/layer.rs:45— rerun_py/src/catalog/layer.rs:45-63 | rerun_py/src/catalog/layer.rs:65-83 | rerun_py/src/catalog/segment.rs:89-110 | rerun_py/src/catalog/segment.rs:113-135 — 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 (28 corresponding lines) · ×5
Edited copy of a member (28 corresponding lines) crates/views/re_view_spatial/src/visualizers/mod.rs:74— crates/views/re_view_spatial/src/visualizers/mod.rs:74-101 | crates/views/re_view_spatial/src/visualizers/mod.rs:105-134 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (28 corresponding lines) crates/ui_tools/re_renderer/src/resource_managers/bayer_converter.rs:150— crates/ui_tools/re_renderer/src/resource_managers/bayer_converter.rs:150-177 | crates/ui_tools/re_renderer/src/resource_managers/yuv_converter.rs:452-483 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (28 corresponding lines) crates/utils/re_case/src/lib.rs:105— crates/utils/re_case/src/lib.rs:105-132 | crates/utils/re_case/src/lib.rs:193-226 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (28 corresponding lines) crates/store/re_lenses_core/src/combinators/map.rs:39— crates/store/re_lenses_core/src/combinators/map.rs:39-66 | crates/store/re_lenses_core/src/combinators/map.rs:94-122 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (28 corresponding lines) rerun_py/rerun_sdk/rerun/experimental/_viewer_client.py:1216— rerun_py/rerun_sdk/rerun/experimental/_viewer_client.py:1216-1243 | rerun_py/rerun_sdk/rerun/experimental/_viewer_client.py:1253-1281 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (34 corresponding lines) · ×5
Edited copy of a member (34 corresponding lines) docs/snippets/all/archetypes/points3d_column_updates.rs:5— docs/snippets/all/archetypes/points3d_column_updates.rs:5-43 | docs/snippets/all/archetypes/points3d_row_updates.rs:5-38 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (34 corresponding lines) crates/store_app/re_datafusion/src/dataframe_query_provider/mod.rs:863— crates/store_app/re_datafusion/src/dataframe_query_provider/mod.rs:863-915 | crates/store_app/re_datafusion/src/dataframe_query_provider_wasm.rs:438-471 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (34 corresponding lines) crates/store_app/re_datafusion/src/dataset_manifest.rs:86— crates/store_app/re_datafusion/src/dataset_manifest.rs:86-124 | crates/store_app/re_datafusion/src/segment_table.rs:85-118 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (34 corresponding lines) crates/store/re_chunk_store/src/query.rs:1080— crates/store/re_chunk_store/src/query.rs:1080-1120 | crates/store/re_chunk_store/src/query.rs:1178-1211 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (34 corresponding lines) examples/python/using_index_values/using_index_values.py:53— examples/python/using_index_values/using_index_values.py:53-92 | examples/python/using_index_values/using_index_values.py:96-129 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (32 corresponding lines) · ×5
Edited copy of a member (32 corresponding lines) crates/store_app/re_server/src/rerun_cloud/mod.rs:1439— crates/store_app/re_server/src/rerun_cloud/mod.rs:1439-1471 | crates/store_app/re_server/src/rerun_cloud/mod.rs:1504-1535 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (32 corresponding lines) crates/utils/re_arrow_util/src/arrays.rs:303— crates/utils/re_arrow_util/src/arrays.rs:303-334 | crates/utils/re_arrow_util/src/arrays.rs:339-370 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (32 corresponding lines) crates/ui_tools/re_ui/src/command/ui_command.rs:491— crates/ui_tools/re_ui/src/command/ui_command.rs:491-522 | crates/viewer_support/re_viewer_context/src/command/recording_command.rs:393-424 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (32 corresponding lines) crates/utils/re_memory/src/accounting_allocator.rs:346— crates/utils/re_memory/src/accounting_allocator.rs:346-378 | crates/utils/re_memory/src/accounting_allocator.rs:381-412 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (32 corresponding lines) docs/snippets/all/tutorials/any_values.rs:7— docs/snippets/all/tutorials/any_values.rs:7-38 | docs/snippets/all/tutorials/dynamic_archetype.rs:7-39 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (26 corresponding lines) · ×5
Edited copy of a member (26 corresponding lines) crates/data_flow/re_importer/src/importer_parquet.rs:29— crates/data_flow/re_importer/src/importer_parquet.rs:29-54 | crates/data_flow/re_importer/src/importer_parquet.rs:62-88 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (26 corresponding lines) rerun_py/src/python_bridge.rs:1408— rerun_py/src/python_bridge.rs:1408-1439 | rerun_py/src/python_bridge.rs:1490-1515 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (26 corresponding lines) crates/viewer_support/re_dataframe_ui/src/re_table_utils.rs:40— crates/viewer_support/re_dataframe_ui/src/re_table_utils.rs:40-68 | crates/viewer_support/re_dataframe_ui/src/re_table_utils.rs:75-100 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (26 corresponding lines) crates/store_app/re_datafusion/src/dataframe_query_provider/mod.rs:919— crates/store_app/re_datafusion/src/dataframe_query_provider/mod.rs:919-944 | crates/store_app/re_datafusion/src/dataframe_query_provider_wasm.rs:526-551 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (26 corresponding lines) rerun_py/src/chunk_stream/stream.rs:188— rerun_py/src/chunk_stream/stream.rs:188-213 | rerun_py/src/chunk_stream/stream.rs:221-251 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (20 corresponding lines) · ×5
Edited copy of a member (20 corresponding lines) crates/store_app/re_server/src/rerun_cloud/mod.rs:99— crates/store_app/re_server/src/rerun_cloud/mod.rs:99-118 | crates/store_app/re_server/src/rerun_cloud/mod.rs:123-142 — 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) docs/snippets/all/archetypes/line_strips2d_batch.rs:3— docs/snippets/all/archetypes/line_strips2d_batch.rs:3-22 | docs/snippets/all/archetypes/line_strips3d_batch.rs:3-28 — 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/store/re_lenses_core/src/execute.rs:24— crates/store/re_lenses_core/src/execute.rs:24-51 | crates/store/re_lenses_core/src/execute.rs:59-78 — 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/store/re_chunk_store/src/lineage.rs:420— crates/store/re_chunk_store/src/lineage.rs:420-439 | crates/store/re_chunk_store/src/lineage.rs:457-476 — 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/top/re_sdk/src/recording_stream.rs:208— crates/top/re_sdk/src/recording_stream.rs:208-229 | crates/top/re_sdk/src/recording_stream.rs:235-254 — 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.
Duplicated block (21 lines × 2) crates/store/re_chunk/src/iter.rs:559— crates/store/re_chunk/src/iter.rs:559-579 | crates/store/re_chunk/src/iter.rs:787-807 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/store/re_chunk/src/iter.rs:559` it does not close everything it opens, so those 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/store/re_chunk/src/iter.rs:784` calls `offsets`, `lengths`, `collect_vec` and `crates/store/re_chunk/src/iter.rs:557` 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 (21 lines × 2) crates/store_app/re_datafusion/src/dataframe_query_provider/segment_store.rs:99— crates/store_app/re_datafusion/src/dataframe_query_provider/segment_store.rs:99-119 | crates/store_app/re_datafusion/src/dataframe_query_provider_wasm.rs:381-401 — 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 (21 lines × 2) crates/top/re_sdk/src/grpc_server.rs:46— crates/top/re_sdk/src/grpc_server.rs:46-66 | crates/top/re_sdk/src/web_viewer.rs:53-73 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (21 lines × 2) crates/top/re_viewer/src/app/command_handling.rs:647— crates/top/re_viewer/src/app/command_handling.rs:647-667 | crates/top/re_viewer/src/app/command_handling.rs:679-699 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/top/re_viewer/src/app/command_handling.rs:647` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (21 lines × 2) crates/views/re_view_spatial/src/visualizers/points2d.rs:309— crates/views/re_view_spatial/src/visualizers/points2d.rs:309-329 | crates/views/re_view_spatial/src/visualizers/points3d.rs:489-509 — before extracting anything, compare `crates/views/re_view_spatial/src/visualizers/points2d.rs` and `crates/views/re_view_spatial/src/visualizers/points3d.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 66 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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/views/re_view_spatial/src/visualizers/points2d.rs:309` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18 lines × 2) crates/store/re_sorbet/src/migrations/v0_1_1__to__v0_1_2.rs:135— crates/store/re_sorbet/src/migrations/v0_1_1__to__v0_1_2.rs:135-152 | crates/store/re_sorbet/src/migrations/v0_1_1__to__v0_1_2.rs:180-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/store/re_sorbet/src/migrations/v0_1_1__to__v0_1_2.rs:135` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18 lines × 2) crates/store_app/re_datafusion/src/dataframe_query_provider/mod.rs:898— crates/store_app/re_datafusion/src/dataframe_query_provider/mod.rs:898-915 | crates/store_app/re_datafusion/src/dataframe_query_provider_wasm.rs:454-471 — 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/store_app/re_datafusion/src/dataframe_query_provider/mod.rs:898` 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/store_app/re_server/src/store/in_memory_store.rs:212— crates/store_app/re_server/src/store/in_memory_store.rs:212-229 | crates/store_app/re_server/src/store/in_memory_store.rs:286-303 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (18 lines × 2) crates/top/re_viewer/src/app/logic.rs:99— crates/top/re_viewer/src/app/logic.rs:99-119 | crates/top/re_viewer/src/app/mod.rs:1909-1926 — before extracting anything, compare `crates/top/re_viewer/src/app/logic.rs` and `crates/top/re_viewer/src/app/mod.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 46 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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/top/re_viewer/src/app/logic.rs:99` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18 lines × 2) crates/views/re_view_spatial/src/visualizers/points2d.rs:108— crates/views/re_view_spatial/src/visualizers/points2d.rs:108-125 | crates/views/re_view_spatial/src/visualizers/points3d.rs:290-307 — before extracting anything, compare `crates/views/re_view_spatial/src/visualizers/points2d.rs` and `crates/views/re_view_spatial/src/visualizers/points3d.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 66 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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/views/re_view_spatial/src/visualizers/points2d.rs:108` 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–12 lines × 2) crates/data_flow/re_mcap/src/parsers/ros2msg/sensor_msgs/joint_state.rs:39— crates/data_flow/re_mcap/src/parsers/ros2msg/sensor_msgs/joint_state.rs:39-50 | crates/data_flow/re_mcap/src/parsers/ros2msg/sensor_msgs/joy.rs:35-44 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `crates/data_flow/re_mcap/src/parsers/ros2msg/sensor_msgs/joint_state.rs:39` 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–12 lines × 2) crates/panels/re_recording_panel/src/recording_panel_ui.rs:886— crates/panels/re_recording_panel/src/recording_panel_ui.rs:886-895 | crates/viewer_support/re_data_ui/src/item_ui.rs:585-596 — 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/panels/re_recording_panel/src/recording_panel_ui.rs:886` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (10–12 lines × 2) crates/viewer_support/re_viewer_context/src/app_context.rs:473— crates/viewer_support/re_viewer_context/src/app_context.rs:473-484 | crates/viewer_support/re_viewer_context/src/blueprint_helpers.rs:201-210 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (10–12 lines × 2) examples/python/dataloader/prepare_dataset.py:109— examples/python/dataloader/prepare_dataset.py:109-118 | examples/python/droid_semantic_search/prepare_dataset.py:128-139 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (10–12 lines × 2) scripts/update_docs_url_rewrite.py:93— scripts/update_docs_url_rewrite.py:93-102 | scripts/update_docs_url_rewrite.py:115-126 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 3) crates/panels/re_selection_panel/src/selection_panel.rs:698— crates/panels/re_selection_panel/src/selection_panel.rs:698-707 | crates/panels/re_selection_panel/src/visualizer_ui.rs:559-567 | crates/viewer_support/re_view/src/component_drop.rs:276-284 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `crates/panels/re_selection_panel/src/selection_panel.rs:698` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 3) crates/ui_tools/re_renderer/src/importer/ply.rs:489— crates/ui_tools/re_renderer/src/importer/ply.rs:489-497 | crates/ui_tools/re_renderer/src/importer/ply.rs:513-521 | crates/ui_tools/re_renderer/src/importer/ply.rs:526-534 — 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/ui_tools/re_renderer/src/importer/ply.rs:489` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 3) crates/store/re_sorbet/src/migrations/make_list_arrays.rs:28— crates/store/re_sorbet/src/migrations/make_list_arrays.rs:28-36 | crates/store/re_sorbet/src/migrations/v0_0_1__to__v0_0_2.rs:91-99 | crates/store/re_sorbet/src/migrations/v0_0_1__to__v0_0_2.rs:216-224 — 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/store/re_sorbet/src/migrations/make_list_arrays.rs:28` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 3) crates/ui_tools/re_renderer/src/renderer/depth_cloud.rs:380— crates/ui_tools/re_renderer/src/renderer/depth_cloud.rs:380-388 | crates/ui_tools/re_renderer/src/renderer/mesh_renderer.rs:444-452 | crates/ui_tools/re_renderer/src/renderer/point_cloud.rs:654-662 — before extracting anything, compare `crates/ui_tools/re_renderer/src/renderer/depth_cloud.rs` and `crates/ui_tools/re_renderer/src/renderer/mesh_renderer.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 35 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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/ui_tools/re_renderer/src/renderer/depth_cloud.rs:380` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 3) rerun_py/rerun_sdk/rerun/archetypes/depth_image_ext.py:116— rerun_py/rerun_sdk/rerun/archetypes/depth_image_ext.py:116-124 | rerun_py/rerun_sdk/rerun/archetypes/image_ext.py:208-216 | rerun_py/rerun_sdk/rerun/archetypes/segmentation_image_ext.py:49-57 — before extracting anything, compare `rerun_py/rerun_sdk/rerun/archetypes/depth_image_ext.py` and `rerun_py/rerun_sdk/rerun/archetypes/segmentation_image_ext.py` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 43 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 (8–9 lines × 2) crates/data_flow/re_importer/src/importer_urdf/joint_transform.rs:110— crates/data_flow/re_importer/src/importer_urdf/joint_transform.rs:110-117 | crates/data_flow/re_importer/src/importer_urdf/joint_transform.rs:137-145 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/data_flow/re_importer/src/importer_urdf/joint_transform.rs:110` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (8–9 lines × 2) crates/data_flow/re_importer/src/importer_urdf/mod.rs:536— crates/data_flow/re_importer/src/importer_urdf/mod.rs:536-543 | crates/data_flow/re_importer/src/importer_urdf/mod.rs:736-744 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/data_flow/re_importer/src/importer_urdf/mod.rs:536` 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–9 lines × 2) crates/top/re_viewer/src/app/mod.rs:1176— crates/top/re_viewer/src/app/mod.rs:1176-1184 | crates/top/re_viewer/src/app/mod.rs:1195-1202 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8–9 lines × 2) crates/viewer_support/re_viewer_context/src/tensor/image_stats.rs:108— crates/viewer_support/re_viewer_context/src/tensor/image_stats.rs:108-116 | crates/viewer_support/re_viewer_context/src/tensor/tensor_stats.rs:104-111 — before extracting anything, compare `crates/viewer_support/re_viewer_context/src/tensor/image_stats.rs` and `crates/viewer_support/re_viewer_context/src/tensor/tensor_stats.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 31 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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/viewer_support/re_viewer_context/src/tensor/image_stats.rs:108` 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–9 lines × 2) crates/views/re_view_time_series/src/line_visualizer_system.rs:51— crates/views/re_view_time_series/src/line_visualizer_system.rs:51-59 | crates/views/re_view_time_series/src/point_visualizer_system.rs:48-55 — before extracting anything, compare `crates/views/re_view_time_series/src/line_visualizer_system.rs` and `crates/views/re_view_time_series/src/point_visualizer_system.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 73 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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/views/re_view_time_series/src/line_visualizer_system.rs:51` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 3) docs/snippets/all/archetypes/transform3d_hierarchy.rs:19— docs/snippets/all/archetypes/transform3d_hierarchy.rs:19-25 | docs/snippets/all/archetypes/transform3d_hierarchy.rs:29-35 | docs/snippets/all/archetypes/transform3d_hierarchy.rs:39-45 — 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 `docs/snippets/all/archetypes/transform3d_hierarchy.rs:19` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 3) crates/viewer_support/re_component_ui/src/geo_line_string.rs:44— crates/viewer_support/re_component_ui/src/geo_line_string.rs:44-50 | crates/viewer_support/re_component_ui/src/line_strip.rs:50-56 | crates/viewer_support/re_component_ui/src/line_strip.rs:112-118 — 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/viewer_support/re_component_ui/src/geo_line_string.rs:44` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `value` to `&mut MaybeMutRef<'_, GeoLineString>` in one and `&mut MaybeMutRef<'_, LineStrip3D>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (7 lines × 3) crates/store/re_uri/src/endpoints/dataset.rs:206— crates/store/re_uri/src/endpoints/dataset.rs:206-212 | crates/store/re_uri/src/endpoints/entry.rs:30-36 | crates/store/re_uri/src/endpoints/folder.rs:43-49 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (7 lines × 3) crates/viewer_support/re_component_ui/src/color.rs:11— crates/viewer_support/re_component_ui/src/color.rs:11-17 | crates/viewer_support/re_component_ui/src/encoding_uis/range1d.rs:10-16 | crates/viewer_support/re_component_ui/src/encoding_uis/singleline_string.rs:44-50 — 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/viewer_support/re_component_ui/src/color.rs:11` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `value` to `&mut MaybeMutRef<'_, impl std::ops::DerefMut<Target = Rgba32>>` in one and `&mut MaybeMutRef<'_, impl std::ops::DerefMut<Target = Range1D>>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (7 lines × 3) crates/ui_tools/re_renderer/src/renderer/lines.rs:681— crates/ui_tools/re_renderer/src/renderer/lines.rs:681-689 | crates/ui_tools/re_renderer/src/renderer/point_cloud.rs:707-715 | crates/ui_tools/re_renderer/src/renderer/voxel_grid.rs:317-323 — before extracting anything, compare `crates/ui_tools/re_renderer/src/renderer/lines.rs` and `crates/ui_tools/re_renderer/src/renderer/point_cloud.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 103 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/ui_tools/re_renderer/src/renderer/lines.rs:681` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
QueryHandle::try_bulk_emit_run (cyclomatic 38) crates/store_app/re_dataframe/src/query.rs:2132— QueryHandle::try_bulk_emit_run has cyclomatic complexity 38 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
QueryHandle::next_n_rows_in_store (cyclomatic 34) crates/store_app/re_dataframe/src/query.rs:1788— QueryHandle::next_n_rows_in_store has cyclomatic complexity 34 (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.
QueryHandle::resolve_one_row (cyclomatic 27) crates/store_app/re_dataframe/src/query.rs:1427— QueryHandle::resolve_one_row 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.
QueryHandle::init_ (cyclomatic 16) crates/store_app/re_dataframe/src/query.rs:564— QueryHandle::init_ 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.
re_datafusion::dataframe_query_provider::cpu_worker::chunk_store_cpu_worker_thread (cyclomatic 32) crates/store_app/re_datafusion/src/dataframe_query_provider/cpu_worker.rs:304— re_datafusion::dataframe_query_provider::cpu_worker::chunk_store_cpu_worker_thread has cyclomatic complexity 32 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
re_datafusion::pushdown_expressions::known_filter_column (cyclomatic 18) crates/store_app/re_datafusion/src/pushdown_expressions.rs:677— re_datafusion::pushdown_expressions::known_filter_column has cyclomatic complexity 18 (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.
re_datafusion::pushdown_expressions::apply_filter_expr_to_queries (cyclomatic 16) crates/store_app/re_datafusion/src/pushdown_expressions.rs:465— re_datafusion::pushdown_expressions::apply_filter_expr_to_queries 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.
re_datafusion::pushdown_expressions::merge_queries_and (cyclomatic 16) crates/store_app/re_datafusion/src/pushdown_expressions.rs:736— re_datafusion::pushdown_expressions::merge_queries_and 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.
re_dataframe_ui::filters::column_filter_ui::column_picker_ui (cyclomatic 31) crates/viewer_support/re_dataframe_ui/src/filters/column_filter_ui.rs:89— re_dataframe_ui::filters::column_filter_ui::column_picker_ui has cyclomatic complexity 31 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
re_dataframe_ui::cards_view::card_content_ui (cyclomatic 20) crates/viewer_support/re_dataframe_ui/src/cards_view.rs:207— re_dataframe_ui::cards_view::card_content_ui has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
re_dataframe_ui::preview_renderer::preview_timeline (cyclomatic 20) crates/viewer_support/re_dataframe_ui/src/preview_renderer.rs:843— re_dataframe_ui::preview_renderer::preview_timeline has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
re_dataframe_ui::preview_renderer::preview_playback_ui (cyclomatic 19) crates/viewer_support/re_dataframe_ui/src/preview_renderer.rs:644— re_dataframe_ui::preview_renderer::preview_playback_ui has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
re_view_spatial::shared_fallbacks::register_fallbacks (cyclomatic 24) crates/views/re_view_spatial/src/shared_fallbacks.rs:27— re_view_spatial::shared_fallbacks::register_fallbacks has cyclomatic complexity 24 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
re_view_spatial::visualizers::video::execute_video_stream_like (cyclomatic 20) crates/views/re_view_spatial/src/visualizers/video/mod.rs:166— re_view_spatial::visualizers::video::execute_video_stream_like has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
re_view_spatial::visualizers::video::show_video_frame (cyclomatic 20) crates/views/re_view_spatial/src/visualizers/video/mod.rs:586— re_view_spatial::visualizers::video::show_video_frame has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
re_view_spatial::picking_ui::picking (cyclomatic 17) crates/views/re_view_spatial/src/picking_ui.rs:28— re_view_spatial::picking_ui::picking 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.
re_data_ui::entity_db_ui::grid_content_ui (cyclomatic 22) crates/viewer_support/re_data_ui/src/entity_db_ui.rs:102— re_data_ui::entity_db_ui::grid_content_ui has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
re_data_ui::video_ui::video_data_ui (cyclomatic 21) crates/viewer_support/re_data_ui/src/video_ui.rs:93— re_data_ui::video_ui::video_data_ui 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.
re_data_ui::item_ui::entity_db_button_ui (cyclomatic 19) crates/viewer_support/re_data_ui/src/item_ui.rs:472— re_data_ui::item_ui::entity_db_button_ui has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
re_data_ui::video_ui::decoded_frame_ui (cyclomatic 16) crates/viewer_support/re_data_ui/src/video_ui.rs:390— re_data_ui::video_ui::decoded_frame_ui 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.
re_component_ui::table_cells::redap_uri_button::redap_uri_button (cognitive 45) crates/viewer_support/re_component_ui/src/table_cells/redap_uri_button.rs:18— re_component_ui::table_cells::redap_uri_button::redap_uri_button has cognitive complexity 45 (threshold 15). Drivers by points: if/else 31 (41 pts), boolean chains 2, match/switch 2 (nesting depth added 10). 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.
re_component_ui::table_cells::layer_names::layer_names (cognitive 22) crates/viewer_support/re_component_ui/src/table_cells/layer_names.rs:15— re_component_ui::table_cells::layer_names::layer_names has cognitive complexity 22 (threshold 15). Drivers by points: if/else 13 (17 pts), loops 3 (4 pts), boolean chains 1 (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
re_component_ui::table_cells::flag::flag_button (cognitive 19) crates/viewer_support/re_component_ui/src/table_cells/flag.rs:37— re_component_ui::table_cells::flag::flag_button has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (18 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_component_ui::encoding_uis::enum_ui::edit_view_enum_impl (cognitive 18) crates/viewer_support/re_component_ui/src/encoding_uis/enum_ui.rs:65— re_component_ui::encoding_uis::enum_ui::edit_view_enum_impl has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (12 pts), loops 2 (6 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.
re_lenses_core::execute::execute (cognitive 43) crates/store/re_lenses_core/src/execute.rs:331— re_lenses_core::execute::execute has cognitive complexity 43 (threshold 15). Drivers by points: if/else 12 (19 pts), match/switch 5 (15 pts), loops 3 (7 pts), boolean chains 2 (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_lenses_core::plan::plan (cognitive 24) crates/store/re_lenses_core/src/plan.rs:95— re_lenses_core::plan::plan has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (18 pts), loops 3, boolean chains 2, match/switch 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_lenses_core::execute::apply_one_to_many (cognitive 18) crates/store/re_lenses_core/src/execute.rs:227— re_lenses_core::execute::apply_one_to_many has cognitive complexity 18 (threshold 15). Drivers by points: match/switch 6 (12 pts), if/else 2 (5 pts), loops 1 (nesting depth added 9). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
re_lenses_core::selector::eval::eval_pack (cognitive 18) crates/store/re_lenses_core/src/selector/eval.rs:249— re_lenses_core::selector::eval::eval_pack has cognitive complexity 18 (threshold 15). Drivers by points: loops 4 (7 pts), if/else 4 (6 pts), match/switch 2 (4 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_renderer::importer::gltf::import_mesh (cognitive 33) crates/ui_tools/re_renderer/src/importer/gltf.rs:173— re_renderer::importer::gltf::import_mesh has cognitive complexity 33 (threshold 15). Drivers by points: if/else 17 (29 pts), boolean chains 3, loops 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_renderer::importer::ply::parse_ply_mesh (cognitive 33) crates/ui_tools/re_renderer/src/importer/ply.rs:439— re_renderer::importer::ply::parse_ply_mesh has cognitive complexity 33 (threshold 15). Drivers by points: if/else 8 (16 pts), loops 4 (12 pts), match/switch 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.
re_renderer::importer::gltf::load_gltf_from_buffer (cognitive 17) crates/ui_tools/re_renderer/src/importer/gltf.rs:43— re_renderer::importer::gltf::load_gltf_from_buffer has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (10 pts), loops 4 (5 pts), match/switch 1 (2 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_renderer::renderer::plane_clustering::overlapping_clusters (cognitive 16) crates/ui_tools/re_renderer/src/renderer/plane_clustering.rs:112— re_renderer::renderer::plane_clustering::overlapping_clusters has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (10 pts), loops 3 (6 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_importer::importer_rrd::decode_and_stream (cognitive 32) crates/data_flow/re_importer/src/importer_rrd.rs:164— re_importer::importer_rrd::decode_and_stream has cognitive complexity 32 (threshold 15). Drivers by points: if/else 8 (25 pts), match/switch 2 (5 pts), boolean chains 1, loops 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.
re_importer::import_file::import (cognitive 18) crates/data_flow/re_importer/src/import_file.rs:136— re_importer::import_file::import has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (17 pts), loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_importer::importer_lerobot::load_and_stream (cognitive 18) crates/data_flow/re_importer/src/importer_lerobot.rs:135— re_importer::importer_lerobot::load_and_stream has cognitive complexity 18 (threshold 15). Drivers by points: if/else 2 (8 pts), match/switch 2 (6 pts), loops 2 (4 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.
re_importer::importer_mcap::robot_description::extract_urdf_from_robot_descriptions (cognitive 17) crates/data_flow/re_importer/src/importer_mcap/robot_description.rs:17— re_importer::importer_mcap::robot_description::extract_urdf_from_robot_descriptions has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (5 pts), loops 3 (5 pts), match/switch 2 (4 pts), boolean chains 3 (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.
re_tf::transform_forest::transforms_at (cognitive 23) crates/store_app/re_tf/src/transform_forest.rs:719— re_tf::transform_forest::transforms_at has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (17 pts), loops 1 (4 pts), boolean chains 2 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_tf::transform_queries::query_and_resolve_instance_poses_at_entity (cognitive 17) crates/store_app/re_tf/src/transform_queries.rs:333— re_tf::transform_queries::query_and_resolve_instance_poses_at_entity has cognitive complexity 17 (threshold 15). Drivers by points: if/else 14 (16 pts), boolean chains 1 (nesting depth added 2). Of this number, 16 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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.
re_tf::transform_queries::query_and_resolve_tree_transform_at_entity (cognitive 16) crates/store_app/re_tf/src/transform_queries.rs:190— re_tf::transform_queries::query_and_resolve_tree_transform_at_entity has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 2 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
re_tf::transform_resolution_cache::transform_cache_snapshot::latest_at (cognitive 16) crates/store_app/re_tf/src/transform_resolution_cache/transform_cache_snapshot.rs:139— re_tf::transform_resolution_cache::transform_cache_snapshot::latest_at has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (13 pts), loops 2, boolean chains 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_mcap::decoders::protobuf::append_message_fields (cognitive 21) crates/data_flow/re_mcap/src/decoders/protobuf.rs:114— re_mcap::decoders::protobuf::append_message_fields has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 2 (4 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_mcap::recover::build_chunk_index (cognitive 21) crates/data_flow/re_mcap/src/recover.rs:72— re_mcap::recover::build_chunk_index has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (18 pts), match/switch 1 (2 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.
re_mcap::parsers::ros2msg::sensor_msgs::point_cloud_2::add_field_value (cognitive 20) crates/data_flow/re_mcap/src/parsers/ros2msg/sensor_msgs/point_cloud_2.rs:213— re_mcap::parsers::ros2msg::sensor_msgs::point_cloud_2::add_field_value has cognitive complexity 20 (threshold 15). Drivers by points: if/else 13 (19 pts), match/switch 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_mcap::recover::reconstruct_summary (cognitive 20) crates/data_flow/re_mcap/src/recover.rs:210— re_mcap::recover::reconstruct_summary has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (11 pts), loops 4 (7 pts), match/switch 1 (2 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_view::query::component_not_found_error (cognitive 21) crates/viewer_support/re_view/src/query.rs:183— re_view::query::component_not_found_error has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (15 pts), boolean chains 3, loops 1 (3 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_view::view_property_ui::view_property_ui_impl (cognitive 20) crates/viewer_support/re_view/src/view_property_ui.rs:81— re_view::view_property_ui::view_property_ui_impl has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 2, 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.
re_view::query::range_with_blueprint_resolved_data_polymorphic (cognitive 17) crates/viewer_support/re_view/src/query.rs:291— re_view::query::range_with_blueprint_resolved_data_polymorphic has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (8 pts), match/switch 2 (5 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_view::query::latest_at_with_blueprint_resolved_data_polymorphic (cognitive 16) crates/viewer_support/re_view/src/query.rs:475— re_view::query::latest_at_with_blueprint_resolved_data_polymorphic has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (10 pts), match/switch 2 (4 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.
re_chunk_optimizer::executor::cut::cut_to_fit (cognitive 20) crates/store/re_chunk_optimizer/src/executor/cut.rs:30— re_chunk_optimizer::executor::cut::cut_to_fit has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (15 pts), boolean chains 2, match/switch 1 (2 pts), loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_chunk_optimizer::executor::gop::decide_codec (cognitive 19) crates/store/re_chunk_optimizer/src/executor/gop.rs:38— re_chunk_optimizer::executor::gop::decide_codec has cognitive complexity 19 (threshold 15). Drivers by points: loops 3 (9 pts), match/switch 3 (8 pts), if/else 1 (2 pts) (nesting depth added 12). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
re_chunk_optimizer::plan::plan (cognitive 19) crates/store/re_chunk_optimizer/src/plan.rs:225— re_chunk_optimizer::plan::plan has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 5 (6 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_chunk_optimizer::executor::accumulator::merge_and_emit (cognitive 17) crates/store/re_chunk_optimizer/src/executor/accumulator.rs:212— re_chunk_optimizer::executor::accumulator::merge_and_emit has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D4 · Code Duplication· Members sharing a duplicated core (5 members, 50+ identical tokens) · ×4
Members sharing a duplicated core (5 members, 50+ identical tokens) crates/top/re_viewer/data/quick_start_guides/quick_start_connect.rs:5— crates/top/re_viewer/data/quick_start_guides/quick_start_connect.rs:5-24 | crates/top/re_viewer/data/quick_start_guides/quick_start_spawn.rs:5-25 | docs/snippets/all/howto/set_sinks.rs:5-34 | docs/snippets/all/quick_start/quick_start_connect.rs:5-25 | docs/snippets/all/quick_start/quick_start_spawn.rs:5-27 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) crates/ui_tools/re_renderer/src/renderer/debug_overlay.rs:247— crates/ui_tools/re_renderer/src/renderer/debug_overlay.rs:247-257 | crates/ui_tools/re_renderer/src/renderer/generic_skybox.rs:174-186 | crates/ui_tools/re_renderer/src/renderer/world_grid.rs:200-210 | crates/ui_tools/re_renderer/src/resource_managers/bayer_converter.rs:272-283 | crates/ui_tools/re_renderer/src/resource_managers/yuv_converter.rs:579-590 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) crates/ui_tools/re_renderer/src/renderer/depth_cloud.rs:379— crates/ui_tools/re_renderer/src/renderer/depth_cloud.rs:379-500 | crates/ui_tools/re_renderer/src/renderer/gaussian_splat.rs:654-818 | crates/ui_tools/re_renderer/src/renderer/lines.rs:627-798 | crates/ui_tools/re_renderer/src/renderer/point_cloud.rs:653-849 | crates/ui_tools/re_renderer/src/renderer/volume.rs:199-337 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) crates/ui_tools/re_renderer/src/renderer/depth_cloud.rs:379— crates/ui_tools/re_renderer/src/renderer/depth_cloud.rs:379-500 | crates/ui_tools/re_renderer/src/renderer/gaussian_splat.rs:654-818 | crates/ui_tools/re_renderer/src/renderer/point_cloud.rs:653-849 | crates/ui_tools/re_renderer/src/renderer/volume.rs:199-337 | crates/ui_tools/re_renderer/src/renderer/voxel_grid.rs:314-415 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
D4 · Code Duplication· Edited copy of a member (40 corresponding lines) · ×4
Edited copy of a member (40 corresponding lines) crates/viewer_support/re_viewer_context/src/blueprint_helpers.rs:304— crates/viewer_support/re_viewer_context/src/blueprint_helpers.rs:304-343 | crates/viewer_support/re_viewer_context/src/blueprint_helpers.rs:349-388 — These two members are one piece of code written twice and then edited apart: 40 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (40 corresponding lines) crates/panels/re_redap_browser/src/entries.rs:436— crates/panels/re_redap_browser/src/entries.rs:436-476 | crates/panels/re_redap_browser/src/entries.rs:535-574 — These two members are one piece of code written twice and then edited apart: 40 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (40 corresponding lines) crates/store_app/re_dataframe/src/query.rs:1281— crates/store_app/re_dataframe/src/query.rs:1281-1320 | crates/store_app/re_dataframe/src/query.rs:1745-1785 — These two members are one piece of code written twice and then edited apart: 40 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (40 corresponding lines) crates/store/re_chunk_store/src/query.rs:556— crates/store/re_chunk_store/src/query.rs:556-598 | crates/store/re_chunk_store/src/query.rs:609-648 — 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 (23 corresponding lines) · ×4
Edited copy of a member (23 corresponding lines) docs/snippets/all/archetypes/points2d_random.rs:5— docs/snippets/all/archetypes/points2d_random.rs:5-27 | docs/snippets/all/archetypes/points3d_random.rs:5-27 — 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/viewer_support/re_component_ui/src/table_cells/checkbox.rs:16— crates/viewer_support/re_component_ui/src/table_cells/checkbox.rs:16-43 | crates/viewer_support/re_component_ui/src/table_cells/flag.rs:13-35 — 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/viewer_support/re_viewer_context/src/view/view_query.rs:427— crates/viewer_support/re_viewer_context/src/view/view_query.rs:427-449 | crates/viewer_support/re_viewer_context/src/view/view_query.rs:462-484 — 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/store/re_chunk_store/src/dataframe.rs:251— crates/store/re_chunk_store/src/dataframe.rs:251-273 | crates/store/re_chunk_store/src/dataframe.rs:275-303 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 20+ corresponding lines) · ×4
Edited copies of one member (3 members, 20+ corresponding lines) crates/utils/re_perf_telemetry/src/prometheus.rs:294— crates/utils/re_perf_telemetry/src/prometheus.rs:294-317 | crates/utils/re_perf_telemetry/src/prometheus.rs:325-348 | crates/utils/re_perf_telemetry/src/prometheus.rs:356-375 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 20 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 20+ corresponding lines) crates/data_flow/re_redap_client/src/connection_client/datasets.rs:111— crates/data_flow/re_redap_client/src/connection_client/datasets.rs:111-132 | crates/data_flow/re_redap_client/src/connection_client/datasets.rs:136-155 | crates/data_flow/re_redap_client/src/connection_client/datasets.rs:163-189 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 20 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 20+ corresponding lines) rerun_py/src/catalog/policy_handle.rs:33— rerun_py/src/catalog/policy_handle.rs:33-52 | rerun_py/src/catalog/unregistration_handle.rs:49-72 | rerun_py/src/catalog/unregistration_handle.rs:77-97 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 20 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 20+ corresponding lines) crates/store_app/re_datafusion/src/dataset_manifest.rs:143— crates/store_app/re_datafusion/src/dataset_manifest.rs:143-162 | crates/store_app/re_datafusion/src/segment_table.rs:134-153 | crates/store_app/re_datafusion/src/table_entry_provider.rs:285-304 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 20 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Duplicated block (26 lines × 2) crates/store_app/re_tf/src/transform_resolution_cache/tree_transforms_for_child_frame.rs:229— crates/store_app/re_tf/src/transform_resolution_cache/tree_transforms_for_child_frame.rs:229-254 | crates/store_app/re_tf/src/transform_resolution_cache/tree_transforms_for_child_frame.rs:301-326 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/store_app/re_tf/src/transform_resolution_cache/tree_transforms_for_child_frame.rs:229` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `crates/store_app/re_tf/src/transform_resolution_cache/tree_transforms_for_child_frame.rs:228` calls `associated_entity_path` and `crates/store_app/re_tf/src/transform_resolution_cache/tree_transforms_for_child_frame.rs:300` 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 (26 lines × 2) crates/views/re_view_spatial/src/visualizers/capsules3d.rs:203— crates/views/re_view_spatial/src/visualizers/capsules3d.rs:203-228 | crates/views/re_view_spatial/src/visualizers/cylinders3d.rs:199-224 — 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/views/re_view_spatial/src/visualizers/capsules3d.rs:203` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `crates/views/re_view_spatial/src/visualizers/cylinders3d.rs:197` calls `iter_optional`, `descriptor_show_labels` and `crates/views/re_view_spatial/src/visualizers/capsules3d.rs:201` 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 (26 lines × 2) crates/ui_tools/re_renderer/src/renderer/gaussian_splat.rs:719— crates/ui_tools/re_renderer/src/renderer/gaussian_splat.rs:719-744 | crates/ui_tools/re_renderer/src/renderer/point_cloud.rs:733-758 — before extracting anything, compare `crates/ui_tools/re_renderer/src/renderer/gaussian_splat.rs` and `crates/ui_tools/re_renderer/src/renderer/point_cloud.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 207 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/ui_tools/re_renderer/src/renderer/gaussian_splat.rs:719` 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 (26 lines × 2) rerun_py/rerun_sdk/rerun/archetypes/depth_image_ext.py:118— rerun_py/rerun_sdk/rerun/archetypes/depth_image_ext.py:118-143 | rerun_py/rerun_sdk/rerun/archetypes/segmentation_image_ext.py:51-76 — before extracting anything, compare `rerun_py/rerun_sdk/rerun/archetypes/depth_image_ext.py` and `rerun_py/rerun_sdk/rerun/archetypes/segmentation_image_ext.py` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 43 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `rerun_py/rerun_sdk/rerun/archetypes/depth_image_ext.py:118` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (22 lines × 2) crates/data_flow/re_grpc_server/src/lib.rs:520— crates/data_flow/re_grpc_server/src/lib.rs:520-541 | crates/data_flow/re_grpc_server/src/lib.rs:617-638 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/data_flow/re_grpc_server/src/lib.rs:520` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (22 lines × 2) crates/store/re_sdk_types/src/archetypes/points2d_ext.rs:160— crates/store/re_sdk_types/src/archetypes/points2d_ext.rs:160-181 | crates/store/re_sdk_types/src/archetypes/points3d_ext.rs:165-186 — before extracting anything, compare `crates/store/re_sdk_types/src/archetypes/points2d_ext.rs` and `crates/store/re_sdk_types/src/archetypes/points3d_ext.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 65 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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/store/re_sdk_types/src/archetypes/points2d_ext.rs:160` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (22 lines × 2) crates/viewer_support/re_dataframe_ui/src/filters/numerical.rs:155— crates/viewer_support/re_dataframe_ui/src/filters/numerical.rs:155-176 | crates/viewer_support/re_dataframe_ui/src/filters/numerical.rs:263-284 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (22 lines × 2) crates/viewer_support/re_viewer_context/src/command/command_kind.rs:221— crates/viewer_support/re_viewer_context/src/command/command_kind.rs:221-242 | crates/viewer_support/re_viewer_context/src/command/command_kind.rs:326-347 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/viewer_support/re_viewer_context/src/command/command_kind.rs:221` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (12–14 lines × 2) crates/data_flow/re_data_source/src/stream_rrd_from_http.rs:21— crates/data_flow/re_data_source/src/stream_rrd_from_http.rs:21-32 | crates/viewer_support/re_viewer_context/src/viewer_url.rs:1101-1114 — 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/data_flow/re_data_source/src/stream_rrd_from_http.rs:21` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (12–14 lines × 2) crates/panels/re_time_panel/src/time_panel.rs:921— crates/panels/re_time_panel/src/time_panel.rs:921-934 | crates/panels/re_time_panel/src/time_panel.rs:1115-1126 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/panels/re_time_panel/src/time_panel.rs:921` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (12–14 lines × 2) crates/top/re_viewer/src/app/logic.rs:465— crates/top/re_viewer/src/app/logic.rs:465-478 | crates/top/re_viewer/src/app/mod.rs:1718-1729 — before extracting anything, compare `crates/top/re_viewer/src/app/logic.rs` and `crates/top/re_viewer/src/app/mod.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 46 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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/top/re_viewer/src/app/logic.rs:465` it does not close everything it opens, so those exact lines 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–14 lines × 2) crates/views/re_view_spatial/src/view_3d.rs:585— crates/views/re_view_spatial/src/view_3d.rs:585-596 | crates/views/re_view_text_log/src/view_class.rs:483-496 — 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/views/re_view_spatial/src/view_3d.rs:585` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (13–14 lines × 2) crates/store_app/re_query/src/latest_at.rs:106— crates/store_app/re_query/src/latest_at.rs:106-119 | crates/store_app/re_query/src/latest_at.rs:170-182 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13–14 lines × 2) crates/views/re_view_spatial/src/visualizers/gaussian_splats3d.rs:408— crates/views/re_view_spatial/src/visualizers/gaussian_splats3d.rs:408-421 | crates/views/re_view_spatial/src/visualizers/points3d.rs:422-434 — before extracting anything, compare `crates/views/re_view_spatial/src/visualizers/gaussian_splats3d.rs` and `crates/views/re_view_spatial/src/visualizers/points3d.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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/views/re_view_spatial/src/visualizers/gaussian_splats3d.rs:408` 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/viewer_support/re_viewer_context/src/image_info.rs:402— crates/viewer_support/re_viewer_context/src/image_info.rs:402-414 | crates/viewer_support/re_viewer_context/src/image_info.rs:417-430 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/viewer_support/re_viewer_context/src/image_info.rs:417` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13–14 lines × 2) examples/python/droid_semantic_search/ingest.py:53— examples/python/droid_semantic_search/ingest.py:53-66 | examples/python/droid_semantic_search/search.py:47-59 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `examples/python/droid_semantic_search/ingest.py:53` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (10 lines × 3) crates/utils/re_perf_telemetry/src/prometheus.rs:295— crates/utils/re_perf_telemetry/src/prometheus.rs:295-304 | crates/utils/re_perf_telemetry/src/prometheus.rs:326-335 | crates/utils/re_perf_telemetry/src/prometheus.rs:357-366 — 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/utils/re_perf_telemetry/src/prometheus.rs:295` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `crates/utils/re_perf_telemetry/src/prometheus.rs:336` calls `value` and `crates/utils/re_perf_telemetry/src/prometheus.rs:307` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10 lines × 3) crates/viewer_support/re_viewer_context/src/cache/image_decode_cache.rs:224— crates/viewer_support/re_viewer_context/src/cache/image_decode_cache.rs:224-233 | crates/views/re_view_spatial/src/caches/mesh_cache.rs:141-150 | crates/views/re_view_spatial/src/proc_mesh.rs:509-518 — 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/viewer_support/re_viewer_context/src/cache/image_decode_cache.rs:224` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 3) crates/views/re_view_spatial/src/visualizers/arrows2d.rs:58— crates/views/re_view_spatial/src/visualizers/arrows2d.rs:58-67 | crates/views/re_view_spatial/src/visualizers/lines2d.rs:57-66 | crates/views/re_view_spatial/src/visualizers/lines3d.rs:58-67 — before extracting anything, compare `crates/views/re_view_spatial/src/visualizers/lines2d.rs` and `crates/views/re_view_spatial/src/visualizers/lines3d.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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/views/re_view_spatial/src/visualizers/arrows2d.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 (10 lines × 3) crates/data_flow/re_lenses/src/semantic/foxglove/compressed_image.rs:12— crates/data_flow/re_lenses/src/semantic/foxglove/compressed_image.rs:12-21 | crates/data_flow/re_lenses/src/semantic/foxglove/compressed_video.rs:12-21 | crates/data_flow/re_lenses/src/semantic/foxglove/raw_image.rs:14-23 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (6 lines × 3) crates/viewer_support/re_component_ui/src/geo_line_string.rs:10— crates/viewer_support/re_component_ui/src/geo_line_string.rs:10-15 | crates/viewer_support/re_component_ui/src/line_strip.rs:12-17 | crates/viewer_support/re_component_ui/src/line_strip.rs:77-82 — 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/viewer_support/re_component_ui/src/geo_line_string.rs:10` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `value` to `&mut MaybeMutRef<'_, GeoLineString>` in one and `&mut MaybeMutRef<'_, LineStrip3D>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (6 lines × 3) docs/snippets/all/concepts/transform3d_hierarchy_named_frames.rs:10— docs/snippets/all/concepts/transform3d_hierarchy_named_frames.rs:10-15 | docs/snippets/all/concepts/transform3d_hierarchy_named_frames.rs:19-26 | docs/snippets/all/concepts/transform3d_hierarchy_named_frames.rs:30-37 — 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 `docs/snippets/all/concepts/transform3d_hierarchy_named_frames.rs:10` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 3) docs/snippets/all/archetypes/asset3d_simple.rs:6— docs/snippets/all/archetypes/asset3d_simple.rs:6-11 | docs/snippets/all/archetypes/asset_audio_simple.rs:6-12 | docs/snippets/all/archetypes/gaussian_splats3d_ply.rs:6-11 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `docs/snippets/all/archetypes/gaussian_splats3d_ply.rs:6` it does not close everything it opens, so those 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 (6 lines × 3) crates/viewer_support/re_component_ui/src/geo_line_string.rs:36— crates/viewer_support/re_component_ui/src/geo_line_string.rs:36-41 | crates/viewer_support/re_component_ui/src/line_strip.rs:39-44 | crates/viewer_support/re_component_ui/src/line_strip.rs:104-109 — 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/viewer_support/re_component_ui/src/geo_line_string.rs:36` 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.
Low contrast colour pair in CSS (4.1:1) rerun_cpp/docs/doxygen-awesome/doxygen-awesome.css:493— `.sm-dox ul a:hover, .sm-dox ul a:active, .sm-dox ul a:focus` sets color: #1C1D1F on background-color: #1982d2 — 4.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (4.1:1) rerun_cpp/docs/doxygen-awesome/doxygen-awesome.css:515— `.sm-dox a:hover, .sm-dox a:active, .tablist li a:hover` sets color: #1C1D1F on background-color: #1982d2 — 4.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (4.1:1) rerun_cpp/docs/doxygen-awesome/doxygen-awesome.css:713— `#MSearchSelectWindow a.SelectItem:hover` sets color: #1C1D1F on background-color: #1982d2 — 4.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
TimeControl::handle_time_command (cyclomatic 60) crates/viewer_support/re_viewer_context/src/time_control/command.rs:214— TimeControl::handle_time_command has cyclomatic complexity 60 (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.
TimeControl::update (cyclomatic 25) crates/viewer_support/re_viewer_context/src/time_control/mod.rs:451— TimeControl::update 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.
TimeControl::update_from_blueprint (cyclomatic 17) crates/viewer_support/re_viewer_context/src/time_control/mod.rs:357— TimeControl::update_from_blueprint 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.
ChunkStore::insert_chunk_impl (cyclomatic 43) crates/store/re_chunk_store/src/writes.rs:113— ChunkStore::insert_chunk_impl has cyclomatic complexity 43 (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.
ChunkStore::find_and_elect_compaction_candidate (cyclomatic 19) crates/store/re_chunk_store/src/compaction_election.rs:22— ChunkStore::find_and_elect_compaction_candidate 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.
ChunkStore::remove_chunk_from_virtual_indices (cyclomatic 17) crates/store/re_chunk_store/src/gc.rs:494— ChunkStore::remove_chunk_from_virtual_indices 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.
re_ui::notifications::show_notification (cyclomatic 28) crates/ui_tools/re_ui/src/notifications.rs:947— re_ui::notifications::show_notification has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
re_ui::drag_and_drop::find_drop_target (cyclomatic 20) crates/ui_tools/re_ui/src/drag_and_drop.rs:178— re_ui::drag_and_drop::find_drop_target has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
re_ui::text_edit::autocomplete_text_edit (cyclomatic 19) crates/ui_tools/re_ui/src/text_edit.rs:211— re_ui::text_edit::autocomplete_text_edit 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.
re_agent_ui::ui::chat_ui::config_menu_ui (cyclomatic 26) crates/ui_tools/re_agent_ui/src/ui/chat_ui.rs:564— re_agent_ui::ui::chat_ui::config_menu_ui 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.
re_agent_ui::ui::elicitation_ui::field_ui (cyclomatic 22) crates/ui_tools/re_agent_ui/src/ui/elicitation_ui.rs:229— re_agent_ui::ui::elicitation_ui::field_ui has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
re_agent_ui::ui::chat_ui::permissions_ui (cyclomatic 19) crates/ui_tools/re_agent_ui/src/ui/chat_ui.rs:1024— re_agent_ui::ui::chat_ui::permissions_ui 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.
re_video::decode::ffmpeg_cli::ffmpeg::read_ffmpeg_output (cyclomatic 26) crates/utils/re_video/src/decode/ffmpeg_cli/ffmpeg.rs:691— re_video::decode::ffmpeg_cli::ffmpeg::read_ffmpeg_output has cyclomatic complexity 26 (threshold 15). Of this number, 25 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, 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.
re_video::decode::av1::create_frame (cyclomatic 21) crates/utils/re_video/src/decode/av1.rs:197— re_video::decode::av1::create_frame has cyclomatic complexity 21 (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.
re_video::demux::mp4::subsampling_mode (cyclomatic 16) crates/utils/re_video/src/demux/mp4.rs:302— re_video::demux::mp4::subsampling_mode 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.
re_viewer_context::view::visualizer_entity_subscriber::process_entity_components (cyclomatic 24) crates/viewer_support/re_viewer_context/src/view/visualizer_entity_subscriber.rs:183— re_viewer_context::view::visualizer_entity_subscriber::process_entity_components 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.
re_viewer_context::gpu_bridge::image_to_gpu::texture_creation_desc_from_color_image (cyclomatic 20) crates/viewer_support/re_viewer_context/src/gpu_bridge/image_to_gpu.rs:253— re_viewer_context::gpu_bridge::image_to_gpu::texture_creation_desc_from_color_image 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. This is NOT this file's highest cyclomatic complexity: re_viewer_context::gpu_bridge::image_to_gpu::general_texture_creation_desc_from_image (cyclomatic 33) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded function is counted neither in this dimension's figures nor in its score.
re_viewer_context::cache::video_stream_cache::handle_out_of_order_chunk (cyclomatic 18) crates/viewer_support/re_viewer_context/src/cache/video_stream_cache/mod.rs:2095— re_viewer_context::cache::video_stream_cache::handle_out_of_order_chunk has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
re_selection_panel::selection_history_ui::history_button_ui (cyclomatic 22) crates/panels/re_selection_panel/src/selection_history_ui.rs:53— re_selection_panel::selection_history_ui::history_button_ui has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
re_selection_panel::view_entity_picker::add_entities_line_ui (cyclomatic 20) crates/panels/re_selection_panel/src/view_entity_picker.rs:177— re_selection_panel::view_entity_picker::add_entities_line_ui has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
re_selection_panel::visualizer_ui::visualizer_components (cyclomatic 17) crates/panels/re_selection_panel/src/visualizer_ui.rs:216— re_selection_panel::visualizer_ui::visualizer_components 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.
ViewerUrl::open (cyclomatic 21) crates/viewer_support/re_viewer_context/src/viewer_url.rs:708— ViewerUrl::open 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.
ViewerUrl::parse_with_options (cyclomatic 19) crates/viewer_support/re_viewer_context/src/viewer_url.rs:190— ViewerUrl::parse_with_options has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ViewerUrl::sharable_url (cyclomatic 19) crates/viewer_support/re_viewer_context/src/viewer_url.rs:527— ViewerUrl::sharable_url 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.
Chunk::sanity_check (cyclomatic 17) crates/store/re_chunk/src/chunk.rs:1822— Chunk::sanity_check 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.
Chunk::earliest_at (cyclomatic 17) crates/store/re_chunk/src/earliest_at.rs:84— Chunk::earliest_at 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.
Chunk::latest_at (cyclomatic 16) crates/store/re_chunk/src/latest_at.rs:109— Chunk::latest_at 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.
re_redap_browser::servers::error_ui (cognitive 54) crates/panels/re_redap_browser/src/servers/mod.rs:417— re_redap_browser::servers::error_ui has cognitive complexity 54 (threshold 15). Drivers by points: if/else 16 (41 pts), match/switch 4 (13 pts) (nesting depth added 34). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
re_redap_browser::folder_card_ui::collect_cards (cognitive 17) crates/panels/re_redap_browser/src/folder_card_ui.rs:128— re_redap_browser::folder_card_ui::collect_cards has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (16 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.
re_redap_browser::server_modal::auth_ui (cognitive 17) crates/panels/re_redap_browser/src/server_modal/mod.rs:416— re_redap_browser::server_modal::auth_ui has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (12 pts), match/switch 2 (5 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.
re_time_panel::time_selection_ui::loop_selection_ui (cognitive 52) crates/panels/re_time_panel/src/time_selection_ui.rs:56— re_time_panel::time_selection_ui::loop_selection_ui has cognitive complexity 52 (threshold 15). Drivers by points: if/else 22 (46 pts), boolean chains 6 (nesting depth added 24). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
re_time_panel::data_density_graph::paint_loaded_indicator_bar (cognitive 26) crates/panels/re_time_panel/src/data_density_graph.rs:422— re_time_panel::data_density_graph::paint_loaded_indicator_bar has cognitive complexity 26 (threshold 15). Drivers by points: if/else 10 (22 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_time_panel::data_density_graph::build_density_graph (cognitive 17) crates/panels/re_time_panel/src/data_density_graph.rs:585— re_time_panel::data_density_graph::build_density_graph has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (11 pts), loops 3 (5 pts), boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_ui::notifications::show_notification (cognitive 50) crates/ui_tools/re_ui/src/notifications.rs:947— re_ui::notifications::show_notification has cognitive complexity 50 (threshold 15). Drivers by points: if/else 17 (34 pts), match/switch 7 (12 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 23). 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.
re_ui::drag_and_drop::find_drop_target (cognitive 40) crates/ui_tools/re_ui/src/drag_and_drop.rs:178— re_ui::drag_and_drop::find_drop_target has cognitive complexity 40 (threshold 15). Drivers by points: if/else 26 (38 pts), boolean chains 1, match/switch 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_ui::text_edit::autocomplete_text_edit (cognitive 28) crates/ui_tools/re_ui/src/text_edit.rs:211— re_ui::text_edit::autocomplete_text_edit has cognitive complexity 28 (threshold 15). Drivers by points: if/else 15 (22 pts), boolean chains 5, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ChunkFetcher::fetch_inner (cognitive 44) crates/store_app/re_entity_db/src/rrd_manifest_index/chunk_prioritizer.rs:1196— ChunkFetcher::fetch_inner has cognitive complexity 44 (threshold 15). Drivers by points: if/else 14 (37 pts), loops 2 (4 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 26). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ChunkFetcher::next_chunk (cognitive 34) crates/store_app/re_entity_db/src/rrd_manifest_index/chunk_prioritizer.rs:885— ChunkFetcher::next_chunk has cognitive complexity 34 (threshold 15). Drivers by points: if/else 11 (25 pts), loops 3 (7 pts), match/switch 1 (2 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.
ChunkFetcher::high_prio_chunk_stage (cognitive 21) crates/store_app/re_entity_db/src/rrd_manifest_index/chunk_prioritizer.rs:1002— ChunkFetcher::high_prio_chunk_stage has cognitive complexity 21 (threshold 15). Drivers by points: if/else 13 (18 pts), match/switch 2, boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_grpc_server::spawn_from_rx_set (cognitive 27) crates/data_flow/re_grpc_server/src/lib.rs:570— re_grpc_server::spawn_from_rx_set has cognitive complexity 27 (threshold 15). Drivers by points: if/else 7 (18 pts), match/switch 3 (8 pts), loops 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_grpc_server::serve_from_channel (cognitive 21) crates/data_flow/re_grpc_server/src/lib.rs:488— re_grpc_server::serve_from_channel has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (12 pts), match/switch 3 (8 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.
re_grpc_server::spawn_with_recv_and_services (cognitive 19) crates/data_flow/re_grpc_server/src/lib.rs:673— re_grpc_server::spawn_with_recv_and_services has cognitive complexity 19 (threshold 15). Drivers by points: match/switch 5 (15 pts), if/else 1 (3 pts), loops 1 (nesting depth added 12). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
re_view_tensor::dimension_mapping::find_width_height_dim_indices (cognitive 24) crates/views/re_view_tensor/src/dimension_mapping.rs:210— re_view_tensor::dimension_mapping::find_width_height_dim_indices has cognitive complexity 24 (threshold 15). Drivers by points: if/else 13 (22 pts), boolean chains 1, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_view_tensor::view_class::paint_axis_names (cognitive 24) crates/views/re_view_tensor/src/view_class.rs:619— re_view_tensor::view_class::paint_axis_names has cognitive complexity 24 (threshold 15). Drivers by points: if/else 14 (24 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_view_tensor::tensor_dimension_mapper::dimension_mapping_ui (cognitive 17) crates/views/re_view_tensor/src/tensor_dimension_mapper.rs:171— re_view_tensor::tensor_dimension_mapper::dimension_mapping_ui has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 3, loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ViewportBlueprint::save_tree_as_containers (cognitive 22) crates/viewer_support/re_viewport_blueprint/src/viewport_blueprint.rs:823— ViewportBlueprint::save_tree_as_containers has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (15 pts), loops 3, boolean chains 2, match/switch 1 (2 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.
ViewportBlueprint::set_content_visibility (cognitive 21) crates/viewer_support/re_viewport_blueprint/src/viewport_blueprint.rs:697— ViewportBlueprint::set_content_visibility has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (20 pts), match/switch 1 (nesting depth added 12). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
ViewportBlueprint::from_db (cognitive 16) crates/viewer_support/re_viewport_blueprint/src/viewport_blueprint.rs:80— ViewportBlueprint::from_db has cognitive complexity 16 (threshold 15). Drivers by points: loops 2 (6 pts), if/else 3 (5 pts), match/switch 1 (5 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D4 · Code Duplication· Edited copy of a member (41 corresponding lines) · ×3
Edited copy of a member (41 corresponding lines) crates/store/re_sorbet/src/migrations/make_list_arrays.rs:18— crates/store/re_sorbet/src/migrations/make_list_arrays.rs:18-61 | crates/store/re_sorbet/src/migrations/v0_0_1__to__v0_0_2.rs:84-124 — 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.
Edited copy of a member (41 corresponding lines) crates/views/re_view_bar_chart/src/view_class.rs:41— crates/views/re_view_bar_chart/src/view_class.rs:41-81 | crates/views/re_view_time_series/src/view_class.rs:143-193 — 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.
Edited copy of a member (41 corresponding lines) rerun_py/rerun_sdk/rerun/__init__.py:512— rerun_py/rerun_sdk/rerun/__init__.py:512-556 | rerun_py/rerun_sdk/rerun/recording_stream.py:784-824 — 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 (39 corresponding lines) · ×3
Edited copy of a member (39 corresponding lines) crates/store/re_sorbet/src/migrations/v0_1_3__to__v0_1_4.rs:52— crates/store/re_sorbet/src/migrations/v0_1_3__to__v0_1_4.rs:52-94 | crates/store/re_sorbet/src/migrations/v0_1_3__to__v0_1_4.rs:160-198 — These two members are one piece of code written twice and then edited apart: 39 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (39 corresponding lines) crates/store/re_chunk_index/src/raw_rrd_manifest.rs:1628— crates/store/re_chunk_index/src/raw_rrd_manifest.rs:1628-1668 | crates/store/re_chunk_index/src/raw_rrd_manifest.rs:1677-1715 — These two members are one piece of code written twice and then edited apart: 39 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (39 corresponding lines) crates/panels/re_blueprint_tree/src/blueprint_tree.rs:809— crates/panels/re_blueprint_tree/src/blueprint_tree.rs:809-847 | crates/panels/re_time_panel/src/time_panel.rs:1357-1397 — These two members are one piece of code written twice and then edited apart: 39 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 16+ corresponding lines) · ×3
Edited copies of one member (3 members, 16+ corresponding lines) crates/store_app/re_server/src/rerun_cloud/mod.rs:1409— crates/store_app/re_server/src/rerun_cloud/mod.rs:1409-1432 | crates/store_app/re_server/src/rerun_cloud/mod.rs:1476-1497 | crates/store_app/re_server/src/rerun_cloud/mod.rs:1540-1555 — 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.
Edited copies of one member (3 members, 16+ corresponding lines) docs/snippets/all/archetypes/mesh3d_indexed.rs:3— docs/snippets/all/archetypes/mesh3d_indexed.rs:3-21 | docs/snippets/all/archetypes/mesh3d_simple.rs:3-19 | docs/snippets/all/archetypes/view_coordinates_simple.rs:3-18 — 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.
Edited copies of one member (3 members, 16+ corresponding lines) crates/store/re_log_types/src/path/parse_path.rs:173— crates/store/re_log_types/src/path/parse_path.rs:173-188 | crates/store/re_log_types/src/path/parse_path.rs:247-266 | crates/store_app/re_entity_db/src/instance_path.rs:101-118 — 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, 15+ corresponding lines) · ×3
Edited copies of one member (3 members, 15+ corresponding lines) crates/store/re_arrow_json/src/special.rs:126— crates/store/re_arrow_json/src/special.rs:126-140 | crates/store/re_arrow_json/src/special.rs:145-160 | crates/store/re_arrow_json/src/special.rs:165-184 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 15+ corresponding lines) crates/store/re_protos/src/v1alpha1/rerun.cloud.v1alpha1.ext.queries.rs:731— crates/store/re_protos/src/v1alpha1/rerun.cloud.v1alpha1.ext.queries.rs:731-746 | crates/store/re_protos/src/v1alpha1/rerun.cloud.v1alpha1.ext.queries.rs:774-789 | crates/store/re_protos/src/v1alpha1/rerun.cloud.v1alpha1.ext.rs:611-625 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 15+ corresponding lines) crates/utils/re_mutex/src/lib.rs:151— crates/utils/re_mutex/src/lib.rs:151-165 | crates/utils/re_mutex/src/lib.rs:177-192 | crates/utils/re_mutex/src/lib.rs:209-223 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Duplicated block (26–27 lines × 2) crates/panels/re_blueprint_tree/src/blueprint_tree.rs:815— crates/panels/re_blueprint_tree/src/blueprint_tree.rs:815-840 | crates/panels/re_time_panel/src/time_panel.rs:1364-1390 — 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/panels/re_blueprint_tree/src/blueprint_tree.rs:815` 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–27 lines × 2) crates/views/re_view_spatial/src/visualizers/boxes2d.rs:84— crates/views/re_view_spatial/src/visualizers/boxes2d.rs:84-110 | crates/views/re_view_spatial/src/visualizers/ellipses2d.rs:210-235 — before extracting anything, compare `crates/views/re_view_spatial/src/visualizers/boxes2d.rs` and `crates/views/re_view_spatial/src/visualizers/ellipses2d.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 97 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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/views/re_view_spatial/src/visualizers/boxes2d.rs:84` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (26–27 lines × 2) rerun_py/rerun_sdk/rerun/experimental/dataloader/_iterable_dataset.py:386— rerun_py/rerun_sdk/rerun/experimental/dataloader/_iterable_dataset.py:386-411 | rerun_py/rerun_sdk/rerun/experimental/dataloader/_map_dataset.py:222-248 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `rerun_py/rerun_sdk/rerun/experimental/dataloader/_iterable_dataset.py:385` calls `_record_query_metrics` and `rerun_py/rerun_sdk/rerun/experimental/dataloader/_map_dataset.py:221` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (13–15 lines × 2) crates/viewer_support/re_view/src/view_highlights.rs:48— crates/viewer_support/re_view/src/view_highlights.rs:48-60 | crates/viewer_support/re_view/src/view_highlights.rs:100-114 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/viewer_support/re_view/src/view_highlights.rs:48` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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–15 lines × 2) crates/viewer_support/re_viewer_context/src/blueprint_helpers.rs:95— crates/viewer_support/re_viewer_context/src/blueprint_helpers.rs:95-107 | crates/viewer_support/re_viewer_context/src/blueprint_helpers.rs:147-161 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/viewer_support/re_viewer_context/src/blueprint_helpers.rs:95` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13–15 lines × 2) docs/snippets/all/howto/any_batch_value_column_updates.rs:29— docs/snippets/all/howto/any_batch_value_column_updates.rs:29-43 | docs/snippets/all/howto/any_values_column_updates.rs:31-43 — 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 `docs/snippets/all/howto/any_batch_value_column_updates.rs:29` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 3) crates/store/re_sorbet/src/migrations/v0_0_1__to__v0_0_2.rs:112— crates/store/re_sorbet/src/migrations/v0_0_1__to__v0_0_2.rs:112-124 | crates/store/re_sorbet/src/migrations/v0_0_1__to__v0_0_2.rs:254-266 | crates/store/re_sorbet/src/migrations/v0_0_1__to__v0_0_2.rs:305-317 — 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/store/re_sorbet/src/migrations/v0_0_1__to__v0_0_2.rs:112` 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 × 3) crates/store_app/re_datafusion/src/dataframe_query_provider/cpu_worker.rs:404— crates/store_app/re_datafusion/src/dataframe_query_provider/cpu_worker.rs:404-416 | crates/store_app/re_datafusion/src/dataframe_query_provider/cpu_worker.rs:476-488 | crates/store_app/re_datafusion/src/dataframe_query_provider/cpu_worker.rs:563-575 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (13 lines × 3) crates/ui_tools/re_renderer/src/renderer/mesh_renderer.rs:522— crates/ui_tools/re_renderer/src/renderer/mesh_renderer.rs:522-534 | crates/ui_tools/re_renderer/src/renderer/mesh_renderer.rs:581-593 | crates/ui_tools/re_renderer/src/renderer/mesh_renderer.rs:613-625 — 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/ui_tools/re_renderer/src/renderer/mesh_renderer.rs:522` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (12–13 lines × 2) crates/store/re_log_types/src/index/time_point.rs:208— crates/store/re_log_types/src/index/time_point.rs:208-219 | crates/store/re_log_types/src/index/time_point.rs:225-237 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (12–13 lines × 2) crates/top/re_viewer/src/ui/dev_panel/server_streaming_tab.rs:532— crates/top/re_viewer/src/ui/dev_panel/server_streaming_tab.rs:532-543 | crates/top/re_viewer/src/ui/dev_panel/server_streaming_tab.rs:557-569 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/top/re_viewer/src/ui/dev_panel/server_streaming_tab.rs:532` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (12–13 lines × 2) rerun_py/src/trace_context.rs:97— rerun_py/src/trace_context.rs:97-109 | rerun_py/src/tracing_session.rs:72-83 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (12 lines × 3) crates/views/re_view_time_series/src/line_visualizer_system.rs:74— crates/views/re_view_time_series/src/line_visualizer_system.rs:74-85 | crates/views/re_view_time_series/src/measurements_visualizer_system.rs:66-77 | crates/views/re_view_time_series/src/point_visualizer_system.rs:70-81 — before extracting anything, compare `crates/views/re_view_time_series/src/line_visualizer_system.rs` and `crates/views/re_view_time_series/src/point_visualizer_system.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 73 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 (12 lines × 3) crates/ui_tools/re_renderer/src/renderer/gaussian_splat.rs:756— crates/ui_tools/re_renderer/src/renderer/gaussian_splat.rs:756-769 | crates/ui_tools/re_renderer/src/renderer/point_cloud.rs:770-781 | crates/ui_tools/re_renderer/src/renderer/volume.rs:275-286 — before extracting anything, compare `crates/ui_tools/re_renderer/src/renderer/gaussian_splat.rs` and `crates/ui_tools/re_renderer/src/renderer/point_cloud.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 207 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/ui_tools/re_renderer/src/renderer/gaussian_splat.rs:756` it does not close everything it opens, so those exact lines 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/ui_tools/re_renderer/src/renderer/depth_cloud.rs:436— crates/ui_tools/re_renderer/src/renderer/depth_cloud.rs:436-448 | crates/ui_tools/re_renderer/src/renderer/mesh_renderer.rs:476-487 | crates/ui_tools/re_renderer/src/renderer/voxel_grid.rs:333-345 — before extracting anything, compare `crates/ui_tools/re_renderer/src/renderer/depth_cloud.rs` and `crates/ui_tools/re_renderer/src/renderer/mesh_renderer.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 35 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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/ui_tools/re_renderer/src/renderer/depth_cloud.rs:436` 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 (11–12 lines × 2) crates/top/rerun/src/commands/rrd/merge_optimize.rs:483— crates/top/rerun/src/commands/rrd/merge_optimize.rs:483-493 | crates/top/rerun/src/commands/rrd/stats.rs:191-202 — 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/top/rerun/src/commands/rrd/merge_optimize.rs:483` 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/top/rerun/src/commands/rrd/merge_optimize.rs:488— crates/top/rerun/src/commands/rrd/merge_optimize.rs:488-498 | crates/top/rerun/src/commands/rrd/split.rs:178-189 — 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/top/rerun/src/commands/rrd/merge_optimize.rs:488` 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/views/re_view_spatial/src/ui_2d.rs:246— crates/views/re_view_spatial/src/ui_2d.rs:246-256 | crates/views/re_view_spatial/src/ui_3d.rs:153-164 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (10 lines × 4) crates/store/re_chunk/src/unit_chunk.rs:109— crates/store/re_chunk/src/unit_chunk.rs:109-118 | crates/store/re_chunk/src/unit_chunk.rs:162-171 | crates/store/re_chunk/src/unit_chunk.rs:403-412 | crates/store/re_chunk/src/unit_chunk.rs:446-455 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/store/re_chunk/src/unit_chunk.rs:109` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 4) crates/ui_tools/re_renderer/src/renderer/depth_cloud.rs:474— crates/ui_tools/re_renderer/src/renderer/depth_cloud.rs:474-483 | crates/ui_tools/re_renderer/src/renderer/gaussian_splat.rs:790-799 | crates/ui_tools/re_renderer/src/renderer/lines.rs:762-771 | crates/ui_tools/re_renderer/src/renderer/point_cloud.rs:819-828 — before extracting anything, compare `crates/ui_tools/re_renderer/src/renderer/depth_cloud.rs` and `crates/ui_tools/re_renderer/src/renderer/point_cloud.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 57 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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/ui_tools/re_renderer/src/renderer/depth_cloud.rs:474` 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 × 4) crates/views/re_view_spatial/src/visualizers/arrows2d.rs:225— crates/views/re_view_spatial/src/visualizers/arrows2d.rs:225-234 | crates/views/re_view_spatial/src/visualizers/arrows3d.rs:229-238 | crates/views/re_view_spatial/src/visualizers/boxes2d.rs:231-240 | crates/views/re_view_spatial/src/visualizers/ellipses2d.rs:350-359 — before extracting anything, compare `crates/views/re_view_spatial/src/visualizers/arrows2d.rs` and `crates/views/re_view_spatial/src/visualizers/arrows3d.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 85 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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/views/re_view_spatial/src/visualizers/arrows2d.rs:225` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 3) crates/views/re_view_time_series/src/point_visualizer_system.rs:333— crates/views/re_view_time_series/src/point_visualizer_system.rs:333-340 | crates/views/re_view_time_series/src/series_query.rs:216-220 | crates/views/re_view_time_series/src/series_query.rs:383-387 — 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/views/re_view_time_series/src/point_visualizer_system.rs:333` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (5 lines × 3) crates/ui_tools/re_renderer/src/renderer/gaussian_splat.rs:670— crates/ui_tools/re_renderer/src/renderer/gaussian_splat.rs:670-696 | crates/ui_tools/re_renderer/src/renderer/lines.rs:632-636 | crates/ui_tools/re_renderer/src/renderer/point_cloud.rs:658-662 — before extracting anything, compare `crates/ui_tools/re_renderer/src/renderer/gaussian_splat.rs` and `crates/ui_tools/re_renderer/src/renderer/lines.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 56 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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/ui_tools/re_renderer/src/renderer/gaussian_splat.rs:670` it does not close everything it opens, so those 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 (5 lines × 3) crates/ui_tools/re_renderer/src/colormap.rs:320— crates/ui_tools/re_renderer/src/colormap.rs:320-324 | crates/ui_tools/re_renderer/src/colormap.rs:338-342 | crates/ui_tools/re_renderer/src/colormap.rs:382-386 — 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.
X2 · Cancellation propagation· Async function without AbortSignal · ×3
Async function without AbortSignal: urlExists rerun_notebook/src/rerun_notebook/error_widget.js:18— `urlExists` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: fetchViewerWasm rerun_js/web-viewer/index.ts:1086— `fetchViewerWasm` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: isPublished rerun_js/scripts/common.mjs:84— `isPublished` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
QueryCache::on_events (cyclomatic 37) crates/store_app/re_query/src/cache.rs:312— QueryCache::on_events has cyclomatic complexity 37 (threshold 15). 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.
QueryCache::latest_at (cyclomatic 20) crates/store_app/re_query/src/latest_at.rs:43— QueryCache::latest_at has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SpatialView3D::view_3d (cyclomatic 28) crates/views/re_view_spatial/src/ui_3d.rs:126— SpatialView3D::view_3d has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SpatialView3D::spawn_heuristics (cyclomatic 16) crates/views/re_view_spatial/src/view_3d.rs:371— SpatialView3D::spawn_heuristics has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
Expr::eval (cyclomatic 26) crates/store/re_lenses_core/src/selector/eval.rs:420— Expr::eval 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.
Expr::fmt (cyclomatic 17) crates/store/re_lenses_core/src/selector/parser.rs:188— Expr::fmt has cyclomatic complexity 17 (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.
ChunkFetcher::next_chunk (cyclomatic 22) crates/store_app/re_entity_db/src/rrd_manifest_index/chunk_prioritizer.rs:885— ChunkFetcher::next_chunk has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ChunkFetcher::fetch_inner (cyclomatic 19) crates/store_app/re_entity_db/src/rrd_manifest_index/chunk_prioritizer.rs:1196— ChunkFetcher::fetch_inner 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.
re_lenses_core::execute::execute (cyclomatic 20) crates/store/re_lenses_core/src/execute.rs:331— re_lenses_core::execute::execute has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
re_lenses_core::plan::plan (cyclomatic 16) crates/store/re_lenses_core/src/plan.rs:95— re_lenses_core::plan::plan 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.
re_sdk::spawn::spawn (cyclomatic 20) crates/top/re_sdk/src/spawn.rs:205— re_sdk::spawn::spawn has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
re_sdk::recording_stream::forwarding_thread (cyclomatic 16) crates/top/re_sdk/src/recording_stream.rs:1644— re_sdk::recording_stream::forwarding_thread has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 4 of the 16 points are its own statements and the rest belongs to one function item inside it that branches (handle_cmd). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
VideoPlayer::frame_at (cyclomatic 19) crates/utils/re_video/src/player/mod.rs:502— VideoPlayer::frame_at 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.
VideoPlayer::enqueue_samples (cyclomatic 18) crates/utils/re_video/src/player/mod.rs:659— VideoPlayer::enqueue_samples has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SegmentUrlUdf::return_type (cyclomatic 19) rerun_py/src/catalog/segment_url_udf.rs:72— SegmentUrlUdf::return_type has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
SegmentUrlUdf::invoke_with_args (cyclomatic 16) rerun_py/src/catalog/segment_url_udf.rs:168— SegmentUrlUdf::invoke_with_args 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.
re_sorbet::migrations::v0_0_2__to__v0_1_0::rewire_tagged_components (cyclomatic 18) crates/store/re_sorbet/src/migrations/v0_0_2__to__v0_1_0.rs:29— re_sorbet::migrations::v0_0_2__to__v0_1_0::rewire_tagged_components has cyclomatic complexity 18 (threshold 15). Of this number, 17 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
re_sorbet::dataframe_to_chunks::stamp_dataframe_metadata (cyclomatic 16) crates/store/re_sorbet/src/dataframe_to_chunks.rs:407— re_sorbet::dataframe_to_chunks::stamp_dataframe_metadata 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.
ImageInfo::to_dynamic_image (cyclomatic 18) crates/viewer_support/re_viewer_context/src/image_info.rs:361— ImageInfo::to_dynamic_image has cyclomatic complexity 18 (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.
ImageInfo::get_xyc (cyclomatic 17) crates/viewer_support/re_viewer_context/src/image_info.rs:270— ImageInfo::get_xyc 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.
re_renderer::importer::gltf::import_mesh (cyclomatic 16) crates/ui_tools/re_renderer/src/importer/gltf.rs:173— re_renderer::importer::gltf::import_mesh 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.
re_renderer::importer::ply::parse_ply_mesh (cyclomatic 16) crates/ui_tools/re_renderer/src/importer/ply.rs:439— re_renderer::importer::ply::parse_ply_mesh 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.
Repeated repair: crates/utils/re_video/src/decode/mod.rs crates/utils/re_video/src/decode/mod.rs:618— crates/utils/re_video/src/decode/mod.rs changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 8 (its worst body is PixelFormat::bits_per_pixel at line 618), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Fix H.264 views stuck on a loading spinner on machines with many cores”; “Nightly failure fix: av1 slow-decode always enabled in tests, link exception”; “Fix video playing when there's many samples at the same timestamp”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 23:06:51 +00:00' --until='2026-11-13 23:06:51 +00:00' --full-history --no-merges -- crates/utils/re_video/src/decode/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.
Repeated repair: crates/utils/re_video/src/player/sample_decoder.rs crates/utils/re_video/src/player/sample_decoder.rs:104— crates/utils/re_video/src/player/sample_decoder.rs changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 6 (its worst body is VideoSampleDecoder::process_decoder_output at line 104), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Fix empty rows for video streams & encoded images”; “Fix H.264 views stuck on a loading spinner on machines with many cores”; “Fix video playing when there's many samples at the same timestamp”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 23:06:51 +00:00' --until='2026-11-13 23:06:51 +00:00' --full-history --no-merges -- crates/utils/re_video/src/player/sample_decoder.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.
QueryCache::on_events (cognitive 99) crates/store_app/re_query/src/cache.rs:312— QueryCache::on_events has cognitive complexity 99 (threshold 15). Drivers by points: loops 20 (62 pts), if/else 10 (30 pts), match/switch 2 (5 pts), boolean chains 2 (nesting depth added 65). 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.
QueryCache::latest_at (cognitive 38) crates/store_app/re_query/src/latest_at.rs:43— QueryCache::latest_at has cognitive complexity 38 (threshold 15). Drivers by points: if/else 11 (29 pts), boolean chains 6, loops 2 (3 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.
CommandPalette::alternatives_ui (cognitive 49) crates/ui_tools/re_ui/src/command_palette.rs:419— CommandPalette::alternatives_ui has cognitive complexity 49 (threshold 15). Drivers by points: if/else 19 (38 pts), boolean chains 7, loops 3 (4 pts) (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.
CommandPalette::window_content_ui (cognitive 17) crates/ui_tools/re_ui/src/command_palette.rs:291— CommandPalette::window_content_ui has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11 (12 pts), match/switch 3 (4 pts), boolean chains 1 (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.
SeriesPointsSystem::load_series (cognitive 43) crates/views/re_view_time_series/src/point_visualizer_system.rs:189— SeriesPointsSystem::load_series has cognitive complexity 43 (threshold 15). Drivers by points: if/else 13 (21 pts), loops 6 (19 pts), boolean chains 2, match/switch 1 (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SeriesPointsSystem::build_draw_data (cognitive 17) crates/views/re_view_time_series/src/point_visualizer_system.rs:112— SeriesPointsSystem::build_draw_data has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (12 pts), loops 2 (3 pts), boolean chains 1, match/switch 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_arrow_util::format::format_dataframe_without_metadata (cognitive 38) crates/utils/re_arrow_util/src/format.rs:335— re_arrow_util::format::format_dataframe_without_metadata has cognitive complexity 38 (threshold 15). Drivers by points: if/else 15 (24 pts), loops 3 (7 pts), match/switch 2 (7 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.
re_arrow_util::compare::ensure_buffers_equal (cognitive 19) crates/utils/re_arrow_util/src/compare.rs:61— re_arrow_util::compare::ensure_buffers_equal has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 3 (6 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.
SpatialView3D::view_3d (cognitive 38) crates/views/re_view_spatial/src/ui_3d.rs:126— SpatialView3D::view_3d has cognitive complexity 38 (threshold 15). Drivers by points: if/else 19 (29 pts), boolean chains 5, loops 2, match/switch 1 (2 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.
SpatialView3D::on_register (cognitive 18) crates/views/re_view_spatial/src/view_3d.rs:66— SpatialView3D::on_register has cognitive complexity 18 (threshold 15). Drivers by points: if/else 13 (16 pts), boolean chains 1, match/switch 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
DataFusionTableWidget::table_ui (cognitive 37) crates/viewer_support/re_dataframe_ui/src/datafusion_table_widget.rs:937— DataFusionTableWidget::table_ui has cognitive complexity 37 (threshold 15). Drivers by points: if/else 20 (27 pts), match/switch 6 (7 pts), boolean chains 3 (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.
DataFusionTableWidget::show (cognitive 23) crates/viewer_support/re_dataframe_ui/src/datafusion_table_widget.rs:651— DataFusionTableWidget::show has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (18 pts), loops 1 (3 pts), boolean chains 1, match/switch 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.
RawRrdManifest::check_index_columns_are_correct (cognitive 35) crates/store/re_chunk_index/src/raw_rrd_manifest.rs:1107— RawRrdManifest::check_index_columns_are_correct has cognitive complexity 35 (threshold 15). Drivers by points: if/else 8 (24 pts), match/switch 3 (10 pts), loops 1 (nesting depth added 23). 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.
RawRrdManifest::check_manifest_schema_matches_sorbet_schema (cognitive 31) crates/store/re_chunk_index/src/raw_rrd_manifest.rs:1240— RawRrdManifest::check_manifest_schema_matches_sorbet_schema has cognitive complexity 31 (threshold 15). Drivers by points: if/else 7 (20 pts), loops 5 (10 pts), boolean chains 1 (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.
re_sdk::spawn::spawn (cognitive 35) crates/top/re_sdk/src/spawn.rs:205— re_sdk::spawn::spawn has cognitive complexity 35 (threshold 15). Drivers by points: if/else 21 (30 pts), boolean chains 3, loops 1 (2 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_sdk::recording_stream::forwarding_thread (cognitive 18) crates/top/re_sdk/src/recording_stream.rs:1644— re_sdk::recording_stream::forwarding_thread has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (9 pts), match/switch 2 (4 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 8). Most of this is not in the body itself: 6 of the 18 points are its own statements and the rest belongs to one function item inside it that branches (handle_cmd). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
SegmentUrlUdf::invoke_with_args (cognitive 34) rerun_py/src/catalog/segment_url_udf.rs:168— SegmentUrlUdf::invoke_with_args has cognitive complexity 34 (threshold 15). Drivers by points: if/else 17 (31 pts), loops 2, boolean chains 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SegmentUrlUdf::return_type (cognitive 18) rerun_py/src/catalog/segment_url_udf.rs:72— SegmentUrlUdf::return_type has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11, boolean chains 7. 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.
Transcript::to_markdown (cognitive 32) crates/utils/re_agent/src/transcript.rs:487— Transcript::to_markdown has cognitive complexity 32 (threshold 15). Drivers by points: if/else 8 (20 pts), loops 4 (10 pts), match/switch 1 (2 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.
Transcript::to_plain_text (cognitive 26) crates/utils/re_agent/src/transcript.rs:419— Transcript::to_plain_text has cognitive complexity 26 (threshold 15). Drivers by points: if/else 5 (13 pts), loops 3 (7 pts), match/switch 2 (6 pts) (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_sorbet::dataframe_to_chunks::stamp_dataframe_metadata (cognitive 31) crates/store/re_sorbet/src/dataframe_to_chunks.rs:407— re_sorbet::dataframe_to_chunks::stamp_dataframe_metadata has cognitive complexity 31 (threshold 15). Drivers by points: if/else 11 (24 pts), loops 2 (3 pts), boolean chains 2, match/switch 1 (2 pts) (nesting depth added 15). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
re_sorbet::migrations::v0_0_2__to__v0_1_0::rewire_tagged_components (cognitive 21) crates/store/re_sorbet/src/migrations/v0_0_2__to__v0_1_0.rs:29— re_sorbet::migrations::v0_0_2__to__v0_1_0::rewire_tagged_components has cognitive complexity 21 (threshold 15). Drivers by points: if/else 12 (17 pts), match/switch 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 6). Of this number, 20 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body 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.
QuotedObject::from_union (cognitive 30) crates/build/re_types_builder/src/codegen/cpp/mod.rs:981— QuotedObject::from_union has cognitive complexity 30 (threshold 15). Drivers by points: if/else 17 (24 pts), loops 4 (6 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.
QuotedObject::from_archetype (cognitive 16) crates/build/re_types_builder/src/codegen/cpp/mod.rs:450— QuotedObject::from_archetype has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (11 pts), boolean chains 4, loops 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
SelectionPanel::item_ui (cognitive 29) crates/panels/re_selection_panel/src/selection_panel.rs:181— SelectionPanel::item_ui has cognitive complexity 29 (threshold 15). Drivers by points: if/else 14 (25 pts), boolean chains 2, match/switch 2 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SelectionPanel::view_selection_ui (cognitive 18) crates/panels/re_selection_panel/src/selection_panel.rs:364— SelectionPanel::view_selection_ui has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (16 pts), loops 1 (2 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.
VideoPlayer::frame_at (cognitive 29) crates/utils/re_video/src/player/mod.rs:502— VideoPlayer::frame_at has cognitive complexity 29 (threshold 15). Drivers by points: if/else 14 (23 pts), boolean chains 4, match/switch 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
VideoPlayer::enqueue_samples (cognitive 27) crates/utils/re_video/src/player/mod.rs:659— VideoPlayer::enqueue_samples has cognitive complexity 27 (threshold 15). Drivers by points: if/else 10 (17 pts), boolean chains 7, match/switch 1 (2 pts), loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TilesDelegate::reports_button (cognitive 28) crates/panels/re_viewport/src/viewport_ui.rs:734— TilesDelegate::reports_button has cognitive complexity 28 (threshold 15). Drivers by points: if/else 6 (15 pts), loops 5 (11 pts), match/switch 1 (2 pts) (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TilesDelegate::top_bar_right_ui (cognitive 21) crates/panels/re_viewport/src/viewport_ui.rs:516— TilesDelegate::top_bar_right_ui has cognitive complexity 21 (threshold 15). Drivers by points: if/else 12 (18 pts), boolean chains 3 (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.
Expr::eval (cognitive 28) crates/store/re_lenses_core/src/selector/eval.rs:420— Expr::eval has cognitive complexity 28 (threshold 15). Drivers by points: match/switch 10 (22 pts), if/else 3 (6 pts) (nesting depth added 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. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
Expr::fmt (cognitive 18) crates/store/re_lenses_core/src/selector/parser.rs:188— Expr::fmt has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 2 (5 pts), 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.
re_log_encoding::rrd::stream_from_http::stream_from_http (cognitive 28) crates/store/re_log_encoding/src/rrd/stream_from_http.rs:45— re_log_encoding::rrd::stream_from_http::stream_from_http has cognitive complexity 28 (threshold 15). Drivers by points: if/else 4 (13 pts), match/switch 4 (12 pts), loops 1 (3 pts) (nesting depth added 19). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
re_log_encoding::rrd::stream_from_http::web_decode::decode_rrd_async (cognitive 16) crates/store/re_log_encoding/src/rrd/stream_from_http.rs:166— re_log_encoding::rrd::stream_from_http::web_decode::decode_rrd_async has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (10 pts), match/switch 2 (4 pts), loops 1 (2 pts) (nesting depth added 10). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
ResolvedEntityPathFilter::is_superset_of (cognitive 27) crates/store/re_log_types/src/path/entity_path_filter.rs:709— ResolvedEntityPathFilter::is_superset_of has cognitive complexity 27 (threshold 15). Drivers by points: if/else 4 (12 pts), match/switch 4 (12 pts), loops 2, boolean chains 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ResolvedEntityPathFilter::evaluate (cognitive 16) crates/store/re_log_types/src/path/entity_path_filter.rs:778— ResolvedEntityPathFilter::evaluate has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (10 pts), boolean chains 3, match/switch 1 (2 pts), loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EntityPathPart::parse_forgiving_with_warning (cognitive 27) crates/store/re_log_types/src/path/entity_path_part.rs:56— EntityPathPart::parse_forgiving_with_warning has cognitive complexity 27 (threshold 15). Drivers by points: if/else 6 (15 pts), match/switch 2 (9 pts), boolean chains 2, loops 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EntityPathPart::parse_strict (cognitive 20) crates/store/re_log_types/src/path/entity_path_part.rs:121— EntityPathPart::parse_strict has cognitive complexity 20 (threshold 15). Drivers by points: match/switch 2 (9 pts), if/else 5 (8 pts), boolean chains 2, loops 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.
re_view_state_timeline::view_class::compute_render_items (cognitive 26) crates/views/re_view_state_timeline/src/view_class.rs:615— re_view_state_timeline::view_class::compute_render_items has cognitive complexity 26 (threshold 15). Drivers by points: if/else 14 (22 pts), match/switch 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_view_state_timeline::view_class::show_group (cognitive 25) crates/views/re_view_state_timeline/src/view_class.rs:947— re_view_state_timeline::view_class::show_group has cognitive complexity 25 (threshold 15). Drivers by points: if/else 6 (18 pts), loops 2 (3 pts), match/switch 1 (3 pts), boolean chains 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CachedTransformsForTimeline::remove_chunk (cognitive 24) crates/store_app/re_tf/src/transform_resolution_cache/cached_transforms_for_timeline.rs:198— CachedTransformsForTimeline::remove_chunk has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (14 pts), loops 4 (8 pts), boolean chains 2 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CachedTransformsForTimeline::add_temporal_chunk (cognitive 17) crates/store_app/re_tf/src/transform_resolution_cache/cached_transforms_for_timeline.rs:115— CachedTransformsForTimeline::add_temporal_chunk has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (8 pts), loops 4 (8 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
VideoStreamCache::handle_store_event (cognitive 24) crates/viewer_support/re_viewer_context/src/cache/video_stream_cache/mod.rs:321— VideoStreamCache::handle_store_event has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (12 pts), match/switch 5 (10 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.
VideoStreamCache::on_store_events (cognitive 16) crates/viewer_support/re_viewer_context/src/cache/video_stream_cache/mod.rs:1575— VideoStreamCache::on_store_events has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_log_types::path::entity_path_filter::split_whitespace_smart (cognitive 23) crates/store/re_log_types/src/path/entity_path_filter.rs:210— re_log_types::path::entity_path_filter::split_whitespace_smart has cognitive complexity 23 (threshold 15). Drivers by points: if/else 5 (12 pts), boolean chains 6, loops 3 (5 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_log_types::path::parse_path::entity_path_parts_from_tokens_strict (cognitive 17) crates/store/re_log_types/src/path/parse_path.rs:269— re_log_types::path::parse_path::entity_path_parts_from_tokens_strict has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (16 pts), loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FilterState::filter_bar_ui (cognitive 23) crates/viewer_support/re_dataframe_ui/src/filters/column_filter_ui.rs:427— FilterState::filter_bar_ui has cognitive complexity 23 (threshold 15). Drivers by points: if/else 13 (16 pts), boolean chains 3, loops 2, match/switch 1 (2 pts) (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
FilterState::section_title_ui_impl (cognitive 16) crates/ui_tools/re_ui/src/filter_widget.rs:128— FilterState::section_title_ui_impl has cognitive complexity 16 (threshold 15). Drivers by points: if/else 13 (15 pts), boolean chains 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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.
re_memory_view::flamegraph::render_flamegraph_node (cognitive 22) crates/panels/re_memory_view/src/flamegraph.rs:266— re_memory_view::flamegraph::render_flamegraph_node has cognitive complexity 22 (threshold 15). Drivers by points: if/else 13 (19 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_memory_view::flamegraph::flamegraph_ui (cognitive 18) crates/panels/re_memory_view/src/flamegraph.rs:156— re_memory_view::flamegraph::flamegraph_ui has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (16 pts), boolean chains 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_view_raw_data::properties::components_section_ui (cognitive 22) crates/views/re_view_raw_data/src/properties.rs:140— re_view_raw_data::properties::components_section_ui has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (16 pts), boolean chains 3, loops 2 (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.
re_view_raw_data::component_list_ui::component_list_ui (cognitive 21) crates/views/re_view_raw_data/src/component_list_ui.rs:13— re_view_raw_data::component_list_ui::component_list_ui has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 4, loops 2 (3 pts), match/switch 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_lenses::semantic::foxglove::packed_element_field::extract_voxel_indices (cognitive 21) crates/data_flow/re_lenses/src/semantic/foxglove/packed_element_field.rs:232— re_lenses::semantic::foxglove::packed_element_field::extract_voxel_indices has cognitive complexity 21 (threshold 15). Drivers by points: loops 4 (10 pts), if/else 3 (9 pts), boolean chains 2 (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.
re_lenses::semantic::ros2msg::ros_map_helpers::ros_map_buffer_to_image_buffer (cognitive 16) crates/data_flow/re_lenses/src/semantic/ros2msg/ros_map_helpers.rs:80— re_lenses::semantic::ros2msg::ros_map_helpers::ros_map_buffer_to_image_buffer has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (9 pts), loops 3 (6 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_agent::session::strip_ansi_escapes (cognitive 21) crates/utils/re_agent/src/session.rs:1497— re_agent::session::strip_ansi_escapes has cognitive complexity 21 (threshold 15). Drivers by points: if/else 3 (10 pts), loops 3 (7 pts), boolean chains 2, match/switch 1 (2 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_agent::agent_harness::backend::drive (cognitive 18) crates/utils/re_agent/src/agent_harness/backend.rs:166— re_agent::agent_harness::backend::drive has cognitive complexity 18 (threshold 15). Drivers by points: if/else 3 (9 pts), match/switch 3 (8 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.
re_redap_client::grpc::stream_blueprint_and_segment_from_server (cognitive 19) crates/data_flow/re_redap_client/src/grpc.rs:828— re_redap_client::grpc::stream_blueprint_and_segment_from_server has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (14 pts), match/switch 2 (4 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_redap_client::grpc::stream_segment_from_server (cognitive 16) crates/data_flow/re_redap_client/src/grpc.rs:965— re_redap_client::grpc::stream_segment_from_server has cognitive complexity 16 (threshold 15). Drivers by points: match/switch 3 (7 pts), if/else 4 (5 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ViewBuilder::new (cognitive 19) crates/ui_tools/re_renderer/src/view_builder.rs:445— ViewBuilder::new has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (12 pts), match/switch 4 (5 pts), boolean chains 1, loops 1 (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.
ViewBuilder::draw (cognitive 19) crates/ui_tools/re_renderer/src/view_builder.rs:751— ViewBuilder::draw has cognitive complexity 19 (threshold 15). Drivers by points: if/else 12 (13 pts), match/switch 2 (4 pts), boolean chains 1, loops 1 (nesting depth added 3). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
re_recording_panel::recording_panel_ui::dataset_entry_ui (cognitive 18) crates/panels/re_recording_panel/src/recording_panel_ui.rs:547— re_recording_panel::recording_panel_ui::dataset_entry_ui has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (9 pts), loops 2 (5 pts), match/switch 1 (3 pts), boolean chains 1 (nesting depth added 6). 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.
re_recording_panel::recording_panel_ui::entry_tree_node_ui (cognitive 16) crates/panels/re_recording_panel/src/recording_panel_ui.rs:467— re_recording_panel::recording_panel_ui::entry_tree_node_ui has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 1 (2 pts), boolean chains 1, match/switch 1 (nesting depth added 8). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
Change-coupling hub: app_state.rs → data.rs, history.rs, navigation.rs, startup_options.rs, share_modal.rs, active_store_context.rs, app_context.rs, route.rs crates/top/re_viewer/src/app_state.rs— `crates/top/re_viewer/src/app_state.rs` changes together with 8 other files — `crates/panels/re_recording_panel/src/data.rs`, `crates/top/re_viewer/src/history.rs`, `crates/top/re_viewer/src/navigation.rs`, `crates/top/re_viewer/src/startup_options.rs`, `crates/top/re_viewer/src/ui/share_modal.rs`, `crates/viewer_support/re_viewer_context/src/active_store_context.rs`, `crates/viewer_support/re_viewer_context/src/app_context.rs`, `crates/viewer_support/re_viewer_context/src/route.rs` — none of which declares a dependency on it: one file is the hub of 8 separate couplings, not 8 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 8.
Change-coupling hub: view_class.rs → view_class.rs, view_class.rs, view_class.rs crates/views/re_view_text_document/src/view_class.rs— `crates/views/re_view_text_document/src/view_class.rs` changes together with 3 other files — `crates/views/re_view_bar_chart/src/view_class.rs`, `crates/views/re_view_tensor/src/view_class.rs`, `crates/views/re_view_text_log/src/view_class.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.
Near-duplicate member pair (48 shared lines) crates/views/re_view_spatial/src/visualizers/points2d.rs:223— crates/views/re_view_spatial/src/visualizers/points2d.rs:223-329 | crates/views/re_view_spatial/src/visualizers/points3d.rs:387-509 — These two members are variants of one another: 48 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
Near-duplicate member pair (48 shared lines) scripts/ci/pixi_install_wheel.py:33— scripts/ci/pixi_install_wheel.py:33-92 | scripts/ci/uv_install_wheel.py:32-92 — These two members are variants of one another: 48 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication· Edited copy of a member (50 corresponding lines) · ×2
Edited copy of a member (50 corresponding lines) crates/panels/re_blueprint_tree/src/blueprint_tree.rs:747— crates/panels/re_blueprint_tree/src/blueprint_tree.rs:747-796 | crates/panels/re_time_panel/src/time_panel.rs:1293-1343 — These two members are one piece of code written twice and then edited apart: 50 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (50 corresponding lines) crates/ui_tools/re_renderer/src/renderer/gaussian_splat.rs:200— crates/ui_tools/re_renderer/src/renderer/gaussian_splat.rs:200-249 | crates/ui_tools/re_renderer/src/renderer/point_cloud.rs:190-244 — These two members are one piece of code written twice and then edited apart: 50 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Members sharing a duplicated core (7 members, 50+ identical tokens) · ×2
Members sharing a duplicated core (7 members, 50+ identical tokens) crates/views/re_view_spatial/src/visualizers/arrows2d.rs:181— crates/views/re_view_spatial/src/visualizers/arrows2d.rs:181-257 | crates/views/re_view_spatial/src/visualizers/arrows3d.rs:185-261 | crates/views/re_view_spatial/src/visualizers/boxes2d.rs:187-269 | crates/views/re_view_spatial/src/visualizers/boxes3d.rs:125-232 | crates/views/re_view_spatial/src/visualizers/ellipses2d.rs:299-390 | crates/views/re_view_spatial/src/visualizers/ellipsoids.rs:133-239 | crates/views/re_view_spatial/src/visualizers/points2d.rs:223-329 — These 7 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 7 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 7 times.
Members sharing a duplicated core (7 members, 50+ identical tokens) examples/python/face_tracking/face_tracking.py:325— examples/python/face_tracking/face_tracking.py:325-336 | examples/python/gesture_detection/gesture_detection.py:173-184 | examples/python/lidar/lidar/download_dataset.py:28-40 | examples/python/nuscenes_dataset/nuscenes_dataset/download_dataset.py:28-40 | examples/python/ocr/ocr.py:448-459 | examples/python/open_photogrammetry_format/open_photogrammetry_format.py:59-70 | scripts/upload_image.py:362-373 — These 7 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 7 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 7 times.
D4 · Code Duplication· Edited copy of a member (55 corresponding lines) · ×2
Edited copy of a member (55 corresponding lines) crates/store/re_sdk_types/src/archetypes/points2d_ext.rs:120— crates/store/re_sdk_types/src/archetypes/points2d_ext.rs:120-181 | crates/store/re_sdk_types/src/archetypes/points3d_ext.rs:132-186 — These two members are one piece of code written twice and then edited apart: 55 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (55 corresponding lines) crates/views/re_view_map/src/map_view.rs:578— crates/views/re_view_map/src/map_view.rs:578-632 | crates/views/re_view_spatial/src/picking.rs:194-263 — These two members are one piece of code written twice and then edited apart: 55 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (56 corresponding lines) · ×2
Edited copy of a member (56 corresponding lines) crates/data_flow/re_redap_client/src/grpc.rs:465— crates/data_flow/re_redap_client/src/grpc.rs:465-556 | crates/data_flow/re_redap_client/src/grpc.rs:563-618 — These two members are one piece of code written twice and then edited apart: 56 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (56 corresponding lines) rerun_py/rerun_sdk/rerun/dynamic_archetype.py:199— rerun_py/rerun_sdk/rerun/dynamic_archetype.py:199-258 | rerun_py/rerun_sdk/rerun/any_value.py:97-152 — These two members are one piece of code written twice and then edited apart: 56 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 43+ corresponding lines) · ×2
Edited copies of one member (3 members, 43+ corresponding lines) crates/viewer_support/re_component_ui/src/geo_line_string.rs:21— crates/viewer_support/re_component_ui/src/geo_line_string.rs:21-70 | crates/viewer_support/re_component_ui/src/line_strip.rs:23-71 | crates/viewer_support/re_component_ui/src/line_strip.rs:88-130 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 43 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 43+ corresponding lines) crates/store/re_sorbet/src/migrations/v0_1_1__to__v0_1_2.rs:103— crates/store/re_sorbet/src/migrations/v0_1_1__to__v0_1_2.rs:103-152 | crates/store/re_sorbet/src/migrations/v0_1_1__to__v0_1_2.rs:155-197 | crates/store/re_sorbet/src/migrations/v0_1_2__to__v0_1_3.rs:24-72 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 43 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (49 corresponding lines) · ×2
Edited copy of a member (49 corresponding lines) crates/store_app/re_tf/src/transform_resolution_cache/tree_transforms_for_child_frame.rs:211— crates/store_app/re_tf/src/transform_resolution_cache/tree_transforms_for_child_frame.rs:211-259 | crates/store_app/re_tf/src/transform_resolution_cache/tree_transforms_for_child_frame.rs:279-340 — These two members are one piece of code written twice and then edited apart: 49 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (49 corresponding lines) examples/python/face_tracking/face_tracking.py:351— examples/python/face_tracking/face_tracking.py:351-411 | examples/python/gesture_detection/gesture_detection.py:210-258 — These two members are one piece of code written twice and then edited apart: 49 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 35+ corresponding lines) · ×2
Edited copies of one member (3 members, 35+ corresponding lines) docs/snippets/all/archetypes/scalars_multiple_plots.rs:3— docs/snippets/all/archetypes/scalars_multiple_plots.rs:3-60 | docs/snippets/all/archetypes/series_lines_style.rs:3-41 | docs/snippets/all/archetypes/series_points_style.rs:3-37 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 35 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 35+ corresponding lines) crates/data_flow/re_redap_client/src/connection_client/datasets.rs:68— crates/data_flow/re_redap_client/src/connection_client/datasets.rs:68-102 | crates/data_flow/re_redap_client/src/connection_client/datasets.rs:221-259 | crates/data_flow/re_redap_client/src/connection_client/datasets.rs:384-422 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 35 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (33 corresponding lines) · ×2
Edited copy of a member (33 corresponding lines) crates/data_flow/re_mcap/src/parsers/ros2msg/sensor_msgs/joint_state.rs:67— crates/data_flow/re_mcap/src/parsers/ros2msg/sensor_msgs/joint_state.rs:67-130 | crates/data_flow/re_mcap/src/parsers/ros2msg/sensor_msgs/joy.rs:58-90 — These two members are one piece of code written twice and then edited apart: 33 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (33 corresponding lines) rerun_py/src/chunk_stream/mcap_reader.rs:487— rerun_py/src/chunk_stream/mcap_reader.rs:487-519 | rerun_py/src/chunk_stream/urdf_tree_stream.rs:26-58 — These two members are one piece of code written twice and then edited apart: 33 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (27 corresponding lines) · ×2
Edited copy of a member (27 corresponding lines) crates/ui_tools/re_renderer/src/draw_phases/depth_resolve.rs:144— crates/ui_tools/re_renderer/src/draw_phases/depth_resolve.rs:144-170 | crates/ui_tools/re_renderer/src/draw_phases/picking_layer.rs:576-602 — 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/utils/re_perf_telemetry/src/telemetry.rs:415— crates/utils/re_perf_telemetry/src/telemetry.rs:415-441 | crates/utils/re_perf_telemetry/src/telemetry.rs:443-475 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 22+ corresponding lines) · ×2
Edited copies of one member (3 members, 22+ corresponding lines) crates/data_flow/re_lenses/src/semantic/ros2msg/voxel_grid.rs:118— crates/data_flow/re_lenses/src/semantic/ros2msg/voxel_grid.rs:118-143 | crates/data_flow/re_lenses/src/semantic/ros2msg/voxel_grid.rs:146-167 | crates/data_flow/re_lenses/src/semantic/ros2msg/voxel_grid.rs:170-191 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 22 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 22+ corresponding lines) crates/data_flow/re_lenses/src/semantic/foxglove/frame_transform.rs:11— crates/data_flow/re_lenses/src/semantic/foxglove/frame_transform.rs:11-37 | crates/data_flow/re_lenses/src/semantic/foxglove/frame_transforms.rs:11-37 | crates/data_flow/re_lenses/src/semantic/ros2msg/tf_message.rs:6-27 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 22 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 21+ corresponding lines) · ×2
Edited copies of one member (3 members, 21+ corresponding lines) crates/data_flow/re_grpc_client/src/lib.rs:47— crates/data_flow/re_grpc_client/src/lib.rs:47-67 | crates/data_flow/re_grpc_server/src/lib.rs:129-149 | crates/data_flow/re_redap_client/src/lib.rs:155-177 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 21 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 21+ corresponding lines) crates/viewer_support/re_viewer_context/src/blueprint_helpers.rs:85— crates/viewer_support/re_viewer_context/src/blueprint_helpers.rs:85-107 | crates/viewer_support/re_viewer_context/src/blueprint_helpers.rs:141-161 | crates/viewer_support/re_viewer_context/src/blueprint_helpers.rs:221-241 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 21 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 14+ corresponding lines) · ×2
Edited copies of one member (3 members, 14+ corresponding lines) docs/snippets/all/archetypes/asset3d_simple.rs:5— docs/snippets/all/archetypes/asset3d_simple.rs:5-18 | docs/snippets/all/archetypes/asset_audio_simple.rs:5-21 | docs/snippets/all/archetypes/gaussian_splats3d_ply.rs:5-20 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 14+ corresponding lines) crates/utils/re_analytics/src/event.rs:160— crates/utils/re_analytics/src/event.rs:160-174 | crates/utils/re_analytics/src/event.rs:696-709 | crates/utils/re_analytics/src/event.rs:1224-1239 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (1 corresponding lines) · ×2
Edited copy of a member (1 corresponding lines) crates/store/re_types_core/src/chunk_id.rs:165— crates/store/re_types_core/src/chunk_id.rs:165-165 | crates/store/re_types_core/src/row_id.rs:185-185 — 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) examples/python/droid_semantic_search/ingest.py:103— examples/python/droid_semantic_search/ingest.py:103-103 | rerun_py/rerun_sdk/rerun/experimental/dataloader/decoders/_arrow.py:65-65 — 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 copies of one member (3 members, 17+ corresponding lines) · ×2
Edited copies of one member (3 members, 17+ corresponding lines) crates/views/re_view_time_series/src/line_visualizer_system.rs:48— crates/views/re_view_time_series/src/line_visualizer_system.rs:48-66 | crates/views/re_view_time_series/src/measurements_visualizer_system.rs:42-58 | crates/views/re_view_time_series/src/point_visualizer_system.rs:45-62 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 17+ corresponding lines) crates/viewer_support/re_viewport_blueprint/src/container.rs:342— crates/viewer_support/re_viewport_blueprint/src/container.rs:342-361 | crates/viewer_support/re_viewport_blueprint/src/container.rs:376-392 | crates/viewer_support/re_viewport_blueprint/src/view.rs:353-372 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 12+ corresponding lines) · ×2
Edited copies of one member (3 members, 12+ corresponding lines) crates/views/re_view_graph/src/view.rs:45— crates/views/re_view_graph/src/view.rs:45-56 | crates/views/re_view_spatial/src/ui_2d.rs:77-88 | crates/views/re_view_tensor/src/view_class.rs:86-102 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 12+ corresponding lines) examples/python/drone_lidar/drone_lidar.py:30— examples/python/drone_lidar/drone_lidar.py:30-47 | examples/python/segment_anything_model/segment_anything_model.py:47-63 | examples/python/structure_from_motion/structure_from_motion/__main__.py:78-89 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 8+ corresponding lines) · ×2
Edited copies of one member (3 members, 8+ corresponding lines) crates/views/re_view_state_timeline/src/visualizer_ui.rs:340— crates/views/re_view_state_timeline/src/visualizer_ui.rs:340-347 | crates/views/re_view_state_timeline/src/visualizer_ui.rs:352-359 | crates/views/re_view_state_timeline/src/visualizer_ui.rs:364-371 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 8+ corresponding lines) crates/data_flow/re_lenses/src/op/semantic.rs:257— crates/data_flow/re_lenses/src/op/semantic.rs:257-264 | crates/data_flow/re_lenses/src/op/semantic.rs:268-275 | crates/data_flow/re_lenses/src/op/semantic.rs:281-288 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 9+ corresponding lines) · ×2
Edited copies of one member (4 members, 9+ corresponding lines) rerun_py/src/python_bridge.rs:2204— rerun_py/src/python_bridge.rs:2204-2212 | rerun_py/src/python_bridge.rs:2221-2229 | rerun_py/src/python_bridge.rs:2238-2246 | rerun_py/src/python_bridge.rs:2251-2259 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
Edited copies of one member (4 members, 9+ corresponding lines) crates/data_flow/re_lenses/src/op/string.rs:13— crates/data_flow/re_lenses/src/op/string.rs:13-21 | crates/data_flow/re_lenses/src/op/string.rs:26-34 | crates/data_flow/re_lenses/src/op/string.rs:39-47 | crates/data_flow/re_lenses/src/op/string.rs:52-60 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 7+ corresponding lines) · ×2
Edited copies of one member (3 members, 7+ corresponding lines) crates/top/re_viewer/src/saving.rs:155— crates/top/re_viewer/src/saving.rs:155-161 | crates/top/re_viewer/src/saving.rs:165-171 | crates/utils/re_auth/src/oauth/storage.rs:90-99 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 7+ corresponding lines) crates/viewer_support/re_component_ui/src/encoding_uis/singleline_string.rs:12— crates/viewer_support/re_component_ui/src/encoding_uis/singleline_string.rs:12-18 | crates/viewer_support/re_component_ui/src/encoding_uis/vec.rs:24-30 | crates/viewer_support/re_component_ui/src/encoding_uis/vec.rs:36-42 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 10+ corresponding lines) · ×2
Edited copies of one member (4 members, 10+ corresponding lines) docs/snippets/all/descriptors/descr_builtin_archetype.rs:18— docs/snippets/all/descriptors/descr_builtin_archetype.rs:18-27 | docs/snippets/all/descriptors/descr_builtin_component.rs:28-37 | docs/snippets/all/descriptors/descr_custom_archetype.rs:63-72 | docs/snippets/all/descriptors/descr_custom_component.rs:23-32 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
Edited copies of one member (4 members, 10+ corresponding lines) scripts/check_crate_dependencies.py:70— scripts/check_crate_dependencies.py:70-80 | scripts/ci/check_test_targets.py:472-482 | scripts/generate_crate_graph.py:141-151 | scripts/render_d2.py:110-119 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
Duplicated block (32 lines × 2) crates/panels/re_redap_browser/src/entries.rs:441— crates/panels/re_redap_browser/src/entries.rs:441-472 | crates/panels/re_redap_browser/src/entries.rs:539-570 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/panels/re_redap_browser/src/entries.rs:441` 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) rerun_py/rerun_sdk/rerun/chunk/_chunk_store.py:95— rerun_py/rerun_sdk/rerun/chunk/_chunk_store.py:95-126 | rerun_py/rerun_sdk/rerun/chunk/_lazy_store.py:85-116 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (29–30 lines × 2) crates/data_flow/re_redap_client/src/grpc.rs:506— crates/data_flow/re_redap_client/src/grpc.rs:506-534 | crates/data_flow/re_redap_client/src/grpc.rs:581-610 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/data_flow/re_redap_client/src/grpc.rs:506` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. Note first that the copies are not typed on the same thing: the declarations holding them bind `decode_time_us` to `Option<Arc<AtomicU64>>` in one and `Option<Arc<std::sync::atomic::AtomicU64>>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (29–30 lines × 2) crates/viewer_support/re_viewer_context/src/cache/video_stream_cache/test_player/encoded_depth_image.rs:57— crates/viewer_support/re_viewer_context/src/cache/video_stream_cache/test_player/encoded_depth_image.rs:57-86 | crates/viewer_support/re_viewer_context/src/cache/video_stream_cache/test_player/encoded_image.rs:83-111 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `crates/viewer_support/re_viewer_context/src/cache/video_stream_cache/test_player/encoded_depth_image.rs:57` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (27 lines × 2) crates/panels/re_redap_browser/src/upload_asset.rs:122— crates/panels/re_redap_browser/src/upload_asset.rs:122-148 | crates/store_app/re_catalog_client/src/asset.rs:380-406 — 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/panels/re_redap_browser/src/upload_asset.rs:122` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (27 lines × 2) scripts/upload_image.py:326— scripts/upload_image.py:326-352 | scripts/upload_rrd.py:62-88 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (25 lines × 2) crates/store_app/re_query/src/bin/clamped_zip.rs:318— crates/store_app/re_query/src/bin/clamped_zip.rs:318-342 | crates/store_app/re_query/src/bin/range_zip.rs:458-482 — 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/store_app/re_query/src/bin/clamped_zip.rs:318` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (25 lines × 2) crates/views/re_view_time_series/src/line_visualizer_system.rs:78— crates/views/re_view_time_series/src/line_visualizer_system.rs:78-102 | crates/views/re_view_time_series/src/point_visualizer_system.rs:74-98 — before extracting anything, compare `crates/views/re_view_time_series/src/line_visualizer_system.rs` and `crates/views/re_view_time_series/src/point_visualizer_system.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 73 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 (31 lines × 2) crates/top/re_viewer/src/ui/dev_panel/mod.rs:421— crates/top/re_viewer/src/ui/dev_panel/mod.rs:421-451 | crates/top/re_viewer/src/ui/dev_panel/mod.rs:459-489 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/top/re_viewer/src/ui/dev_panel/mod.rs:421` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (31 lines × 2) scripts/ci/pixi_install_wheel.py:54— scripts/ci/pixi_install_wheel.py:54-84 | scripts/ci/uv_install_wheel.py:48-78 — before extracting anything, compare `scripts/ci/pixi_install_wheel.py` and `scripts/ci/uv_install_wheel.py` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 (24 lines × 2) crates/ui_tools/re_renderer/src/renderer/gaussian_splat.rs:226— crates/ui_tools/re_renderer/src/renderer/gaussian_splat.rs:226-249 | crates/ui_tools/re_renderer/src/renderer/point_cloud.rs:221-244 — before extracting anything, compare `crates/ui_tools/re_renderer/src/renderer/gaussian_splat.rs` and `crates/ui_tools/re_renderer/src/renderer/point_cloud.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 207 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/ui_tools/re_renderer/src/renderer/gaussian_splat.rs:226` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (24 lines × 2) examples/python/any_scalar/any_scalar/market_demo.py:98— examples/python/any_scalar/any_scalar/market_demo.py:98-121 | examples/python/any_scalar/any_scalar/market_demo.py:122-145 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17–19 lines × 2) crates/data_flow/re_grpc_server/src/lib.rs:497— crates/data_flow/re_grpc_server/src/lib.rs:497-513 | crates/data_flow/re_grpc_server/src/lib.rs:585-603 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/data_flow/re_grpc_server/src/lib.rs:497` it does not close everything it opens, so those 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/data_flow/re_grpc_server/src/lib.rs:604` calls `is_empty` and `crates/data_flow/re_grpc_server/src/lib.rs:514` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (17–19 lines × 2) crates/store/re_chunk/src/merge.rs:183— crates/store/re_chunk/src/merge.rs:183-199 | crates/store/re_chunk/src/merge.rs:229-247 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/store/re_chunk/src/merge.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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (18–19 lines × 2) crates/panels/re_selection_panel/src/view_entity_picker.rs:238— crates/panels/re_selection_panel/src/view_entity_picker.rs:238-255 | crates/panels/re_selection_panel/src/view_entity_picker.rs:294-312 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/panels/re_selection_panel/src/view_entity_picker.rs:238` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `crates/panels/re_selection_panel/src/view_entity_picker.rs:237` calls `remove_filter_rule_for` and `crates/panels/re_selection_panel/src/view_entity_picker.rs:293` 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 (18–19 lines × 2) crates/views/re_view_time_series/src/line_series_loader.rs:112— crates/views/re_view_time_series/src/line_series_loader.rs:112-130 | crates/views/re_view_time_series/src/point_visualizer_system.rs:197-214 — before extracting anything, compare `crates/views/re_view_time_series/src/line_series_loader.rs` and `crates/views/re_view_time_series/src/point_visualizer_system.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 50 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (10–13 lines × 2) crates/top/re_viewer/src/ui/share_modal.rs:294— crates/top/re_viewer/src/ui/share_modal.rs:294-303 | crates/top/re_viewer/src/ui/share_modal.rs:322-334 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/top/re_viewer/src/ui/share_modal.rs:294` 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–13 lines × 2) crates/utils/re_crash_handler/src/lib.rs:284— crates/utils/re_crash_handler/src/lib.rs:284-296 | crates/utils/re_memory/src/backtrace_native.rs:95-104 — 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/utils/re_crash_handler/src/lib.rs:284` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (10–11 lines × 4) crates/views/re_view_spatial/src/visualizers/arrows2d.rs:206— crates/views/re_view_spatial/src/visualizers/arrows2d.rs:206-215 | crates/views/re_view_spatial/src/visualizers/arrows3d.rs:210-219 | crates/views/re_view_spatial/src/visualizers/boxes2d.rs:212-221 | crates/views/re_view_spatial/src/visualizers/ellipses2d.rs:329-339 — before extracting anything, compare `crates/views/re_view_spatial/src/visualizers/arrows2d.rs` and `crates/views/re_view_spatial/src/visualizers/arrows3d.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 85 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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/views/re_view_spatial/src/visualizers/arrows2d.rs:206` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10–11 lines × 4) rerun_py/src/catalog/layer.rs:48— rerun_py/src/catalog/layer.rs:48-57 | rerun_py/src/catalog/layer.rs:68-77 | rerun_py/src/catalog/segment.rs:94-104 | rerun_py/src/catalog/segment.rs:118-128 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `rerun_py/src/catalog/layer.rs:48` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 3) crates/ui_tools/re_renderer/src/renderer/gaussian_splat.rs:701— crates/ui_tools/re_renderer/src/renderer/gaussian_splat.rs:701-711 | crates/ui_tools/re_renderer/src/renderer/lines.rs:690-700 | crates/ui_tools/re_renderer/src/renderer/point_cloud.rs:716-726 — before extracting anything, compare `crates/ui_tools/re_renderer/src/renderer/gaussian_splat.rs` and `crates/ui_tools/re_renderer/src/renderer/lines.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 56 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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/ui_tools/re_renderer/src/renderer/gaussian_splat.rs:701` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 3) crates/store/re_chunk_index/src/raw_rrd_manifest.rs:1166— crates/store/re_chunk_index/src/raw_rrd_manifest.rs:1166-1176 | crates/store/re_chunk_index/src/raw_rrd_manifest.rs:1300-1310 | crates/store/re_chunk_index/src/raw_rrd_manifest.rs:1331-1341 — 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/store/re_chunk_index/src/raw_rrd_manifest.rs:1166` 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–11 lines × 2) crates/data_flow/re_redap_client/src/connection_client/segments_schema.rs:189— crates/data_flow/re_redap_client/src/connection_client/segments_schema.rs:189-199 | crates/store_app/re_catalog_client/src/asset.rs:227-236 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `crates/data_flow/re_redap_client/src/connection_client/segments_schema.rs:189` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (10–11 lines × 2) crates/viewer_support/re_viewer_context/src/cache/video_stream_cache/mod.rs:1123— crates/viewer_support/re_viewer_context/src/cache/video_stream_cache/mod.rs:1123-1133 | crates/viewer_support/re_viewer_context/src/cache/video_stream_cache/mod.rs:1450-1459 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/viewer_support/re_viewer_context/src/cache/video_stream_cache/mod.rs:1123` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
Outbound HTTP without resilience crates/utils/re_agent/src/model_api_backend.rs:454— `reqwest::Client::builder(` 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/utils/re_agent/src/model_api_backend.rs:461— `reqwest::Client::builder(` 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.
Unused dependency 'typedoc-github-theme' — Declared in rerun_js/web-viewer/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 'typedoc-github-theme' — Declared in rerun_js/web-viewer-react/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.
AC3 · Page structure· Page without a main landmark · ×1
Page without a main landmark REDACTED:3— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
re_types_core::reflection::generic_placeholder_for_datatype (cyclomatic 49) crates/store/re_types_core/src/reflection.rs:92— re_types_core::reflection::generic_placeholder_for_datatype has cyclomatic complexity 49 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
TimeSeriesView::ui (cyclomatic 41) crates/views/re_view_time_series/src/view_class.rs:412— TimeSeriesView::ui 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.
compare_snippet_output.main (cyclomatic 41) docs/snippets/compare_snippet_output.py:91— compare_snippet_output.main 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.
DurationFormatOptions::format_nanos (cyclomatic 38) crates/utils/re_format/src/duration.rs:113— DurationFormatOptions::format_nanos has cyclomatic complexity 38 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AgentSession::handle_event (cyclomatic 37) crates/utils/re_agent/src/session.rs:1079— AgentSession::handle_event has cyclomatic complexity 37 (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.
re_protos::v1alpha1::rerun::cloud::v1alpha1::ext::legacy_adapter::adapt_legacy (cyclomatic 34) crates/store/re_protos/src/v1alpha1/rerun.cloud.v1alpha1.ext.legacy_adapter.rs:53— re_protos::v1alpha1::rerun::cloud::v1alpha1::ext::legacy_adapter::adapt_legacy has cyclomatic complexity 34 (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.
ListItem::ui (cyclomatic 34) crates/ui_tools/re_ui/src/list_item/list_item.rs:535— ListItem::ui has cyclomatic complexity 34 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
BarChartView::ui (cyclomatic 34) crates/views/re_view_bar_chart/src/view_class.rs:135— BarChartView::ui has cyclomatic complexity 34 (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.
RedapServers::handle_command (cyclomatic 33) crates/panels/re_redap_browser/src/servers/mod.rs:1114— RedapServers::handle_command has cyclomatic complexity 33 (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.
ViewportUi::viewport_ui (cyclomatic 31) crates/panels/re_viewport/src/viewport_ui.rs:55— ViewportUi::viewport_ui has cyclomatic complexity 31 (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.
VideoFrameDecoder._decode_run (cyclomatic 31) rerun_py/rerun_sdk/rerun/experimental/dataloader/decoders/_video.py:386— VideoFrameDecoder._decode_run has cyclomatic complexity 31 (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.
ServerModal::ui (cyclomatic 30) crates/panels/re_redap_browser/src/server_modal/mod.rs:166— ServerModal::ui has cyclomatic complexity 30 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
App::with_commands (cyclomatic 30) crates/top/re_viewer/src/app/mod.rs:332— App::with_commands has cyclomatic complexity 30 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
StateTimelineView::ui (cyclomatic 30) crates/views/re_view_state_timeline/src/view_class.rs:250— StateTimelineView::ui has cyclomatic complexity 30 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Window::collect (cyclomatic 29) crates/store_app/re_datafusion/src/pipeline/columnar/mod.rs:337— Window::collect has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
StatsCommand::run (cyclomatic 29) crates/top/rerun/src/commands/rrd/stats.rs:38— StatsCommand::run has cyclomatic complexity 29 (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.
ImageExt.__init__ (cyclomatic 29) rerun_py/rerun_sdk/rerun/archetypes/image_ext.py:77— ImageExt.__init__ has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Telemetry::init (cyclomatic 28) crates/utils/re_perf_telemetry/src/telemetry.rs:513— Telemetry::init has cyclomatic complexity 28 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
DataFusionTableWidget::table_ui (cyclomatic 28) crates/viewer_support/re_dataframe_ui/src/datafusion_table_widget.rs:937— DataFusionTableWidget::table_ui has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ItemCollection::copy_to_clipboard (cyclomatic 28) crates/viewer_support/re_viewer_context/src/item_collection.rs:187— ItemCollection::copy_to_clipboard has cyclomatic complexity 28 (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.
re_time_panel::time_selection_ui::loop_selection_ui (cyclomatic 27) crates/panels/re_time_panel/src/time_selection_ui.rs:56— re_time_panel::time_selection_ui::loop_selection_ui 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.
re_view_audio::waveform::waveform_ui (cyclomatic 27) crates/views/re_view_audio/src/waveform.rs:80— re_view_audio::waveform::waveform_ui has cyclomatic complexity 27 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Objects::validate (cyclomatic 26) crates/build/re_types_builder/src/objects/mod.rs:31— Objects::validate 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.
re_viewport_blueprint::viewport_blueprint::apply_viewport_command (cyclomatic 26) crates/viewer_support/re_viewport_blueprint/src/viewport_blueprint.rs:974— re_viewport_blueprint::viewport_blueprint::apply_viewport_command 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.
CommandPalette::alternatives_ui (cyclomatic 25) crates/ui_tools/re_ui/src/command_palette.rs:419— CommandPalette::alternatives_ui 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.
CrateVersion::try_parse (cyclomatic 25) crates/utils/re_build_info/src/crate_version.rs:366— CrateVersion::try_parse has cyclomatic complexity 25 (threshold 15). Of this number, 21 points are the body's own statements and 4 belong to 2 function items inside it that branch. 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.
re_component_ui::table_cells::redap_uri_button::redap_uri_button (cyclomatic 25) crates/viewer_support/re_component_ui/src/table_cells/redap_uri_button.rs:18— re_component_ui::table_cells::redap_uri_button::redap_uri_button has cyclomatic complexity 25 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
_utils._discover_prior_keyframes (cyclomatic 25) rerun_py/rerun_sdk/rerun/experimental/dataloader/_utils.py:1234— _utils._discover_prior_keyframes 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.
DataQueryPropertyResolver::update_overrides_recursive (cyclomatic 24) crates/viewer_support/re_viewport_blueprint/src/view_contents.rs:449— DataQueryPropertyResolver::update_overrides_recursive 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.
PythonCodeGenerator::generate_folder (cyclomatic 23) crates/build/re_types_builder/src/codegen/python/mod.rs:433— PythonCodeGenerator::generate_folder 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.
LogDataSource::from_uri (cyclomatic 23) crates/data_flow/re_data_source/src/data_source.rs:86— LogDataSource::from_uri has cyclomatic complexity 23 (threshold 15). Of this number, 19 points are the body's own statements and 4 belong to one function item inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
SelectionPanel::item_ui (cyclomatic 23) crates/panels/re_selection_panel/src/selection_panel.rs:181— SelectionPanel::item_ui 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.
Decoder::try_read_impl (cyclomatic 23) crates/store/re_log_encoding/src/rrd/decoder/state_machine.rs:174— Decoder::try_read_impl 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.
MeshRenderer::draw (cyclomatic 23) crates/ui_tools/re_renderer/src/renderer/mesh_renderer.rs:651— MeshRenderer::draw has cyclomatic complexity 23 (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.
VideoDataDescription::load_mp4_from_reader (cyclomatic 23) crates/utils/re_video/src/demux/mp4.rs:36— VideoDataDescription::load_mp4_from_reader has cyclomatic complexity 23 (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.
ImageStats::from_image (cyclomatic 23) crates/viewer_support/re_viewer_context/src/tensor/image_stats.rs:22— ImageStats::from_image has cyclomatic complexity 23 (threshold 15). Of this number, 20 points are the body's own statements and 3 belong to 3 function items inside it that branch. 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.
MaxImageDimensionsStoreSubscriber::on_events (cyclomatic 23) crates/views/re_view_spatial/src/max_image_dimension_subscriber.rs:97— MaxImageDimensionsStoreSubscriber::on_events 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.
PinholeExt.__init__ (cyclomatic 23) rerun_py/rerun_sdk/rerun/archetypes/pinhole_ext.py:16— PinholeExt.__init__ 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.
SpanTable._span_batch (cyclomatic 23) rerun_py/rerun_sdk/rerun/experimental/spans.py:425— SpanTable._span_batch has cyclomatic complexity 23 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
MessageDecoderRunner::process (cyclomatic 22) crates/data_flow/re_mcap/src/decoders/mod.rs:387— MessageDecoderRunner::process has cyclomatic complexity 22 (threshold 15). 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.
DataframeQueryTableProvider::scan (cyclomatic 22) crates/store_app/re_datafusion/src/dataframe_query_common/mod.rs:753— DataframeQueryTableProvider::scan has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
FieldInput::value (cyclomatic 22) crates/ui_tools/re_agent_ui/src/ui/elicitation_ui.rs:75— FieldInput::value has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AppContext::handle_select_hover_drag_interactions (cyclomatic 22) crates/viewer_support/re_viewer_context/src/app_context.rs:285— AppContext::handle_select_hover_drag_interactions has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TensorStats::from_tensor (cyclomatic 22) crates/viewer_support/re_viewer_context/src/tensor/tensor_stats.rs:21— TensorStats::from_tensor has cyclomatic complexity 22 (threshold 15). Of this number, 19 points are the body's own statements and 3 belong to 3 function items inside it that branch. 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.
Query::column_visibility_ui_impl (cyclomatic 22) crates/views/re_view_dataframe/src/view_query/ui.rs:353— Query::column_visibility_ui_impl has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
_utils._resolve_decode_requests (cyclomatic 22) rerun_py/rerun_sdk/rerun/experimental/dataloader/_utils.py:753— _utils._resolve_decode_requests has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
re_redap_browser::servers::error_ui (cyclomatic 21) crates/panels/re_redap_browser/src/servers/mod.rs:417— re_redap_browser::servers::error_ui 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.
CommandPaletteProviderImpl::all_matching (cyclomatic 21) crates/top/re_viewer/src/command_palette.rs:123— CommandPaletteProviderImpl::all_matching 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.
SplitCommand::run (cyclomatic 21) crates/top/rerun/src/commands/rrd/split.rs:82— SplitCommand::run 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.
ParsedMeshVertex::set_property (cyclomatic 21) crates/ui_tools/re_renderer/src/importer/ply.rs:225— ParsedMeshVertex::set_property 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.
Parser::parse_named_type (cyclomatic 20) crates/build/re_types_builder/src/objects/from_rust.rs:680— Parser::parse_named_type 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.
CardLayout::show (cyclomatic 20) crates/ui_tools/re_ui/src/egui_ext/card_layout.rs:132— CardLayout::show has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CompletionPopup::show (cyclomatic 20) crates/ui_tools/re_ui/src/egui_ext/completion.rs:255— CompletionPopup::show has cyclomatic complexity 20 (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.
TimestampFilter::popup_ui (cyclomatic 20) crates/viewer_support/re_dataframe_ui/src/filters/timestamp.rs:404— TimestampFilter::popup_ui has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Boxes2DExt.__init__ (cyclomatic 20) rerun_py/rerun_sdk/rerun/archetypes/boxes2d_ext.py:40— Boxes2DExt.__init__ has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SnippetsRefCodeGenerator::generate_fallible (cyclomatic 19) crates/build/re_types_builder/src/codegen/docs/snippets_ref.rs:126— SnippetsRefCodeGenerator::generate_fallible has cyclomatic complexity 19 (threshold 15). Of this number, 11 points are the body's own statements and 8 belong to one function item inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Args::generate_markdown_manual (cyclomatic 19) crates/top/rerun/src/commands/entrypoint.rs:418— Args::generate_markdown_manual has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 1 of the 19 points is its own statement and the rest belongs to 2 function items inside it that branch (generate_markdown_manual, generate_arg_doc). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
FilterState::filter_bar_ui (cyclomatic 19) crates/viewer_support/re_dataframe_ui/src/filters/column_filter_ui.rs:427— FilterState::filter_bar_ui has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
VideoStreamCache::handle_store_event (cyclomatic 19) crates/viewer_support/re_viewer_context/src/cache/video_stream_cache/mod.rs:321— VideoStreamCache::handle_store_event 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.
re_viewer_control_tools::message_schema (cyclomatic 19) crates/viewer_support/re_viewer_control_tools/src/lib.rs:346— re_viewer_control_tools::message_schema has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
SeriesPointsSystem::load_series (cyclomatic 19) crates/views/re_view_time_series/src/point_visualizer_system.rs:189— SeriesPointsSystem::load_series 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.
_utils._build_query_plans (cyclomatic 19) rerun_py/rerun_sdk/rerun/experimental/dataloader/_utils.py:488— _utils._build_query_plans 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.
url_generation.segment_url (cyclomatic 19) rerun_py/rerun_sdk/rerun/utilities/datafusion/functions/url_generation.py:19— url_generation.segment_url has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
re_lerobot::emits::build_emits (cyclomatic 18) crates/data_flow/re_lerobot/src/emits.rs:104— re_lerobot::emits::build_emits has cyclomatic complexity 18 (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.
re_mcap::decoders::protobuf::append_value (cyclomatic 18) crates/data_flow/re_mcap/src/decoders/protobuf.rs:278— re_mcap::decoders::protobuf::append_value has cyclomatic complexity 18 (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.
re_chunk_store::rebatch_videos::rebatch_video_chunks_to_gops (cyclomatic 18) crates/store/re_chunk_store/src/rebatch_videos.rs:46— re_chunk_store::rebatch_videos::rebatch_video_chunks_to_gops has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ListItemNavigation::end_if_root (cyclomatic 18) crates/ui_tools/re_ui/src/list_item/navigation.rs:75— ListItemNavigation::end_if_root has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
UiExt::native_window_buttons_ui (cyclomatic 18) crates/ui_tools/re_ui/src/ui_ext.rs:1074— UiExt::native_window_buttons_ui has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 6 of the 18 points are its own statements and the rest belongs to one function item inside it that branches (window_button). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
Transform3DExt.__init__ (cyclomatic 18) rerun_py/rerun_sdk/rerun/archetypes/transform3d_ext.py:23— Transform3DExt.__init__ has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TensorDataExt.__init__ (cyclomatic 18) rerun_py/rerun_sdk/rerun/encodings/tensor_data_ext.py:53— TensorDataExt.__init__ has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CoverageEditor::show_mode (cyclomatic 17) crates/panels/re_redap_browser/src/asset_coverage_modal.rs:456— CoverageEditor::show_mode has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
AssetCoverageModal::ui (cyclomatic 17) crates/panels/re_redap_browser/src/asset_coverage_modal.rs:712— AssetCoverageModal::ui has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Flatten::transform (cyclomatic 17) crates/store/re_lenses_core/src/combinators/reshape.rs:114— Flatten::transform 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.
PipelineBudget::reserve_with_priority (cyclomatic 17) crates/store_app/re_datafusion/src/pipeline_budget/mod.rs:1483— PipelineBudget::reserve_with_priority 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.
ArrowNode::show (cyclomatic 17) crates/ui_tools/re_arrow_ui/src/arrow_node.rs:59— ArrowNode::show 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.
GaussianSplatBatchBuilder::add_gaussians (cyclomatic 17) crates/ui_tools/re_renderer/src/gaussian_splat_builder.rs:203— GaussianSplatBatchBuilder::add_gaussians has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Transcript::to_markdown (cyclomatic 17) crates/utils/re_agent/src/transcript.rs:487— Transcript::to_markdown 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.
re_audio::decoding::decode (cyclomatic 17) crates/utils/re_audio/src/decoding.rs:55— re_audio::decoding::decode 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.
UiTableConfig::ui (cyclomatic 17) crates/viewer_support/re_dataframe_ui/src/re_table_utils.rs:178— UiTableConfig::ui 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.
MinMaxAggregator::aggregate (cyclomatic 17) crates/views/re_view_time_series/src/aggregation.rs:121— MinMaxAggregator::aggregate 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.
VideoFrameDecoder._feed_run (cyclomatic 17) rerun_py/rerun_sdk/rerun/experimental/dataloader/decoders/_video.py:634— VideoFrameDecoder._feed_run has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
collectTargets (cyclomatic 17) rerun_js/web-viewer/typedoc-used-by.mjs:97— collectTargets has cyclomatic complexity 17 (threshold 15). 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.
ExternalImporter::import_from_path (cyclomatic 16) crates/data_flow/re_importer/src/importer_external.rs:141— ExternalImporter::import_from_path 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.
ViewerAgentPanel::show (cyclomatic 16) crates/panels/re_agent_panel/src/lib.rs:214— ViewerAgentPanel::show 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.
UniformBuffer::from_textured_rect_with_outline_mask (cyclomatic 16) crates/ui_tools/re_renderer/src/renderer/rectangles.rs:346— UniformBuffer::from_textured_rect_with_outline_mask 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.
ComboItem::ui (cyclomatic 16) crates/ui_tools/re_ui/src/combo_item.rs:93— ComboItem::ui 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.
re_agent::model_api_backend::hosted_tool_update (cyclomatic 16) crates/utils/re_agent/src/model_api_backend.rs:898— re_agent::model_api_backend::hosted_tool_update 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.
CommandKind::is_easily_undone (cyclomatic 16) crates/viewer_support/re_viewer_context/src/command/command_kind.rs:371— CommandKind::is_easily_undone 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.
DataframeTableDelegate::header_cell_ui (cyclomatic 16) crates/views/re_view_dataframe/src/dataframe_ui.rs:258— DataframeTableDelegate::header_cell_ui 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.
TextLogTableDelegate::cell_ui (cyclomatic 16) crates/views/re_view_text_log/src/view_class.rs:386— TextLogTableDelegate::cell_ui 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.
re_view_time_series::line_visualizer_system::build_line_draw_data (cyclomatic 16) crates/views/re_view_time_series/src/line_visualizer_system.rs:116— re_view_time_series::line_visualizer_system::build_line_draw_data 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.
compare_traces.main (cyclomatic 16) skills/investigate-puffin/compare_traces.py:95— compare_traces.main 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.
compare_snippet_output.main (cognitive 77) docs/snippets/compare_snippet_output.py:91— compare_snippet_output.main has cognitive complexity 77 (threshold 15). Drivers by points: if/else 28 (46 pts), loops 9 (15 pts), error handling 3 (11 pts), boolean chains 5 (nesting depth added 32). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TimeSeriesView::ui (cognitive 70) crates/views/re_view_time_series/src/view_class.rs:412— TimeSeriesView::ui has cognitive complexity 70 (threshold 15). Drivers by points: if/else 27 (48 pts), boolean chains 10, match/switch 4 (7 pts), loops 4 (5 pts) (nesting depth added 25). 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.
StatsCommand::run (cognitive 68) crates/top/rerun/src/commands/rrd/stats.rs:38— StatsCommand::run has cognitive complexity 68 (threshold 15). Drivers by points: if/else 15 (29 pts), loops 10 (29 pts), match/switch 4 (9 pts), boolean chains 1 (nesting depth added 38). 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.
MaxImageDimensionsStoreSubscriber::on_events (cognitive 67) crates/views/re_view_spatial/src/max_image_dimension_subscriber.rs:97— MaxImageDimensionsStoreSubscriber::on_events has cognitive complexity 67 (threshold 15). Drivers by points: if/else 14 (47 pts), loops 6 (18 pts), boolean chains 2 (nesting depth added 45). 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.
Objects::validate (cognitive 61) crates/build/re_types_builder/src/objects/mod.rs:31— Objects::validate has cognitive complexity 61 (threshold 15). Drivers by points: if/else 13 (44 pts), boolean chains 7, loops 4 (6 pts), match/switch 1 (4 pts) (nesting depth added 36). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DurationFormatOptions::format_nanos (cognitive 61) crates/utils/re_format/src/duration.rs:113— DurationFormatOptions::format_nanos has cognitive complexity 61 (threshold 15). Drivers by points: if/else 25 (40 pts), boolean chains 14, match/switch 5 (7 pts) (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.
Window::collect (cognitive 55) crates/store_app/re_datafusion/src/pipeline/columnar/mod.rs:337— Window::collect has cognitive complexity 55 (threshold 15). Drivers by points: if/else 10 (28 pts), loops 9 (15 pts), boolean chains 6, match/switch 3 (6 pts) (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.
CommandPaletteProviderImpl::all_matching (cognitive 55) crates/top/re_viewer/src/command_palette.rs:123— CommandPaletteProviderImpl::all_matching has cognitive complexity 55 (threshold 15). Drivers by points: if/else 19 (41 pts), loops 4 (12 pts), boolean chains 2 (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.
ViewportUi::viewport_ui (cognitive 54) crates/panels/re_viewport/src/viewport_ui.rs:55— ViewportUi::viewport_ui has cognitive complexity 54 (threshold 15). Drivers by points: if/else 21 (43 pts), boolean chains 6, loops 5 (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.
DataQueryPropertyResolver::update_overrides_recursive (cognitive 51) crates/viewer_support/re_viewport_blueprint/src/view_contents.rs:449— DataQueryPropertyResolver::update_overrides_recursive has cognitive complexity 51 (threshold 15). Drivers by points: if/else 15 (38 pts), loops 5 (9 pts), boolean chains 4 (nesting depth added 27). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
Decoder::try_read_impl (cognitive 49) crates/store/re_log_encoding/src/rrd/decoder/state_machine.rs:174— Decoder::try_read_impl has cognitive complexity 49 (threshold 15). Drivers by points: if/else 10 (25 pts), match/switch 8 (20 pts), loops 1 (4 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.
AppContext::handle_select_hover_drag_interactions (cognitive 49) crates/viewer_support/re_viewer_context/src/app_context.rs:285— AppContext::handle_select_hover_drag_interactions has cognitive complexity 49 (threshold 15). Drivers by points: if/else 21 (40 pts), boolean chains 5, loops 1 (4 pts) (nesting depth added 22). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_utils._discover_prior_keyframes (cognitive 49) rerun_py/rerun_sdk/rerun/experimental/dataloader/_utils.py:1234— _utils._discover_prior_keyframes has cognitive complexity 49 (threshold 15). Drivers by points: if/else 9 (19 pts), loops 8 (18 pts), ternaries 3 (8 pts), boolean chains 4 (nesting depth added 25). 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.
PythonCodeGenerator::generate_folder (cognitive 48) crates/build/re_types_builder/src/codegen/python/mod.rs:433— PythonCodeGenerator::generate_folder has cognitive complexity 48 (threshold 15). Drivers by points: if/else 24 (40 pts), loops 3 (4 pts), match/switch 2 (4 pts) (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_utils._resolve_decode_requests (cognitive 48) rerun_py/rerun_sdk/rerun/experimental/dataloader/_utils.py:753— _utils._resolve_decode_requests has cognitive complexity 48 (threshold 15). Drivers by points: if/else 10 (32 pts), boolean chains 6, ternaries 2 (6 pts), loops 3 (4 pts) (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.
VideoFrameDecoder._decode_run (cognitive 47) rerun_py/rerun_sdk/rerun/experimental/dataloader/decoders/_video.py:386— VideoFrameDecoder._decode_run has cognitive complexity 47 (threshold 15). Drivers by points: if/else 15 (27 pts), loops 6 (9 pts), boolean chains 7, ternaries 2 (4 pts) (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.
CardLayout::show (cognitive 46) crates/ui_tools/re_ui/src/egui_ext/card_layout.rs:132— CardLayout::show has cognitive complexity 46 (threshold 15). Drivers by points: if/else 17 (39 pts), boolean chains 4, loops 2 (3 pts) (nesting depth added 23). 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.
ImageExt.__init__ (cognitive 45) rerun_py/rerun_sdk/rerun/archetypes/image_ext.py:77— ImageExt.__init__ has cognitive complexity 45 (threshold 15). Drivers by points: if/else 21 (34 pts), boolean chains 6, error handling 2 (3 pts), loops 2 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ListItem::ui (cognitive 44) crates/ui_tools/re_ui/src/list_item/list_item.rs:535— ListItem::ui has cognitive complexity 44 (threshold 15). Drivers by points: if/else 26 (33 pts), boolean chains 9, match/switch 2 (nesting depth added 7). 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.
re_viewport_blueprint::viewport_blueprint::apply_viewport_command (cognitive 44) crates/viewer_support/re_viewport_blueprint/src/viewport_blueprint.rs:974— re_viewport_blueprint::viewport_blueprint::apply_viewport_command has cognitive complexity 44 (threshold 15). Drivers by points: if/else 13 (29 pts), match/switch 4 (9 pts), loops 3 (6 pts) (nesting depth added 24). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
re_protos::v1alpha1::rerun::cloud::v1alpha1::ext::legacy_adapter::adapt_legacy (cognitive 43) crates/store/re_protos/src/v1alpha1/rerun.cloud.v1alpha1.ext.legacy_adapter.rs:53— re_protos::v1alpha1::rerun::cloud::v1alpha1::ext::legacy_adapter::adapt_legacy has cognitive complexity 43 (threshold 15). Drivers by points: if/else 25 (34 pts), boolean chains 5, loops 1 (2 pts), match/switch 2 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MessageDecoderRunner::process (cognitive 42) crates/data_flow/re_mcap/src/decoders/mod.rs:387— MessageDecoderRunner::process has cognitive complexity 42 (threshold 15). Drivers by points: loops 10 (20 pts), if/else 7 (14 pts), match/switch 4 (7 pts), boolean chains 1 (nesting depth added 20). 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.
ServerModal::ui (cognitive 42) crates/panels/re_redap_browser/src/server_modal/mod.rs:166— ServerModal::ui has cognitive complexity 42 (threshold 15). Drivers by points: if/else 23 (32 pts), boolean chains 5, match/switch 4 (5 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SplitCommand::run (cognitive 42) crates/top/rerun/src/commands/rrd/split.rs:82— SplitCommand::run has cognitive complexity 42 (threshold 15). Drivers by points: if/else 9 (21 pts), loops 7 (12 pts), match/switch 3 (9 pts) (nesting depth added 23). 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.
Query::column_visibility_ui_impl (cognitive 42) crates/views/re_view_dataframe/src/view_query/ui.rs:353— Query::column_visibility_ui_impl has cognitive complexity 42 (threshold 15). Drivers by points: if/else 21 (37 pts), loops 3, boolean chains 2 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PinholeExt.__init__ (cognitive 41) rerun_py/rerun_sdk/rerun/archetypes/pinhole_ext.py:16— PinholeExt.__init__ has cognitive complexity 41 (threshold 15). Drivers by points: if/else 17 (29 pts), boolean chains 7, error handling 2 (5 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AgentSession::handle_event (cognitive 40) crates/utils/re_agent/src/session.rs:1079— AgentSession::handle_event has cognitive complexity 40 (threshold 15). Drivers by points: if/else 17 (31 pts), boolean chains 6, match/switch 2 (3 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.
Telemetry::init (cognitive 40) crates/utils/re_perf_telemetry/src/telemetry.rs:513— Telemetry::init has cognitive complexity 40 (threshold 15). Drivers by points: if/else 29 (34 pts), boolean chains 3, match/switch 3 (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
ForceLayoutProvider::layout (cognitive 40) crates/views/re_view_graph/src/layout/provider.rs:185— ForceLayoutProvider::layout has cognitive complexity 40 (threshold 15). Drivers by points: if/else 8 (25 pts), loops 4 (10 pts), match/switch 1 (3 pts), boolean chains 2 (nesting depth added 25). 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.
App::with_commands (cognitive 38) crates/top/re_viewer/src/app/mod.rs:332— App::with_commands has cognitive complexity 38 (threshold 15). Drivers by points: if/else 24 (28 pts), boolean chains 7, match/switch 1 (2 pts), loops 1 (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
RedapServers::handle_command (cognitive 37) crates/panels/re_redap_browser/src/servers/mod.rs:1114— RedapServers::handle_command has cognitive complexity 37 (threshold 15). Drivers by points: if/else 17 (34 pts), match/switch 2 (3 pts) (nesting depth added 18). 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.
MeshRenderer::draw (cognitive 36) crates/ui_tools/re_renderer/src/renderer/mesh_renderer.rs:651— MeshRenderer::draw has cognitive complexity 36 (threshold 15). Drivers by points: if/else 6 (18 pts), match/switch 3 (10 pts), loops 3 (6 pts), boolean chains 2 (nesting depth added 22). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CrateVersion::try_parse (cognitive 36) crates/utils/re_build_info/src/crate_version.rs:366— CrateVersion::try_parse has cognitive complexity 36 (threshold 15). Drivers by points: if/else 21 (29 pts), boolean chains 4, match/switch 1 (2 pts), loops 1 (nesting depth added 9). Of this number, 30 points are the body's own statements and 6 belong to 2 function items inside it that branch. 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.
_utils._build_query_plans (cognitive 36) rerun_py/rerun_sdk/rerun/experimental/dataloader/_utils.py:488— _utils._build_query_plans has cognitive complexity 36 (threshold 15). Drivers by points: if/else 7 (17 pts), loops 4 (10 pts), ternaries 3 (6 pts), boolean chains 3 (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DataframeQueryTableProvider::scan (cognitive 35) crates/store_app/re_datafusion/src/dataframe_query_common/mod.rs:753— DataframeQueryTableProvider::scan has cognitive complexity 35 (threshold 15). Drivers by points: if/else 12 (20 pts), loops 5 (7 pts), boolean chains 4, match/switch 2 (4 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.
StateTimelineView::ui (cognitive 35) crates/views/re_view_state_timeline/src/view_class.rs:250— StateTimelineView::ui has cognitive complexity 35 (threshold 15). Drivers by points: if/else 21 (24 pts), boolean chains 9, loops 2 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
Flatten::transform (cognitive 34) crates/store/re_lenses_core/src/combinators/reshape.rs:114— Flatten::transform has cognitive complexity 34 (threshold 15). Drivers by points: if/else 14 (27 pts), loops 4 (6 pts), boolean chains 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RrdManifestIndex::mark_roots_as (cognitive 34) crates/store_app/re_entity_db/src/rrd_manifest_index/mod.rs:449— RrdManifestIndex::mark_roots_as has cognitive complexity 34 (threshold 15). Drivers by points: if/else 11 (28 pts), loops 2 (4 pts), boolean chains 2 (nesting depth added 19). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
FloatFormatOptions::format_f64 (cognitive 34) crates/utils/re_format/src/lib.rs:194— FloatFormatOptions::format_f64 has cognitive complexity 34 (threshold 15). Drivers by points: if/else 16 (29 pts), loops 1 (4 pts), boolean chains 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Sender::send_impl (cognitive 34) crates/utils/re_quota_channel/src/sync/mod.rs:112— Sender::send_impl has cognitive complexity 34 (threshold 15). Drivers by points: if/else 11 (27 pts), loops 2 (5 pts), boolean chains 2 (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.
EyeState::handle_tracking_entity (cognitive 34) crates/views/re_view_spatial/src/eye.rs:961— EyeState::handle_tracking_entity has cognitive complexity 34 (threshold 15). Drivers by points: if/else 13 (28 pts), boolean chains 3, match/switch 2 (3 pts) (nesting depth added 16). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
Boxes2DExt.__init__ (cognitive 34) rerun_py/rerun_sdk/rerun/archetypes/boxes2d_ext.py:40— Boxes2DExt.__init__ has cognitive complexity 34 (threshold 15). Drivers by points: if/else 17 (34 pts) (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.
PipelineBudget::reserve_with_priority (cognitive 33) crates/store_app/re_datafusion/src/pipeline_budget/mod.rs:1483— PipelineBudget::reserve_with_priority has cognitive complexity 33 (threshold 15). Drivers by points: if/else 11 (25 pts), loops 3 (5 pts), match/switch 1 (2 pts), boolean chains 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.
TransformAxes3DVisualizer::execute (cognitive 33) crates/views/re_view_spatial/src/visualizers/transform_axes_3d.rs:59— TransformAxes3DVisualizer::execute has cognitive complexity 33 (threshold 15). Drivers by points: if/else 12 (27 pts), loops 2 (3 pts), match/switch 1 (2 pts), boolean chains 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.
CompareCommand::run (cognitive 32) crates/top/rerun/src/commands/rrd/compare.rs:48— CompareCommand::run has cognitive complexity 32 (threshold 15). Drivers by points: loops 6 (16 pts), if/else 8 (15 pts), boolean chains 1 (nesting depth added 17). 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.
VerifyCommand::run (cognitive 32) crates/top/rerun/src/commands/rrd/verify.rs:29— VerifyCommand::run has cognitive complexity 32 (threshold 15). Drivers by points: if/else 8 (17 pts), loops 5 (10 pts), match/switch 1 (4 pts), boolean chains 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.
ProcMeshDrawableBuilder::add_batch (cognitive 32) crates/views/re_view_spatial/src/visualizers/utilities/proc_mesh_vis.rs:159— ProcMeshDrawableBuilder::add_batch has cognitive complexity 32 (threshold 15). Drivers by points: if/else 13 (27 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Rgba32Ext.native_to_pa_array_override (cognitive 32) rerun_py/rerun_sdk/rerun/encodings/rgba32_ext.py:63— Rgba32Ext.native_to_pa_array_override has cognitive complexity 32 (threshold 15). Drivers by points: if/else 11 (25 pts), error handling 2 (5 pts), boolean chains 2 (nesting depth added 17). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
re_parquet::grouping::compute_column_groups (cognitive 31) crates/data_flow/re_parquet/src/grouping.rs:38— re_parquet::grouping::compute_column_groups has cognitive complexity 31 (threshold 15). Drivers by points: if/else 5 (18 pts), loops 4 (9 pts), match/switch 2 (4 pts) (nesting depth added 20). 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.
ParsedMeshVertex::set_property (cognitive 31) crates/ui_tools/re_renderer/src/importer/ply.rs:225— ParsedMeshVertex::set_property has cognitive complexity 31 (threshold 15). Drivers by points: if/else 20 (30 pts), 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.
VideoDataDescription::load_mp4_from_reader (cognitive 31) crates/utils/re_video/src/demux/mp4.rs:36— VideoDataDescription::load_mp4_from_reader has cognitive complexity 31 (threshold 15). Drivers by points: if/else 8 (14 pts), match/switch 4 (11 pts), loops 4 (5 pts), boolean chains 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LogDataSource::from_uri (cognitive 30) crates/data_flow/re_data_source/src/data_source.rs:86— LogDataSource::from_uri has cognitive complexity 30 (threshold 15). Drivers by points: if/else 18 (23 pts), boolean chains 7 (nesting depth added 5). Of this number, 26 points are the body's own statements and 4 belong to one function item inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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.
ExternalImporter::import_from_path (cognitive 30) crates/data_flow/re_importer/src/importer_external.rs:141— ExternalImporter::import_from_path has cognitive complexity 30 (threshold 15). Drivers by points: if/else 8 (18 pts), match/switch 4 (9 pts), loops 2 (3 pts) (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GaussianSplatBatchBuilder::add_gaussians (cognitive 30) crates/ui_tools/re_renderer/src/gaussian_splat_builder.rs:203— GaussianSplatBatchBuilder::add_gaussians has cognitive complexity 30 (threshold 15). Drivers by points: if/else 14 (17 pts), loops 3 (10 pts), boolean chains 3 (nesting depth added 10). 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.
LatestAllInstanceResult::data_ui (cognitive 30) crates/viewer_support/re_data_ui/src/latest_all_instance_ui.rs:31— LatestAllInstanceResult::data_ui has cognitive complexity 30 (threshold 15). Drivers by points: if/else 14 (27 pts), loops 1 (3 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_view_audio::waveform::waveform_ui (cognitive 30) crates/views/re_view_audio/src/waveform.rs:80— re_view_audio::waveform::waveform_ui has cognitive complexity 30 (threshold 15). Drivers by points: if/else 21 (22 pts), boolean chains 8 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
DataResultData::from_data_result_and_filter (cognitive 29) crates/panels/re_blueprint_tree/src/data.rs:372— DataResultData::from_data_result_and_filter has cognitive complexity 29 (threshold 15). Drivers by points: if/else 19 (26 pts), boolean chains 2, match/switch 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_sdk_types::archetypes::gaussian_splats3d_ext::read_ply (cognitive 29) crates/store/re_sdk_types/src/archetypes/gaussian_splats3d_ext.rs:301— re_sdk_types::archetypes::gaussian_splats3d_ext::read_ply has cognitive complexity 29 (threshold 15). Drivers by points: if/else 10 (22 pts), loops 3 (6 pts), boolean chains 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FilterCommand::run (cognitive 29) crates/top/rerun/src/commands/rrd/filter.rs:38— FilterCommand::run has cognitive complexity 29 (threshold 15). Drivers by points: if/else 11 (21 pts), match/switch 2 (5 pts), loops 2, 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.
BarChartView::ui (cognitive 29) crates/views/re_view_bar_chart/src/view_class.rs:135— BarChartView::ui has cognitive complexity 29 (threshold 15). Drivers by points: if/else 11 (20 pts), loops 3 (4 pts), match/switch 2 (4 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.
find_scopes.main (cognitive 29) skills/investigate-puffin/find_scopes.py:54— find_scopes.main has cognitive complexity 29 (threshold 15). Drivers by points: loops 7 (15 pts), if/else 5 (12 pts), boolean chains 2 (nesting depth added 15). 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.
PendingRow::many_into_chunks (cognitive 28) crates/store/re_chunk/src/batcher.rs:879— PendingRow::many_into_chunks has cognitive complexity 28 (threshold 15). Drivers by points: loops 10 (17 pts), if/else 3 (10 pts), boolean chains 1 (nesting depth added 14). 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.
EntityDb::app_ui (cognitive 28) crates/viewer_support/re_data_ui/src/entity_db_ui.rs:16— EntityDb::app_ui has cognitive complexity 28 (threshold 15). Drivers by points: if/else 9 (22 pts), match/switch 2 (5 pts), boolean chains 1 (nesting depth added 16). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
Transform3DExt.__init__ (cognitive 28) rerun_py/rerun_sdk/rerun/archetypes/transform3d_ext.py:23— Transform3DExt.__init__ has cognitive complexity 28 (threshold 15). Drivers by points: if/else 11 (20 pts), error handling 2 (5 pts), boolean chains 3 (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.
_manifest_build._resolve_rows (cognitive 28) rerun_py/rerun_sdk/rerun/experimental/dataloader/manifest/_manifest_build.py:276— _manifest_build._resolve_rows has cognitive complexity 28 (threshold 15). Drivers by points: if/else 4 (12 pts), loops 4 (8 pts), ternaries 4 (7 pts), boolean chains 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Client::flush_blocking (cognitive 27) crates/data_flow/re_grpc_client/src/write.rs:237— Client::flush_blocking has cognitive complexity 27 (threshold 15). Drivers by points: if/else 8 (20 pts), match/switch 2 (5 pts), boolean chains 1, loops 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_grpc_client::write::message_proxy_client (cognitive 27) crates/data_flow/re_grpc_client/src/write.rs:349— re_grpc_client::write::message_proxy_client has cognitive complexity 27 (threshold 15). Drivers by points: match/switch 7 (15 pts), if/else 5 (10 pts), loops 2 (nesting depth added 13). 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.
DecoderRegistry::plan (cognitive 27) crates/data_flow/re_mcap/src/decoders/mod.rs:800— DecoderRegistry::plan has cognitive complexity 27 (threshold 15). Drivers by points: if/else 10 (21 pts), loops 4 (5 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.
DataMetaPerTimeline::handle_event_for_row_count (cognitive 27) crates/store_app/re_entity_db/src/data_meta_per_timeline.rs:42— DataMetaPerTimeline::handle_event_for_row_count has cognitive complexity 27 (threshold 15). Drivers by points: loops 7 (21 pts), if/else 2 (5 pts), match/switch 1 (nesting depth added 17). 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.
FieldInput::value (cognitive 27) crates/ui_tools/re_agent_ui/src/ui/elicitation_ui.rs:75— FieldInput::value has cognitive complexity 27 (threshold 15). Drivers by points: if/else 10 (20 pts), boolean chains 6, 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.
re_log::add_builtin_log_filter (cognitive 27) crates/utils/re_log/src/lib.rs:212— re_log::add_builtin_log_filter has cognitive complexity 27 (threshold 15). Drivers by points: if/else 6 (18 pts), loops 3 (9 pts) (nesting depth added 18). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
UiTableConfig::ui (cognitive 27) crates/viewer_support/re_dataframe_ui/src/re_table_utils.rs:178— UiTableConfig::ui has cognitive complexity 27 (threshold 15). Drivers by points: if/else 12 (21 pts), loops 2 (3 pts), boolean chains 2, match/switch 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.
Boxes3DExt.__init__ (cognitive 27) rerun_py/rerun_sdk/rerun/archetypes/boxes3d_ext.py:16— Boxes3DExt.__init__ has cognitive complexity 27 (threshold 15). Drivers by points: if/else 10 (18 pts), error handling 2 (7 pts), boolean chains 2 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DataframeTableDelegate::header_cell_ui (cognitive 26) crates/views/re_view_dataframe/src/dataframe_ui.rs:258— DataframeTableDelegate::header_cell_ui has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (19 pts), match/switch 3 (6 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MinMaxAggregator::aggregate (cognitive 26) crates/views/re_view_time_series/src/aggregation.rs:121— MinMaxAggregator::aggregate has cognitive complexity 26 (threshold 15). Drivers by points: if/else 7 (16 pts), match/switch 3 (6 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_arrow_json::to_json::json_from_store (cognitive 25) crates/store/re_arrow_json/src/to_json.rs:39— re_arrow_json::to_json::json_from_store has cognitive complexity 25 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 5 (7 pts), match/switch 1 (3 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.
Args::generate_markdown_manual (cognitive 25) crates/top/rerun/src/commands/entrypoint.rs:418— Args::generate_markdown_manual has cognitive complexity 25 (threshold 15). Drivers by points: if/else 17 (19 pts), boolean chains 5, loops 1 (nesting depth added 2). None of this is in the body itself: all 25 points belong to 2 function items inside it that branch (generate_arg_doc, generate_markdown_manual). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
CpuMesh::compute_flat_normals_except (cognitive 25) crates/ui_tools/re_renderer/src/mesh.rs:90— CpuMesh::compute_flat_normals_except has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (16 pts), loops 4 (8 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.
MeshDrawData::new (cognitive 25) crates/ui_tools/re_renderer/src/renderer/mesh_renderer.rs:226— MeshDrawData::new has cognitive complexity 25 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 6 (11 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.
TensorDataExt.__init__ (cognitive 25) rerun_py/rerun_sdk/rerun/encodings/tensor_data_ext.py:53— TensorDataExt.__init__ has cognitive complexity 25 (threshold 15). Drivers by points: if/else 17 (22 pts), boolean chains 3 (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
url_generation.segment_url (cognitive 25) rerun_py/rerun_sdk/rerun/utilities/datafusion/functions/url_generation.py:19— url_generation.segment_url has cognitive complexity 25 (threshold 15). Drivers by points: if/else 16 (20 pts), boolean chains 4, ternaries 1 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
SnippetsRefCodeGenerator::generate_fallible (cognitive 24) crates/build/re_types_builder/src/codegen/docs/snippets_ref.rs:126— SnippetsRefCodeGenerator::generate_fallible has cognitive complexity 24 (threshold 15). Drivers by points: if/else 20, boolean chains 3, match/switch 1. Of this number, 14 points are the body's own statements and 10 belong 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.
FrameIdRegistry::register_all_frames_in_chunk (cognitive 24) crates/store_app/re_tf/src/frame_id_registry.rs:58— FrameIdRegistry::register_all_frames_in_chunk has cognitive complexity 24 (threshold 15). Drivers by points: if/else 4 (17 pts), loops 3 (6 pts), boolean chains 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ArrowNode::show (cognitive 24) crates/ui_tools/re_arrow_ui/src/arrow_node.rs:59— ArrowNode::show has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 4, loops 1 (3 pts), match/switch 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.
CompletionPopup::show (cognitive 24) crates/ui_tools/re_ui/src/egui_ext/completion.rs:255— CompletionPopup::show has cognitive complexity 24 (threshold 15). Drivers by points: if/else 12 (15 pts), boolean chains 6, loops 2 (3 pts) (nesting depth added 4). 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.
VideoFrameReferenceVisualizer::process_video_frame (cognitive 24) crates/views/re_view_spatial/src/visualizers/video/video_frame_reference.rs:144— VideoFrameReferenceVisualizer::process_video_frame has cognitive complexity 24 (threshold 15). Drivers by points: if/else 6 (16 pts), match/switch 4 (8 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TextLogSpanIndex::reconcile (cognitive 24) crates/views/re_view_text_log/src/text_log_span_index.rs:65— TextLogSpanIndex::reconcile has cognitive complexity 24 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 6 (10 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.
CompileContext::take_split_receiver (cognitive 24) rerun_py/src/chunk_stream/engine.rs:98— CompileContext::take_split_receiver has cognitive complexity 24 (threshold 15). Drivers by points: if/else 6 (15 pts), match/switch 2 (4 pts), boolean chains 3, loops 1 (2 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Server.__init__ (cognitive 24) rerun_py/rerun_sdk/rerun/server.py:48— Server.__init__ has cognitive complexity 24 (threshold 15). Drivers by points: if/else 6 (15 pts), loops 2 (6 pts), boolean chains 2, ternaries 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.
LeRobotEpisodeV3MetaData::parse_feature_metadata (cognitive 23) crates/data_flow/re_lerobot/src/parse_v3.rs:846— LeRobotEpisodeV3MetaData::parse_feature_metadata has cognitive complexity 23 (threshold 15). Drivers by points: if/else 5 (18 pts), match/switch 1 (3 pts), boolean chains 1, loops 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_chunk_store::rebatch_videos::rebatch_video_chunks_to_gops (cognitive 23) crates/store/re_chunk_store/src/rebatch_videos.rs:46— re_chunk_store::rebatch_videos::rebatch_video_chunks_to_gops has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (16 pts), loops 5, match/switch 1 (2 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Fragment::from_str (cognitive 23) crates/store/re_uri/src/fragment.rs:70— Fragment::from_str has cognitive complexity 23 (threshold 15). Drivers by points: match/switch 4 (16 pts), if/else 2 (6 pts), loops 1 (nesting depth added 16). 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.
NativeMenu::new (cognitive 23) crates/top/re_viewer/src/native_menu.rs:116— NativeMenu::new has cognitive complexity 23 (threshold 15). Drivers by points: loops 5 (9 pts), if/else 4 (8 pts), boolean chains 3, match/switch 1 (3 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ComboItem::ui (cognitive 23) crates/ui_tools/re_ui/src/combo_item.rs:93— ComboItem::ui has cognitive complexity 23 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 3, match/switch 2 (3 pts), loops 1 (2 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
StoreHub::purge_fraction_of_ram (cognitive 23) crates/viewer_support/re_viewer_context/src/store_hub/mod.rs:724— StoreHub::purge_fraction_of_ram has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (16 pts), loops 6 (7 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.
TextLogTableDelegate::cell_ui (cognitive 23) crates/views/re_view_text_log/src/view_class.rs:386— TextLogTableDelegate::cell_ui has cognitive complexity 23 (threshold 15). Drivers by points: if/else 13 (19 pts), match/switch 2 (3 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PooledBatchCollator._collate (cognitive 23) rerun_py/rerun_sdk/rerun/experimental/dataloader/_pooled_batches.py:392— PooledBatchCollator._collate has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (16 pts), loops 3 (4 pts), boolean chains 2, error handling 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SpanTable._span_batch (cognitive 23) rerun_py/rerun_sdk/rerun/experimental/spans.py:425— SpanTable._span_batch has cognitive complexity 23 (threshold 15). Drivers by points: if/else 13 (14 pts), boolean chains 5, ternaries 2 (3 pts), loops 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
TabWidget::new (cognitive 22) crates/panels/re_viewport/src/viewport_ui.rs:927— TabWidget::new has cognitive complexity 22 (threshold 15). Drivers by points: if/else 14 (20 pts), boolean chains 1, match/switch 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SortedTemporalChunks::update (cognitive 22) crates/store_app/re_entity_db/src/rrd_manifest_index/sorted_temporal_chunks.rs:90— SortedTemporalChunks::update has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 6 (10 pts) (nesting depth added 10). Of this number, 21 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ReceiversFromUrlParams::new (cognitive 22) crates/top/rerun/src/commands/entrypoint.rs:2012— ReceiversFromUrlParams::new has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (18 pts), match/switch 1 (3 pts), loops 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TimestampFilter::popup_ui (cognitive 22) crates/viewer_support/re_dataframe_ui/src/filters/timestamp.rs:404— TimestampFilter::popup_ui has cognitive complexity 22 (threshold 15). Drivers by points: if/else 13 (18 pts), boolean chains 2, loops 1, 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.
TableSelectionState::handle_row_click (cognitive 22) crates/viewer_support/re_dataframe_ui/src/table_selection.rs:45— TableSelectionState::handle_row_click has cognitive complexity 22 (threshold 15). Drivers by points: if/else 11 (18 pts), loops 1 (3 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_view_bar_chart::view_class::find_nearest_bar (cognitive 22) crates/views/re_view_bar_chart/src/view_class.rs:425— re_view_bar_chart::view_class::find_nearest_bar has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (16 pts), boolean chains 3, 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.
Blueprint.__init__ (cognitive 22) rerun_py/rerun_sdk/rerun/blueprint/api.py:601— Blueprint.__init__ has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (21 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.
ServerEntriesData::new (cognitive 21) crates/panels/re_recording_panel/src/data.rs:372— ServerEntriesData::new has cognitive complexity 21 (threshold 15). Drivers by points: if/else 3 (9 pts), match/switch 3 (8 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 12). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
RrdManifest::merge (cognitive 21) crates/store/re_chunk_index/src/rrd_manifest.rs:459— RrdManifest::merge has cognitive complexity 21 (threshold 15). Drivers by points: loops 8 (21 pts) (nesting depth added 13). 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.
QueryResults::from_chunk_ids (cognitive 21) crates/store/re_chunk_store/src/query.rs:731— QueryResults::from_chunk_ids has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (14 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.
LocalChunkStoreExec::execute (cognitive 21) crates/store_app/re_datafusion/src/local_chunk_store_provider.rs:248— LocalChunkStoreExec::execute has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (16 pts), match/switch 2 (4 pts), loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_server::rerun_cloud::chunk_selection::select_chunks (cognitive 21) crates/store_app/re_server/src/rerun_cloud/chunk_selection.rs:116— re_server::rerun_cloud::chunk_selection::select_chunks has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 2 (4 pts), match/switch 2 (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.
LensesSink::send (cognitive 21) crates/top/re_sdk/src/lenses/sink.rs:51— LensesSink::send has cognitive complexity 21 (threshold 15). Drivers by points: loops 2 (8 pts), match/switch 3 (7 pts), if/else 1 (5 pts), boolean chains 1 (nesting depth added 14). 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.
re_arrow_ui::arrow_ui::arrow_ui (cognitive 21) crates/ui_tools/re_arrow_ui/src/arrow_ui.rs:10— re_arrow_ui::arrow_ui::arrow_ui has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (14 pts), match/switch 3 (6 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.
GaussianSplatDrawData::new (cognitive 21) crates/ui_tools/re_renderer/src/renderer/gaussian_splat.rs:337— GaussianSplatDrawData::new has cognitive complexity 21 (threshold 15). Drivers by points: if/else 13 (17 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
ListItemNavigation::end_if_root (cognitive 21) crates/ui_tools/re_ui/src/list_item/navigation.rs:75— ListItemNavigation::end_if_root has cognitive complexity 21 (threshold 15). Drivers by points: if/else 13 (16 pts), boolean chains 3, match/switch 1 (2 pts) (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
re_analytics::native::pipeline::flush_pending_events (cognitive 21) crates/utils/re_analytics/src/native/pipeline.rs:161— re_analytics::native::pipeline::flush_pending_events has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (14 pts), match/switch 2 (6 pts), loops 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_audio::decoding::decode (cognitive 21) crates/utils/re_audio/src/decoding.rs:55— re_audio::decoding::decode has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (12 pts), match/switch 3 (6 pts), boolean chains 2, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_perf_telemetry::prometheus::convert_to_prometheus (cognitive 21) crates/utils/re_perf_telemetry/src/prometheus.rs:65— re_perf_telemetry::prometheus::convert_to_prometheus has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (15 pts), loops 2 (3 pts), match/switch 1 (3 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.
DataFusionQuery::execute_streaming (cognitive 21) crates/viewer_support/re_dataframe_ui/src/datafusion_adapter.rs:414— DataFusionQuery::execute_streaming has cognitive complexity 21 (threshold 15). Drivers by points: if/else 4 (11 pts), match/switch 3 (7 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 12). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
re_component_fallbacks::component_fallbacks::archetype_field_fallbacks (cognitive 21) crates/viewer_support/re_component_fallbacks/src/component_fallbacks.rs:30— re_component_fallbacks::component_fallbacks::archetype_field_fallbacks has cognitive complexity 21 (threshold 15). Drivers by points: if/else 12 (18 pts), boolean chains 3 (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.
ConnectionRegistryHandle::connect_and_validate_client_stack (cognitive 20) crates/data_flow/re_redap_client/src/connection_registry.rs:560— ConnectionRegistryHandle::connect_and_validate_client_stack has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (13 pts), match/switch 5 (7 pts) (nesting depth added 8). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
ViewerAgentPanel::show (cognitive 20) crates/panels/re_agent_panel/src/lib.rs:214— ViewerAgentPanel::show has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (11 pts), loops 3 (5 pts), boolean chains 2, match/switch 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BlueprintTree::data_result_ui (cognitive 20) crates/panels/re_blueprint_tree/src/blueprint_tree.rs:528— BlueprintTree::data_result_ui has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (14 pts), match/switch 2 (3 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DatastoreUi::ui (cognitive 20) crates/panels/re_chunk_store_ui/src/chunk_store_ui.rs:191— DatastoreUi::ui has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (13 pts), match/switch 2 (5 pts), boolean chains 2 (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
RecordingPanelData::new (cognitive 20) crates/panels/re_recording_panel/src/data.rs:51— RecordingPanelData::new has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (13 pts), match/switch 2 (4 pts), loops 2, boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Server::asset_ui (cognitive 20) crates/panels/re_redap_browser/src/servers/dataset.rs:610— Server::asset_ui has cognitive complexity 20 (threshold 15). Drivers by points: if/else 15 (18 pts), boolean chains 2 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
MergeSplitRunState::step (cognitive 20) crates/store/re_chunk_optimizer/src/executor/merge_split.rs:88— MergeSplitRunState::step has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 2 (6 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.
ChunkIndexView::try_from_raw (cognitive 20) crates/store/re_chunk_optimizer/src/view.rs:154— ChunkIndexView::try_from_raw has cognitive complexity 20 (threshold 15). Drivers by points: loops 8 (18 pts), if/else 1 (2 pts) (nesting depth added 11). 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.
PartitionDriver::run_inner (cognitive 20) crates/store_app/re_datafusion/src/pipeline/driver.rs:175— PartitionDriver::run_inner has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (17 pts), loops 2 (3 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.
Source::index_ranges (cognitive 20) crates/store_app/re_server/src/store/source.rs:234— Source::index_ranges has cognitive complexity 20 (threshold 15). Drivers by points: loops 6 (19 pts), match/switch 1 (nesting depth added 13). 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.
TransformResolutionCache::add_static_chunk (cognitive 20) crates/store_app/re_tf/src/transform_resolution_cache/cache.rs:281— TransformResolutionCache::add_static_chunk has cognitive complexity 20 (threshold 15). Drivers by points: loops 7 (17 pts), if/else 3 (nesting depth added 10). 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.
ReTable::header_cell_ui (cognitive 20) crates/viewer_support/re_dataframe_ui/src/re_table.rs:193— ReTable::header_cell_ui has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (17 pts), boolean chains 3 (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.
VideoFrameDecoder._feed_run (cognitive 20) rerun_py/rerun_sdk/rerun/experimental/dataloader/decoders/_video.py:634— VideoFrameDecoder._feed_run has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9, loops 4 (6 pts), boolean chains 5 (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.
collectTargets (cognitive 20) rerun_js/web-viewer/typedoc-used-by.mjs:97— collectTargets has cognitive complexity 20 (threshold 15). Drivers by points: loops 4 (8 pts), other 7, if/else 3, boolean chains 2 (nesting depth added 4). 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.
ExampleInfo::parse (cognitive 19) crates/build/re_types_builder/src/codegen/common.rs:43— ExampleInfo::parse has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 2, loops 1 (nesting depth added 7). Of this number, 10 points are the body's own statements and 9 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ParquetChunkIterator::next (cognitive 19) crates/data_flow/re_parquet/src/streaming.rs:228— ParquetChunkIterator::next has cognitive complexity 19 (threshold 15). Drivers by points: if/else 4 (13 pts), match/switch 2 (5 pts), loops 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CoverageEditor::show_mode (cognitive 19) crates/panels/re_redap_browser/src/asset_coverage_modal.rs:456— CoverageEditor::show_mode has cognitive complexity 19 (threshold 15). Drivers by points: if/else 13 (14 pts), boolean chains 5 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
AssetCoverageModal::ui (cognitive 19) crates/panels/re_redap_browser/src/asset_coverage_modal.rs:712— AssetCoverageModal::ui has cognitive complexity 19 (threshold 15). Drivers by points: if/else 13, boolean chains 4, match/switch 1 (2 pts) (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
re_types_core::reflection::generic_placeholder_for_datatype (cognitive 19) crates/store/re_types_core/src/reflection.rs:92— re_types_core::reflection::generic_placeholder_for_datatype has cognitive complexity 19 (threshold 15). Drivers by points: match/switch 7 (13 pts), if/else 4 (6 pts) (nesting depth added 8). 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.
Origin::replace_and_parse (cognitive 19) crates/store/re_uri/src/origin.rs:95— Origin::replace_and_parse has cognitive complexity 19 (threshold 15). Drivers by points: if/else 15 (18 pts), boolean chains 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
PointCloudDrawData::new (cognitive 19) crates/ui_tools/re_renderer/src/renderer/point_cloud.rs:336— PointCloudDrawData::new has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (15 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RectangleDrawData::new (cognitive 19) crates/ui_tools/re_renderer/src/renderer/rectangles.rs:504— RectangleDrawData::new has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 3, match/switch 1 (2 pts), loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_byte_size_derive::enum_body (cognitive 19) crates/utils/re_byte_size_derive/src/lib.rs:202— re_byte_size_derive::enum_body has cognitive complexity 19 (threshold 15). Drivers by points: if/else 4 (10 pts), loops 3 (7 pts), match/switch 1 (2 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.
re_ros_msg::deserialize::decode_value (cognitive 19) crates/utils/re_ros_msg/src/deserialize/mod.rs:142— re_ros_msg::deserialize::decode_value has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (11 pts), match/switch 3 (5 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.
VisualizerEntityMapping::add_visualizability_reason (cognitive 19) crates/viewer_support/re_viewer_context/src/view/visualizer_entity_subscriber.rs:93— VisualizerEntityMapping::add_visualizability_reason has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (16 pts), match/switch 2 (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.
Points3DVisualizer::process_data (cognitive 19) crates/views/re_view_spatial/src/visualizers/points3d.rs:222— Points3DVisualizer::process_data has cognitive complexity 19 (threshold 15). Drivers by points: if/else 4 (12 pts), loops 3 (6 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_view_text_log::view_class::view_property_ui_rows (cognitive 19) crates/views/re_view_text_log/src/view_class.rs:480— re_view_text_log::view_class::view_property_ui_rows has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (15 pts), loops 2 (4 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.
AnyBatchValue.__init__ (cognitive 19) rerun_py/rerun_sdk/rerun/any_batch_value.py:194— AnyBatchValue.__init__ has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (17 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.
_entry._python_objects_to_record_batch (cognitive 19) rerun_py/rerun_sdk/rerun/catalog/_entry.py:2448— _entry._python_objects_to_record_batch has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 2, error handling 1 (2 pts), loops 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ViewerClient.quit (cognitive 19) rerun_py/rerun_sdk/rerun/experimental/_viewer_client.py:1563— ViewerClient.quit has cognitive complexity 19 (threshold 15). Drivers by points: error handling 4 (8 pts), if/else 7 (8 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_LeaseTracker._collect_released (cognitive 19) rerun_py/rerun_sdk/rerun/experimental/dataloader/_pooled_batches.py:121— _LeaseTracker._collect_released has cognitive complexity 19 (threshold 15). Drivers by points: error handling 3 (9 pts), if/else 2 (5 pts), loops 3 (5 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.
compare_traces.main (cognitive 19) skills/investigate-puffin/compare_traces.py:95— compare_traces.main has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 5 (8 pts), if/else 5 (7 pts), boolean chains 2, loops 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GopRunState::step (cognitive 18) crates/store/re_chunk_optimizer/src/executor/gop.rs:269— GopRunState::step has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (16 pts), loops 1, match/switch 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FetchExecutor::issue (cognitive 18) crates/store_app/re_datafusion/src/pipeline/executor.rs:90— FetchExecutor::issue has cognitive complexity 18 (threshold 15). Drivers by points: match/switch 5 (11 pts), if/else 3 (5 pts), loops 2 (nesting depth added 8). 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.
AgentPanel::ui (cognitive 18) crates/ui_tools/re_agent_ui/src/ui/agent_panel.rs:629— AgentPanel::ui has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (14 pts), match/switch 2 (3 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Toasts::show (cognitive 18) crates/ui_tools/re_ui/src/notifications.rs:818— Toasts::show has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 2, 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.
ImageStats::from_image (cognitive 18) crates/viewer_support/re_viewer_context/src/tensor/image_stats.rs:22— ImageStats::from_image has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (12 pts), match/switch 3 (4 pts), boolean chains 2 (nesting depth added 2). Of this number, 12 points are the body's own statements and 6 belong to 3 function items inside it that branch. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
re_viewer_control_tools::message_schema (cognitive 18) crates/viewer_support/re_viewer_control_tools/src/lib.rs:346— re_viewer_control_tools::message_schema has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (10 pts), boolean chains 4, match/switch 2 (3 pts), loops 1 (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.
View._log_to_stream (cognitive 18) rerun_py/rerun_sdk/rerun/blueprint/api.py:162— View._log_to_stream has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (13 pts), loops 4 (5 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DataloaderMetrics.summary (cognitive 18) rerun_py/rerun_sdk/rerun/experimental/dataloader/_metrics.py:338— DataloaderMetrics.summary has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (11 pts), loops 3 (5 pts), boolean chains 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PooledBatchCollator._acquire (cognitive 18) rerun_py/rerun_sdk/rerun/experimental/dataloader/_pooled_batches.py:344— PooledBatchCollator._acquire has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 3, ternaries 1 (2 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ExtensionClass::new (cognitive 17) crates/build/re_types_builder/src/codegen/python/mod.rs:201— ExtensionClass::new has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (15 pts), loops 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DirectoryImporter::import_from_path (cognitive 17) crates/data_flow/re_importer/src/importer_directory.rs:17— DirectoryImporter::import_from_path has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (8 pts), match/switch 2 (5 pts), loops 2 (4 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.
McapImporter::emit_chunks (cognitive 17) crates/data_flow/re_importer/src/importer_mcap/importer.rs:141— McapImporter::emit_chunks has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (7 pts), loops 2 (6 pts), match/switch 1 (3 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EntityPath::short_names_with_disambiguation (cognitive 17) crates/store/re_log_types/src/path/entity_path.rs:349— EntityPath::short_names_with_disambiguation has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (13 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RecordBatchGrpcOutputStream::poll_next (cognitive 17) crates/store_app/re_datafusion/src/table_entry_provider.rs:551— RecordBatchGrpcOutputStream::poll_next has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (11 pts), match/switch 3 (6 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RerunCloudHandler::find_entries (cognitive 17) crates/store_app/re_server/src/rerun_cloud/mod.rs:843— RerunCloudHandler::find_entries has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (14 pts), match/switch 2, boolean chains 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
InMemoryStore::load_directory_as_dataset (cognitive 17) crates/store_app/re_server/src/store/in_memory_store.rs:206— InMemoryStore::load_directory_as_dataset has cognitive complexity 17 (threshold 15). Drivers by points: match/switch 3 (10 pts), if/else 3 (6 pts), loops 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.
PrintCommand::run (cognitive 17) crates/top/rerun/src/commands/rrd/print.rs:70— PrintCommand::run has cognitive complexity 17 (threshold 15). Drivers by points: loops 3 (6 pts), if/else 4 (5 pts), boolean chains 4, match/switch 1 (2 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
rerun_c::rr_recording_stream_flush_blocking (cognitive 17) crates/top/rerun_c/src/lib.rs:733— rerun_c::rr_recording_stream_flush_blocking has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (13 pts), match/switch 1 (3 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DataFusionTableDelegate::header_cell_ui (cognitive 17) crates/viewer_support/re_dataframe_ui/src/datafusion_table_widget.rs:1990— DataFusionTableDelegate::header_cell_ui has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (15 pts), loops 1 (2 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.
BlueprintResolvedLatestAtResults::resolve_annotation_context (cognitive 17) crates/viewer_support/re_view/src/annotation_context_resolver.rs:285— BlueprintResolvedLatestAtResults::resolve_annotation_context has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (14 pts), match/switch 1 (2 pts), loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ViewerUrl::parse_with_options (cognitive 17) crates/viewer_support/re_viewer_context/src/viewer_url.rs:190— ViewerUrl::parse_with_options has cognitive complexity 17 (threshold 15). Drivers by points: if/else 13, 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.
VoxelGridMapVisualizer::process_voxel_grid_map (cognitive 17) crates/views/re_view_spatial/src/visualizers/voxel_grid_map.rs:189— VoxelGridMapVisualizer::process_voxel_grid_map has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 2, loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_utils._uncovered_integer_ranges (cognitive 17) rerun_py/rerun_sdk/rerun/experimental/dataloader/_utils.py:1152— _utils._uncovered_integer_ranges has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (14 pts), loops 2 (3 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
VideoFrameDecoder._try_emit_view_windows (cognitive 17) rerun_py/rerun_sdk/rerun/experimental/dataloader/decoders/_video.py:569— VideoFrameDecoder._try_emit_view_windows has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 3, loops 2 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_build_tools::export_build_info_vars_for_crate (cognitive 16) crates/build/re_build_tools/src/lib.rs:128— re_build_tools::export_build_info_vars_for_crate has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10, match/switch 3 (4 pts), boolean chains 2 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Visitor::visit_children (cognitive 16) crates/build/re_dev_tools/src/build_search_index/ingest/cpp.rs:79— Visitor::visit_children has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (10 pts), loops 2 (4 pts), match/switch 1 (2 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_dev_tools::build_search_index::ingest::docs::parse_inline_list (cognitive 16) crates/build/re_dev_tools/src/build_search_index/ingest/docs.rs:168— re_dev_tools::build_search_index::ingest::docs::parse_inline_list has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (13 pts), match/switch 1 (2 pts), loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ArchetypeImporter::import_from_file_contents (cognitive 16) crates/data_flow/re_importer/src/importer_archetype.rs:55— ArchetypeImporter::import_from_file_contents has cognitive complexity 16 (threshold 15). Drivers by points: if/else 14 (15 pts), boolean chains 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
UrdfTree::compute_joint_transform_batches (cognitive 16) crates/data_flow/re_importer/src/importer_urdf/urdf_tree.rs:247— UrdfTree::compute_joint_transform_batches has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_lerobot::emits::build_emits (cognitive 16) crates/data_flow/re_lerobot/src/emits.rs:104— re_lerobot::emits::build_emits has cognitive complexity 16 (threshold 15). Drivers by points: match/switch 3 (8 pts), if/else 1 (4 pts), boolean chains 3, loops 1 (nesting depth added 8). 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.
TimeColumn::sanity_check (cognitive 16) crates/store/re_chunk/src/chunk.rs:1969— TimeColumn::sanity_check has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (10 pts), boolean chains 4, loops 1 (2 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RrdManifestBuilder::append (cognitive 16) crates/store/re_chunk_index/src/rrd_manifest_builder.rs:79— RrdManifestBuilder::append has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 3 (5 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Parser::term (cognitive 16) crates/store/re_lenses_core/src/selector/parser.rs:305— Parser::term has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 2, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ChunkPrioritizer::find_chunks_with_archetypes (cognitive 16) crates/store_app/re_entity_db/src/rrd_manifest_index/chunk_prioritizer.rs:471— ChunkPrioritizer::find_chunks_with_archetypes has cognitive complexity 16 (threshold 15). Drivers by points: loops 5 (12 pts), if/else 1 (4 pts) (nesting depth added 10). 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.
DownloadCommand::run (cognitive 16) crates/top/rerun/src/commands/download.rs:28— DownloadCommand::run has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (13 pts), match/switch 1 (2 pts), loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Verifier::verify_component_column (cognitive 16) crates/top/rerun/src/commands/rrd/verify.rs:150— Verifier::verify_component_column has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 1, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LegendWidget::show_entries (cognitive 16) crates/ui_tools/re_plot/src/legend.rs:76— LegendWidget::show_entries has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (14 pts), loops 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
UiExt::native_window_buttons_ui::window_button (cognitive 16) crates/ui_tools/re_ui/src/ui_ext.rs:1089— UiExt::native_window_buttons_ui::window_button has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 3, match/switch 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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.
TimestampFormat::format_opt (cognitive 16) crates/utils/re_format/src/timestamp_format.rs:153— TimestampFormat::format_opt has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (9 pts), match/switch 3 (6 pts), boolean chains 1 (nesting depth added 6). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
Vp9KeyframeHeader::parse (cognitive 16) crates/utils/re_video/src/vp9.rs:41— Vp9KeyframeHeader::parse has cognitive complexity 16 (threshold 15). Drivers by points: if/else 14 (16 pts) (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
LatestAtInstanceResult::data_ui (cognitive 16) crates/viewer_support/re_data_ui/src/latest_at_instance_ui.rs:30— LatestAtInstanceResult::data_ui has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 2, match/switch 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
SegmentPreviewRenderer::show_preview (cognitive 16) crates/viewer_support/re_dataframe_ui/src/preview_renderer.rs:330— SegmentPreviewRenderer::show_preview has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (13 pts), loops 2, match/switch 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_time_ruler::paint_ticks::paint_ticks (cognitive 16) crates/viewer_support/re_time_ruler/src/paint_ticks.rs:103— re_time_ruler::paint_ticks::paint_ticks has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (13 pts), loops 2, boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
re_view_dataframe::dataframe_ui::line_ui (cognitive 16) crates/views/re_view_dataframe/src/dataframe_ui.rs:567— re_view_dataframe::dataframe_ui::line_ui has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (13 pts), match/switch 2, boolean chains 1 (nesting depth added 6). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity· rerun_py" # name of the rust crate · ×1
rerun_py" # name of the rust crate::catalog::dataset_selection::build_dataframe_query_table_provider (cognitive 16) rerun_py/src/catalog/dataset_selection.rs:486— rerun_py" # name of the rust crate::catalog::dataset_selection::build_dataframe_query_table_provider has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TimeColumn.__init__ (cognitive 16) rerun_py/rerun_sdk/rerun/_send_columns.py:66— TimeColumn.__init__ has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (16 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Mesh3DExt.__init__ (cognitive 16) rerun_py/rerun_sdk/rerun/archetypes/mesh3d_ext.py:47— Mesh3DExt.__init__ has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (8 pts), error handling 1 (4 pts), ternaries 1 (4 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.
DatasetEntry._set_asset_applies_to (cognitive 16) rerun_py/rerun_sdk/rerun/catalog/_entry.py:706— DatasetEntry._set_asset_applies_to has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (12 pts), error handling 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_iterable_dataset._skip_incomplete (cognitive 16) rerun_py/rerun_sdk/rerun/experimental/dataloader/_iterable_dataset.py:54— _iterable_dataset._skip_incomplete has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (9 pts), loops 3 (5 pts), boolean chains 2 (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.
_sample_index._build (cognitive 16) rerun_py/rerun_sdk/rerun/experimental/dataloader/_sample_index.py:305— _sample_index._build has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (8 pts), ternaries 3 (5 pts), boolean chains 2, error handling 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.
_utils._fetch_keyframe_ranges (cognitive 16) rerun_py/rerun_sdk/rerun/experimental/dataloader/_utils.py:1172— _utils._fetch_keyframe_ranges has cognitive complexity 16 (threshold 15). Drivers by points: loops 5 (9 pts), ternaries 3 (5 pts), if/else 2 (nesting depth added 6). 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.
check_joint_mapping.main (cognitive 16) skills/rerun-urdf/scripts/check_joint_mapping.py:108— check_joint_mapping.main has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (10 pts), loops 3 (4 pts), ternaries 2 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Near-duplicate member pair (64 shared lines) crates/panels/re_selection_panel/src/view_entity_picker.rs:333— crates/panels/re_selection_panel/src/view_entity_picker.rs:333-437 | crates/panels/re_time_panel/src/streams_tree_data.rs:109-214 — These two members are variants of one another: 64 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
Near-duplicate member pair (38 shared lines) crates/views/re_view_spatial/src/visualizers/lines2d.rs:176— crates/views/re_view_spatial/src/visualizers/lines2d.rs:176-251 | crates/views/re_view_spatial/src/visualizers/lines3d.rs:187-262 — These two members are variants of one another: 38 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
Near-duplicate member pair (35 shared lines) crates/views/re_view_time_series/src/line_visualizer_system.rs:278— crates/views/re_view_time_series/src/line_visualizer_system.rs:278-343 | crates/views/re_view_time_series/src/line_visualizer_system.rs:352-412 — These two members are variants of one another: 35 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
Near-duplicate member pair (32 shared lines) crates/viewer_support/re_viewer_context/src/cache/video_stream_cache/mod.rs:1090— crates/viewer_support/re_viewer_context/src/cache/video_stream_cache/mod.rs:1090-1225 | crates/viewer_support/re_viewer_context/src/cache/video_stream_cache/mod.rs:1396-1544 — These two members are variants of one another: 32 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
Near-duplicate member pair (24 shared lines) crates/views/re_view_time_series/src/series_query.rs:202— crates/views/re_view_time_series/src/series_query.rs:202-291 | crates/views/re_view_time_series/src/series_query.rs:377-436 — These two members are variants of one another: 24 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication· Members sharing a duplicated core (6 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (6 members, 50+ identical tokens) crates/utils/re_perf_telemetry/src/prometheus.rs:208— crates/utils/re_perf_telemetry/src/prometheus.rs:208-230 | crates/utils/re_perf_telemetry/src/prometheus.rs:238-257 | crates/utils/re_perf_telemetry/src/prometheus.rs:265-286 | crates/utils/re_perf_telemetry/src/prometheus.rs:383-405 | crates/utils/re_perf_telemetry/src/prometheus.rs:413-432 | crates/utils/re_perf_telemetry/src/prometheus.rs:440-461 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
D4 · Code Duplication· Edited copy of a member (156 corresponding lines) · ×1
Edited copy of a member (156 corresponding lines) crates/viewer_support/re_viewer_context/src/tensor/image_stats.rs:22— crates/viewer_support/re_viewer_context/src/tensor/image_stats.rs:22-189 | crates/viewer_support/re_viewer_context/src/tensor/tensor_stats.rs:21-176 — These two members are one piece of code written twice and then edited apart: 156 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (95 corresponding lines) · ×1
Edited copy of a member (95 corresponding lines) docs/snippets/all/archetypes/transform3d_hierarchy.rs:3— docs/snippets/all/archetypes/transform3d_hierarchy.rs:3-97 | docs/snippets/all/archetypes/transform3d_hierarchy_frames.rs:3-121 — These two members are one piece of code written twice and then edited apart: 95 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (118 corresponding lines) · ×1
Edited copy of a member (118 corresponding lines) crates/views/re_view_spatial/src/visualizers/volume_3d.rs:64— crates/views/re_view_spatial/src/visualizers/volume_3d.rs:64-188 | crates/views/re_view_spatial/src/visualizers/voxel_grid_map.rs:68-185 — These two members are one piece of code written twice and then edited apart: 118 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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 (138 corresponding lines) · ×1
Edited copy of a member (138 corresponding lines) crates/viewer_support/re_view/src/query.rs:299— crates/viewer_support/re_view/src/query.rs:299-436 | crates/viewer_support/re_view/src/query.rs:483-621 — These two members are one piece of code written twice and then edited apart: 138 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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 (101 corresponding lines) · ×1
Edited copy of a member (101 corresponding lines) crates/views/re_view_spatial/src/visualizers/boxes2d.rs:32— crates/views/re_view_spatial/src/visualizers/boxes2d.rs:32-132 | crates/views/re_view_spatial/src/visualizers/ellipses2d.rs:139-247 — These two members are one piece of code written twice and then edited apart: 101 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (76 corresponding lines) · ×1
Edited copy of a member (76 corresponding lines) crates/views/re_view_map/src/visualizers/geo_line_strings.rs:57— crates/views/re_view_map/src/visualizers/geo_line_strings.rs:57-132 | crates/views/re_view_map/src/visualizers/geo_points.rs:70-145 — 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 copies of one member (3 members, 86+ corresponding lines) · ×1
Edited copies of one member (3 members, 86+ corresponding lines) crates/views/re_view_spatial/src/visualizers/arrows2d.rs:32— crates/views/re_view_spatial/src/visualizers/arrows2d.rs:32-126 | crates/views/re_view_spatial/src/visualizers/lines2d.rs:31-116 | crates/views/re_view_spatial/src/visualizers/lines3d.rs:32-127 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 86 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 (89 corresponding lines) · ×1
Edited copy of a member (89 corresponding lines) crates/views/re_view_spatial/src/visualizers/images.rs:89— crates/views/re_view_spatial/src/visualizers/images.rs:89-177 | crates/views/re_view_spatial/src/visualizers/segmentation_images.rs:53-152 — These two members are one piece of code written twice and then edited apart: 89 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (88 corresponding lines) · ×1
Edited copy of a member (88 corresponding lines) crates/store/re_chunk/src/earliest_at.rs:88— crates/store/re_chunk/src/earliest_at.rs:88-183 | crates/store/re_chunk/src/latest_at.rs:113-200 — These two members are one piece of code written twice and then edited apart: 88 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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 (58 corresponding lines) · ×1
Edited copy of a member (58 corresponding lines) crates/data_flow/re_lenses/src/semantic/foxglove/packed_element_field.rs:168— crates/data_flow/re_lenses/src/semantic/foxglove/packed_element_field.rs:168-229 | crates/data_flow/re_lenses/src/semantic/foxglove/packed_element_field.rs:323-380 — These two members are one piece of code written twice and then edited apart: 58 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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/ui_tools/re_renderer/src/renderer/generic_skybox.rs:102— crates/ui_tools/re_renderer/src/renderer/generic_skybox.rs:102-166 | crates/ui_tools/re_renderer/src/renderer/world_grid.rs:121-192 — 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 (66 corresponding lines) · ×1
Edited copy of a member (66 corresponding lines) crates/views/re_view_spatial/src/visualizers/capsules3d.rs:33— crates/views/re_view_spatial/src/visualizers/capsules3d.rs:33-102 | crates/views/re_view_spatial/src/visualizers/cylinders3d.rs:32-97 — These two members are one piece of code written twice and then edited apart: 66 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (77 corresponding lines) · ×1
Edited copy of a member (77 corresponding lines) crates/store_app/re_query/src/bin/clamped_zip.rs:121— crates/store_app/re_query/src/bin/clamped_zip.rs:121-197 | crates/store_app/re_query/src/bin/clamped_zip.rs:238-315 — These two members are one piece of code written twice and then edited apart: 77 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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 (59 corresponding lines) · ×1
Edited copy of a member (59 corresponding lines) crates/views/re_view_spatial/src/visualizers/assets3d.rs:40— crates/views/re_view_spatial/src/visualizers/assets3d.rs:40-99 | crates/views/re_view_spatial/src/visualizers/meshes.rs:42-100 — These two members are one piece of code written twice and then edited apart: 59 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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 (68 corresponding lines) · ×1
Edited copy of a member (68 corresponding lines) crates/data_flow/re_grpc_server/src/lib.rs:493— crates/data_flow/re_grpc_server/src/lib.rs:493-560 | crates/data_flow/re_grpc_server/src/lib.rs:575-648 — These two members are one piece of code written twice and then edited apart: 68 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 102+ corresponding lines) · ×1
Edited copies of one member (3 members, 102+ corresponding lines) crates/viewer_support/re_viewer_context/src/command/command_kind.rs:155— crates/viewer_support/re_viewer_context/src/command/command_kind.rs:155-256 | crates/viewer_support/re_viewer_context/src/command/command_kind.rs:260-361 | crates/viewer_support/re_viewer_context/src/command/command_kind.rs:371-475 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 102 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 (47 corresponding lines) · ×1
Edited copy of a member (47 corresponding lines) crates/ui_tools/re_renderer/src/resource_managers/bayer_converter.rs:101— crates/ui_tools/re_renderer/src/resource_managers/bayer_converter.rs:101-147 | crates/ui_tools/re_renderer/src/resource_managers/yuv_converter.rs:387-449 — These two members are one piece of code written twice and then edited apart: 47 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (53 corresponding lines) · ×1
Edited copy of a member (53 corresponding lines) crates/ui_tools/re_renderer/src/allocator/cpu_write_gpu_read_belt.rs:571— crates/ui_tools/re_renderer/src/allocator/cpu_write_gpu_read_belt.rs:571-633 | crates/ui_tools/re_renderer/src/allocator/gpu_readback_belt.rs:267-319 — These two members are one piece of code written twice and then edited apart: 53 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (54 corresponding lines) · ×1
Edited copy of a member (54 corresponding lines) crates/panels/re_selection_panel/src/selection_panel.rs:677— crates/panels/re_selection_panel/src/selection_panel.rs:677-730 | crates/viewer_support/re_view/src/component_drop.rs:251-309 — These two members are one piece of code written twice and then edited apart: 54 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (46 corresponding lines) · ×1
Edited copy of a member (46 corresponding lines) crates/ui_tools/re_renderer/src/renderer/gaussian_splat.rs:826— crates/ui_tools/re_renderer/src/renderer/gaussian_splat.rs:826-871 | crates/ui_tools/re_renderer/src/renderer/point_cloud.rs:857-908 — These two members are one piece of code written twice and then edited apart: 46 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (73 corresponding lines) · ×1
Edited copy of a member (73 corresponding lines) crates/ui_tools/re_renderer/src/resource_managers/bayer_converter.rs:192— crates/ui_tools/re_renderer/src/resource_managers/bayer_converter.rs:192-264 | crates/ui_tools/re_renderer/src/resource_managers/yuv_converter.rs:499-571 — These two members are one piece of code written twice and then edited apart: 73 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (37 corresponding lines) · ×1
Edited copy of a member (37 corresponding lines) crates/store/re_lenses_core/src/selector/parser.rs:506— crates/store/re_lenses_core/src/selector/parser.rs:506-542 | crates/store/re_lenses_core/src/selector/parser.rs:611-647 — These two members are one piece of code written twice and then edited apart: 37 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (6 members, 16+ corresponding lines) · ×1
Edited copies of one member (6 members, 16+ corresponding lines) crates/ui_tools/re_renderer/src/colormap.rs:277— crates/ui_tools/re_renderer/src/colormap.rs:277-292 | crates/ui_tools/re_renderer/src/colormap.rs:295-310 | crates/ui_tools/re_renderer/src/colormap.rs:313-328 | crates/ui_tools/re_renderer/src/colormap.rs:331-346 | crates/ui_tools/re_renderer/src/colormap.rs:371-390 | crates/ui_tools/re_renderer/src/colormap.rs:400-417 — These 6 members are one piece of code written 6 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 6 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 34+ corresponding lines) · ×1
Edited copies of one member (4 members, 34+ corresponding lines) rerun_py/src/chunk_stream/hdf5_reader.rs:227— rerun_py/src/chunk_stream/hdf5_reader.rs:227-267 | rerun_py/src/chunk_stream/lerobot_reader.rs:155-188 | rerun_py/src/chunk_stream/mp4_reader.rs:189-230 | rerun_py/src/chunk_stream/parquet_reader.rs:185-230 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 34 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (36 corresponding lines) · ×1
Edited copy of a member (36 corresponding lines) crates/viewer_support/re_viewer_context/src/time_control/command.rs:561— crates/viewer_support/re_viewer_context/src/time_control/command.rs:561-596 | crates/viewer_support/re_viewer_context/src/time_control/command.rs:598-633 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 30+ corresponding lines) · ×1
Edited copies of one member (3 members, 30+ corresponding lines) crates/utils/re_perf_telemetry/src/prometheus.rs:657— crates/utils/re_perf_telemetry/src/prometheus.rs:657-686 | crates/utils/re_perf_telemetry/src/prometheus.rs:694-723 | crates/utils/re_perf_telemetry/src/prometheus.rs:731-760 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 30 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 40+ corresponding lines) · ×1
Edited copies of one member (3 members, 40+ corresponding lines) crates/views/re_view_time_series/src/line_visualizer_system.rs:73— crates/views/re_view_time_series/src/line_visualizer_system.rs:73-112 | crates/views/re_view_time_series/src/measurements_visualizer_system.rs:65-112 | crates/views/re_view_time_series/src/point_visualizer_system.rs:69-108 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 40 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 (45 corresponding lines) · ×1
Edited copy of a member (45 corresponding lines) crates/data_flow/re_lenses/src/semantic/foxglove/point_cloud.rs:12— crates/data_flow/re_lenses/src/semantic/foxglove/point_cloud.rs:12-57 | crates/data_flow/re_lenses/src/semantic/foxglove/voxel_grid.rs:12-56 — These two members are one piece of code written twice and then edited apart: 45 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 34+ corresponding lines) · ×1
Edited copies of one member (3 members, 34+ corresponding lines) crates/viewer_support/re_viewer_context/src/component_ui_registry.rs:211— crates/viewer_support/re_viewer_context/src/component_ui_registry.rs:211-252 | crates/viewer_support/re_viewer_context/src/component_ui_registry.rs:349-382 | crates/viewer_support/re_viewer_context/src/component_ui_registry.rs:395-428 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 34 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (42 corresponding lines) · ×1
Edited copy of a member (42 corresponding lines) crates/utils/re_auth/src/oauth/login_flow.rs:30— crates/utils/re_auth/src/oauth/login_flow.rs:30-71 | crates/utils/re_auth/src/oauth/login_flow.rs:113-157 — These two members are one piece of code written twice and then edited apart: 42 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 16+ corresponding lines) · ×1
Edited copies of one member (5 members, 16+ corresponding lines) crates/viewer_support/re_viewer_context/src/cache/image_decode_cache.rs:214— crates/viewer_support/re_viewer_context/src/cache/image_decode_cache.rs:214-233 | crates/viewer_support/re_viewer_context/src/cache/video_asset_cache.rs:146-166 | crates/views/re_view_audio/src/audio_asset_cache.rs:215-231 | crates/views/re_view_spatial/src/caches/mesh_cache.rs:187-202 | crates/views/re_view_spatial/src/proc_mesh.rs:500-518 — 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 (44 corresponding lines) · ×1
Edited copy of a member (44 corresponding lines) rerun_py/rerun_sdk/rerun/experimental/dataloader/_iterable_dataset.py:269— rerun_py/rerun_sdk/rerun/experimental/dataloader/_iterable_dataset.py:269-312 | rerun_py/rerun_sdk/rerun/experimental/dataloader/_map_dataset.py:123-170 — These two members are one piece of code written twice and then edited apart: 44 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 15+ corresponding lines) · ×1
Edited copies of one member (4 members, 15+ corresponding lines) docs/snippets/all/archetypes/annotation_context_segmentation.rs:5— docs/snippets/all/archetypes/annotation_context_segmentation.rs:5-31 | docs/snippets/all/archetypes/depth_image_simple.rs:5-19 | docs/snippets/all/archetypes/image_simple.rs:5-23 | docs/snippets/all/archetypes/segmentation_image_simple.rs:5-27 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 42+ corresponding lines) · ×1
Edited copies of one member (4 members, 42+ corresponding lines) rerun_py/rerun_sdk/rerun/archetypes/asset3d_ext.py:23— rerun_py/rerun_sdk/rerun/archetypes/asset3d_ext.py:23-70 | rerun_py/rerun_sdk/rerun/archetypes/asset_audio_ext.py:22-65 | rerun_py/rerun_sdk/rerun/archetypes/asset_video_ext.py:27-68 | rerun_py/rerun_sdk/rerun/archetypes/encoded_image_ext.py:43-106 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 21+ corresponding lines) · ×1
Edited copies of one member (4 members, 21+ corresponding lines) crates/store/re_chunk/src/chunk.rs:1253— crates/store/re_chunk/src/chunk.rs:1253-1273 | crates/store/re_chunk/src/chunk.rs:1279-1299 | crates/store/re_chunk/src/chunk.rs:1305-1328 | crates/store/re_chunk/src/chunk.rs:1334-1357 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 21 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 50+ corresponding lines) · ×1
Edited copies of one member (4 members, 50+ corresponding lines) rerun_py/rerun_sdk/rerun/sinks.py:122— rerun_py/rerun_sdk/rerun/sinks.py:122-171 | rerun_py/rerun_sdk/rerun/sinks.py:181-242 | rerun_py/rerun_sdk/rerun/sinks.py:251-305 | rerun_py/rerun_sdk/rerun/sinks.py:338-412 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 50 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (6 members, 21+ corresponding lines) · ×1
Edited copies of one member (6 members, 21+ corresponding lines) crates/data_flow/re_lenses/src/semantic/foxglove/compressed_image.rs:11— crates/data_flow/re_lenses/src/semantic/foxglove/compressed_image.rs:11-33 | crates/data_flow/re_lenses/src/semantic/foxglove/compressed_video.rs:11-31 | crates/data_flow/re_lenses/src/semantic/foxglove/location_fix.rs:15-37 | crates/data_flow/re_lenses/src/semantic/foxglove/pose_in_frame.rs:11-33 | crates/data_flow/re_lenses/src/semantic/foxglove/poses_in_frame.rs:11-33 | crates/data_flow/re_lenses/src/semantic/foxglove/raw_image.rs:13-33 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 21 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (7 members, 14+ corresponding lines) · ×1
Edited copies of one member (7 members, 14+ corresponding lines) rerun_py/src/catalog/dataset_entry.rs:381— rerun_py/src/catalog/dataset_entry.rs:381-394 | rerun_py/src/catalog/dataset_entry.rs:403-417 | rerun_py/src/catalog/dataset_entry.rs:429-443 | rerun_py/src/catalog/dataset_entry.rs:497-511 | rerun_py/src/catalog/dataset_entry.rs:521-538 | rerun_py/src/catalog/table_entry.rs:100-113 | rerun_py/src/catalog/table_entry.rs:125-141 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 7 times and the copies 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/data_flow/re_importer/src/importer_archetype.rs:218— crates/data_flow/re_importer/src/importer_archetype.rs:218-237 | crates/data_flow/re_importer/src/importer_archetype.rs:345-362 | crates/data_flow/re_importer/src/importer_archetype.rs:417-435 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 16+ corresponding lines) · ×1
Edited copies of one member (4 members, 16+ corresponding lines) crates/data_flow/re_lenses/src/semantic/ros2msg/fluid_pressure.rs:6— crates/data_flow/re_lenses/src/semantic/ros2msg/fluid_pressure.rs:6-25 | crates/data_flow/re_lenses/src/semantic/ros2msg/illuminance.rs:6-25 | crates/data_flow/re_lenses/src/semantic/ros2msg/relative_humidity.rs:8-23 | crates/data_flow/re_lenses/src/semantic/ros2msg/temperature.rs:6-25 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (8 members, 7+ corresponding lines) · ×1
Edited copies of one member (8 members, 7+ corresponding lines) crates/viewer_support/re_component_ui/src/encoding_uis/bool_toggle.rs:8— crates/viewer_support/re_component_ui/src/encoding_uis/bool_toggle.rs:8-14 | crates/viewer_support/re_component_ui/src/encoding_uis/float_drag.rs:23-29 | crates/viewer_support/re_component_ui/src/encoding_uis/float_drag.rs:45-51 | crates/viewer_support/re_component_ui/src/encoding_uis/float_drag.rs:95-101 | crates/viewer_support/re_component_ui/src/encoding_uis/float_drag.rs:125-131 | crates/viewer_support/re_component_ui/src/encoding_uis/float_drag.rs:138-144 | crates/viewer_support/re_component_ui/src/encoding_uis/int_drag.rs:15-21 | crates/viewer_support/re_component_ui/src/encoding_uis/int_drag.rs:29-35 — These 8 members are one piece of code written 8 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 8 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 19+ corresponding lines) · ×1
Edited copies of one member (3 members, 19+ corresponding lines) crates/ui_tools/re_renderer/src/renderer/gaussian_splat.rs:630— crates/ui_tools/re_renderer/src/renderer/gaussian_splat.rs:630-648 | crates/ui_tools/re_renderer/src/renderer/lines.rs:600-621 | crates/ui_tools/re_renderer/src/renderer/point_cloud.rs:627-647 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 19 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 9+ corresponding lines) · ×1
Edited copies of one member (3 members, 9+ corresponding lines) crates/store/re_chunk_store/src/subscribers.rs:195— crates/store/re_chunk_store/src/subscribers.rs:195-204 | crates/store/re_chunk_store/src/subscribers.rs:217-225 | crates/store/re_chunk_store/src/subscribers.rs:238-246 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 11+ corresponding lines) · ×1
Edited copies of one member (3 members, 11+ corresponding lines) crates/store/re_protos/src/lib.rs:403— crates/store/re_protos/src/lib.rs:403-413 | crates/store/re_sorbet/src/chunk_schema.rs:144-157 | crates/store/re_sorbet/src/sorbet_schema.rs:161-174 — 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 copy of a member (4 corresponding lines) · ×1
Edited copy of a member (4 corresponding lines) rerun_py/src/catalog/dataset_entry.rs:168— rerun_py/src/catalog/dataset_entry.rs:168-171 | rerun_py/src/catalog/table_entry.rs:59-62 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 4+ corresponding lines) · ×1
Edited copies of one member (3 members, 4+ corresponding lines) crates/store/re_chunk/src/batcher.rs:440— crates/store/re_chunk/src/batcher.rs:440-443 | crates/store/re_log_encoding/src/rrd/file_sink.rs:53-56 | crates/top/re_sdk/src/recording_stream.rs:1156-1159 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Duplicated block (41–42 lines × 2) crates/viewer_support/re_view/src/query.rs:333— crates/viewer_support/re_view/src/query.rs:333-374 | crates/viewer_support/re_view/src/query.rs:525-565 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/viewer_support/re_view/src/query.rs:333` 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 (39 lines × 2) crates/panels/re_blueprint_tree/src/blueprint_tree.rs:758— crates/panels/re_blueprint_tree/src/blueprint_tree.rs:758-796 | crates/panels/re_time_panel/src/time_panel.rs:1305-1343 — 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/panels/re_blueprint_tree/src/blueprint_tree.rs:758` 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 (30 lines × 2) crates/data_flow/re_importer/src/importer_urdf/mod.rs:78— crates/data_flow/re_importer/src/importer_urdf/mod.rs:78-107 | crates/data_flow/re_importer/src/importer_urdf/mod.rs:123-152 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/data_flow/re_importer/src/importer_urdf/mod.rs:78` 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 (25–27 lines × 2) crates/ui_tools/re_renderer/src/renderer/gaussian_splat.rs:845— crates/ui_tools/re_renderer/src/renderer/gaussian_splat.rs:845-871 | crates/ui_tools/re_renderer/src/renderer/point_cloud.rs:884-908 — before extracting anything, compare `crates/ui_tools/re_renderer/src/renderer/gaussian_splat.rs` and `crates/ui_tools/re_renderer/src/renderer/point_cloud.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 207 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/ui_tools/re_renderer/src/renderer/gaussian_splat.rs:845` 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 (24–26 lines × 2) crates/viewer_support/re_view/src/blueprint_resolved_results.rs:162— crates/viewer_support/re_view/src/blueprint_resolved_results.rs:162-185 | crates/viewer_support/re_view/src/blueprint_resolved_results.rs:337-362 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/viewer_support/re_view/src/blueprint_resolved_results.rs:162` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19–24 lines × 3) crates/ui_tools/re_renderer/src/renderer/depth_cloud.rs:454— crates/ui_tools/re_renderer/src/renderer/depth_cloud.rs:454-472 | crates/ui_tools/re_renderer/src/renderer/lines.rs:722-743 | crates/ui_tools/re_renderer/src/renderer/point_cloud.rs:777-800 — before extracting anything, compare `crates/ui_tools/re_renderer/src/renderer/depth_cloud.rs` and `crates/ui_tools/re_renderer/src/renderer/point_cloud.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 57 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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/ui_tools/re_renderer/src/renderer/depth_cloud.rs:454` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (15–23 lines × 2) crates/store_app/re_dataframe/src/query.rs:1298— crates/store_app/re_dataframe/src/query.rs:1298-1320 | crates/store_app/re_dataframe/src/query.rs:1771-1785 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/store_app/re_dataframe/src/query.rs:1298` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (20–22 lines × 2) docs/snippets/all/archetypes/clear_recursive.rs:8— docs/snippets/all/archetypes/clear_recursive.rs:8-29 | docs/snippets/all/archetypes/clear_simple.rs:9-28 — 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 `docs/snippets/all/archetypes/clear_recursive.rs:8` 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–21 lines × 2) docs/snippets/all/archetypes/state_configuration.rs:6— docs/snippets/all/archetypes/state_configuration.rs:6-18 | docs/snippets/all/howto/state_timeline.rs:6-26 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `docs/snippets/all/archetypes/state_configuration.rs:6` 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–20 lines × 2) crates/panels/re_selection_panel/src/view_entity_picker.rs:360— crates/panels/re_selection_panel/src/view_entity_picker.rs:360-377 | crates/panels/re_time_panel/src/streams_tree_data.rs:137-156 — before extracting anything, compare `crates/panels/re_selection_panel/src/view_entity_picker.rs` and `crates/panels/re_time_panel/src/streams_tree_data.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 66 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/panels/re_selection_panel/src/view_entity_picker.rs:360` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `crates/panels/re_time_panel/src/streams_tree_data.rs:157` calls `is_root` and `crates/panels/re_selection_panel/src/view_entity_picker.rs:378` 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 (19–20 lines × 2) crates/store/re_sorbet/src/migrations/v0_1_1__to__v0_1_2.rs:80— crates/store/re_sorbet/src/migrations/v0_1_1__to__v0_1_2.rs:80-99 | crates/store/re_sorbet/src/migrations/v0_1_2__to__v0_1_3.rs:53-71 — 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/store/re_sorbet/src/migrations/v0_1_1__to__v0_1_2.rs:80` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (16–20 lines × 2) crates/ui_tools/re_renderer/src/renderer/gaussian_splat.rs:204— crates/ui_tools/re_renderer/src/renderer/gaussian_splat.rs:204-219 | crates/ui_tools/re_renderer/src/renderer/point_cloud.rs:195-214 — before extracting anything, compare `crates/ui_tools/re_renderer/src/renderer/gaussian_splat.rs` and `crates/ui_tools/re_renderer/src/renderer/point_cloud.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 207 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/ui_tools/re_renderer/src/renderer/gaussian_splat.rs:204` 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–20 lines × 2) crates/viewer_support/re_viewer_context/src/cache/video_stream_cache/mod.rs:1164— crates/viewer_support/re_viewer_context/src/cache/video_stream_cache/mod.rs:1164-1183 | crates/viewer_support/re_viewer_context/src/cache/video_stream_cache/mod.rs:1494-1510 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/viewer_support/re_viewer_context/src/cache/video_stream_cache/mod.rs:1164` 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 (19 lines × 2) crates/viewer_support/re_viewer_context/src/blueprint_helpers.rs:325— crates/viewer_support/re_viewer_context/src/blueprint_helpers.rs:325-343 | crates/viewer_support/re_viewer_context/src/blueprint_helpers.rs:370-388 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/viewer_support/re_viewer_context/src/blueprint_helpers.rs:325` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18 lines × 3) crates/utils/re_perf_telemetry/src/prometheus.rs:658— crates/utils/re_perf_telemetry/src/prometheus.rs:658-675 | crates/utils/re_perf_telemetry/src/prometheus.rs:695-712 | crates/utils/re_perf_telemetry/src/prometheus.rs:732-749 — 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/utils/re_perf_telemetry/src/prometheus.rs:658` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16–17 lines × 4) crates/views/re_view_spatial/src/visualizers/boxes3d.rs:217— crates/views/re_view_spatial/src/visualizers/boxes3d.rs:217-232 | crates/views/re_view_spatial/src/visualizers/capsules3d.rs:241-257 | crates/views/re_view_spatial/src/visualizers/cylinders3d.rs:237-253 | crates/views/re_view_spatial/src/visualizers/ellipsoids.rs:224-239 — before extracting anything, compare `crates/views/re_view_spatial/src/visualizers/boxes3d.rs` and `crates/views/re_view_spatial/src/visualizers/ellipsoids.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 53 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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/views/re_view_spatial/src/visualizers/boxes3d.rs:217` 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/views/re_view_spatial/src/visualizers/ellipsoids.rs:223` calls `unwrap_or_default` and `crates/views/re_view_spatial/src/visualizers/capsules3d.rs:241` 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 (14–17 lines × 3) crates/views/re_view_time_series/src/line_visualizer_system.rs:317— crates/views/re_view_time_series/src/line_visualizer_system.rs:317-330 | crates/views/re_view_time_series/src/line_visualizer_system.rs:386-399 | crates/views/re_view_time_series/src/point_visualizer_system.rs:158-174 — before extracting anything, compare `crates/views/re_view_time_series/src/line_visualizer_system.rs` and `crates/views/re_view_time_series/src/point_visualizer_system.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 73 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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/views/re_view_time_series/src/line_visualizer_system.rs:317` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16–17 lines × 2) crates/utils/re_video/src/decode/mod.rs:286— crates/utils/re_video/src/decode/mod.rs:286-302 | crates/utils/re_video/src/decode/mod.rs:352-367 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/utils/re_video/src/decode/mod.rs:286` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (13–17 lines × 2) crates/viewer_support/re_view/src/annotation_context_resolver.rs:303— crates/viewer_support/re_view/src/annotation_context_resolver.rs:303-319 | crates/viewer_support/re_view/src/annotation_context_resolver.rs:370-382 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/viewer_support/re_view/src/annotation_context_resolver.rs:303` it does not close everything it opens, so those exact lines 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/panels/re_time_panel/src/recursive_chunks_per_timeline_subscriber.rs:180— crates/panels/re_time_panel/src/recursive_chunks_per_timeline_subscriber.rs:180-195 | crates/viewer_support/re_viewer_context/src/annotations.rs:359-371 — 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/panels/re_time_panel/src/recursive_chunks_per_timeline_subscriber.rs:180` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15–16 lines × 2) crates/store/re_log_types/src/path/entity_path_part.rs:60— crates/store/re_log_types/src/path/entity_path_part.rs:60-75 | crates/store/re_log_types/src/path/entity_path_part.rs:122-136 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/store/re_log_types/src/path/entity_path_part.rs:60` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12–16 lines × 2) crates/store_app/re_datafusion/src/pipeline_budget/mod.rs:1499— crates/store_app/re_datafusion/src/pipeline_budget/mod.rs:1499-1514 | crates/store_app/re_datafusion/src/pipeline_budget/mod.rs:1530-1541 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/store_app/re_datafusion/src/pipeline_budget/mod.rs:1499` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (10–16 lines × 2) crates/views/re_view_time_series/src/line_series_loader.rs:349— crates/views/re_view_time_series/src/line_series_loader.rs:349-364 | crates/views/re_view_time_series/src/point_visualizer_system.rs:446-455 — before extracting anything, compare `crates/views/re_view_time_series/src/line_series_loader.rs` and `crates/views/re_view_time_series/src/point_visualizer_system.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 50 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/views/re_view_time_series/src/line_series_loader.rs:349` 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–15 lines × 5) crates/top/re_viewer/data/quick_start_guides/quick_start_connect.rs:12— crates/top/re_viewer/data/quick_start_guides/quick_start_connect.rs:12-24 | crates/top/re_viewer/data/quick_start_guides/quick_start_spawn.rs:11-25 | docs/snippets/all/howto/set_sinks.rs:22-34 | docs/snippets/all/quick_start/quick_start_connect.rs:13-25 | docs/snippets/all/quick_start/quick_start_spawn.rs:13-27 — before extracting anything, compare `crates/top/re_viewer/data/quick_start_guides/quick_start_connect.rs` and `docs/snippets/all/howto/set_sinks.rs` as WHOLE FILES: 83% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/top/re_viewer/data/quick_start_guides/quick_start_connect.rs:12` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14–15 lines × 4) crates/store/re_chunk/src/iter.rs:479— crates/store/re_chunk/src/iter.rs:479-492 | crates/store/re_chunk/src/iter.rs:567-581 | crates/store/re_chunk/src/iter.rs:640-653 | crates/store/re_chunk/src/iter.rs:795-809 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/store/re_chunk/src/iter.rs:479` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (15 lines × 4) crates/top/re_viewer/src/app/route_ui.rs:516— crates/top/re_viewer/src/app/route_ui.rs:516-530 | crates/top/re_viewer/src/app/route_ui.rs:558-572 | crates/top/re_viewer/src/app/route_ui.rs:624-638 | crates/top/re_viewer/src/app/route_ui.rs:658-672 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/top/re_viewer/src/app/route_ui.rs:516` it does not close everything it opens, so those exact lines 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–15 lines × 4) crates/views/re_view_spatial/src/visualizers/arrows2d.rs:239— crates/views/re_view_spatial/src/visualizers/arrows2d.rs:239-246 | crates/views/re_view_spatial/src/visualizers/arrows3d.rs:243-250 | crates/views/re_view_spatial/src/visualizers/boxes2d.rs:245-258 | crates/views/re_view_spatial/src/visualizers/ellipses2d.rs:364-378 — before extracting anything, compare `crates/views/re_view_spatial/src/visualizers/arrows2d.rs` and `crates/views/re_view_spatial/src/visualizers/arrows3d.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 85 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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/views/re_view_spatial/src/visualizers/arrows2d.rs:239` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `crates/views/re_view_spatial/src/visualizers/ellipses2d.rs:379` calls `as_ref` and `crates/views/re_view_spatial/src/visualizers/boxes2d.rs:259` 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 (14–15 lines × 2) crates/views/re_view_graph/src/layout/provider.rs:130— crates/views/re_view_graph/src/layout/provider.rs:130-144 | crates/views/re_view_graph/src/layout/provider.rs:170-183 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/views/re_view_graph/src/layout/provider.rs:130` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12–15 lines × 2) rerun_py/src/python_bridge.rs:1414— rerun_py/src/python_bridge.rs:1414-1428 | rerun_py/src/python_bridge.rs:1631-1642 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `rerun_py/src/python_bridge.rs:1414` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (13–14 lines × 5) crates/ui_tools/re_renderer/src/renderer/depth_cloud.rs:485— crates/ui_tools/re_renderer/src/renderer/depth_cloud.rs:485-498 | crates/ui_tools/re_renderer/src/renderer/gaussian_splat.rs:801-813 | crates/ui_tools/re_renderer/src/renderer/point_cloud.rs:830-843 | crates/ui_tools/re_renderer/src/renderer/volume.rs:322-334 | crates/ui_tools/re_renderer/src/renderer/voxel_grid.rs:400-412 — before extracting anything, compare `crates/ui_tools/re_renderer/src/renderer/depth_cloud.rs` and `crates/ui_tools/re_renderer/src/renderer/point_cloud.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 57 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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/ui_tools/re_renderer/src/renderer/depth_cloud.rs:485` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (14 lines × 4) docs/snippets/all/descriptors/descr_builtin_archetype.rs:36— docs/snippets/all/descriptors/descr_builtin_archetype.rs:36-49 | docs/snippets/all/descriptors/descr_builtin_component.rs:46-59 | docs/snippets/all/descriptors/descr_custom_archetype.rs:81-94 | docs/snippets/all/descriptors/descr_custom_component.rs:41-54 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 4 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `docs/snippets/all/descriptors/descr_builtin_archetype.rs:36` it does not close everything it opens, so those exact lines 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/views/re_view_spatial/src/visualizers/arrows2d.rs:199— crates/views/re_view_spatial/src/visualizers/arrows2d.rs:199-212 | crates/views/re_view_spatial/src/visualizers/arrows3d.rs:203-216 | crates/views/re_view_spatial/src/visualizers/points2d.rs:249-261 — before extracting anything, compare `crates/views/re_view_spatial/src/visualizers/arrows2d.rs` and `crates/views/re_view_spatial/src/visualizers/arrows3d.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 85 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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/views/re_view_spatial/src/visualizers/arrows2d.rs:199` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10–14 lines × 2) crates/store_app/re_tf/src/transform_resolution_cache/cached_transforms_for_timeline.rs:438— crates/store_app/re_tf/src/transform_resolution_cache/cached_transforms_for_timeline.rs:438-447 | crates/store_app/re_tf/src/transform_resolution_cache/cached_transforms_for_timeline.rs:464-477 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/store_app/re_tf/src/transform_resolution_cache/cached_transforms_for_timeline.rs:438` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (8–14 lines × 2) crates/views/re_view_spatial/src/visualizers/boxes3d.rs:150— crates/views/re_view_spatial/src/visualizers/boxes3d.rs:150-157 | crates/views/re_view_spatial/src/visualizers/ellipsoids.rs:159-172 — before extracting anything, compare `crates/views/re_view_spatial/src/visualizers/boxes3d.rs` and `crates/views/re_view_spatial/src/visualizers/ellipsoids.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 53 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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/views/re_view_spatial/src/visualizers/boxes3d.rs:150` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (13 lines × 4) crates/views/re_view_spatial/src/visualizers/arrows2d.rs:245— crates/views/re_view_spatial/src/visualizers/arrows2d.rs:245-257 | crates/views/re_view_spatial/src/visualizers/arrows3d.rs:249-261 | crates/views/re_view_spatial/src/visualizers/lines2d.rs:239-251 | crates/views/re_view_spatial/src/visualizers/lines3d.rs:250-262 — before extracting anything, compare `crates/views/re_view_spatial/src/visualizers/arrows2d.rs` and `crates/views/re_view_spatial/src/visualizers/arrows3d.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 85 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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/views/re_view_spatial/src/visualizers/arrows2d.rs:245` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12–13 lines × 4) crates/views/re_view_spatial/src/visualizers/boxes2d.rs:205— crates/views/re_view_spatial/src/visualizers/boxes2d.rs:205-217 | crates/views/re_view_spatial/src/visualizers/boxes3d.rs:145-156 | crates/views/re_view_spatial/src/visualizers/ellipses2d.rs:323-334 | crates/views/re_view_spatial/src/visualizers/ellipsoids.rs:153-165 — before extracting anything, compare `crates/views/re_view_spatial/src/visualizers/boxes2d.rs` and `crates/views/re_view_spatial/src/visualizers/ellipses2d.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 97 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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/views/re_view_spatial/src/visualizers/boxes2d.rs:205` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9–13 lines × 2) crates/viewer_support/re_data_ui/src/video_ui.rs:837— crates/viewer_support/re_data_ui/src/video_ui.rs:837-849 | crates/viewer_support/re_data_ui/src/video_ui.rs:873-881 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (11–13 lines × 2) docs/snippets/all/archetypes/state_change.rs:7— docs/snippets/all/archetypes/state_change.rs:7-17 | docs/snippets/all/archetypes/state_configuration.rs:15-27 — 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 `docs/snippets/all/archetypes/state_change.rs:7` 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–12 lines × 6) crates/utils/re_perf_telemetry/src/prometheus.rs:209— crates/utils/re_perf_telemetry/src/prometheus.rs:209-220 | crates/utils/re_perf_telemetry/src/prometheus.rs:239-248 | crates/utils/re_perf_telemetry/src/prometheus.rs:266-276 | crates/utils/re_perf_telemetry/src/prometheus.rs:384-395 | crates/utils/re_perf_telemetry/src/prometheus.rs:414-423 | crates/utils/re_perf_telemetry/src/prometheus.rs:441-451 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/utils/re_perf_telemetry/src/prometheus.rs:209` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (8–12 lines × 2) crates/utils/re_perf_telemetry/src/prometheus.rs:297— crates/utils/re_perf_telemetry/src/prometheus.rs:297-308 | crates/utils/re_perf_telemetry/src/prometheus.rs:359-366 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/utils/re_perf_telemetry/src/prometheus.rs:297` 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 (4–12 lines × 3) docs/snippets/all/archetypes/scalars_multiple_plots.rs:38— docs/snippets/all/archetypes/scalars_multiple_plots.rs:38-49 | docs/snippets/all/archetypes/series_lines_style.rs:26-37 | docs/snippets/all/archetypes/series_points_style.rs:26-29 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `docs/snippets/all/archetypes/scalars_multiple_plots.rs:38` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (10–11 lines × 5) crates/ui_tools/re_renderer/src/renderer/debug_overlay.rs:248— crates/ui_tools/re_renderer/src/renderer/debug_overlay.rs:248-257 | crates/ui_tools/re_renderer/src/renderer/generic_skybox.rs:177-186 | crates/ui_tools/re_renderer/src/renderer/world_grid.rs:201-210 | crates/ui_tools/re_renderer/src/resource_managers/bayer_converter.rs:273-283 | crates/ui_tools/re_renderer/src/resource_managers/yuv_converter.rs:580-590 — before extracting anything, compare `crates/ui_tools/re_renderer/src/resource_managers/bayer_converter.rs` and `crates/ui_tools/re_renderer/src/resource_managers/yuv_converter.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 99 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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/ui_tools/re_renderer/src/renderer/generic_skybox.rs:177` 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–11 lines × 3) crates/data_flow/re_grpc_client/src/lib.rs:57— crates/data_flow/re_grpc_client/src/lib.rs:57-67 | crates/data_flow/re_grpc_server/src/lib.rs:139-149 | crates/data_flow/re_redap_client/src/lib.rs:168-177 — 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/data_flow/re_grpc_client/src/lib.rs:57` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `crates/data_flow/re_grpc_client/src/lib.rs:56` calls `code` and `crates/data_flow/re_redap_client/src/lib.rs:163` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (5–10 lines × 3) crates/utils/re_format/src/duration.rs:143— crates/utils/re_format/src/duration.rs:143-147 | crates/utils/re_format/src/duration.rs:149-158 | crates/utils/re_format/src/duration.rs:161-171 — 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/utils/re_format/src/duration.rs:143` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `crates/utils/re_format/src/duration.rs:160` calls `push`, `to_string` and `crates/utils/re_format/src/duration.rs:173` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8–10 lines × 2) crates/viewer_support/re_viewer_context/src/component_ui_registry.rs:212— crates/viewer_support/re_viewer_context/src/component_ui_registry.rs:212-221 | crates/viewer_support/re_viewer_context/src/component_ui_registry.rs:350-357 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/viewer_support/re_viewer_context/src/component_ui_registry.rs:212` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (8 lines × 7) crates/views/re_view_spatial/src/visualizers/arrows2d.rs:205— crates/views/re_view_spatial/src/visualizers/arrows2d.rs:205-213 | crates/views/re_view_spatial/src/visualizers/arrows3d.rs:209-217 | crates/views/re_view_spatial/src/visualizers/boxes2d.rs:211-218 | crates/views/re_view_spatial/src/visualizers/boxes3d.rs:150-157 | crates/views/re_view_spatial/src/visualizers/ellipses2d.rs:328-335 | crates/views/re_view_spatial/src/visualizers/ellipsoids.rs:159-166 | crates/views/re_view_spatial/src/visualizers/points2d.rs:254-262 — before extracting anything, compare `crates/views/re_view_spatial/src/visualizers/arrows2d.rs` and `crates/views/re_view_spatial/src/visualizers/arrows3d.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 85 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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/views/re_view_spatial/src/visualizers/arrows2d.rs:205` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (3–7 lines × 3) crates/store/re_chunk/src/iter.rs:661— crates/store/re_chunk/src/iter.rs:661-663 | crates/store/re_chunk/src/iter.rs:683-689 | crates/store/re_chunk/src/iter.rs:697-703 — 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/store/re_chunk/src/iter.rs:683` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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–7 lines × 2) crates/viewer_support/re_viewer_context/src/viewer_url.rs:963— crates/viewer_support/re_viewer_context/src/viewer_url.rs:963-968 | crates/viewer_support/re_viewer_context/src/viewer_url.rs:1016-1022 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/viewer_support/re_viewer_context/src/viewer_url.rs:963` it does not close everything it opens, so those 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/viewer_support/re_viewer_context/src/viewer_url.rs:1023` calls `Some` and `crates/viewer_support/re_viewer_context/src/viewer_url.rs:969` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (5 lines × 5) crates/store/re_uri/src/endpoints/catalog.rs:47— crates/store/re_uri/src/endpoints/catalog.rs:47-51 | crates/store/re_uri/src/endpoints/dataset.rs:231-235 | crates/store/re_uri/src/endpoints/folder.rs:66-70 | crates/store/re_uri/src/endpoints/proxy.rs:46-50 | crates/store/re_uri/src/redap_uri.rs:166-170 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times.
Duplicated block (7 lines × 7) rerun_py/src/chunk_stream/engine.rs:666— rerun_py/src/chunk_stream/engine.rs:666-672 | rerun_py/src/chunk_stream/hdf5_reader.rs:276-282 | rerun_py/src/chunk_stream/lerobot_reader.rs:203-209 | rerun_py/src/chunk_stream/mcap_reader.rs:528-534 | rerun_py/src/chunk_stream/mp4_reader.rs:239-245 | rerun_py/src/chunk_stream/parquet_reader.rs:239-245 | rerun_py/src/chunk_stream/urdf_tree_stream.rs:66-72 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 7 call sites, so a change lands once.
Duplicated block (57 lines × 2) crates/ui_tools/re_renderer/src/resource_managers/bayer_converter.rs:193— crates/ui_tools/re_renderer/src/resource_managers/bayer_converter.rs:193-249 | crates/ui_tools/re_renderer/src/resource_managers/yuv_converter.rs:500-556 — before extracting anything, compare `crates/ui_tools/re_renderer/src/resource_managers/bayer_converter.rs` and `crates/ui_tools/re_renderer/src/resource_managers/yuv_converter.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 99 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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/ui_tools/re_renderer/src/resource_managers/bayer_converter.rs:193` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (55 lines × 2) rerun_py/rerun_sdk/rerun/archetypes/capsules3d_ext.py:29— rerun_py/rerun_sdk/rerun/archetypes/capsules3d_ext.py:29-83 | rerun_py/rerun_sdk/rerun/archetypes/cylinders3d_ext.py:29-83 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (49–55 lines × 2) rerun_py/rerun_sdk/rerun/sinks.py:181— rerun_py/rerun_sdk/rerun/sinks.py:181-235 | rerun_py/rerun_sdk/rerun/sinks.py:251-299 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (52–53 lines × 2) rerun_py/rerun_sdk/rerun/archetypes/points2d_ext.py:26— rerun_py/rerun_sdk/rerun/archetypes/points2d_ext.py:26-78 | rerun_py/rerun_sdk/rerun/archetypes/points3d_ext.py:26-77 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (37–43 lines × 3) rerun_py/rerun_sdk/rerun/archetypes/asset3d_ext.py:23— rerun_py/rerun_sdk/rerun/archetypes/asset3d_ext.py:23-65 | rerun_py/rerun_sdk/rerun/archetypes/asset_audio_ext.py:22-60 | rerun_py/rerun_sdk/rerun/archetypes/asset_video_ext.py:27-63 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (27–30 lines × 2) rerun_py/rerun_sdk/rerun/blueprint/api.py:785— rerun_py/rerun_sdk/rerun/blueprint/api.py:785-814 | rerun_py/rerun_sdk/rerun/blueprint/table.py:293-319 — 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–10 lines × 3) docs/snippets/all/tutorials/dna.py:50— docs/snippets/all/tutorials/dna.py:50-56 | docs/snippets/all/tutorials/dna.py:66-75 | examples/python/dna/dna.py:45-50 — 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 `docs/snippets/all/tutorials/dna.py:66` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `docs/snippets/all/tutorials/dna.py:76` calls `bounce_lerp` and `docs/snippets/all/tutorials/dna.py:56` 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 (43 lines × 2) rerun_py/rerun_sdk/rerun/archetypes/arrows2d_ext.py:26— rerun_py/rerun_sdk/rerun/archetypes/arrows2d_ext.py:26-73 | rerun_py/rerun_sdk/rerun/archetypes/ellipses2d_ext.py:26-68 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 4) rerun_py/rerun_sdk/rerun/archetypes/depth_image_ext.py:43— rerun_py/rerun_sdk/rerun/archetypes/depth_image_ext.py:43-50 | rerun_py/rerun_sdk/rerun/archetypes/mesh3d_ext.py:34-41 | rerun_py/rerun_sdk/rerun/archetypes/segmentation_image_ext.py:29-36 | rerun_py/rerun_sdk/rerun/encodings/tensor_data_ext.py:36-43 — before extracting anything, compare `rerun_py/rerun_sdk/rerun/archetypes/depth_image_ext.py` and `rerun_py/rerun_sdk/rerun/archetypes/segmentation_image_ext.py` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 43 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note first that the copies are not typed on the same thing: the declarations holding them bind `tensor` to `ImageLike` in one and `TensorLike` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication· Edited copies of one member (8 members, 11+ corresponding lines) · ×1
Edited copies of one member (8 members, 11+ corresponding lines) scripts/generate_view_coordinate_defs.py:166— scripts/generate_view_coordinate_defs.py:166-177 | scripts/generate_view_coordinate_defs.py:185-195 | scripts/generate_view_coordinate_defs.py:210-221 | scripts/generate_view_coordinate_defs.py:229-239 | scripts/generate_view_coordinate_defs.py:253-263 | scripts/generate_view_coordinate_defs.py:275-285 | scripts/generate_view_coordinate_defs.py:299-309 | scripts/generate_view_coordinate_defs.py:321-331 — These 8 members are one piece of code written 8 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 8 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 2+ corresponding lines) · ×1
Edited copies of one member (4 members, 2+ corresponding lines) scripts/ci/build_and_upload_rerun_notebook.py:26— scripts/ci/build_and_upload_rerun_notebook.py:26-27 | scripts/ci/build_and_upload_wheels.py:31-32 | scripts/ci/publish_wheels.py:33-34 | scripts/ci/update_rerun_notebook_version.py:29-30 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 2 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
Duplicated block (38 lines × 2) crates/ui_tools/re_renderer_examples/depth_cloud.rs:110— crates/ui_tools/re_renderer_examples/depth_cloud.rs:110-147 | crates/ui_tools/re_renderer_examples/depth_cloud.rs:192-229 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/ui_tools/re_renderer_examples/depth_cloud.rs:110` 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–18 lines × 2) examples/python/face_tracking/face_tracking.py:438— examples/python/face_tracking/face_tracking.py:438-455 | examples/python/gesture_detection/gesture_detection.py:277-293 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `examples/python/face_tracking/face_tracking.py:438` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `examples/python/gesture_detection/gesture_detection.py:276` calls `add_argument` and `examples/python/face_tracking/face_tracking.py:438` 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 (15 lines × 3) examples/python/structure_from_motion/structure_from_motion/read_write_model.py:106— examples/python/structure_from_motion/structure_from_motion/read_write_model.py:106-120 | examples/python/structure_from_motion/structure_from_motion/read_write_model.py:191-205 | examples/python/structure_from_motion/structure_from_motion/read_write_model.py:313-327 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11–14 lines × 2) examples/python/live_depth_sensor/live_depth_sensor.py:27— examples/python/live_depth_sensor/live_depth_sensor.py:27-37 | examples/python/live_depth_sensor/live_depth_sensor.py:51-64 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `examples/python/live_depth_sensor/live_depth_sensor.py:51` 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–11 lines × 2) examples/python/imu_signals/imu_signals.py:94— examples/python/imu_signals/imu_signals.py:94-102 | examples/python/imu_signals/imu_signals.py:153-163 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `examples/python/imu_signals/imu_signals.py:94` 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 (9 lines × 7) examples/python/face_tracking/face_tracking.py:328— examples/python/face_tracking/face_tracking.py:328-336 | examples/python/gesture_detection/gesture_detection.py:176-184 | examples/python/lidar/lidar/download_dataset.py:32-40 | examples/python/nuscenes_dataset/nuscenes_dataset/download_dataset.py:32-40 | examples/python/ocr/ocr.py:451-459 | examples/python/open_photogrammetry_format/open_photogrammetry_format.py:62-70 | scripts/upload_image.py:365-373 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 7 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 7 times.
Sync-over-async blocking crates/utils/re_auth/src/cli.rs:51— `login` is async and calls thread::sleep — a blocking call inside async code stalls the executor thread, and every task scheduled on it for as long as it runs.
Duplicated block (13 lines × 2 locations) rerun_js/web-viewer/index.ts:2036— rerun_js/web-viewer/index.ts:2036 · rerun_js/web-viewer/index.ts:2051 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2 locations) rerun_js/web-viewer/index.ts:1831— rerun_js/web-viewer/index.ts:1831 · rerun_js/web-viewer/index.ts:1850 — 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.
Complex function collectTargets (cyclomatic 17, cognitive 20) rerun_js/web-viewer/typedoc-used-by.mjs:97— collectTargets has cyclomatic complexity 17 and cognitive complexity 20; 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 start (cyclomatic 14, cognitive 13) rerun_js/web-viewer/index.ts:1644— start has cyclomatic complexity 14 and cognitive complexity 13; 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 closeTargetOf (cyclomatic 13, cognitive 9) rerun_js/web-viewer/index.ts:842— closeTargetOf has cyclomatic complexity 13 and cognitive complexity 9; 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 (top-level) (cyclomatic 12, cognitive 24) rerun_js/scripts/version.mjs:4— (top-level) has cyclomatic complexity 12 and cognitive complexity 24; 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.
R3 · Large Files· rerun_js/web-viewer/index.ts · ×1
rerun_js/web-viewer/index.ts: 2719 lines of code rerun_js/web-viewer/index.ts:1— rerun_js/web-viewer/index.ts has 2719 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
Unused dependency 'dts-buddy' — Declared in rerun_js/web-viewer/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.
Third-party script without Subresource Integrity scripts/ci/templates/benchmark.html:111— `https://cdn.jsdelivr.net/npm/chart.js@4.4.0/dist/chart.umd.min.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session.
Blocking `thread::sleep` inside an `async` body crates/utils/re_auth/src/cli.rs:92— This `async` body is polled on an executor's worker thread, and `std::thread::sleep` blocks that thread: for the whole delay no other task scheduled on it makes progress — the Rust form of blocking on a task. Use `tokio::time::sleep(…).await` (or the runtime's own timer), which suspends only this task. Where the blocking work is not a sleep but a synchronous call that cannot be made async, move it off the executor with `tokio::task::spawn_blocking(…).await`.
Orphaned file crates/store/re_log_types/src/vec_deque_ext.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 rerun_py/rerun_sdk/rerun/encodings/tensor_data_ext.py: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/utils/re_perf_telemetry/src/args.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/viewer_support/re_viewer_context/src/blueprint_id.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 rerun_py/rerun_sdk/rerun/blueprint/containers.py: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 rerun_py/rerun_sdk/rerun/encodings/class_description_ext.py: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/top/re_sdk/src/blueprint/panel.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/store/re_log_encoding/src/rrd/log_msg.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/store/re_sdk_types/src/encodings/image_format_ext.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 rerun_pixi_env/src/rerun_pixi_env/__init__.py: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/ui_tools/re_renderer/src/file_system.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/store/re_sdk_types/src/view_coordinates.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/top/rerun/src/demo_util.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/store/re_sdk_types/src/archetypes/capsules3d_ext.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/store/re_log_encoding/src/rrd/decoder/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/store_app/re_query/src/cache_stats.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 scripts/ci/uv_install_wheel.py: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 rerun_py/rerun_sdk/rerun/archetypes/ellipsoids3d_ext.py: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/store/re_sdk_types/src/encodings/vec3d_ext.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/store_app/re_entity_db/src/versioned_instance_path.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/store/re_sdk_types/src/encodings/vec4d_ext.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 rerun_py/rerun_sdk/rerun/archetypes/capsules3d_ext.py: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 rerun_py/rerun_sdk/rerun/archetypes/points2d_ext.py: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 rerun_py/rerun_sdk/rerun/archetypes/points3d_ext.py: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/store_app/re_query/src/range_zip/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.
Interpolated log message defeats structured logging rerun_py/rerun_sdk/rerun/catalog/_catalog_client.py:181— `warning` at line 181 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.warning("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.warning("order moved", order_id=order_id, status=status)` with structlog.
Interpolated log message defeats structured logging rerun_notebook/src/rerun_notebook/__init__.py:272— `warning` at line 272 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.warning("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.warning("order moved", order_id=order_id, status=status)` with structlog.
Interpolated log message defeats structured logging rerun_py/src/trace_context.rs:149— `debug!` at line 149 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 rerun_py/src/trace_context.rs:160— `debug!` at line 160 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 rerun_py/src/tracing_session.rs:136— `info!` at line 136 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 rerun_py/src/catalog/connection_handle.rs:404— `warn!` at line 404 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/utils/re_perf_telemetry/src/metrics_server.rs:49— `error!` at line 49 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/utils/re_perf_telemetry/src/metrics_server.rs:53— `info!` at line 53 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `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/utils/re_perf_telemetry/src/metrics_server.rs:78— `error!` at line 78 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/utils/re_perf_telemetry/src/metrics_server.rs:98— `error!` at line 98 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/utils/re_perf_telemetry/src/telemetry.rs:186— `warn!` at line 186 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/utils/re_perf_telemetry/src/telemetry.rs:310— `warn!` at line 310 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/utils/re_perf_telemetry/src/tracestate.rs:139— `debug!` at line 139 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/utils/re_perf_telemetry/src/tracing_session.rs:329— `info!` at line 329 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `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/store_app/re_server/src/server.rs:101— `error!` at line 101 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/store_app/re_server/src/server.rs:112— `info!` at line 112 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/store_app/re_server/src/server.rs:127— `error!` at line 127 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/store_app/re_server/src/server.rs:175— `error!` at line 175 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/store_app/re_server/src/server.rs:324— `error!` at line 324 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/store_app/re_datafusion/src/dataframe_query_provider/fetch_plan.rs:342— `debug!` at line 342 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/store_app/re_datafusion/src/dataframe_query_provider/fetch_plan.rs:403— `debug!` at line 403 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/data_flow/re_redap_client/src/lib.rs:329— `trace!` at line 329 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(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/data_flow/re_redap_client/src/lib.rs:340— `trace!` at line 340 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: `trace!(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/data_flow/re_redap_client/src/lib.rs:348— `trace!` at line 348 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: `trace!(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/data_flow/re_redap_client/src/lib.rs:357— `trace!` at line 357 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: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Duplicated predicate rerun_js/web-viewer/compat.ts:119— `value === null || typeof value !== "object"` appears character-identically in 2 files — rerun_js/web-viewer/compat.ts, rerun_js/web-viewer/index.ts. 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 skills/rerun-lerobot/scripts/fetch_lerobot_episodes.py:60— `HfApi().dataset_info(repo_id, files_metadata=True).siblings or []` appears character-identically in 2 files — skills/rerun-lerobot/scripts/fetch_lerobot_episodes.py, skills/rerun-lerobot/scripts/find_lerobot_dataset.py. 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 rerun_py/rerun_sdk/rerun/archetypes/points2d_ext.py:64— `class_ids is None and keypoint_ids is not None` appears character-identically in 2 files — rerun_py/rerun_sdk/rerun/archetypes/points2d_ext.py, rerun_py/rerun_sdk/rerun/archetypes/points3d_ext.py. 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 rerun_py/rerun_sdk/rerun/components/geo_line_string_ext.py:55— `isinstance(data[0], Sequence) and len(data[0]) > 0 and isinstance(data[0][0], numbers.Number)` appears character-identically in 3 files — rerun_py/rerun_sdk/rerun/components/geo_line_string_ext.py, rerun_py/rerun_sdk/rerun/components/line_strip2d_ext.py, rerun_py/rerun_sdk/rerun/components/line_strip3d_ext.py. 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 rerun_py/rerun_sdk/rerun/components/geo_line_string_ext.py:64— `isinstance(data[0], np.ndarray) and data[0].shape == (2,)` appears character-identically in 2 files — rerun_py/rerun_sdk/rerun/components/geo_line_string_ext.py, rerun_py/rerun_sdk/rerun/components/line_strip2d_ext.py. 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 skills/investigate-puffin/compare_traces.py:92— `name.startswith(prefix) or data.startswith(prefix)` appears character-identically in 2 files — skills/investigate-puffin/compare_traces.py, skills/investigate-puffin/find_scopes.py. 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/panels/re_selection_panel/src/view_entity_picker.rs:419— `!node_info.is_leaf && !entity_tree.path.is_root()` appears character-identically in 2 files — crates/panels/re_selection_panel/src/view_entity_picker.rs, crates/panels/re_time_panel/src/streams_tree_data.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/views/re_view_time_series/src/line_visualizer_system.rs:186— `!series.visible || series.points.is_empty()` appears character-identically in 2 files — crates/views/re_view_time_series/src/line_visualizer_system.rs, crates/views/re_view_time_series/src/point_visualizer_system.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/views/re_view_spatial/src/visualizers/volume_3d.rs:224— `!voxel_size.is_finite() || !voxel_size.cmpgt(glam::Vec3::ZERO).all()` appears character-identically in 2 files — crates/views/re_view_spatial/src/visualizers/volume_3d.rs, crates/views/re_view_spatial/src/visualizers/voxel_grid_map.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/utils/re_quota_channel/src/async_broadcast_channel.rs:230— `!warned && BLOCKED_WARNING_THRESHOLD < start.elapsed()` appears character-identically in 2 files — crates/utils/re_quota_channel/src/async_broadcast_channel.rs, crates/utils/re_quota_channel/src/sync/mod.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate crates/views/re_view_time_series/src/line_series_loader.rs:188— `all_scalar_chunks.chunks.first() && chunk.is_static()` appears character-identically in 2 files — crates/views/re_view_time_series/src/line_series_loader.rs, crates/views/re_view_time_series/src/point_visualizer_system.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/viewer_support/re_data_ui/src/component_path_ui.rs:39— `any_missing_chunks && ctx.db.can_fetch_chunks_from_redap()` appears character-identically in 2 files — crates/viewer_support/re_data_ui/src/component_path_ui.rs, crates/viewer_support/re_data_ui/src/instance_path_ui.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/top/rerun/src/commands/entrypoint.rs:765— `cfg!(feature = "perf_telemetry") && re_log::env_var_is_truthy("TELEMETRY_ENABLED")` appears character-identically in 2 files — crates/top/rerun/src/commands/entrypoint.rs, rerun_py/src/python_bridge.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/utils/re_video/src/h264.rs:198— `chunk.is_sync && !state.previous_frame_was_idr` appears character-identically in 2 files — crates/utils/re_video/src/h264.rs, crates/utils/re_video/src/h265.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/data_flow/re_lerobot/src/emits.rs:185— `key.as_str() == "task_index" || key.as_str() == "subtask_index"` appears character-identically in 2 files — crates/data_flow/re_lerobot/src/emits.rs, crates/data_flow/re_lerobot/src/parse_v3.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/viewer_support/re_viewer_context/src/gpu_bridge/mod.rs:129— `resolution_in_pixel[0] == 0 || resolution_in_pixel[1] == 0` appears character-identically in 3 files — crates/viewer_support/re_viewer_context/src/gpu_bridge/mod.rs, crates/views/re_view_spatial/src/ui_3d.rs, crates/views/re_view_time_series/src/view_class.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/store/re_sdk_types/src/components/draw_order_ext.rs:33— `self.0.is_nan() && other.0.is_nan() || self.0 == other.0` appears character-identically in 2 files — crates/store/re_sdk_types/src/components/draw_order_ext.rs, crates/ui_tools/re_renderer/src/size.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/views/re_view_spatial/src/visualizers/capsules3d.rs:261— `suspicious_length.is_finite() && suspicious_length > 0.0` appears character-identically in 2 files — crates/views/re_view_spatial/src/visualizers/capsules3d.rs, crates/views/re_view_spatial/src/visualizers/cylinders3d.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, 28 significant file(s) lose their only recent owner: scripts/generate_crate_graph.py, crates/utils/re_quota_channel/src/async_broadcast_channel.rs, crates/utils/re_quota_channel/src/sync/mod.rs, crates/top/re_viewer/src/ui/app_modals.rs, crates/views/re_view_spatial/src/visualizers/gaussian_splats3d.rs, crates/utils/re_audio/src/mixer.rs, crates/store/re_arrow_json/src/arrow_union.rs, crates/top/re_viewer/src/native_menu.rs (+20 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 10 significant file(s) lose their only recent owner: crates/store/re_chunk_optimizer/src/plan.rs, crates/store/re_chunk_optimizer/src/executor/accumulator.rs, crates/data_flow/re_hdf5/src/walk.rs, crates/store/re_chunk_optimizer/src/settings.rs, crates/store/re_chunk_optimizer/src/executor/merge_split.rs, rerun_py/rerun_sdk/rerun/catalog/_dataset_info.py, crates/store/re_chunk_optimizer/src/executor/cut.rs, crates/data_flow/re_hdf5/src/load.rs (+2 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #3 — If anonymized user #3 becomes unavailable, 5 significant file(s) lose their only recent owner: crates/viewer_support/re_view/src/source_selector.rs, crates/viewer_support/re_view/src/annotation_context_resolver.rs, crates/viewer_support/re_view/src/component_mapping_query_plan.rs, crates/store/re_sdk_types/src/transform_frame_id_hash.rs, crates/viewer_support/re_viewport_blueprint/src/test_view_class.rs. Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #4 — If anonymized user #4 becomes unavailable, 5 significant file(s) lose their only recent owner: crates/store_app/re_datafusion/src/pipeline/driver.rs, crates/store_app/re_datafusion/src/dataframe_query_provider/segment_store.rs, crates/store_app/re_datafusion/src/pipeline/window.rs, crates/store_app/re_datafusion/src/pipeline/bridge.rs, crates/store_app/re_datafusion/src/pipeline/config.rs. Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #5 — If anonymized user #5 becomes unavailable, 4 significant file(s) lose their only recent owner: rerun_py/rerun_sdk/rerun/blueprint/_table_filters.py, crates/data_flow/re_importer/src/importer_puffin.rs, crates/store/re_protos/src/v1alpha1/rerun.cloud.v1alpha1.ext.asset_properties.rs, crates/store/re_chunk_store/src/entity_tree.rs. Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #6 — If anonymized user #6 becomes unavailable, 3 significant file(s) lose their only recent owner: crates/data_flow/re_lerobot/src/lenses.rs, crates/data_flow/re_lerobot/src/features.rs, crates/data_flow/re_lerobot/src/error.rs. Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #7 — If anonymized user #7 becomes unavailable, 3 significant file(s) lose their only recent owner: crates/utils/re_web/src/fs.rs, crates/top/re_viewer/src/background_tasks.rs, crates/store/re_lenses_core/src/selector/runtime.rs. Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #8 — If anonymized user #8 becomes unavailable, 3 significant file(s) lose their only recent owner: crates/top/re_viewer/src/ui/dev_panel/transform_cache_ui/mod.rs, crates/top/re_viewer/src/ui/dev_panel/transform_cache_ui/model.rs, crates/top/re_viewer/src/ui/dev_panel/transform_cache_ui/layout.rs. Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #9 — If anonymized user #9 becomes unavailable, 3 significant file(s) lose their only recent owner: crates/store/re_chunk/src/earliest_at.rs, crates/data_flow/re_mp4_reader/src/asset.rs, scripts/ci/check_skills.py. Pair on, review, or document these before any departure.
Silent fallback default on Err crates/ui_tools/re_renderer/src/file_resolver.rs:209— `from_env` turns every `Err` into `Self::default()` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the arm or in the doc comment, and the row stops firing.
Silent fallback default on Err crates/utils/re_tuid/src/lib.rs:345— `nanos_since_epoch` turns every `Err` into `0` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the arm or in the doc comment, and the row stops firing.
Silent fallback default on Err crates/utils/re_video/src/decode/ffmpeg_cli/ffmpeg.rs:850— `download_advice` (in `read_ffmpeg_output`) turns every `Err` into `String::new()` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the arm or in the doc comment, and the row stops firing.
Silent fallback default on Err crates/views/re_view_graph/src/view.rs:70— `on_register` turns every `Err` into `re_sdk_types::blueprint::components::VisualBounds2D::default()` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the arm or in the doc comment, and the row stops firing.
Silent fallback default on Err crates/views/re_view_spatial/src/view_2d.rs:64— `on_register` turns every `Err` into `re_sdk_types::blueprint::components::VisualBounds2D::default()` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the arm or in the doc comment, and the row stops firing.
Silent fallback default on Err crates/views/re_view_spatial/src/view_3d.rs:130— `on_register` turns every `Err` into `1.0.into()` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the arm or in the doc comment, and the row stops firing.
Silent fallback default on Err crates/views/re_view_spatial/src/shared_fallbacks.rs:65— `register_fallbacks` turns every `Err` into `Default::default()` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the arm or in the doc comment, and the row stops firing.
D30 · Dependency Vulnerabilities· Medium advisory (unmaintained) · ×5
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
D30 · Dependency Vulnerabilities· Medium vulnerability · ×2
REDACTED
REDACTED
D16 · Bus Factor· Further sole-owners (lower concentration) · ×1
Further sole-owners (lower concentration) — 5 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (71 single-owned of 1457 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 1457 of the 2063 production source files in this repository met that bar). They are anonymized user #10 (2 file(s)), anonymized user #11 (2 file(s)), anonymized user #12 (1 file(s)), anonymized user #13 (1 file(s)), anonymized user #14 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: skills/investigate-puffin/compare_traces.py, skills/investigate-puffin/find_scopes.py, crates/data_flow/re_lerobot/src/metadata.rs, scripts/ci/build_and_upload_rerun_notebook.py, scripts/update_docs_url_rewrite.py, rerun_pixi_env/src/rerun_pixi_env/__init__.py, crates/viewer_support/re_component_ui/src/color_swatch.rs.
No ADRs found rerun_py/REDACTED:78— 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 `rerun_py/REDACTED` makes this repository a deployable product (line 78).
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 10 of 124 project(s) overshoot their size bounds, lowering Project Cohesion to 8.4/10. The most over is `rerun_py` (43839 LoC, 1099 module-visible types across 29 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.
D30 · Dependency Vulnerabilities· Medium advisory (unsound) · ×1
REDACTED
D30 · Dependency Vulnerabilities· High vulnerability · ×1
REDACTED
D34 · Knowledge Freshness· Orphaned files with no living knowledge · ×1
Orphaned files with no living knowledge — 29 of 1459 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; 1459 of the 2063 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/store/re_log_types/src/vec_deque_ext.rs, rerun_py/rerun_sdk/rerun/encodings/tensor_data_ext.py, crates/utils/re_perf_telemetry/src/args.rs, crates/viewer_support/re_viewer_context/src/blueprint_id.rs, rerun_py/rerun_sdk/rerun/blueprint/containers.py, rerun_py/rerun_sdk/rerun/encodings/class_description_ext.py, crates/top/re_sdk/src/blueprint/panel.rs, crates/store/re_log_encoding/src/rrd/log_msg.rs (and 21 more). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
Logging is not universal — Only 66/70 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `crates/build/re_dev_tools`, `crates/store_app/re_query`, `crates/top/rerun-cli`, `rerun_pixi_env`.
No dependency-update automation examples/js/viewer_control/package.json:10— `examples/js/viewer_control/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`.
R7 · Dead Code· Unused export 'parse_exact_json' · ×1
Unused export 'parse_exact_json' rerun_js/web-viewer/exact_json.ts:51— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'stringify_exact_json' · ×1
Unused export 'stringify_exact_json' rerun_js/web-viewer/exact_json.ts:55— Nothing imports this binding — it is safe to review for removal.
X2 · Cancellation propagation· Not all async functions that make a request accept an AbortSignal · ×1
Not all async functions that make a request accept an AbortSignal — Only 0/3 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
Null assertions (`!`) override strict null checking — ~1.7 `!` null assertions per 1k TypeScript source lines — 6 assertion(s) across the 3616 source line(s) of the 5 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: rerun_js/web-viewer/index.ts (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.
Subsumed condition operand crates/store_app/re_datafusion/src/chunk_fetcher/mod.rs:372— `msg.contains("connection")` can never decide this `||` — every value satisfying `msg.contains("connection")` also satisfies `msg.contains("connect")`, so the `||` chain is already decided by the latter. The expression is equivalent to the chain without it, which means it is wider than it reads. Delete the dead operand, or narrow the surviving one if IT is the accident.
Outdated: accesskit — `accesskit` is locked at 0.25.1 but 0.25.2 is the current stable release on crates.io, and it already satisfies the `"0.25"` requirement declared in crates/utils/re_workspace_hack/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p accesskit` and commit the updated REDACTED.
Outdated: agent-client-protocol-schema — `agent-client-protocol-schema` is locked at 1.9.1 but 1.18.0 is the current stable release on crates.io, and it already satisfies the `"1.9.1"` requirement declared in crates/utils/re_agent/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p agent-client-protocol-schema` and commit the updated REDACTED.
Outdated: aho-corasick — `aho-corasick` is locked at 1.1.4 but 1.1.5 is the current stable release on crates.io, and it already satisfies the `"1"` requirement declared in crates/utils/re_workspace_hack/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p aho-corasick` and commit the updated REDACTED.
Outdated: async-trait — `async-trait` is locked at 0.1.91 but 0.1.92 is the current stable release on crates.io, and it already satisfies the `"0.1.91"` requirement declared in crates/data_flow/re_redap_client/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p async-trait` and commit the updated REDACTED.
Outdated: axum-core — `axum-core` is locked at 0.5.5 but 0.5.6 is the current stable release on crates.io, and it already satisfies the `"0.5"` requirement declared in crates/utils/re_workspace_hack/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p axum-core` and commit the updated REDACTED.
Outdated: backtrace — `backtrace` is locked at 0.3.76 but 0.3.77 is the current stable release on crates.io, and it already satisfies the `"0.3.76"` requirement declared in crates/utils/re_crash_handler/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p backtrace` and commit the updated REDACTED.
Outdated: bitflags — `bitflags` is locked at 2.13.1 but 2.13.2 is the current stable release on crates.io, and it already satisfies the `"2.13"` requirement declared in crates/data_flow/re_redap_client/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p bitflags` and commit the updated REDACTED.
Outdated: camino — `camino` is locked at 1.2.3 but 1.2.6 is the current stable release on crates.io, and it already satisfies the `"1.2"` requirement declared in crates/build/re_dev_tools/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p camino` and commit the updated REDACTED.
Outdated: cc — `cc` is locked at 1.4.0 but 1.11.2 is the current stable release on crates.io, and it already satisfies the `"1"` requirement declared in crates/utils/re_workspace_hack/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p cc` and commit the updated REDACTED.
Outdated: clap — `clap` is locked at 4.6.1 but 4.6.7 is the current stable release on crates.io, and it already satisfies the `"4.6"` requirement declared in crates/store_app/re_server/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p clap` and commit the updated REDACTED.
Outdated: clap_builder — `clap_builder` is locked at 4.6.0 but 4.6.7 is the current stable release on crates.io, and it already satisfies the `"4"` requirement declared in crates/utils/re_workspace_hack/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p clap_builder` and commit the updated REDACTED.
Outdated: console — `console` is locked at 0.16.4 but 0.16.6 is the current stable release on crates.io, and it already satisfies the `"0.16"` requirement declared in crates/utils/re_workspace_hack/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p console` and commit the updated REDACTED.
Outdated: const_format — `const_format` is locked at 0.2.36 but 0.2.37 is the current stable release on crates.io, and it already satisfies the `"0.2.36"` requirement declared in crates/top/re_sdk/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p const_format` and commit the updated REDACTED.
Outdated: crossbeam — `crossbeam` is locked at 0.8.4 but 0.8.5 is the current stable release on crates.io, and it already satisfies the `"0.8.4"` requirement declared in rerun_py/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p crossbeam` and commit the updated REDACTED.
Outdated: crossbeam-channel — `crossbeam-channel` is locked at 0.5.15 but 0.5.17 is the current stable release on crates.io, and it already satisfies the `"0.5"` requirement declared in crates/utils/re_workspace_hack/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p crossbeam-channel` and commit the updated REDACTED.
Outdated: crossbeam-deque — `crossbeam-deque` is locked at 0.8.7 but 0.8.8 is the current stable release on crates.io, and it already satisfies the `"0.8"` requirement declared in crates/utils/re_workspace_hack/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p crossbeam-deque` and commit the updated REDACTED.
Outdated: crossbeam-epoch — `crossbeam-epoch` is locked at 0.9.20 but 0.9.21 is the current stable release on crates.io, and it already satisfies the `"0.9"` requirement declared in crates/utils/re_workspace_hack/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p crossbeam-epoch` and commit the updated REDACTED.
Outdated: crossbeam-queue — `crossbeam-queue` is locked at 0.3.12 but 0.3.14 is the current stable release on crates.io, and it already satisfies the `"0.3"` requirement declared in crates/utils/re_workspace_hack/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p crossbeam-queue` and commit the updated REDACTED.
Outdated: crossbeam-utils — `crossbeam-utils` is locked at 0.8.22 but 0.8.23 is the current stable release on crates.io, and it already satisfies the `"0.8"` requirement declared in crates/utils/re_workspace_hack/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p crossbeam-utils` and commit the updated REDACTED.
Outdated: either — `either` is locked at 1.17.0 but 1.19.0 is the current stable release on crates.io, and it already satisfies the `"1"` requirement declared in crates/utils/re_workspace_hack/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p either` and commit the updated REDACTED.
Outdated: enumset — `enumset` is locked at 1.1.13 but 1.1.15 is the current stable release on crates.io, and it already satisfies the `"1.1"` requirement declared in crates/ui_tools/re_renderer/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p enumset` and commit the updated REDACTED.
Outdated: errno — `errno` is locked at 0.3.14 but 0.3.15 is the current stable release on crates.io, and it already satisfies the `"0.3"` requirement declared in crates/utils/re_workspace_hack/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p errno` and commit the updated REDACTED.
Outdated: fastrand — `fastrand` is locked at 2.3.0 but 2.5.0 is the current stable release on crates.io, and it already satisfies the `"2"` requirement declared in crates/utils/re_workspace_hack/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p fastrand` and commit the updated REDACTED.
Outdated: ffmpeg-sidecar — `ffmpeg-sidecar` is locked at 2.5.2 but 2.7.0 is the current stable release on crates.io, and it already satisfies the `"2.5"` requirement declared in crates/utils/re_video/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p ffmpeg-sidecar` and commit the updated REDACTED.
Outdated: flate2 — `flate2` is locked at 1.1.9 but 1.1.11 is the current stable release on crates.io, and it already satisfies the `"1"` requirement declared in crates/utils/re_workspace_hack/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p flate2` and commit the updated REDACTED.
doc comments repeat the names rerun_js/web-viewer/index.ts:70— 0 of 11 documented parameters and 10 of 274 summaries in `@rerun-io/web-viewer` only repeat the member or parameter name (e.g. "The version of the viewer." for `viewerVersion`). 3 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
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. semgrep could not parse 1 file(s) — `rerun_py/rerun_sdk/rerun/catalog/_entry.py` — so the PII/GDPR sweep did not cover them at all.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
Run 01a1dae6-fa89-7341-835d-bd762e35d612 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 149 · Warnings: 3405 · Recommendations: 115 · Info: 103 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 14-11-2026 @ 16:32 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.