Public report of xiaozhaoCcz/CC_ETL, published 16 November 2026. It has the same score, grades and number of findings as the full report. The details of security findings (where they are in the code, which known vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive report Measured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey → Signed and filed in the standard's public register, 16 November 2026, 20:33 UTC · Survey ID cd_8476cf300147406a9d304419346002f7

xiaozhaoCcz/CC_ETL

Measured 16 November 2026, 20:32 UTC, at code version bef2ef3

First survey, so nothing to compare with yet
CAI score 43.6out of 100 At risk

The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.

A medium codebase: 90,479 lines of product code in 8 projects, tests not counted · Estimated rebuild effort: about 0.5 person-years · Weakest lens: Maturity, 32.0

Findings by how serious they are

21 critical 1168 serious 404 minor

17 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.

This survey was produced by

Assert small markCanine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
16 November 2026, 20: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 ▸

57of 57 dimensions measured by tools.
1584of 1593 findings point to an exact file and line, so you can open each one in the code. The other 9 concern the repository as a whole, such as missing documentation.
57dimensions across 5 lenses, read from 90,479 lines of product code in 8 projects.
Chapters

Executive summary

xiaozhaoCcz/CC_ETL is rated At risk because critical security findings are open, most of them in the packages it uses. Its score is held back because 269 files are no longer known to anyone active in the project and the project keeps no record of its design decisions. It scores 43.6 out of 100, which the At risk rating leaves unchanged.

Maturity, at 32.0, is the weakest lens and counts most in the score. The best first step for the work it takes is making the naming consistent, worth about 7.2 points. Recording design decisions would lift Maturity itself, worth about 9.3 points. Raising Maturity to 70 would lift the score to about 53.5.

Fifteen known security holes in the packages the code depends on can be used by attackers. Three passwords or keys are open to anyone who can read the repository, and two settings leave the servers or containers unsafe. Updating the vulnerable packages, replacing each exposed password or key and correcting the unsafe settings would close these risks. Reading outside data into plain values would fix the place where outside data is turned straight into objects.

The product code is 90,479 lines, about €72,000 to rebuild.

A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.

How the score is built: what each lens counts for The lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
Maturity 32.0 · counts for 47%Production Readiness 40.5 · counts for 26%Code Health 55.2 · counts for 14%Security and Compliance 75.5 · counts for 8%Architecture 91.6 · counts for 4%

If Maturity rose from 32.0 to 70, the lowest score rated Strong, the score would rise from 43.6 to about 53.5.

Code composition: what the lines of code are
Product code 99%Tests 1%
Rebuild cost: about €72,000 · Estimate
Cost to rebuild€24,000 to €120,000, for 398 to 1,262 hours of work, about 0.5 person-years for one engineer
Difficulty of the problemLow, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor×0.7 at a score of 44. 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.
SizeMedium: 90,479 lines of product code
What it is notNot a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.

How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.

Top priorities

The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.

1
Resolve the 1 `applyWriterConfigToUi` spells `Ui` where 15 names in the project spell… finding(s) in Naming Consistency — start with ShowDataxSyncDialog.java.
Raises the score by about 7.2 points · Low effort · Naming Consistency
2
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with REDACTED.
Raises the score by about 9.3 points · Low effort · ADR Quality
3
Resolve the 269 Orphaned file finding(s) in Knowledge Freshness — start with XxlJobConfig.java (3), SampleXxlJob.java (2), JobInfoService.java (2).
Raises the score by about 11.2 points · High effort · Knowledge Freshness

Diagnosis: what the measurements show together

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

Where the investment is most exposed · Value at risk
This code would cost about €72,000 to build again, about 0.5 person-years of work. Its weakest lens is Maturity, at 32.0 (Weak). Maturity is about how well the project explains and looks after itself, which decides whether a new developer, or a new supplier, can take over. Because the weakest lens counts most in the score, work on Maturity also moves the score most.
Based on: the rebuild estimate · the Maturity grade · how much each lens counts
What to do: Start with the Maturity actions in Top priorities.
If you do one thing first · First action
Resolve the 1 `applyWriterConfigToUi` spells `Ui` where 15 names in the project spell… finding(s) in Naming Consistency. Of all the actions in this report, it raises the score most for the work it takes: about 7.2 points for low effort, because it clears the 1 Naming Consistency findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 5.7 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 6% to 13% on every change. The history of the code shows how much it changes: about 93,691 lines over the last 90 days, which is about 379,969 lines a year. At that pace, the extra work comes to an estimated 54.6 to 327.9 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.

Architecture — module dependency graph

Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.

arch cc-job-admin cc-job-admin cc-job-core cc-job-core cc-job-admin->cc-job-core cc-job-xo cc-job-xo cc-job-admin->cc-job-xo cc-job-executor cc-job-executor cc-job-executor->cc-job-core cc-job-executor->cc-job-xo cc-job-executor-compose cc-job-executor-compose cc-job-executor-compose->cc-job-core cc-job-executor-compose->cc-job-xo cc-job-executor-sample-frameless cc-job-executor-sample-frameless cc-job-executor-sample-frameless->cc-job-core cc-job-executor-sample-springboot cc-job-executor-sample-springboot cc-job-executor-sample-springboot->cc-job-core cc-job-gui cc-job-gui cc-job-gui->cc-job-xo

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.

111 modules, with 199 dependencies between them. 5 loops run through 14 of the modules, marked above the diagonal.

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

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →1 cc.job.admin.config.properties2 cc.job.admin.task.enums3 cc.job.executor.compose.core.context4 cc.job.gui.model5 cc.job.xo.model.datax6 cc.job.xo.model.entity7 cc.job.xo.model.form8 cc.job.xo.model.query9 cc.job.xo.model.vo10 xxl.job.core.handler11 cc.job.admin.task.alarm12 cc.job.admin.task.converter13 cc.job.executor.compose.client14 cc.job.executor.compose.core.resolver15 cc.job.executor.compose.engine.wrapper16 cc.job.gui.view17 cc.job.xo.mapper18 xxl.job.core.context19 cc.job.admin.config20 cc.job.admin.task.alarm.impl21 cc.job.executor.compose.core.model22 cc.job.executor.compose.engine.worker23 cc.job.executor.core.service.datax24 cc.job.gui.util25 xxl.job.core.biz.model26 cc.job.admin.task.service27 cc.job.admin.task.thread28 cc.job.executor.compose.engine.callback29 cc.job.executor.core.service30 cc.job.gui.service31 xxl.job.core.biz32 cc.job.admin.task.controller33 cc.job.admin.task.service.impl34 cc.job.executor.compose.handler35 cc.job.executor.compose.service36 cc.job.gui.manager37 xxl.job.core.executor38 cc.job.executor.compose.core.service39 xxl.job.core.executor.impl40 cc.job.executor.compose.core.orchestrator
1 cc.job.admin.config.properties
2 cc.job.admin.task.enums
3 cc.job.executor.compose.core.context
4 cc.job.gui.model
5 cc.job.xo.model.datax
6 cc.job.xo.model.entity
7 cc.job.xo.model.form
8 cc.job.xo.model.query
9 cc.job.xo.model.vo
10 xxl.job.core.handler
11 cc.job.admin.task.alarm15
12 cc.job.admin.task.converter111
13 cc.job.executor.compose.client4
14 cc.job.executor.compose.core.resolver1
15 cc.job.executor.compose.engine.wrapper22
16 cc.job.gui.view4915682323531
17 cc.job.xo.mapper4
18 xxl.job.core.context1
19 cc.job.admin.config38
20 cc.job.admin.task.alarm.impl4105
21 cc.job.executor.compose.core.model262
22 cc.job.executor.compose.engine.worker1
23 cc.job.executor.core.service.datax231
24 cc.job.gui.util111
25 xxl.job.core.biz.model1
26 cc.job.admin.task.service2106472
27 cc.job.admin.task.thread1124
28 cc.job.executor.compose.engine.callback12
29 cc.job.executor.core.service413
30 cc.job.gui.service21125493
31 xxl.job.core.biz9
32 cc.job.admin.task.controller217541083231
33 cc.job.admin.task.service.impl2157491115341
34 cc.job.executor.compose.handler1321
35 cc.job.executor.compose.service131112111
36 cc.job.gui.manager3924124214
37 xxl.job.core.executor11
38 cc.job.executor.compose.core.service29434143
39 xxl.job.core.executor.impl2
40 cc.job.executor.compose.core.orchestrator22111115
Uses a module listed above itPart of a loopThe module itself
1 cc.job.admin.config.properties2 cc.job.admin.task.enums3 cc.job.executor.compose.core.context4 cc.job.gui.model5 cc.job.xo.model.datax6 cc.job.xo.model.entity7 cc.job.xo.model.form8 cc.job.xo.model.query9 cc.job.xo.model.vo10 xxl.job.core.handler11 cc.job.admin.task.alarm12 cc.job.admin.task.converter13 cc.job.executor.compose.client14 cc.job.executor.compose.core.resolver15 cc.job.executor.compose.engine.wrapper16 cc.job.gui.view17 cc.job.xo.mapper18 xxl.job.core.context19 cc.job.admin.config20 cc.job.admin.task.alarm.impl21 cc.job.executor.compose.core.model22 cc.job.executor.compose.engine.worker23 cc.job.executor.core.service.datax24 cc.job.gui.util25 xxl.job.core.biz.model26 cc.job.admin.task.service27 cc.job.admin.task.thread28 cc.job.executor.compose.engine.callback29 cc.job.executor.core.service30 cc.job.gui.service31 xxl.job.core.biz32 cc.job.admin.task.controller33 cc.job.admin.task.service.impl34 cc.job.executor.compose.handler35 cc.job.executor.compose.service36 cc.job.gui.manager37 xxl.job.core.executor38 cc.job.executor.compose.core.service39 xxl.job.core.executor.impl40 cc.job.executor.compose.core.orchestratorcc.job.admin.config.properties1cc.job.admin.task.enums2cc.job.executor.compose.core.context3cc.job.gui.model4cc.job.xo.model.datax5cc.job.xo.model.entity6cc.job.xo.model.form7cc.job.xo.model.query8cc.job.xo.model.vo9xxl.job.core.handler10cc.job.admin.task.alarm11cc.job.admin.task.converter12cc.job.executor.compose.client13cc.job.executor.compose.core.resolver14cc.job.executor.compose.engine.wrapper15cc.job.gui.view16cc.job.xo.mapper17xxl.job.core.context18cc.job.admin.config19cc.job.admin.task.alarm.impl20cc.job.executor.compose.core.model21cc.job.executor.compose.engine.worker22cc.job.executor.core.service.datax23cc.job.gui.util24xxl.job.core.biz.model25cc.job.admin.task.service26cc.job.admin.task.thread27cc.job.executor.compose.engine.callback28cc.job.executor.core.service29cc.job.gui.service30xxl.job.core.biz31cc.job.admin.task.controller32cc.job.admin.task.service.impl33cc.job.executor.compose.handler34cc.job.executor.compose.service35cc.job.gui.manager36xxl.job.core.executor37cc.job.executor.compose.core.service38xxl.job.core.executor.impl39cc.job.executor.compose.core.orchestrator401511141224915682323531413841052621231111121064721124124132112549392175410832312157491115341132113111211139241242141129434143222111115+71 more modules (most-connected shown)

At a glance — Code Health · 55.2 · Adequate · gated by D4, X5 ·

At a glance — Architecture · 91.6 · Adequate · gated by D26 ·

At a glance — Maturity · 32.0 · Weak · gated by D34, M2, M4 ·

At a glance — Readiness · 40.5 · Weak · gated by P1, P3 ·

At a glance — Security · 75.5 · Checked 4 of 10 · gated by D29 ·

Security & Compliance — OWASP Top-10 mapping

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

OWASP categoryFindingsSeverity
A03:2025 — Software Supply Chain Failures22High / Critical
A05:2025 — Injection19High / Critical
A07:2025 — Authentication Failures14High / Critical
A02:2025 — Security Misconfiguration4High / Critical

Roadmap

Top priorities: Resolve the 269 Orphaned file finding(s) in Knowledge Freshness — start with XxlJobConfig.java (3), SampleXxlJob.java (2), JobInfoService.java (2); Resolve the 1 No ADRs found finding(s) in ADR Quality — start with REDACTED; 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.

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

Do thisHelpsEffortDimension
Resolve the 1 `applyWriterConfigToUi` spells `Ui` where 15 names in the project spell… finding(s) in Naming Consistency — start with ShowDataxSyncDialog.java.+7.2 ptsLowNaming Consistency
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with REDACTED.+9.3 ptsLowADR Quality
Resolve the 269 Orphaned file finding(s) in Knowledge Freshness — start with XxlJobConfig.java (3), SampleXxlJob.java (2), JobInfoService.java (2).+11.2 ptsHighKnowledge Freshness
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.+7.3 ptsMediumArchitecture documentation
Resolve the 5 No direct assertions finding(s) in Test Quality — start with CcJobApplicationTest.java (5).+3.0 ptsLowTest Quality
Reconcile the README with reality: cc-job/cc-job-executor-compose/README.md links to `./COMPLETE_IMPLEMENTATION.md`, but `cc-job/cc-job-executor-compose/COMPLETE_IMPLEMENTATION.md` does not exist; cc-job/cc-job-executor-compose/README.md links to `../doc/architecture-analysis.md`, but `cc-job/doc/architecture-analysis.md` does not exist; cc-job/cc-job-executor-compose/README.md links to `../doc/migration-guide.md`, but `cc-job/doc/migration-guide.md` does not exist; cc-job/cc-job-executor-compose/README.md links to `../doc/api-specification.md`, but `cc-job/doc/api-specification.md` does not exist.+5.6 ptsMediumDocumentation accuracy
Add a CI workflow that builds and runs the test suite on every push/PR.+4.2 ptsMediumCI/CD gates
Run what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.+4.2 ptsMediumSecurity & performance tooling

File quality

Per-file score 0–10 — a quality signature. Of 198 files carrying findings, judged against the Production bar: 2% slop · 68% mixed · 30% near-clean.

FileScoreBandWorst signal
REDACTED0.2SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED1.6SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED3.0SlopIaC & Container Security: High IaC: REDACTED
REDACTED4.0MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED4.0MixedStatic Analysis (SAST): Medium: REDACTED
cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/LogPanel.java4.8MixedCognitive Complexity: LogPanel.exportLogsToFile (cognitive 24)
REDACTED5.1MixedStatic Analysis (SAST): Medium: REDACTED
cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobPartService.java5.5MixedCyclomatic Complexity: JobPartService.parseJobComposeData (cyclomatic 31)
cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java5.5MixedGod Classes: ClassTooLong: ShowJobListDialog
cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/component/SmartParameterInput.java5.5MixedCyclomatic Complexity: SmartParameterInput.handleSmartDelete (cyclomatic 40)
cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/TopToolBar.java5.5MixedCognitive Complexity: TopToolBar.updateButtonState (cognitive 20)
cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/client/AdminApiClient.java5.5MixedCode Duplication: Members sharing a duplicated core (4 members, 50+ identical tokens)
cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/datax/reader/MysqlReader.java5.5MixedCognitive Complexity: MysqlReader.buildJson (cognitive 21)
cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/NodeConnection.java5.6MixedGod Classes: TooManyMethods: NodeConnection
REDACTED5.7MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED5.7MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.8MixedSecrets (history): REDACTED: REDACTED
cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/NodeSearchManager.java5.9MixedCyclomatic Complexity: NodeSearchManager.search (cyclomatic 22)
cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java6.0MixedExplicit Debt: TodoComment
cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobLogServiceImpl.java6.0MixedExplicit Debt: TodoComment

How the grades work

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

Critical — 21

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

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

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

Could not be resolved — 17

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 57 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 — 57 dimensions across the health lenses
D1D2D3D4D5D6D10D13D14D15D17D19D20D21D26D27D28D29D30D31D34D35D43D44AX1AX10AX2AX3AX5AX6GD1IC1M1M2M3M4P1P10P2P3P4P7X13X14X16X18X19X23X24X25X26X27X28X29X3X4X5

Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.

How to trust any code-health report — three questions
  1. Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 1584 of 1593 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
  2. Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
  3. Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.

This report answers yes to all three. That's the bar to hold any assessment to.

Tools & methods

The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.

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

Every finding is locatable in findings.md. Run 01a1e60f-e753-7dcc-8391-6f7cea159c1b.

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

Run transparency — what happened this run

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

  • D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.java) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo.
  • D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.java) and this repository declares a JVM test suite (cc-job, Maven), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
  • D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — a Maven build resolved 68 artifact(s) (65 behind a shipped release, reported), but the build resolved only part of the graph, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
  • D16 Bus Factor — 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. Single-maintainer repository — bus factor is not applicable (5 contributor(s) across 662 commit(s) sampled, automation and bot accounts excluded). One of them holds 95% of the history; the other 4 hold 1.2% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
  • 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 — 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. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
  • D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (cc-job/pom.xml), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict.
  • D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
  • 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 ToolchainServer (cc-job/cc-job-admin). the service did not build — `mvn -B -q -DskipTests compile` exited 1: ; runtime evidence skipped (launch chosen because cc-job/cc-job-admin/pom.xml declares spring-boot-starter-web and the Spring Boot Maven plugin).
  • 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.
  • 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.
  • S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
  • X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X10 Duplicated predicate — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 34 further occurrence(s) are not listed individually; the score already reflects all 74.
  • X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin or Rust was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X17 Uncapped recursion over a caller-supplied document — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin or Rust was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X4 Structured logging — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 8 further occurrence(s) are not listed individually; the score already reflects all 48.

Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.

Limitations & what we did not check

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

Per-dimension blind spots

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

  • D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
  • D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
  • D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
  • D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
  • D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
  • D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • 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.
  • D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
  • D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
  • D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
  • D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
  • D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
  • D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
  • D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
  • D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
  • D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
  • D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
  • D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
  • AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
  • 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".

Dimensions

D1 · Cyclomatic Complexity6.3 / 10Adequate✓ Tool-verified

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

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

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

102 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was ShowDataxSyncDialog.applyEditData at 76. A further 3 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 CanvasDataLoader.mapNodeType at 38 — they are counted neither in the figure above nor in this dimension's score.

SampleXxlJob.httpJobHandler (cyclomatic 19) · ×2cc-job/cc-job-executor-samples/cc-job-executor-sample-frameless/src/main/java/com/cc/job/executor/sample/sample/frameless/jobhandler/SampleXxlJob.java:126
1.run (cyclomatic 18) · ×2cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/thread/JobFailMonitorHelper.java:38
ShowDataxSyncDialog.applyEditData (cyclomatic 76)cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:434
NodeDetailsDialog.loadDetails (cyclomatic 69)cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeDetailsDialog.java:233
CronExpression.getTimeAfter (cyclomatic 67)cc-job/cc-job-admin/src/main/java/com/cc/job/admin/cron/CronExpression.java:1162

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

What to do

  1. Bring the 5 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with ShowDataxSyncDialog.applyEditData (cyclomatic 76), NodeDetailsDialog.loadDetails (cyclomatic 69), CronExpression.getTimeAfter (cyclomatic 67). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 5 together lifts Cyclomatic Complexity from 6.3 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.

D2 · Cognitive Complexity4.7 / 10Weak✓ Tool-verified

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

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

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

183 method(s) exceeded the cognitive complexity threshold of 15; the worst was ShowDataxSyncDialog.applyEditData at 189.

SampleXxlJob.httpJobHandler (cognitive 21) · ×2cc-job/cc-job-executor-samples/cc-job-executor-sample-frameless/src/main/java/com/cc/job/executor/sample/sample/frameless/jobhandler/SampleXxlJob.java:126
ShowDataxSyncDialog.applyEditData (cognitive 189)cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:434
NodeCanvas.loadFromComposeData (cognitive 164)cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:2060
CronExpression.getTimeAfter (cognitive 161)cc-job/cc-job-admin/src/main/java/com/cc/job/admin/cron/CronExpression.java:1162
NodeDetailsDialog.loadDetails (cognitive 137)cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeDetailsDialog.java:233

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

What to do

  1. Bring the 6 bodies over 120 down to 120 or less in Cognitive Complexity — start with ShowDataxSyncDialog.applyEditData (cognitive 189), NodeCanvas.loadFromComposeData (cognitive 164), CronExpression.getTimeAfter (cognitive 161). — 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 6 together lifts Cognitive Complexity from 4.7 to about 5.3/10, projected with the scoring formula itself and assuming each lands exactly at 120; a cleaner split scores higher.

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

D3 · God Classes7.5 / 10Strong✓ Tool-verified

What it measures: Over-large classes that try to do too much ("god classes").

Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.

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

110 god class(es) detected.

MethodTooLong: MainView.setupCallbacks · ×34cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:261
TooManyMethods: NodeCanvas · ×31cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:37
ClassTooLong: NodeCanvas · ×24cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:37
FileTooLong: view/NodeCanvas.java · ×21cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java

What to do

  1. Resolve the 34 MethodTooLong finding(s) in God Classes — start with ShowDataxSyncDialog.java (4), JobComposeServiceImpl.java (4), CronExpression.java (3). — One of this dimension's main actionable groups (34 warning-level).
  2. Resolve the 31 TooManyMethods finding(s) in God Classes — start with MainView.java (2), NodeCanvas.java, ProcessNode.java. — One of this dimension's main actionable groups (31 warning-level).
  3. Resolve the 24 ClassTooLong finding(s) in God Classes — start with NodeCanvas.java, MainView.java, ShowDataxSyncDialog.java. — One of this dimension's main actionable groups (24 warning-level).

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

D4 · Code Duplication2.3 / 10Critical✓ Tool-verified

What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.

Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.

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

443 duplicated block group(s) detected. 19.2 % of the production lines (17,346 of 90,479) are in a reported copy. A further 210 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.

Members sharing a duplicated core (4 members, 50+ identical tokens) · ×25cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/alarm/impl/DingTalkJobAlarm.java:42
Duplicated block (8 lines × 2) · ×23cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:485
Duplicated block (7 lines × 2) · ×19REDACTED:80
Duplicated block (10 lines × 2) · ×18cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/thread/JobRegistryHelper.java:157
Duplicated block (9 lines × 2) · ×18cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:1062

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

What to do

  1. Resolve the 25 Members sharing a duplicated core (4 members, 50+ identical tokens) finding(s) in Code Duplication — start with AdminApiClient.java (3), ShowDatasourceListDialog.java (3), JobDataxService.java (2). — One of this dimension's main actionable groups (25 warning-level).
  2. Resolve the 23 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with ShowDataxGroupSyncDialog.java (3), JobComposeServiceImpl.java (2), MainView.java (2). — One of this dimension's main actionable groups (23 warning-level).
  3. Resolve the 19 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with ConditionNode.java (2), AddJobFromListDialog.java (2), ShowDataxGroupSyncDialog.java (2). — One of this dimension's main actionable groups (19 warning-level).

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

D5 · Coupling8.0 / 10Strong✓ Tool-verified

What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.

Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.

Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.

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

8 production modules (Maven), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 2 module(s) off the main sequence.

Off the main sequence: cc-job-core · ×2

What to do

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

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

D6 · Cohesion (LCOM4)9.5 / 10Stronggated by 8 serious findings✓ Tool-verified

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

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

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

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

8 of 176 classes have LCOM4 above 3.

Low cohesion: DependencyNavigator (LCOM4 7) · ×8cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DependencyNavigator.java:18

What to do

  1. Resolve the 8 Low cohesion finding(s) in Cohesion (LCOM4) — start with DependencyNavigator.java, NodeSearchManager.java, SmartParameterInput.java. — One of this dimension's main actionable groups (8 warning-level).

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

D10 · Test Quality7.7 / 10Strong✓ Tool-verified

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

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

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

0 skipped, 7 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 13 tests (1 harness-style project(s) excluded from the assertion penalty).

No assertions: test · ×2cc-job/cc-job-executor-samples/cc-job-executor-sample-frameless/src/test/java/com/cc/job/executor/sample/sample/frameless/test/FramelessApplicationTest.java:8
Test project verifies nothing: cc-job-executor-sample-frameless · ×2cc-job/cc-job-executor-samples/cc-job-executor-sample-frameless/src/test/java/com/cc/job/executor/sample/sample/frameless/test/FramelessApplicationTest.java:8
No direct assertions: test1 · ×5cc-job/cc-job-admin/src/test/java/com/cc/job/test/CcJobApplicationTest.java:56
Test project verifies nothing: cc-job-admincc-job/cc-job-admin/src/test/java/com/cc/job/test/CcJobApplicationTest.java:56

What to do

  1. Resolve the 5 No direct assertions finding(s) in Test Quality — start with CcJobApplicationTest.java (5). — One of this dimension's main actionable groups (5 recommendation-level).
  2. Resolve the 2 No assertions finding(s) in Test Quality — start with FramelessApplicationTest.java, XxlJobExecutorExampleBootApplicationTests.java. — One of this dimension's main actionable groups (2 warning-level).
  3. Resolve the 2 Test project verifies nothing finding(s) in Test Quality — start with FramelessApplicationTest.java, XxlJobExecutorExampleBootApplicationTests.java. — One of this dimension's main actionable groups (2 warning-level).

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

D13 · REDACTED Scanning10.0 / 10Exemplary○ Nothing flagged

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

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

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

REDACTED scan ran and found no leaked secrets. 1 detection(s) on lines whose every credible literal is a keyboard-row or short-ascending-run composition (`1234567890abcdef`) were excluded — a value a hand typed for a documentation example was never minted, and there is no issuer at which it could be revoked. 1 detection(s) were excluded as holding no minted credential in material that runs: a name, reference or comparison rather than a value, a readable phrase or pattern, a value that declares itself fake, or development, test, example, mock or demo material. 5 password hash(es) are listed to check and are not counted as leaked credentials.

REDACTED

✓ On the Gold path — maintain.

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

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

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

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

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

0 of 16 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 10 Maven/Gradle manifest(s) declare with a version resolvable from the manifest itself — the same declaration-site closure this analysis reads for dependency currency. The JVM has no lockfile a checkout is guaranteed to carry, so this is deliberately NOT the transitive closure. 52 further coordinate(s) are declared with no version at the declaration site — inherited from a parent POM, a BOM or an unresolved Gradle version reference — and are NOT graded: this verdict covers what the checkout pins, not the full transitive graph. A further 1 coordinate(s) are not published to Maven Central — another repository (Google's Maven hosts androidx), a SNAPSHOT, or a private artifact — so their licences are not readable from here and they are outside this verdict.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

D15 · Churn × Complexity Hotspots8.9 / 10Strong✓ Tool-verified

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

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

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

Top hotspots: cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java (34×56=1904); cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java (19×76=1444); cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java (44×30=1320)

Hotspot: cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java · ×26cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:2060

What to do

  1. Resolve the 26 Hotspot finding(s) in Churn × Complexity Hotspots — start with NodeCanvas.java, ShowDataxSyncDialog.java, MainView.java. — One of this dimension's main actionable groups (26 warning-level).

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

D17 · Explicit Debt10.0 / 10Stronggated by 11 serious findings✓ Tool-verified

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

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

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

11 deducted task-comment markers across 90479 LoC (0.0/KLoC) → score 10.0. 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.

TodoComment · ×11cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:849

What to do

  1. Resolve the 11 TodoComment finding(s) in Explicit Debt — start with MainView.java (6), TaskTreeView.java, ParameterAutocompleteService.java. — One of this dimension's main actionable groups (11 warning-level).

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

D19 · Documentation Quality10.0 / 10Exemplary○ Nothing flagged

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

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

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

1 of 1 documentation facets pass in full. 3 document(s) read across 1 unit(s).

✓ On the Gold path — maintain.

Detailed fixes: d19_recommendation.md.

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.

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

No architecture decision records were found.

No ADRs foundcc-job/cc-job-gui/pom.xml:157

What to do

  1. 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.

D21 · Naming Consistency3.8 / 10Weak✓ Tool-verified

What it measures: Whether names — types, methods, variables — are clear and consistent.

Method: Seven vocabulary-free rules (N1-N7) mine each naming convention from the repository and flag a name that breaks a convention its structural peers in the same unit follow; production C# and TypeScript, each its own population. Deterministic, no model, no sample. Advisory.

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

1 naming inconsistencies among 16 declarations measured against a convention their peers follow.

`applyWriterConfigToUi` spells `Ui` where 15 names in the project spell it `UI`cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:667

What to do

  1. Resolve the 1 `applyWriterConfigToUi` spells `Ui` where 15 names in the project spell… finding(s) in Naming Consistency — start with ShowDataxSyncDialog.java. — One of this dimension's main actionable groups (1 recommendation-level).

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

D26 · Project Cohesion0.9 / 10Critical✓ Tool-verified

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

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

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

4 of 8 build units (Maven) flagged as possibly oversized/incoherent.

Projects may be oversized for their cohesion · ×4cc-job/cc-job-gui/pom.xml:1

What to do

  1. Resolve the 4 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with REDACTED (4). — One of this dimension's main actionable groups (4 recommendation-level).

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

D27 · Navigability9.3 / 10Exemplary✓ Tool-verified

What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.

Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.

Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.

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

85 % of calls cross a namespace and 14 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.

✓ On the Gold path — maintain.

Detailed fixes: d27_recommendation.md.

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

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

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

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

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

REDACTED
REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 2 High secret finding(s) in Secrets (history) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
  2. Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  3. Resolve the 5 REDACTED finding(s) in Secrets (history) — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (5 recommendation-level).

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

D29 · Static Analysis (SAST)4.0 / 10Weak✓ Tool-verified

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

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

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

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

19 finding(s): 0 critical, 1 high, 13 medium, 5 low.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

  1. Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  2. Resolve the 5 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED, REDACTED. — One of this dimension's main actionable groups (5 warning-level).
  3. Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4). — One of this dimension's main actionable groups (4 warning-level).

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

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

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

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

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

22 finding(s): 3 critical, 12 high, 7 medium, 0 low.

REDACTED
REDACTED
REDACTED

What to do

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

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

D31 · IaC & Container Security9.2 / 10Adequategated by 2 critical findings✓ Tool-verified

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

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

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

4 finding(s): 0 critical, 2 high, 1 medium, 1 low.

REDACTED
REDACTED
REDACTED

What to do

  1. 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).
  2. Resolve the 1 Medium IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 Low IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).

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

D34 · Knowledge Freshness0.0 / 10Critical✓ Tool-verified

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

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

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

272 of 272 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java. Counted over 272 of the 505 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned file · ×269cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:1
Most significant orphaned file · ×3cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:1
Dormant codebase

What to do

  1. Resolve the 269 Orphaned file finding(s) in Knowledge Freshness — start with XxlJobConfig.java (3), SampleXxlJob.java (2), JobInfoService.java (2). — One of this dimension's main actionable groups (269 recommendation-level).
  2. Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with NodeCanvas.java, MainView.java, ShowDataxSyncDialog.java. — One of this dimension's main actionable groups (3 recommendation-level).
  3. Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).

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

D35 · Change Coupling9.9 / 10Stronggated by 7 serious findings✓ Tool-verified

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

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

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

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

Strongest change-coupling: JobPartService.java↔NodeCanvas.java 69%; MysqlReader.java↔DataxHandler.java 67%; JobInfo.java↔JobInfoForm.java 64%

Change coupling: JobPartService.java ↔ NodeCanvas.java · ×7cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobPartService.java:1

What to do

  1. Resolve the 7 Change coupling finding(s) in Change Coupling — start with JobPartService.java, MysqlReader.java, JobInfo.java. — One of this dimension's main actionable groups (7 warning-level).

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

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

What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.

Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.

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

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

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

D44 · Platform End-of-Life10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

Frontend & cross-cutting dimensions

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

AX1 · Captive dependencies10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether any singleton service captures a scoped/transient dependency — a silent lifetime/threading bug.

Method: Roslyn scan: DI registrations parsed from AddSingleton/Scoped/Transient; each singleton checked for captured shorter-lifetime dependencies. Exhaustive, deterministic.

AX10 · Code composition9.7 / 10Exemplary✓ Tool-verified

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

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

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

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

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

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

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

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

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

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

AX6 · Interface segregation9.9 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').

Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.

  • `JobInfoService` declares 25 abstract methods: `baseSaveJobInfo`, `baseUpdateJobInfo`, `checkJobGroupRunningInExecutor`, `countJobs`, `countTaskGroups`, `delNodes`, `deleteJobInfos`, `getGlueList`, `getGlueList`, `getJobInfoForm`, `getJobInfoListWithPermission`, `getJobInfoPage`, `initData`, `nextTriggerTime`, `pauseJob`, `resetTriggerOneStatus`, `saveGlueSource`, `saveJobCompose`, `saveJobInfo`, `startJob`, `stopJob`, `stopJobCompose`, `triggerJob`, `updateJobCompose`, `updateJobInfo`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. Those 25 declarations carry 24 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 24 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/JobInfoService.java:23
  • `ToolBarCallback` declares 43 abstract methods: `onAlignBottom`, `onAlignHorizontalCenter`, `onAlignLeft`, `onAlignRight`, `onAlignToCenter`, `onAlignToGroupBottom`, `onAlignToGroupHorizontalCenter`, `onAlignToGroupLeft`, `onAlignToGroupRight`, `onAlignToGroupTop`, `onAlignToGroupVerticalCenter`, `onAlignTop`, `onAlignVerticalCenter`, `onClear`, `onDashboardBigScreen`, `onDatasourceList`, `onDataxGroupSync`, `onDataxSync`, `onDetectCycles`, `onDistributeHorizontally`, `onDistributeVertically`, `onExportCanvas`, `onJobGroupList`, `onJobList`, `onJobLogList`, `onLayoutHorizontal`, `onLayoutVertical`, `onNew`, `onNewPart`, `onNodeHistory`, `onOpen`, `onRedo`, `onRun`, `onSave`, `onSelect`, `onSettings`, `onStop`, `onTaskReport`, `onToggleSnapToGrid`, `onUndo`, and 3 more. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/TopToolBar.java:46

What to do

  • Split fat interfaces into focused role-interfaces so clients depend only on what they use.
GD1 · Unfinished & placeholder code10.0 / 10Exemplary✓ Tool-verified

Other · Code Health — Unreviewed-generation residue in this repository's Java: methods whose whole body only throws a "not implemented" or bare unsupported-operation exception, or returns a default value (or nothing) under a TODO/FIXME marker, and placeholder text (lorem ipsum, changeme/replace_me…) left in strings of non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.

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

  • `getTimeBefore` is a shipped method whose whole body returns a default value under a TODO/FIXME — a placeholder standing in for the implementation. Implement it or remove it. — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/cron/CronExpression.java:1584
  • `getFinalFireTime` is a shipped method whose whole body returns a default value under a TODO/FIXME — a placeholder standing in for the implementation. Implement it or remove it. — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/cron/CronExpression.java:1593
  • `getAttributesFromTaskGroup` is a shipped method whose whole body returns a default value under a TODO/FIXME — a placeholder standing in for the implementation. Implement it or remove it. — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/ParameterAutocompleteService.java:474

What to do

  • Finish or delete the methods that still throw "not implemented" or return a placeholder under a TODO, and replace placeholder text before shipping.
IC1 · Incompleteness & stubs10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Unfinished work detected by code SHAPE, not keywords, in this repository's Java: methods that only throw a "not implemented" exception, methods that take inputs and return a constant or do nothing, dead `if (false)` branches, and skeleton classes most of whose methods are holes.

Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.

M1 · Documentation (README)6.2 / 10Adequate✓ Tool-verified

Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.

Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.

What to do

  • Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
  • Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation0.0 / 10Critical✓ Tool-verified

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

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

  • No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
  • No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.

What to do

  • Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
  • Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure10.0 / 10Exemplary✓ Tool-verified

Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.

Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.

M4 · Documentation accuracy2.0 / 10Critical✓ Tool-verified

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.

  • cc-job/cc-job-executor-compose/README.md links to `./COMPLETE_IMPLEMENTATION.md`, but `cc-job/cc-job-executor-compose/COMPLETE_IMPLEMENTATION.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — cc-job/cc-job-executor-compose/README.md:328
  • cc-job/cc-job-executor-compose/README.md links to `../doc/architecture-analysis.md`, but `cc-job/doc/architecture-analysis.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — cc-job/cc-job-executor-compose/README.md:474
  • cc-job/cc-job-executor-compose/README.md links to `../doc/migration-guide.md`, but `cc-job/doc/migration-guide.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — cc-job/cc-job-executor-compose/README.md:475
  • cc-job/cc-job-executor-compose/README.md links to `../doc/api-specification.md`, but `cc-job/doc/api-specification.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — cc-job/cc-job-executor-compose/README.md:476

What to do

  • Reconcile the README with reality: cc-job/cc-job-executor-compose/README.md links to `./COMPLETE_IMPLEMENTATION.md`, but `cc-job/cc-job-executor-compose/COMPLETE_IMPLEMENTATION.md` does not exist; cc-job/cc-job-executor-compose/README.md links to `../doc/architecture-analysis.md`, but `cc-job/doc/architecture-analysis.md` does not exist; cc-job/cc-job-executor-compose/README.md links to `../doc/migration-guide.md`, but `cc-job/doc/migration-guide.md` does not exist; cc-job/cc-job-executor-compose/README.md links to `../doc/api-specification.md`, but `cc-job/doc/api-specification.md` does not exist.
P1 · CI/CD gates0.0 / 10Critical✓ Tool-verified

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.

  • No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.

What to do

  • Add a CI workflow that builds and runs the test suite on every push/PR.
P10 · Library API & versioning9.6 / 10Exemplary✓ Tool-verified

Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.

Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.

  • 5 public types in `com.cc.job.admin.task.alarm.impl` are marked as implementation by their own namespace, folder or name: `DingTalkJobAlarm` (cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/alarm/impl/DingTalkJobAlarm.java:29, `impl`), `EmailJobAlarm` (cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/alarm/impl/EmailJobAlarm.java:28, `impl`), `FeishuJobAlarm` (cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/alarm/impl/FeishuJobAlarm.java:25, `impl`), `WeComJobAlarm` (cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/alarm/impl/WeComJobAlarm.java:25, `impl`), `WebhookJobAlarm` (cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/alarm/impl/WebhookJobAlarm.java:32, `impl`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/alarm/impl/DingTalkJobAlarm.java:29
  • 20 public types in `com.cc.job.admin.task.service.impl` are marked as implementation by their own namespace, folder or name: `AdminBizImpl` (cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/AdminBizImpl.java:17, `impl`), `DataxServiceImpl` (cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/DataxServiceImpl.java:22, `impl`), `JobCanvasBookmarkServiceImpl` (cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobCanvasBookmarkServiceImpl.java:13, `impl`), `JobComposeServiceImpl` (cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:39, `impl`), `LfNode` (cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:55, `impl`), `LfEdge` (cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:121, `impl`), `JobEdgeServiceImpl` (cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobEdgeServiceImpl.java:10, `impl`), `JobGroupServiceImpl` (cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobGroupServiceImpl.java:32, `impl`), and 12 more. While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/AdminBizImpl.java:17
  • 1 public type in `com.xxl.job.core.biz.impl` is marked as implementation by its own namespace, folder or name: `ExecutorBizImpl` (cc-job/cc-job-core/src/main/java/com/xxl/job/core/biz/impl/ExecutorBizImpl.java:26, `impl`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — cc-job/cc-job-core/src/main/java/com/xxl/job/core/biz/impl/ExecutorBizImpl.java:26
  • 2 public types in `com.xxl.job.core.executor.impl` are marked as implementation by their own namespace, folder or name: `XxlJobSimpleExecutor` (cc-job/cc-job-core/src/main/java/com/xxl/job/core/executor/impl/XxlJobSimpleExecutor.java:20, `impl`), `XxlJobSpringExecutor` (cc-job/cc-job-core/src/main/java/com/xxl/job/core/executor/impl/XxlJobSpringExecutor.java:26, `impl`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — cc-job/cc-job-core/src/main/java/com/xxl/job/core/executor/impl/XxlJobSimpleExecutor.java:20
  • 1 public type in `com.xxl.job.core.glue.impl` is marked as implementation by its own namespace, folder or name: `SpringGlueFactory` (cc-job/cc-job-core/src/main/java/com/xxl/job/core/glue/impl/SpringGlueFactory.java:17, `impl`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — cc-job/cc-job-core/src/main/java/com/xxl/job/core/glue/impl/SpringGlueFactory.java:17
  • 4 public types in `com.xxl.job.core.handler.impl` are marked as implementation by their own namespace, folder or name: `CSharpGlueJobHandler` (cc-job/cc-job-core/src/main/java/com/xxl/job/core/handler/impl/CSharpGlueJobHandler.java:13, `impl`), `GlueJobHandler` (cc-job/cc-job-core/src/main/java/com/xxl/job/core/handler/impl/GlueJobHandler.java:11, `impl`), `MethodJobHandler` (cc-job/cc-job-core/src/main/java/com/xxl/job/core/handler/impl/MethodJobHandler.java:10, `impl`), `ScriptJobHandler` (cc-job/cc-job-core/src/main/java/com/xxl/job/core/handler/impl/ScriptJobHandler.java:15, `impl`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — cc-job/cc-job-core/src/main/java/com/xxl/job/core/handler/impl/CSharpGlueJobHandler.java:13

What to do

  • Hide `com.cc.job.admin.task.alarm.impl` (`DingTalkJobAlarm`, `EmailJobAlarm`, `FeishuJobAlarm`, `WeComJobAlarm`, `WebhookJobAlarm`) (Java: package-private (no modifier), or leave its package out of `module-info` exports): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
  • Hide `com.cc.job.admin.task.service.impl` (`AdminBizImpl`, `DataxServiceImpl`, `JobCanvasBookmarkServiceImpl`, `JobComposeServiceImpl`, `LfNode`, `LfEdge`, `JobEdgeServiceImpl`, `JobGroupServiceImpl`, and 12 more) (Java: package-private (no modifier), or leave its package out of `module-info` exports): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
  • Hide `com.xxl.job.core.biz.impl` (`ExecutorBizImpl`) (Java: package-private (no modifier), or leave its package out of `module-info` exports): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
  • Hide `com.xxl.job.core.executor.impl` (`XxlJobSimpleExecutor`, `XxlJobSpringExecutor`) (Java: package-private (no modifier), or leave its package out of `module-info` exports): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
  • Hide `com.xxl.job.core.glue.impl` (`SpringGlueFactory`) (Java: package-private (no modifier), or leave its package out of `module-info` exports): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
  • Hide `com.xxl.job.core.handler.impl` (`CSharpGlueJobHandler`, `GlueJobHandler`, `MethodJobHandler`, `ScriptJobHandler`) (Java: package-private (no modifier), or leave its package out of `module-info` exports): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
P2 · Observability10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.

Method: Filesystem/Roslyn scan: structured-logging frameworks (Serilog, NLog), OpenTelemetry, and health-check endpoint patterns. Exhaustive, deterministic.

P3 · Security & performance tooling0.0 / 10Critical✓ Tool-verified

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

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

  • No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
  • `cc-job/cc-job-admin/pom.xml` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — cc-job/cc-job-admin/pom.xml:17

What to do

  • Run what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
  • Enable Dependabot/Renovate or a dependency-review gate.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback5.0 / 10Adequate✓ Tool-verified

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

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

What to do

  • Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P7 · Outbound HTTP resilience10.0 / 10Exemplary○ Nothing flagged

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.

X13 · Undrained process stream4.8 / 10Weak✓ Tool-verified

Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.

Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.

  • The JDK pipes both `stdout` and `stderr` of this child — no `redirectErrorStream`, `redirectError`, `redirectOutput` or `inheritIO` is set — and the parent waits on `process.waitFor()` while nothing in this scope ever reads stdout and stderr. The JDK's own `Process` documentation warns that failing to read a child's output promptly "may cause the process to block, or even deadlock": once the child writes more than the pipe holds (measured on OpenJDK 25 / Linux: 60,000 bytes finishes, 70,000 hangs forever), it blocks on the write, never exits, and the wait never returns. Nothing fails loudly. Read every piped stream before (or while) waiting — a thread or `CompletableFuture` per stream — merge them with `redirectErrorStream(true)` and read the one stream before `waitFor`, or discard what you do not want with `redirectOutput`/`redirectError(ProcessBuilder.Redirect.DISCARD)` (or a file). — cc-job/cc-job-core/src/main/java/com/xxl/job/core/glue/CSharpGlueFactory.java:455
  • The JDK pipes both `stdout` and `stderr` of this child — no `redirectErrorStream`, `redirectError`, `redirectOutput` or `inheritIO` is set — and the parent waits on `process.waitFor()` while nothing in this scope ever reads stderr. The JDK's own `Process` documentation warns that failing to read a child's output promptly "may cause the process to block, or even deadlock": once the child writes more than the pipe holds (measured on OpenJDK 25 / Linux: 60,000 bytes finishes, 70,000 hangs forever), it blocks on the write, never exits, and the wait never returns. Nothing fails loudly. Read every piped stream before (or while) waiting — a thread or `CompletableFuture` per stream — merge them with `redirectErrorStream(true)` and read the one stream before `waitFor`, or discard what you do not want with `redirectOutput`/`redirectError(ProcessBuilder.Redirect.DISCARD)` (or a file). — cc-job/cc-job-core/src/main/java/com/xxl/job/core/glue/CSharpGlueFactory.java:470

What to do

  • Each finding names the span that makes the branch dead and the span it is dead because of. Confirm from the two, then delete the dead arm or fix the predicate that was meant to be reachable.
X14 · Bypassable address classification10.0 / 10Exemplary○ Nothing flagged

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.

X16 · Unfloored truncation loop10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.

Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.

X18 · Disposal-pattern correctness10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.

Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.

X19 · Unrestored process-global state10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.

Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.

X23 · Unguarded diagnostic materialisation10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.

Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.

X24 · Document value interpolated into markup unescaped10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.

Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.

X25 · Inert configuration knob6.1 / 10Adequate✓ Tool-verified

Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.

Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.

  • `ConditionNodeDialog` takes `editData` from the caller and stores it in `conditionData` on line 80, defaulting to `new ConditionData()` when none is supplied — but `conditionData` is never read anywhere in the type, and line 393 spells `new ConditionData()` out again where that field's value belongs. Every caller that passes `editData` therefore gets `new ConditionData()` regardless, and nothing in the type reports that its argument was ignored. Read `conditionData` at line 393 — or, if the value genuinely is fixed, delete `editData` and `conditionData` together so the signature stops advertising a knob that does nothing. — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ConditionNodeDialog.java:393

What to do

  • Each finding names the spans that disagree — the knob the caller supplies and the site that ignores it, whether by re-spelling its default, by falling back under the wrong key, by parsing with no format provider at all, or by printing under whatever culture the host supplies. Confirm from those spans, then decide which of the two the type meant: read the knob at the named site, or drop the knob so the signature stops advertising something the type cannot feel. Leaving both is the one option that cannot be right.
X26 · Unsynchronised callback handoff10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a value handed from a callback to the body that waits on it crosses on something built to be crossed — a `Queue<T>`/`List<T>`/`Dictionary<K,V>` written inside an event handler and read back outside it is mutated by two flows at once, and the semaphore or completion source beside it orders how MANY items exist while leaving the collection's own head, tail and backing array unprotected.

Method: Roslyn syntax: method, accessor, local-function and lambda bodies that declare BOTH a non-thread-safe generic collection (`Queue`/`Stack`/`List`/`Dictionary`/`HashSet`/`Sorted*`/`LinkedList`) and a synchronisation primitive (`SemaphoreSlim`/`TaskCompletionSource`/`ManualResetEvent(Slim)`/`AutoResetEvent`/`CountdownEvent`) as locals, then read for a `+=`-registered lambda that raises that primitive while the body outside every lambda waits on it — and, in that scope, a mutating call on the collection inside the lambda paired with a mention of it outside. Any `lock` in the scope abstains it. On a repository with no .NET source the same handoff is read in Java off the engine’s own token stream (test source sets, vendored and demonstration paths not): an `ArrayList`/`LinkedList`/`ArrayDeque`/`PriorityQueue`/`Hash*`/`LinkedHash*`/`Tree*` local and a `CountDownLatch`/`Semaphore`/`CompletableFuture` local, a lambda or anonymous class that raises the primitive and mutates the collection, and a wait outside it; any `synchronized` or `lock()` abstains the body. Because each of those primitives orders what the callback wrote before raising it, only a touch that provably overlaps the callback is convicted: one after the registration and before the next wait, or one in a loop registered-before, waiting on every pass and not declaring the collection. Deterministic, provable per finding. Advisory.

X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether an enhanced `for` leaves the collection it is walking alone — a body that adds to or removes from the very collection the loop is iterating invalidates the fail-fast iterator it is holding, so the next `next()` throws `ConcurrentModificationException` and the remaining elements are never seen.

Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.

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.

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.

X3 · Exception handling6.8 / 10Adequate✓ Tool-verified

Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.

Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.

  • An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×18) — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/CcJobGuiApplication.java:110, cc-job/cc-job-gui/src/main/java/com/cc/job/gui/CcJobGuiApplication.java:178, cc-job/cc-job-gui/src/main/java/com/cc/job/gui/CcJobGuiApplication.java:204, …
  • `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×16) — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/LogPanel.java:741, cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:2417, cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:1031, …

What to do

  • Swallowed exception (empty catch)
X4 · Structured logging6.9 / 10Adequate✓ Tool-verified

Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.

Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `package.json` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.

  • `info` at line 332 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:332
  • `info` at line 549 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:549
  • `info` at line 841 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:841
  • `info` at line 872 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:872
  • `info` at line 885 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:885
  • `info` at line 1048 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:1048
  • `warn` at line 1380 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:1380
  • `info` at line 1403 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:1403
  • `info` at line 1732 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:1732
  • `warn` at line 1737 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:1737
  • `info` at line 1745 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:1745
  • `info` at line 1775 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:1775
  • `warn` at line 1778 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:1778
  • `info` at line 1788 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:1788
  • `warn` at line 1791 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:1791
  • `info` at line 1838 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:1838
  • `info` at line 1954 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:1954
  • `info` at line 2363 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:2363
  • `info` at line 2409 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:2409
  • `info` at line 2517 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:2517
  • `info` at line 2602 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:2602
  • `info` at line 2852 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:2852
  • `info` at line 2891 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:2891
  • `warn` at line 2894 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:2894
  • `info` at line 3053 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:3053
  • `debug` at line 367 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeHistoryView.java:367
  • `warn` at line 1003 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobLogListDialog.java:1003
  • `debug` at line 1252 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobLogListDialog.java:1252
  • `info` at line 97 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DialogManager.java:97
  • `info` at line 104 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DialogManager.java:104
  • `info` at line 139 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DialogManager.java:139
  • `info` at line 146 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DialogManager.java:146
  • `info` at line 172 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/NodeCallbackConfigurator.java:172
  • `info` at line 193 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/NodeCallbackConfigurator.java:193
  • `info` at line 203 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/NodeCallbackConfigurator.java:203
  • `error` at line 206 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/NodeCallbackConfigurator.java:206
  • `error` at line 214 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/NodeCallbackConfigurator.java:214
  • `error` at line 663 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/NodeOperationManager.java:663
  • `error` at line 708 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/NodeOperationManager.java:708
  • `error` at line 735 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/NodeOperationManager.java:735

What to do

  • Interpolated log message defeats structured logging
X5 · Nullable reference types2.0 / 10Critical✓ Tool-verified

Other · Code Health — Whether Java packages are null-marked and not undermined by heavy nullness suppression — a package under `@NullMarked` (or `@NonNullApi`, `@ParametersAreNonnullByDefault`, `@NonNullByDefault`, or a NullAway/Checker Framework configuration naming it) makes an unannotated reference exclude null, and `@SuppressWarnings("NullAway")`, `("nullness")`, `("null")` and `castToNonNull(…)` are what silence it.

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

  • 0/118 of this repository's Java package directories are under a non-null default: a `package-info.java` declaring `@NullMarked` (JSpecify) or `@NonNullApi`, `@ParametersAreNonnullByDefault`, `@NonNullByDefault`, `@DefaultQualifier(NonNull.class)`; a `module-info.java` declaring `@NullMarked`; every type in it `@NullMarked`; or a build that runs NullAway with the package in `AnnotatedPackages`, or the Checker Framework's `NullnessChecker`. Elsewhere every reference admits null and no checker warns on the dereference that throws a `NullPointerException`.

What to do

  • Declare the default where Java declares it: `@NullMarked` (org.jspecify.annotations) in each package's `package-info.java`, or once in `module-info.java`, and run NullAway (Error Prone) or the Checker Framework so the declaration is enforced. Then annotate the real exceptions `@Nullable` and resolve the suppressions rather than adding to them: a `@SuppressWarnings("NullAway")` or `castToNonNull(x)` on a value the checker could show to be null is a `NullPointerException` waiting for the path that makes it true — where the value genuinely cannot be null, say something the checker can see instead (a null check, `Objects.requireNonNull`, a non-null field initialised in the constructor).

Reference — by lens

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

LensScoreRatingImpact
Code Health55.2Adequate — gated by D4, X5Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture91.6Adequate — gated by D26Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity32.0Weak — gated by D34, M2, M4Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness40.5Weak — gated by P1, P3Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security75.5Checked 4 of 10Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Unscored — 2 check(s) recorded observations but carry no score

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

  • X10 Duplicated predicate — 40 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X7 Silent fallback defaults — 5 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 5 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
  • P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
Not included — 53 check(s) not relevant to this codebase

These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.

  • AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
  • AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
  • AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
  • AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
  • AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
  • AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
  • AX4 Dependency direction — not applicable to a transaction-script/CRUD architecture (the inward-dependency rule is for layered/clean styles)
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AX8 Test isolation — no test/production split to check
  • AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • AXR1 Runtime accessibility — the service did not build — `mvn -B -q -DskipTests compile` exited 1: ; runtime evidence skipped (launch chosen because cc-job/cc-job-admin/pom.xml declares spring-boot-starter-web and the Spring Boot Maven plugin) 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 included — the .java suite was found but not re-run
  • D12 Dependency Hygiene — Not scored — a Maven build resolved 68 artifact(s) (65 behind a shipped release, reported), but the build resolved only part of the graph, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
  • D16 Bus Factor — single-maintainer repository — bus factor is not applicable
  • 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.
  • D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
  • D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
  • D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .java, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
  • D25 ADR Conformance — no ADRs to check
  • D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
  • D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
  • D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
  • D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
  • D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
  • D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
  • D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
  • D8 Code Coverage — Coverage not included — suite not readable by the collector
  • DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (6 value object(s))
  • ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
  • ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
  • ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
  • P12 CI test-gate honesty — no CI workflow found
  • P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
  • P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
  • PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a REDACTED, Gradle or sbt build, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
  • PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
  • PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
  • S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • X1 Async correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X12 Unreachable branch — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X17 Uncapped recursion over a caller-supplied document — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X2 Cancellation propagation — no C# was loaded; this repository's Java was read, and no request in it can be cancelled by a caller — a Java request off Android takes no token: it is cancelled through the handle it returns (Future.cancel, Call.cancel, a Disposable), ambiently (io.grpc.Context) or by interrupting its thread, not through a parameter
  • X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X21 Side-effecting pattern guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X32 Type resolved by simple name across every loaded assembly — 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.
  • X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

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

Critical — 21 finding(s)
D30 · Dependency Vulnerabilities · High CVE · ×12
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D30 · Dependency Vulnerabilities · Critical CVE · ×3
  • REDACTED
  • REDACTED
  • REDACTED
D28 · Secrets (history) · High secret · ×2
  • REDACTED
  • REDACTED
D31 · IaC & Container Security · High IaC · ×2
  • REDACTED
  • REDACTED
D28 · Secrets (history) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
Serious — 1168 finding(s)
D3 · God Classes · MethodTooLong · ×34
  • MethodTooLong: MainView.setupCallbacks cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:261 — MethodTooLong — setupCallbacks runs 893 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 793 over it, 8.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: CronExpression.getTimeAfter cc-job/cc-job-admin/src/main/java/com/cc/job/admin/cron/CronExpression.java:1162 — MethodTooLong — getTimeAfter runs 281 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 181 over it, 2.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.
  • MethodTooLong: ShowDataxSyncDialog.createReaderPane cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:747 — MethodTooLong — createReaderPane runs 209 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 109 over it, 2.09× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: JobComposeServiceImpl.operateToSaveJobCompose cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:321 — MethodTooLong — operateToSaveJobCompose runs 190 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 90 over it, 1.90× 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: NodeCallbackConfigurator.configureNodeCallbacks cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/NodeCallbackConfigurator.java:59 — MethodTooLong — configureNodeCallbacks runs 185 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 85 over it, 1.85× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: MainView.setupTreeViewCallback cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:1638 — MethodTooLong — setupTreeViewCallback runs 176 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 76 over it, 1.76× 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: NotificationToast.show cc-job/cc-job-gui/src/main/java/com/cc/job/gui/util/NotificationToast.java:62 — MethodTooLong — show runs 174 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 74 over it, 1.74× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: ShowJobListDialog.createTable cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:316 — MethodTooLong — createTable runs 172 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 72 over it, 1.72× 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: ShowDatasourceListDialog.showDatasourceFormDialog cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:466 — MethodTooLong — showDatasourceFormDialog runs 168 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 68 over it, 1.68× 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: NodeDetailsDialog.loadDetails cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeDetailsDialog.java:233 — MethodTooLong — loadDetails runs 147 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 47 over it, 1.47× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: JobComposeServiceImpl.buildAllNodesAndEdgesRecursive cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:1006 — MethodTooLong — buildAllNodesAndEdgesRecursive runs 145 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 45 over it, 1.45× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: TopToolBar.createToolBar cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/TopToolBar.java:845 — MethodTooLong — createToolBar runs 141 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 41 over it, 1.41× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: CronExpression.storeExpressionVals cc-job/cc-job-admin/src/main/java/com/cc/job/admin/cron/CronExpression.java:517 — MethodTooLong — storeExpressionVals runs 137 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 37 over it, 1.37× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: ShowDataxSyncDialog.createWriterPane cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1000 — MethodTooLong — createWriterPane runs 137 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 37 over it, 1.37× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: TaskGroupOrchestrator.prepareExecution cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/orchestrator/TaskGroupOrchestrator.java:199 — MethodTooLong — prepareExecution runs 131 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 31 over it, 1.31× 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: JobComposeServiceImpl.operateToUpdateJobCompose cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:702 — MethodTooLong — operateToUpdateJobCompose runs 128 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 28 over it, 1.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: ShowDataxGroupSyncDialog.createResultPane cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:444 — MethodTooLong — createResultPane runs 127 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 27 over it, 1.27× 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: JobComposeServiceImpl.saveJobNodeAndJobEdges cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:1424 — MethodTooLong — saveJobNodeAndJobEdges runs 125 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 25 over it, 1.25× 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: ShowJobLogListDialog.showExecutionLogDialog cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobLogListDialog.java:758 — MethodTooLong — showExecutionLogDialog runs 125 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 25 over it, 1.25× 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: ProcessNode.setupContextMenu cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ProcessNode.java:689 — MethodTooLong — setupContextMenu runs 121 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 21 over it, 1.21× 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: ConditionNode.<init> cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:109 — MethodTooLong — <init> runs 118 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 18 over it, 1.18× 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: NodeDetailsDialog.<init> cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeDetailsDialog.java:37 — MethodTooLong — <init> runs 118 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 18 over it, 1.18× 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: JobScheduleHelper.start cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/thread/JobScheduleHelper.java:39 — MethodTooLong — start runs 115 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 15 over it, 1.15× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: JobThread.run cc-job/cc-job-core/src/main/java/com/xxl/job/core/thread/JobThread.java:98 — MethodTooLong — run runs 115 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 15 over it, 1.15× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: NodeCanvas.loadFromComposeData cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:2060 — MethodTooLong — loadFromComposeData runs 115 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 15 over it, 1.15× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • + 9 more in this group — see findings.md.
D3 · God Classes · TooManyMethods · ×31
  • TooManyMethods: NodeCanvas cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:37 — TooManyMethods — 214 methods. The bar is 30 methods; this is 184 over it, 7.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: 1 cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:263 — TooManyMethods — 119 methods. The bar is 30 methods; this is 89 over it, 3.97× the bar. Most of these members implement view.ToolBarCallback (118 of 118 members), so moving them onto a smaller type would remove them from that contract rather than reduce it. To reduce it, split the contract instead: give each cohesive group of operations its own smaller interface and its own implementing type. Where the contract has to stay whole, move the work behind these members into collaborator types, so what is left here is a forward per member rather than a responsibility per member.
  • TooManyMethods: ProcessNode cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ProcessNode.java:29 — TooManyMethods — 98 methods. The bar is 30 methods; this is 68 over it, 3.27× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: JobInfo cc-job/cc-job-xo/src/main/java/com/cc/job/xo/model/entity/JobInfo.java:16 — TooManyMethods — 81 methods. The bar is 30 methods; this is 51 over it, 2.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: JobInfoForm cc-job/cc-job-xo/src/main/java/com/cc/job/xo/model/form/JobInfoForm.java:18 — TooManyMethods — 78 methods. The bar is 30 methods; this is 48 over it, 2.60× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: TaskInfoData cc-job/cc-job-xo/src/main/java/com/cc/job/xo/model/dto/PartitionExportData.java:121 — TooManyMethods — 74 methods. The bar is 30 methods; this is 44 over it, 2.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: ShowDataxSyncDialog cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:44 — TooManyMethods — 70 methods. The bar is 30 methods; this is 40 over it, 2.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: JobInfoVO cc-job/cc-job-xo/src/main/java/com/cc/job/xo/model/vo/JobInfoVO.java:17 — TooManyMethods — 60 methods. The bar is 30 methods; this is 30 over it, 2.00× 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: ConditionNode cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:30 — TooManyMethods — 56 methods. The bar is 30 methods; this is 26 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.
  • TooManyMethods: LogPanel cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/LogPanel.java:31 — TooManyMethods — 56 methods. The bar is 30 methods; this is 26 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.
  • TooManyMethods: MainView cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:40 — TooManyMethods — 47 methods. The bar is 30 methods; this is 17 over it, 1.57× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: ShowDataxGroupSyncDialog cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:44 — TooManyMethods — 46 methods. The bar is 30 methods; this is 16 over it, 1.53× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: TriggerParam cc-job/cc-job-core/src/main/java/com/xxl/job/core/biz/model/TriggerParam.java:11 — 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: NodeConnection cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/NodeConnection.java:25 — TooManyMethods — 43 methods. The bar is 30 methods; this is 13 over it, 1.43× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: TopToolBar cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/TopToolBar.java:41 — TooManyMethods — 41 methods. The bar is 30 methods; this is 11 over it, 1.37× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: JobInfoController cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/controller/JobInfoController.java:45 — TooManyMethods — 38 methods. The bar is 30 methods; this is 8 over it, 1.27× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: GroupContainer cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/GroupContainer.java:26 — TooManyMethods — 38 methods. The bar is 30 methods; this is 8 over it, 1.27× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: CanvasSelectionManager cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasSelectionManager.java:17 — 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: DataXParams cc-job/cc-job-xo/src/main/java/com/cc/job/xo/model/datax/DataXParams.java:7 — 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: PermissionManageDialog cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/PermissionManageDialog.java:41 — TooManyMethods — 36 methods. The bar is 30 methods; this is 6 over it, 1.20× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: JobLogVO cc-job/cc-job-xo/src/main/java/com/cc/job/xo/model/vo/JobLogVO.java:15 — TooManyMethods — 36 methods. The bar is 30 methods; this is 6 over it, 1.20× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: TaskNavigationBar cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/TaskNavigationBar.java:33 — TooManyMethods — 35 methods. The bar is 30 methods; this is 5 over it, 1.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: TaskTreeView cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/TaskTreeView.java:24 — TooManyMethods — 35 methods. The bar is 30 methods; this is 5 over it, 1.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: JobNodeVo cc-job/cc-job-xo/src/main/java/com/cc/job/xo/model/vo/JobNodeVo.java:8 — TooManyMethods — 35 methods. The bar is 30 methods; this is 5 over it, 1.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: CronExpression cc-job/cc-job-admin/src/main/java/com/cc/job/admin/cron/CronExpression.java:193 — TooManyMethods — 34 methods. The bar is 30 methods; this is 4 over it, 1.13× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • + 6 more in this group — see findings.md.
D15 · Churn × Complexity Hotspots · Hotspot · ×26
  • Hotspot: cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:2060 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java changed 34 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 56 in NodeCanvas.loadFromComposeData at line 2060. 2 of those changes were fix/bug commits, and the other 32 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 2025-12-15..2026-03-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2025-12-15 09:48:41 +08:00' --until='2026-03-15 09:48:41 +08:00' --full-history --no-merges -- cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:434 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java changed 19 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 76 in ShowDataxSyncDialog.applyEditData at line 434. 1 of those changes was a fix/bug commit, and the other 18 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 2025-12-15..2026-03-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2025-12-15 09:48:41 +08:00' --until='2026-03-15 09:48:41 +08:00' --full-history --no-merges -- cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:261 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java changed 44 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 30 in MainView.setupCallbacks at line 261. 2 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 2025-12-15..2026-03-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2025-12-15 09:48:41 +08:00' --until='2026-03-15 09:48:41 +08:00' --full-history --no-merges -- cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:321 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 63 in JobComposeServiceImpl.operateToSaveJobCompose at line 321. 1 of those changes was a fix/bug commit, and the other 10 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 2025-12-15..2026-03-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2025-12-15 09:48:41 +08:00' --until='2026-03-15 09:48:41 +08:00' --full-history --no-merges -- cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ProcessNode.java cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ProcessNode.java:532 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ProcessNode.java changed 21 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 27 in ProcessNode.setupDragHandlers at line 532. 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 2025-12-15..2026-03-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2025-12-15 09:48:41 +08:00' --until='2026-03-15 09:48:41 +08:00' --full-history --no-merges -- cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ProcessNode.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/orchestrator/TaskGroupOrchestrator.java cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/orchestrator/TaskGroupOrchestrator.java:199 — cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/orchestrator/TaskGroupOrchestrator.java changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 38 in TaskGroupOrchestrator.prepareExecution at line 199. 2 of those changes were fix/bug commits, and the other 10 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 2025-12-15..2026-03-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2025-12-15 09:48:41 +08:00' --until='2026-03-15 09:48:41 +08:00' --full-history --no-merges -- cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/orchestrator/TaskGroupOrchestrator.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:1130 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java changed 15 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 27 in NewJobNodeDialog.fillFormData at line 1130. 3 of those changes were fix/bug commits, and the other 12 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2025-12-15..2026-03-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2025-12-15 09:48:41 +08:00' --until='2026-03-15 09:48:41 +08:00' --full-history --no-merges -- cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:862 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java changed 13 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 31 in NewJobDialog.fillFormData at line 862. 2 of those changes were fix/bug commits, and the other 11 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 2025-12-15..2026-03-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2025-12-15 09:48:41 +08:00' --until='2026-03-15 09:48:41 +08:00' --full-history --no-merges -- cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobInfoServiceImpl.java cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobInfoServiceImpl.java:366 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobInfoServiceImpl.java changed 17 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in JobInfoServiceImpl.triggerJob at line 366. 2 of those changes were fix/bug commits, and the other 15 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 2025-12-15..2026-03-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2025-12-15 09:48:41 +08:00' --until='2026-03-15 09:48:41 +08:00' --full-history --no-merges -- cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobInfoServiceImpl.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/NodeCallbackConfigurator.java cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/NodeCallbackConfigurator.java:59 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/NodeCallbackConfigurator.java changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 37 in NodeCallbackConfigurator.configureNodeCallbacks at line 59. 1 of those changes was a fix/bug commit, and the other 9 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 2025-12-15..2026-03-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2025-12-15 09:48:41 +08:00' --until='2026-03-15 09:48:41 +08:00' --full-history --no-merges -- cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/NodeCallbackConfigurator.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasDataLoader.java cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasDataLoader.java:47 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasDataLoader.java changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 48 in CanvasDataLoader.createNodeFromData at line 47. 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 2025-12-15..2026-03-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2025-12-15 09:48:41 +08:00' --until='2026-03-15 09:48:41 +08:00' --full-history --no-merges -- cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasDataLoader.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/component/SmartParameterInput.java cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/component/SmartParameterInput.java:769 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/component/SmartParameterInput.java changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 40 in SmartParameterInput.handleSmartDelete at line 769. 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 2025-12-15..2026-03-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2025-12-15 09:48:41 +08:00' --until='2026-03-15 09:48:41 +08:00' --full-history --no-merges -- cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/component/SmartParameterInput.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/TaskExecutionManager.java cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/TaskExecutionManager.java:224 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/TaskExecutionManager.java changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in TaskExecutionManager.handleSSEMessage at line 224. 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 2025-12-15..2026-03-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2025-12-15 09:48:41 +08:00' --until='2026-03-15 09:48:41 +08:00' --full-history --no-merges -- cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/TaskExecutionManager.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:811 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in ShowDataxGroupSyncDialog.handleNext at line 811. 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 2025-12-15..2026-03-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2025-12-15 09:48:41 +08:00' --until='2026-03-15 09:48:41 +08:00' --full-history --no-merges -- cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobLogListDialog.java cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobLogListDialog.java:462 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobLogListDialog.java changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in ShowJobLogListDialog.loadPage at line 462. 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 2025-12-15..2026-03-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2025-12-15 09:48:41 +08:00' --until='2026-03-15 09:48:41 +08:00' --full-history --no-merges -- cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobLogListDialog.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:663 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 37 in ConditionNode.bindCanvasNodes at line 663. 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 2025-12-15..2026-03-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2025-12-15 09:48:41 +08:00' --until='2026-03-15 09:48:41 +08:00' --full-history --no-merges -- cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:466 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in ShowDatasourceListDialog.showDatasourceFormDialog at line 466. 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 2025-12-15..2026-03-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2025-12-15 09:48:41 +08:00' --until='2026-03-15 09:48:41 +08:00' --full-history --no-merges -- cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/resolver/ParameterResolver.java cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/resolver/ParameterResolver.java:163 — cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/resolver/ParameterResolver.java changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 41 in ParameterResolver.getValueFromContext at line 163. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2025-12-15..2026-03-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2025-12-15 09:48:41 +08:00' --until='2026-03-15 09:48:41 +08:00' --full-history --no-merges -- cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/resolver/ParameterResolver.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: REDACTED REDACTED:74 — REDACTED changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in JobPartServiceImpl.getTree at line 74. 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 2025-12-15..2026-03-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2025-12-15 09:48:41 +08:00' --until='2026-03-15 09:48:41 +08:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: cc-job/cc-job-core/src/main/java/com/xxl/job/core/thread/JobThread.java cc-job/cc-job-core/src/main/java/com/xxl/job/core/thread/JobThread.java:98 — cc-job/cc-job-core/src/main/java/com/xxl/job/core/thread/JobThread.java changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in JobThread.run at line 98. 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 2025-12-15..2026-03-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2025-12-15 09:48:41 +08:00' --until='2026-03-15 09:48:41 +08:00' --full-history --no-merges -- cc-job/cc-job-core/src/main/java/com/xxl/job/core/thread/JobThread.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasConnectionManager.java cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasConnectionManager.java:185 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasConnectionManager.java changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 25 in CanvasConnectionManager.configureConnectionInteractions at line 185. 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 2025-12-15..2026-03-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2025-12-15 09:48:41 +08:00' --until='2026-03-15 09:48:41 +08:00' --full-history --no-merges -- cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasConnectionManager.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: REDACTED REDACTED:210 — REDACTED changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in JobTriggerService.createTriggerParam at line 210. 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 2025-12-15..2026-03-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2025-12-15 09:48:41 +08:00' --until='2026-03-15 09:48:41 +08:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: cc-job/cc-job-core/src/main/java/com/xxl/job/core/biz/impl/ExecutorBizImpl.java cc-job/cc-job-core/src/main/java/com/xxl/job/core/biz/impl/ExecutorBizImpl.java:51 — cc-job/cc-job-core/src/main/java/com/xxl/job/core/biz/impl/ExecutorBizImpl.java changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 32 in ExecutorBizImpl.run at line 51. 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 2025-12-15..2026-03-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2025-12-15 09:48:41 +08:00' --until='2026-03-15 09:48:41 +08:00' --full-history --no-merges -- cc-job/cc-job-core/src/main/java/com/xxl/job/core/biz/impl/ExecutorBizImpl.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/service/HistoricalDataLoader.java cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/service/HistoricalDataLoader.java:44 — cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/service/HistoricalDataLoader.java changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 29 in HistoricalDataLoader.loadFromDatabase at line 44. 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 2025-12-15..2026-03-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2025-12-15 09:48:41 +08:00' --until='2026-03-15 09:48:41 +08:00' --full-history --no-merges -- cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/service/HistoricalDataLoader.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/thread/JobFailMonitorHelper.java cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/thread/JobFailMonitorHelper.java:38 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/thread/JobFailMonitorHelper.java changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in 1.run at line 38. 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 2025-12-15..2026-03-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2025-12-15 09:48:41 +08:00' --until='2026-03-15 09:48:41 +08:00' --full-history --no-merges -- cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/thread/JobFailMonitorHelper.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • + 1 more in this group — see findings.md.
D4 · Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) · ×25
  • Members sharing a duplicated core (4 members, 50+ identical tokens) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/alarm/impl/DingTalkJobAlarm.java:42 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/alarm/impl/DingTalkJobAlarm.java:42-81 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/alarm/impl/FeishuJobAlarm.java:38-72 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/alarm/impl/WeComJobAlarm.java:38-72 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/alarm/impl/WebhookJobAlarm.java:55-122 — 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) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/datax/reader/MysqlReader.java:23 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/datax/reader/MysqlReader.java:23-90 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/datax/reader/OracleReader.java:22-105 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/datax/writer/MysqlWriter.java:14-33 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/datax/writer/OracleWriter.java:15-34 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) REDACTED:326 — REDACTED:326-457 | REDACTED:464-538 | REDACTED:592-718 | REDACTED:725-831 — 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) cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/client/AdminApiClient.java:86 — cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/client/AdminApiClient.java:86-113 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/infrastructure/client/ApiClient.java:100-127 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/HttpClientUtil.java:89-116 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/util/ApiUtil.java:118-145 — 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) cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/client/AdminApiClient.java:191 — cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/client/AdminApiClient.java:191-210 | cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/client/AdminApiClient.java:218-243 | cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/client/AdminApiClient.java:251-270 | cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/client/AdminApiClient.java:278-297 — 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) cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/client/AdminApiClient.java:537 — cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/client/AdminApiClient.java:537-566 | cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/client/AdminApiClient.java:574-598 | cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/client/AdminApiClient.java:606-630 | cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/client/AdminApiClient.java:639-664 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/infrastructure/client/ApiClient.java:168 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/infrastructure/client/ApiClient.java:168-205 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/infrastructure/client/ApiClient.java:233-271 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/infrastructure/client/ApiClient.java:290-328 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/infrastructure/client/ApiClient.java:345-382 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:485 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:485-516 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:1062-1170 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/GroupContainer.java:464-496 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/GroupContainer.java:688-777 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobDataxService.java:33 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobDataxService.java:33-50 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobJdbcDatasourceService.java:39-58 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobJdbcDatasourceService.java:63-88 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobJdbcDatasourceService.java:93-110 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobDataxService.java:55 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobDataxService.java:55-85 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobDataxService.java:90-108 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobDataxService.java:113-131 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobJdbcDatasourceService.java:115-129 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobJdbcDatasourceService.java:115 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobJdbcDatasourceService.java:115-129 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobJdbcDatasourceService.java:134-148 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobJdbcDatasourceService.java:153-166 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobPartService.java:458-501 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobPartService.java:396 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobPartService.java:396-413 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobPartService.java:421-436 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobPartService.java:458-501 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobPartService.java:510-541 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ConditionNodeDialog.java:133 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ConditionNodeDialog.java:133-158 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:182-227 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java:115-147 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:196-240 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/GlueIdeDialog.java:62 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/GlueIdeDialog.java:62-122 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:100-180 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java:50-110 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:107-191 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:1148 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:1148-1172 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:1908-1932 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:2948-2997 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:3002-3066 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MiniMapView.java:217 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MiniMapView.java:217-319 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MiniMapView.java:324-376 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MiniMapView.java:381-446 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MiniMapView.java:451-505 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:451 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:451-469 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java:268-292 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:456-480 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1426-1443 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:988 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:988-1026 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1888-1929 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobLogListDialog.java:1033-1105 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/component/SmartParameterInput.java:228-293 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:4327 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:4327-4337 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:4340-4350 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:4364-4374 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:4377-4387 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:4787 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:4787-4803 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:4808-4824 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:4848-4864 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:4869-4885 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:324 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:324-387 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowExecutorListDialog.java:321-384 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:691-753 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobLogListDialog.java:397-460 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:844 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:844-860 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowExecutorListDialog.java:591-607 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:1024-1040 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobLogListDialog.java:1107-1149 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:879 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:879-897 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowExecutorListDialog.java:655-675 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:1186-1207 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobLogListDialog.java:1185-1205 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:244 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:244-370 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:372-442 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:747-998 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1000-1166 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:2272 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:2272-2304 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:2308-2329 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:2332-2364 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:2367-2382 — 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.
D3 · God Classes · ClassTooLong · ×24
  • ClassTooLong: NodeCanvas cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:37 — ClassTooLong — 2753 significant lines (blank, comment-only and punctuation-only lines excluded), 214 methods. The bar is 400 significant lines; this is 2353 over it, 6.88× 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: MainView cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:40 — ClassTooLong — 2075 significant lines (blank, comment-only and punctuation-only lines excluded), 47 methods. The bar is 400 significant lines; this is 1675 over it, 5.19× 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: ShowDataxSyncDialog cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:44 — ClassTooLong — 1822 significant lines (blank, comment-only and punctuation-only lines excluded), 70 methods. The bar is 400 significant lines; this is 1422 over it, 4.56× 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: JobComposeServiceImpl cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:39 — ClassTooLong — 1183 significant lines (blank, comment-only and punctuation-only lines excluded), 26 methods. The bar is 400 significant lines; this is 783 over it, 2.96× 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: ProcessNode cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ProcessNode.java:29 — ClassTooLong — 1080 significant lines (blank, comment-only and punctuation-only lines excluded), 98 methods. The bar is 400 significant lines; this is 680 over it, 2.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.
  • ClassTooLong: NewJobNodeDialog cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:51 — ClassTooLong — 1072 significant lines (blank, comment-only and punctuation-only lines excluded), 24 methods. The bar is 400 significant lines; this is 672 over it, 2.68× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: TopToolBar cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/TopToolBar.java:41 — ClassTooLong — 1017 significant lines (blank, comment-only and punctuation-only lines excluded), 41 methods. The bar is 400 significant lines; this is 617 over it, 2.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: ShowDataxGroupSyncDialog cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:44 — ClassTooLong — 1001 significant lines (blank, comment-only and punctuation-only lines excluded), 46 methods. The bar is 400 significant lines; this is 601 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.
  • ClassTooLong: NewJobDialog cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:40 — ClassTooLong — 964 significant lines (blank, comment-only and punctuation-only lines excluded), 23 methods. The bar is 400 significant lines; this is 564 over it, 2.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: CronExpression cc-job/cc-job-admin/src/main/java/com/cc/job/admin/cron/CronExpression.java:193 — ClassTooLong — 949 significant lines (blank, comment-only and punctuation-only lines excluded), 34 methods. The bar is 400 significant lines; this is 549 over it, 2.37× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: PermissionManageDialog cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/PermissionManageDialog.java:41 — ClassTooLong — 876 significant lines (blank, comment-only and punctuation-only lines excluded), 36 methods. The bar is 400 significant lines; this is 476 over it, 2.19× 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: ConditionNode cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:30 — ClassTooLong — 865 significant lines (blank, comment-only and punctuation-only lines excluded), 56 methods. The bar is 400 significant lines; this is 465 over it, 2.16× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: JobInfoServiceImpl cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobInfoServiceImpl.java:75 — ClassTooLong — 813 significant lines (blank, comment-only and punctuation-only lines excluded), 31 methods. The bar is 400 significant lines; this is 413 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: ShowJobLogListDialog cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobLogListDialog.java:52 — ClassTooLong — 810 significant lines (blank, comment-only and punctuation-only lines excluded), 30 methods. The bar is 400 significant lines; this is 410 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: ShowJobListDialog cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:36 — ClassTooLong — 767 significant lines (blank, comment-only and punctuation-only lines excluded), 34 methods. The bar is 400 significant lines; this is 367 over it, 1.92× 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: LogPanel cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/LogPanel.java:31 — ClassTooLong — 710 significant lines (blank, comment-only and punctuation-only lines excluded), 56 methods. The bar is 400 significant lines; this is 310 over it, 1.78× 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: ShowDatasourceListDialog cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:36 — ClassTooLong — 659 significant lines (blank, comment-only and punctuation-only lines excluded), 30 methods. The bar is 400 significant lines; this is 259 over it, 1.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: GroupContainer cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/GroupContainer.java:26 — ClassTooLong — 600 significant lines (blank, comment-only and punctuation-only lines excluded), 38 methods. The bar is 400 significant lines; this is 200 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: JobPartServiceImpl REDACTED:42 — ClassTooLong — 594 significant lines (blank, comment-only and punctuation-only lines excluded), 12 methods. The bar is 400 significant lines; this is 194 over it, 1.49× 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: TaskGroupOrchestrator cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/orchestrator/TaskGroupOrchestrator.java:49 — ClassTooLong — 560 significant lines (blank, comment-only and punctuation-only lines excluded), 30 methods. The bar is 400 significant lines; this is 160 over it, 1.40× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: NodeOperationManager cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/NodeOperationManager.java:21 — ClassTooLong — 474 significant lines (blank, comment-only and punctuation-only lines excluded), 24 methods. The bar is 400 significant lines; this is 74 over it, 1.19× 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: ShowExecutorListDialog cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowExecutorListDialog.java:31 — ClassTooLong — 455 significant lines (blank, comment-only and punctuation-only lines excluded), 21 methods. The bar is 400 significant lines; this is 55 over it, 1.14× 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: NewJobGroupDialog cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java:22 — ClassTooLong — 455 significant lines (blank, comment-only and punctuation-only lines excluded), 14 methods. The bar is 400 significant lines; this is 55 over it, 1.14× 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: TaskNavigationBar cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/TaskNavigationBar.java:33 — ClassTooLong — 448 significant lines (blank, comment-only and punctuation-only lines excluded), 35 methods. The bar is 400 significant lines; this is 48 over it, 1.12× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication · Duplicated block (8 lines × 2) · ×23
  • Duplicated block (8 lines × 2) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:485 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:485-492 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:761-768 — both copies are in the same file, so extract the 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) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:1074 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:1074-1081 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:1140-1147 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:1074` it does not close everything it opens, so those exact lines 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DataManager.java:189 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DataManager.java:189-196 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DataManager.java:218-225 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DataManager.java: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.
  • Duplicated block (8 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/AddBookmarkDialog.java:62 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/AddBookmarkDialog.java:62-69 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/SaveNodeTemplateDialog.java:71-78 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/AddBookmarkDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/SaveNodeTemplateDialog.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/AddJobFromListDialog.java:115 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/AddJobFromListDialog.java:115-122 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:152-159 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/AddJobFromListDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 175 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/AddJobFromListDialog.java:115` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/CanvasExportDialog.java:61 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/CanvasExportDialog.java:61-68 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeApprovalSettingDialog.java: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. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/CanvasExportDialog.java:61` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/LogPanel.java:601 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/LogPanel.java:601-608 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/TaskNavigationBar.java:245-252 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/LogPanel.java:601` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note first that the copies are not typed on the same thing: the declarations holding them bind `tab` to `LogTabManager.LogTab` in one and `TaskTab` 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:679 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:679-686 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:2928-2935 — both copies are in the same file, so extract the 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:2371 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:2371-2379 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:2857-2864 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:2371` it begins part-way through the construct above it, so those exact lines 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:4673 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:4673-4680 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:4701-4708 — both copies are in the same file, so extract the 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:1124 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:1124-1131 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:1141-1148 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:1124` it does not close everything it opens, so those exact lines 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:1297 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:1297-1304 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:2555-2562 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java` as WHOLE FILES: this scan already matched 42 separate duplicated blocks between them, totalling at least 585 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (8 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java:470 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java:470-477 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:1132-1139 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java` as WHOLE FILES: this scan already matched 25 separate duplicated blocks between them, totalling at least 367 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java:470` it begins part-way through the construct above it, so those exact lines 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobLogListDialog.java:294 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobLogListDialog.java:294-301 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobLogListDialog.java:338-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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobLogListDialog.java: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 (8 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MiniMapView.java:355 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MiniMapView.java:355-362 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MiniMapView.java:417-424 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (8 lines × 2) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobGroupServiceImpl.java:108 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobGroupServiceImpl.java:108-115 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobJdbcDatasourceServiceImpl.java:122-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. 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasConnectionManager.java:346 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasConnectionManager.java:346-353 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/NodeConnection.java:380-387 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. 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 `owner` to `javafx.scene.Node` in one and `Node` 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobCanvasBookmarkApiService.java:40 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobCanvasBookmarkApiService.java:40-47 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobNodeTemplateApiService.java:50-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 (8 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/LoginView.java:56 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/LoginView.java:56-63 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/RegisterView.java:51-58 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:1414 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:1414-1421 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:1553-1560 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java` as WHOLE FILES: this scan already matched 46 separate duplicated blocks between them, totalling at least 798 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (8 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:189 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:189-196 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:264-271 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java` as WHOLE FILES: this scan already matched 42 separate duplicated blocks between them, totalling at least 585 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (8 lines × 2) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/enums/MisfireStrategyEnum.java:31 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/enums/MisfireStrategyEnum.java:31-38 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/enums/ScheduleTypeEnum.java:38-45 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note first that the copies are not typed on the same thing: the declarations holding them bind `defaultItem` to `MisfireStrategyEnum` in one and `ScheduleTypeEnum` 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/LoginView.java:43 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/LoginView.java:43-54 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/RegisterView.java:42-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.
D3 · God Classes · FileTooLong · ×21
  • FileTooLong: view/NodeCanvas.java cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java — FileTooLong — 2783 significant lines (blank, comment-only and punctuation-only lines excluded), about 99% of them inside a single declaration: NodeCanvas (37-5002). The bar is 500 significant lines; this is 2283 over it, 5.57× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: view/MainView.java cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java — FileTooLong — 2106 significant lines (blank, comment-only and punctuation-only lines excluded), about 99% of them inside a single declaration: MainView (40-3330). The bar is 500 significant lines; this is 1606 over it, 4.21× 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: view/ShowDataxSyncDialog.java cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java — FileTooLong — 1859 significant lines (blank, comment-only and punctuation-only lines excluded), about 98% of them inside a single declaration: ShowDataxSyncDialog (44-2563). The bar is 500 significant lines; this is 1359 over it, 3.72× 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: impl/JobComposeServiceImpl.java cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java — FileTooLong — 1216 significant lines (blank, comment-only and punctuation-only lines excluded), about 97% of them inside a single declaration: JobComposeServiceImpl (39-2089). The bar is 500 significant lines; this is 716 over it, 2.43× 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: view/NewJobNodeDialog.java cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java — FileTooLong — 1116 significant lines (blank, comment-only and punctuation-only lines excluded), about 96% of them inside a single declaration: NewJobNodeDialog (51-1718). The bar is 500 significant lines; this is 616 over it, 2.23× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: model/ProcessNode.java cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ProcessNode.java — FileTooLong — 1103 significant lines (blank, comment-only and punctuation-only lines excluded), about 98% of them inside a single declaration: ProcessNode (29-2072). The bar is 500 significant lines; this is 603 over it, 2.21× 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: view/TopToolBar.java cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/TopToolBar.java — FileTooLong — 1051 significant lines (blank, comment-only and punctuation-only lines excluded), about 97% of them inside a single declaration: TopToolBar (41-1660). The bar is 500 significant lines; this is 551 over it, 2.10× 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: view/ShowDataxGroupSyncDialog.java cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java — FileTooLong — 1037 significant lines (blank, comment-only and punctuation-only lines excluded), about 97% of them inside a single declaration: ShowDataxGroupSyncDialog (44-1327). The bar is 500 significant lines; this is 537 over it, 2.07× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: view/NewJobDialog.java cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java — FileTooLong — 996 significant lines (blank, comment-only and punctuation-only lines excluded), about 97% of them inside a single declaration: NewJobDialog (40-1457). The bar is 500 significant lines; this is 496 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: cron/CronExpression.java cc-job/cc-job-admin/src/main/java/com/cc/job/admin/cron/CronExpression.java — FileTooLong — 956 significant lines (blank, comment-only and punctuation-only lines excluded), about 99% of them inside a single declaration: CronExpression (193-1651). The bar is 500 significant lines; this is 456 over it, 1.91× 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: view/PermissionManageDialog.java cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/PermissionManageDialog.java — FileTooLong — 908 significant lines (blank, comment-only and punctuation-only lines excluded), about 96% of them inside a single declaration: PermissionManageDialog (41-1126). The bar is 500 significant lines; this is 408 over it, 1.82× 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: model/ConditionNode.java cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java — FileTooLong — 888 significant lines (blank, comment-only and punctuation-only lines excluded), about 97% of them inside a single declaration: ConditionNode (30-1510). The bar is 500 significant lines; this is 388 over it, 1.78× 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: impl/JobInfoServiceImpl.java cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobInfoServiceImpl.java — FileTooLong — 876 significant lines (blank, comment-only and punctuation-only lines excluded), about 93% of them inside a single declaration: JobInfoServiceImpl (75-1396). The bar is 500 significant lines; this is 376 over it, 1.75× 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: view/ShowJobLogListDialog.java cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobLogListDialog.java — FileTooLong — 855 significant lines (blank, comment-only and punctuation-only lines excluded), about 95% of them inside a single declaration: ShowJobLogListDialog (52-1272). The bar is 500 significant lines; this is 355 over it, 1.71× 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: view/ShowJobListDialog.java cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java — FileTooLong — 795 significant lines (blank, comment-only and punctuation-only lines excluded), about 96% of them inside a single declaration: ShowJobListDialog (36-1231). The bar is 500 significant lines; this is 295 over it, 1.59× 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: view/LogPanel.java cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/LogPanel.java — FileTooLong — 734 significant lines (blank, comment-only and punctuation-only lines excluded), about 97% of them inside a single declaration: LogPanel (31-1185). The bar is 500 significant lines; this is 234 over it, 1.47× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: view/ShowDatasourceListDialog.java cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java — FileTooLong — 688 significant lines (blank, comment-only and punctuation-only lines excluded), about 96% of them inside a single declaration: ShowDatasourceListDialog (36-955). The bar is 500 significant lines; this is 188 over it, 1.38× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: REDACTED REDACTED — FileTooLong — 629 significant lines (blank, comment-only and punctuation-only lines excluded), about 94% of them inside a single declaration: JobPartServiceImpl (42-875). The bar is 500 significant lines; this is 129 over it, 1.26× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: model/GroupContainer.java cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/GroupContainer.java — FileTooLong — 619 significant lines (blank, comment-only and punctuation-only lines excluded), about 97% of them inside a single declaration: GroupContainer (26-1009). The bar is 500 significant lines; this is 119 over it, 1.24× 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: orchestrator/TaskGroupOrchestrator.java cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/orchestrator/TaskGroupOrchestrator.java — FileTooLong — 598 significant lines (blank, comment-only and punctuation-only lines excluded), about 94% of them inside a single declaration: TaskGroupOrchestrator (49-1071). The bar is 500 significant lines; this is 98 over it, 1.20× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: component/SmartParameterInput.java cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/component/SmartParameterInput.java — FileTooLong — 559 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 59 over it, 1.12× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×19
  • Duplicated block (7 lines × 2) REDACTED:80 — REDACTED:80-86 | REDACTED:88-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. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:80` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (7 lines × 2) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/datax/writer/MysqlWriter.java:18 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/datax/writer/MysqlWriter.java:18-24 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/datax/writer/OracleWriter.java:19-25 — 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 `cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/datax/writer/MysqlWriter.java:18` it does not close everything it opens, so those exact lines 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) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:1272 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:1272-1278 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:1318-1324 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:1272` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 2) REDACTED:547 — REDACTED:547-553 | REDACTED:838-844 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `REDACTED:554` calls `setFailStrategy`, `getFailStrategy` and `REDACTED:845` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (7 lines × 2) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/websocket/WebSocketServer.java:106 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/websocket/WebSocketServer.java:106-112 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/websocket/WebSocketServer.java:135-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 `cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/websocket/WebSocketServer.java:106` it does not close everything it opens, so those 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, `cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/websocket/WebSocketServer.java:129` calls `sendInfo`, `getParentJobId`, `getRandomId` and `cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/websocket/WebSocketServer.java:105` 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasDataLoader.java:248 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasDataLoader.java:248-254 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/ParameterAutocompleteService.java:155-161 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/NodeOperationManager.java:123 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/NodeOperationManager.java:123-130 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/NodeOperationManager.java:278-284 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/NodeOperationManager.java:123` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:1331 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:1331-1337 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/GroupContainer.java:900-906 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/GroupContainer.java` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 569 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:1331` it begins part-way through the construct above it, so those exact lines 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/DashboardService.java:42 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/DashboardService.java:42-48 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobDataxService.java:58-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.
  • Duplicated block (7 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/AddJobFromListDialog.java:121 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/AddJobFromListDialog.java:121-127 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:1338-1344 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/AddJobFromListDialog.java:388 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/AddJobFromListDialog.java:388-394 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:827-834 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/AddJobFromListDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 175 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/AddJobFromListDialog.java:388` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:422 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:422-428 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:441-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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:422` it begins part-way through the construct above it, so those exact lines 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:618 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:618-624 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowExecutorListDialog.java:497-503 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowExecutorListDialog.java` as WHOLE FILES: this scan already matched 26 separate duplicated blocks between them, totalling at least 339 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:618` it does not close everything it opens, so those exact lines 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:1037 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:1037-1043 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1932-1938 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java` as WHOLE FILES: this scan already matched 42 separate duplicated blocks between them, totalling at least 585 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (7 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasSelectionManager.java:295 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasSelectionManager.java:295-301 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasSelectionManager.java:347-353 — both copies are in the same file, so extract the 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobApprovalService.java:31 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobApprovalService.java:31-37 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobApprovalService.java:40-46 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (7 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:1184 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:1184-1190 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/GroupContainer.java:801-808 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/GroupContainer.java` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 569 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:174 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:174-180 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:249-255 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java` as WHOLE FILES: this scan already matched 42 separate duplicated blocks between them, totalling at least 585 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) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/controller/JobRoleManageController.java:112 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/controller/JobRoleManageController.java:112-118 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/controller/JobUserManageController.java:71-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.
D4 · Code Duplication · Duplicated block (10 lines × 2) · ×18
  • Duplicated block (10 lines × 2) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/thread/JobRegistryHelper.java:157 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/thread/JobRegistryHelper.java:157-166 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/thread/JobRegistryHelper.java:183-192 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/thread/JobRegistryHelper.java:157` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 2) cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/controller/JobGroupControlController.java:57 — cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/controller/JobGroupControlController.java:57-66 | cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/controller/JobGroupControlController.java:93-102 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/controller/JobGroupControlController.java:57` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (10 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/infrastructure/client/ApiClient.java:234 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/infrastructure/client/ApiClient.java:234-243 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/infrastructure/client/ApiClient.java:291-300 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/infrastructure/client/ApiClient.java:234` it does not close everything it opens, so those exact lines 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:1093 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:1093-1102 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:1345-1354 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:1093` it begins part-way through the construct above it, so those 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, `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:1090` calls `isExpanded` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:1343` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (10 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/AddBookmarkDialog.java:97 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/AddBookmarkDialog.java:97-106 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/SaveNodeTemplateDialog.java:90-99 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/AddBookmarkDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/SaveNodeTemplateDialog.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/AddBookmarkDialog.java:97` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/AddBookmarkDialog.java:107` calls `getSelectedToggle`, `getUserData` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/SaveNodeTemplateDialog.java:100` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (10 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ConditionNodeDialog.java:264 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ConditionNodeDialog.java:264-273 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ConditionNodeDialog.java:275-284 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ConditionNodeDialog.java:264` 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:668 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:668-677 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:1650-1659 — both copies are in the same file, so extract the 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, `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:679` calls `isBlank` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:1661` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (10 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:3072 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:3072-3081 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:3255-3264 — both copies are in the same file, so extract the 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:692 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:692-701 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:627-636 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java` as WHOLE FILES: this scan already matched 46 separate duplicated blocks between them, totalling at least 798 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (10 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:1171 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:1171-1180 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:1201-1210 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (10 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:2943 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:2943-2952 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:2973-2982 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:2943` 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:3666 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:3666-3675 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:3679-3688 — both copies are in the same file, so extract the 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:4594 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:4594-4603 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:4605-4614 — both copies are in the same file, so extract the 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:864 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:864-873 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowExecutorListDialog.java:576-585 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowExecutorListDialog.java` as WHOLE FILES: this scan already matched 26 separate duplicated blocks between them, totalling at least 339 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:864` it does not close everything it opens, so those exact lines 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/ParameterAutocompleteService.java:326 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/ParameterAutocompleteService.java:326-335 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/ParameterAutocompleteService.java:408-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.
  • Duplicated block (10 lines × 2) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobInfoServiceImpl.java:795 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobInfoServiceImpl.java:795-804 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobInfoServiceImpl.java:1166-1175 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobInfoServiceImpl.java:795` it does not close everything it opens, so those exact lines 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:1222 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:1222-1231 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:1627-1636 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java` as WHOLE FILES: this scan already matched 46 separate duplicated blocks between them, totalling at least 798 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:1625` calls `isApi` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:1220` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (10 lines × 2) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/enums/ExecutorRouteStrategyEnum.java:39 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/enums/ExecutorRouteStrategyEnum.java:39-48 | cc-job/cc-job-core/src/main/java/com/xxl/job/core/enums/ExecutorBlockStrategyEnum.java:25-34 — 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `defaultItem` to `ExecutorRouteStrategyEnum` in one and `ExecutorBlockStrategyEnum` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (9 lines × 2) · ×18
  • Duplicated block (9 lines × 2) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:1062 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:1062-1070 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:1119-1127 — both copies are in the same file, so extract the 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) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:1287 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:1287-1295 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:1336-1344 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:1287` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (9 lines × 2) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:1459 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:1459-1467 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:1498-1506 — both copies are in the same file, so extract the 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) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:1677 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:1677-1685 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:1687-1695 — both copies are in the same file, so extract the 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) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobInfoServiceImpl.java:547 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobInfoServiceImpl.java:547-555 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobInfoServiceImpl.java:1258-1266 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobInfoServiceImpl.java:547` it begins part-way through the construct above it, so those exact lines 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/AddJobFromListDialog.java:71 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/AddJobFromListDialog.java:71-79 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:92-100 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/AddJobFromListDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 175 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (9 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:3174 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:3174-3182 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:3280-3288 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:3174` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:621 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:621-629 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:688-696 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java` as WHOLE FILES: this scan already matched 46 separate duplicated blocks between them, totalling at least 798 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:621` it begins part-way through the construct above it, so those exact lines 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:1404 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:1404-1412 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:1543-1551 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java` as WHOLE FILES: this scan already matched 46 separate duplicated blocks between them, totalling at least 798 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (9 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:173 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:173-181 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:125-133 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (9 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:490 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:490-498 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:526-534 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:490` it does not close everything it opens, so those exact lines 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:960 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:960-968 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1725-1733 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java` as WHOLE FILES: this scan already matched 42 separate duplicated blocks between them, totalling at least 585 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:960` it does not close everything it opens, so those exact lines 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobLogListDialog.java:549 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobLogListDialog.java:549-557 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobLogListDialog.java:598-606 — both copies are in the same file, so extract the 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) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/command/JdbcCommand.java:59 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/command/JdbcCommand.java:59-67 | cc-job/cc-job-executor/src/main/java/com/cc/job/executor/command/JdbcCommand.java:43-51 — before extracting anything, compare `cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/command/JdbcCommand.java` and `cc-job/cc-job-executor/src/main/java/com/cc/job/executor/command/JdbcCommand.java` as WHOLE FILES: 87% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (9 lines × 2) REDACTED:179 — REDACTED:179-187 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/sse/SSEService.java:123-132 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (9 lines × 2) cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/service/TaskExecutor.java:294 — cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/service/TaskExecutor.java:294-302 | cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/service/TaskWrapperFactory.java:183-191 — 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) cc-job/cc-job-executor/src/main/java/com/cc/job/executor/core/service/JdbcTaskExecutor.java:89 — cc-job/cc-job-executor/src/main/java/com/cc/job/executor/core/service/JdbcTaskExecutor.java:89-97 | cc-job/cc-job-executor/src/main/java/com/cc/job/executor/core/service/datax/IncrementalDataRefresher.java:135-143 — 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 (9 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/AddJobFromListDialog.java:231 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/AddJobFromListDialog.java:231-239 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:305-313 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/AddJobFromListDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 175 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 after the matched lines, `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:315` calls `SuppressWarnings` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/AddJobFromListDialog.java: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.
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×18
  • Duplicated block (6 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DataManager.java:186 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DataManager.java:186-191 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DataManager.java:210-215 — both copies are in the same file, so extract the 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/TreeContextMenuManager.java:123 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/TreeContextMenuManager.java:123-128 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/TreeContextMenuManager.java:131-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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/TreeContextMenuManager.java:123` it begins part-way through the construct above it, so those exact lines 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:2452 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:2452-2457 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:2459-2464 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:2452` 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:2949 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:2949-2954 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:3003-3008 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:2949` it does not close everything it opens, so those 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, `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:2955` calls `getType`, `getChildren` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:3009` 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:4769 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:4769-4774 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:4830-4835 — both copies are in the same file, so extract the 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/SelectTaskGroupDialog.java:103 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/SelectTaskGroupDialog.java:103-108 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/SelectTaskGroupDialog.java:110-115 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/SelectTaskGroupDialog.java:103` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/SelectTaskGroupDialog.java:103 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/SelectTaskGroupDialog.java:103-108 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/SelectTaskGroupDialog.java:123-128 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/SelectTaskGroupDialog.java:103` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/SelectTaskGroupDialog.java:110 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/SelectTaskGroupDialog.java:110-115 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/SelectTaskGroupDialog.java:130-135 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/SelectTaskGroupDialog.java: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 (6 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:2415 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:2415-2420 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:2459-2464 — both copies are in the same file, so extract the 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) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:1088 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:1088-1093 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:1180-1185 — both copies are in the same file, so extract the 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) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobLogServiceImpl.java:147 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobLogServiceImpl.java:147-152 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobLogServiceImpl.java:160-165 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobLogServiceImpl.java: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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (6 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/TreeDataManager.java:71 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/TreeDataManager.java:71-76 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/TreeDataManager.java:88-93 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/TreeDataManager.java:71` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/TreeDataManager.java:77` calls `getType` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/TreeDataManager.java:94` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (6 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:681 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:681-686 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:616-621 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java` as WHOLE FILES: this scan already matched 46 separate duplicated blocks between them, totalling at least 798 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (6 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:182 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:182-187 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:257-262 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java` as WHOLE FILES: this scan already matched 42 separate duplicated blocks between them, totalling at least 585 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (6 lines × 2) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/controller/DashboardController.java:61 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/controller/DashboardController.java:61-66 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/controller/DashboardController.java:160-165 — both copies are in the same file, so extract the 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DataManager.java:138 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DataManager.java:138-143 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DataManager.java:278-283 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DataManager.java:138` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DataManager.java:275` calls `info`, `format`, `size` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DataManager.java:137` 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DataManager.java:179 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DataManager.java:179-184 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DataManager.java:199-204 — both copies are in the same file, so extract the 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:501 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:501-506 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:538-543 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:501` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
X3 · Exception handling · Swallowed exception (empty catch) · ×18
  • Swallowed exception (empty catch) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/CcJobGuiApplication.java:110 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/CcJobGuiApplication.java:178 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/CcJobGuiApplication.java:204 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/CcJobGuiApplication.java:271 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:1397 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:1536 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/PermissionManageDialog.java:775 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/TaskTreeView.java:175 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobPartService.java:582 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobPartService.java:616 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasDataLoader.java:198 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/service/TaskExecutor.java:311 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/service/TaskExecutor.java:323 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) cc-job/cc-job-executor/src/main/java/com/cc/job/executor/core/service/datax/IncrementalDataRefresher.java:457 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) cc-job/cc-job-core/src/main/java/com/xxl/job/core/glue/impl/SpringGlueFactory.java:52 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/controller/JobApprovalController.java:125 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/controller/JobApprovalController.java:176 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/cron/CronExpression.java:1642 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
D4 · Code Duplication · Duplicated block (14 lines × 2) · ×16
  • Duplicated block (14 lines × 2) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/DataxServiceImpl.java:116 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/DataxServiceImpl.java:116-129 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/DataxServiceImpl.java:132-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 (14 lines × 2) cc-job/cc-job-core/src/main/java/com/xxl/job/core/glue/CSharpGlueFactory.java:194 — cc-job/cc-job-core/src/main/java/com/xxl/job/core/glue/CSharpGlueFactory.java:194-207 | cc-job/cc-job-core/src/main/java/com/xxl/job/core/glue/CSharpGlueFactory.java:223-236 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-core/src/main/java/com/xxl/job/core/glue/CSharpGlueFactory.java:194` it does not close everything it opens, so those 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, `cc-job/cc-job-core/src/main/java/com/xxl/job/core/glue/CSharpGlueFactory.java:209` calls `isEmpty`, `replaceAll`, `trim` and `cc-job/cc-job-core/src/main/java/com/xxl/job/core/glue/CSharpGlueFactory.java:238` 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 (14 lines × 2) cc-job/cc-job-core/src/main/java/com/xxl/job/core/log/XxlJobFileAppender.java:117 — cc-job/cc-job-core/src/main/java/com/xxl/job/core/log/XxlJobFileAppender.java:117-130 | cc-job/cc-job-core/src/main/java/com/xxl/job/core/util/FileUtil.java:63-76 — 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 `cc-job/cc-job-core/src/main/java/com/xxl/job/core/log/XxlJobFileAppender.java:117` 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) cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/resolver/ParameterResolver.java:227 — cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/resolver/ParameterResolver.java:227-240 | cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/resolver/ParameterResolver.java:275-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 `cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/resolver/ParameterResolver.java:227` it does not close everything it opens, so those exact lines 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ProcessNode.java:1204 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ProcessNode.java:1204-1217 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ProcessNode.java:1226-1239 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ProcessNode.java:1204` it does not close everything it opens, so those exact lines 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/BatchEditDialog.java:59 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/BatchEditDialog.java:59-72 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeRemarkDialog.java:36-49 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/BatchEditDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeRemarkDialog.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 52 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/BatchEditDialog.java:59` it does not close everything it opens, so those exact lines 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/GlueIdeDialog.java:238 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/GlueIdeDialog.java:238-251 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/GlueIdeDialog.java:253-266 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/GlueIdeDialog.java: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.
  • Duplicated block (14 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/LoginView.java:97 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/LoginView.java:97-110 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/RegisterView.java:64-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. 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeDetailsDialog.java:125 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeDetailsDialog.java:125-138 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeDetailsDialog.java:168-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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeDetailsDialog.java:123` calls `setStyle`, `linkPrimaryColor` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeDetailsDialog.java:166` 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 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeStyleDialog.java:103 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeStyleDialog.java:103-116 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeStyleDialog.java:122-135 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeStyleDialog.java:103` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:165 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:165-178 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowExecutorListDialog.java:156-169 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowExecutorListDialog.java` as WHOLE FILES: this scan already matched 26 separate duplicated blocks between them, totalling at least 339 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 (14 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:225 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:225-238 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:300-313 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java` as WHOLE FILES: this scan already matched 42 separate duplicated blocks between them, totalling at least 585 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java: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 (14 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobLogListDialog.java:304 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobLogListDialog.java:304-317 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobLogListDialog.java:348-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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobLogListDialog.java:304` it begins part-way through the construct above it, so those exact lines 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:2966 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:2966-2979 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:3020-3033 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (14 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:265 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:265-278 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:777-790 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java` as WHOLE FILES: this scan already matched 42 separate duplicated blocks between them, totalling at least 585 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 (14 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:393 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:393-406 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1030-1043 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java` as WHOLE FILES: this scan already matched 42 separate duplicated blocks between them, totalling at least 585 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.
D4 · Code Duplication · Duplicated block (11 lines × 2) · ×16
  • Duplicated block (11 lines × 2) REDACTED:46 — REDACTED:46-56 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/route/strategy/ExecutorRouteLRU.java:52-62 — 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) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:362 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:362-372 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:387-397 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:362` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (11 lines × 2) cc-job/cc-job-core/src/main/java/com/xxl/job/core/log/XxlJobFileAppender.java:165 — cc-job/cc-job-core/src/main/java/com/xxl/job/core/log/XxlJobFileAppender.java:165-175 | cc-job/cc-job-core/src/main/java/com/xxl/job/core/log/XxlJobFileAppender.java:206-216 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-core/src/main/java/com/xxl/job/core/log/XxlJobFileAppender.java:165` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `cc-job/cc-job-core/src/main/java/com/xxl/job/core/log/XxlJobFileAppender.java:204` calls `toString` and `cc-job/cc-job-core/src/main/java/com/xxl/job/core/log/XxlJobFileAppender.java:163` 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/LoginService.java:53 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/LoginService.java:53-63 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/LoginService.java:160-170 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/LoginService.java:53` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/util/NotificationToast.java:270 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/util/NotificationToast.java:270-280 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/util/NotificationToast.java:311-321 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (11 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/LoginView.java:171 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/LoginView.java:171-181 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/RegisterView.java:144-154 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/LoginView.java:182` calls `getChildren`, `add` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/RegisterView.java:156` 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:217 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:217-227 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java:137-147 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java` as WHOLE FILES: this scan already matched 31 separate duplicated blocks between them, totalling at least 451 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java: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. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (11 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:4562 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:4562-4572 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:4582-4592 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (11 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/PermissionManageDialog.java:462 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/PermissionManageDialog.java:462-472 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/PermissionManageDialog.java:1013-1023 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (11 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:245 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:245-255 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:373-383 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (11 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1747 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1747-1757 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1780-1790 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (11 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:405 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:405-415 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:477-487 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:405` 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/TaskNavigationBar.java:536 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/TaskNavigationBar.java:536-546 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/TopToolBar.java:1592-1602 — 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/TaskNavigationBar.java:536` it does not close everything it opens, so those exact lines 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) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/controller/DashboardController.java:94 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/controller/DashboardController.java:94-104 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/controller/DashboardController.java:174-184 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (11 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MiniMapView.java:272 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MiniMapView.java:272-282 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MiniMapView.java:285-295 — both copies are in the same file, so extract the 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 (11 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:832 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:832-842 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowExecutorListDialog.java:562-572 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowExecutorListDialog.java` as WHOLE FILES: this scan already matched 26 separate duplicated blocks between them, totalling at least 339 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 first that the copies are not typed on the same thing: the declarations holding them bind `form` to `JobJdbcDatasourceForm` in one and `JobGroupForm` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×16
  • Duplicated block (5 lines × 2) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/cron/CronExpression.java:1520 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/cron/CronExpression.java:1520-1524 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/cron/CronExpression.java:1547-1551 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-admin/src/main/java/com/cc/job/admin/cron/CronExpression.java:1520` it does not close everything it opens, so those exact lines 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) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:355 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:355-359 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobInfoServiceImpl.java:698-702 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasLayoutManager.java:334 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasLayoutManager.java:334-338 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DependencyNavigator.java:77-81 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasLayoutManager.java: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 (5 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:874 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:874-879 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/GroupContainer.java:668-672 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/GroupContainer.java` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 569 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MiniMapView.java:139 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MiniMapView.java:139-145 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/TaskTreeView.java:99-103 — 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MiniMapView.java:139` it does not close everything it opens, so those 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 × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:999 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:999-1003 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:1253-1257 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java` as WHOLE FILES: this scan already matched 46 separate duplicated blocks between them, totalling at least 798 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:999` it begins part-way through the construct above it, so those 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, `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:1251` calls `setExecutorHandler` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:997` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (5 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeDetailsDialog.java:118 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeDetailsDialog.java:118-122 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeDetailsDialog.java:162-166 — both copies are in the same file, so extract the 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, `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeDetailsDialog.java:123` calls `setStyle`, `linkPrimaryColor` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeDetailsDialog.java:168` 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/PermissionManageDialog.java:129 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/PermissionManageDialog.java:129-133 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/SettingsDialog.java:46-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 (5 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:1108 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:1108-1112 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1985-1990 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java` as WHOLE FILES: this scan already matched 42 separate duplicated blocks between them, totalling at least 585 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:1108` 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:1116 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:1116-1120 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1994-1999 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java` as WHOLE FILES: this scan already matched 42 separate duplicated blocks between them, totalling at least 585 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:1116` 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobGroupService.java:31 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobGroupService.java:31-35 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobPartService.java:24-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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (5 lines × 2) cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/service/HistoricalDataLoader.java:77 — cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/service/HistoricalDataLoader.java:77-81 | cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/service/HistoricalDataLoader.java:173-177 — both copies are in the same file, so extract the 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobDataxService.java:91 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobDataxService.java:91-95 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobDataxService.java:114-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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobDataxService.java:91` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobPartService.java:549 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobPartService.java:549-553 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobPartService.java:565-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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobPartService.java:549` it does not close everything it opens, so those 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, `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobPartService.java:547` calls `parseComposeFromGuiSnapshot`, `JobComposeData` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobPartService.java:564` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (5 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:700 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:700-704 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:718-722 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:700` it does not close everything it opens, so those 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 (5 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/TaskTreeView.java:485 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/TaskTreeView.java:485-489 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/TaskTreeView.java:502-506 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/TaskTreeView.java:485` it does not close everything it opens, so those 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.
X3 · Exception handling · Swallowed exception (caught, then discarded) · ×16
  • Swallowed exception (caught, then discarded) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/LogPanel.java:741 — `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:2417 — `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:1031 — `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:376 — `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1818 — `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobLogListDialog.java:1025 — `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/util/I18n.java:34 — `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/LogContentManager.java:510 — `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/service/HistoricalDataLoader.java:201 — `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) cc-job/cc-job-executor/src/main/java/com/cc/job/executor/utils/DataxUtils.java:59 — `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) cc-job/cc-job-core/src/main/java/com/xxl/job/core/glue/CSharpGlueFactory.java:458 — `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/utils/JwtUtil.java:146 — `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:342 — `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/controller/DashboardController.java:216 — `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/controller/JobApprovalController.java:63 — `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/alarm/AlarmRuleChecker.java:61 — `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
D17 · Explicit Debt · TodoComment · ×11
  • TodoComment cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:849 — // TODO: 实现查找下一个 — 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 cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:855 — // TODO: 实现查找上一个 — 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 cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:1129 — // TODO: 实现运行选中的节点 — 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 cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:1135 — // TODO: 实现运行到此处 — 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 cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:1207 — // TODO: 实现复制任务组 — 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 cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:1260 — // TODO: 实现保存布局 — 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 cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/TaskTreeView.java:239 — // TODO 显示只有任务组类型(type == 1)且正在运行时才显示绿色圆点 — 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 cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/ParameterAutocompleteService.java:475 — // TODO: 实现从任务组中动态获取属性的逻辑 — 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 cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasTemplateManager.java:360 — // TODO: 保存到数据库 — 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 cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobLogServiceImpl.java:135 — // todo, need to improve performance — 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 cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/controller/AuthController.java:73 — // TODO: 可以在这里清理session、token黑名单等 — 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.
D4 · Code Duplication · Edited copy of a member (9 corresponding lines) · ×10
  • Edited copy of a member (9 corresponding lines) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobInfoService.java:119 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobInfoService.java:119-127 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobInfoService.java:356-364 — 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) cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/service/HistoricalDataLoader.java:337 — cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/service/HistoricalDataLoader.java:337-345 | cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/service/ResultStorageService.java:309-321 — 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) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/controller/JobPartController.java:71 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/controller/JobPartController.java:71-80 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/controller/JobPartController.java:85-93 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:1296 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:1296-1304 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:2554-2562 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/ParameterAutocompleteService.java:487 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/ParameterAutocompleteService.java:487-496 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/component/SmartParameterInput.java:953-961 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobLogListDialog.java:1016 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobLogListDialog.java:1016-1028 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/LogPanel.java:736-744 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasTemplateManager.java:387 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasTemplateManager.java:387-395 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/NodeTemplateManager.java:135-143 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/BookmarkListDialog.java:55 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/BookmarkListDialog.java:55-63 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/CreateNodeFromTemplateDialog.java:62-70 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1812 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1812-1821 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:1026-1034 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/LogPanel.java:235 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/LogPanel.java:235-243 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/TopToolBar.java:1174-1183 — 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 · Duplicated block (13 lines × 2) · ×10
  • Duplicated block (13 lines × 2) cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/controller/JobCallbackController.java:74 — cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/controller/JobCallbackController.java:74-86 | cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/interfaces/api/TaskGroupControlApi.java:49-61 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/controller/JobCallbackController.java: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 (13 lines × 2) cc-job/cc-job-executor-samples/cc-job-executor-sample-springboot/src/main/java/com/cc/job/executor/sample/core/config/XxlJobConfig.java:46 — cc-job/cc-job-executor-samples/cc-job-executor-sample-springboot/src/main/java/com/cc/job/executor/sample/core/config/XxlJobConfig.java:46-58 | cc-job/cc-job-executor/src/main/java/com/cc/job/executor/config/XxlJobConfig.java:46-58 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (13 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/CcJobGuiApplication.java:99 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/CcJobGuiApplication.java:99-111 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/CcJobGuiApplication.java:167-179 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/CcJobGuiApplication.java: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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/CcJobGuiApplication.java:114` calls `Stage` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/CcJobGuiApplication.java:182` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (13 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/NodeOperationManager.java:543 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/NodeOperationManager.java:543-555 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:2543-2555 — 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/NodeOperationManager.java:543` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (13 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:1222 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:1222-1234 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/GroupContainer.java:824-838 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/GroupContainer.java` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 569 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:1222` 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:661 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:661-673 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:2910-2922 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:661` it does not close everything it opens, so those exact lines 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MiniMapView.java:364 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MiniMapView.java:364-376 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MiniMapView.java:434-446 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MiniMapView.java:364` 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:927 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:927-939 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:2781-2793 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:927` 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:154 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:154-166 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:229-241 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java` as WHOLE FILES: this scan already matched 42 separate duplicated blocks between them, totalling at least 585 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (13 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:959 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:959-971 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:1059-1071 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:959` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (12 lines × 2) · ×10
  • Duplicated block (12 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasDataLoader.java:84 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasDataLoader.java:84-95 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasDataLoader.java:96-107 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasDataLoader.java:108` calls `setNodeSize` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasDataLoader.java:96` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (12 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasDataLoader.java:257 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasDataLoader.java:257-268 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/ParameterAutocompleteService.java:166-177 — 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasDataLoader.java:257` it does not close everything it opens, so those exact lines 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/SSEService.java:270 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/SSEService.java:270-281 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/WebSocketService.java:119-130 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/SSEService.java:270` 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:353 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:353-364 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:313-324 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java` as WHOLE FILES: this scan already matched 46 separate duplicated blocks between them, totalling at least 798 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 × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:706 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:706-717 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:788-799 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java` as WHOLE FILES: this scan already matched 46 separate duplicated blocks between them, totalling at least 798 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 × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:1390 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:1390-1401 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:1529-1540 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java` as WHOLE FILES: this scan already matched 46 separate duplicated blocks between them, totalling at least 798 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (12 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:924 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:924-935 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1827-1838 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:3852 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:3852-3863 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:3883-3894 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:3852` it does not close everything it opens, so those exact lines 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:838 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:838-849 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1092-1103 — both copies are in the same file, so extract the 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:474 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:474-485 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:510-521 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:474` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Edited copy of a member (16 corresponding lines) · ×8
  • Edited copy of a member (16 corresponding lines) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobGroupServiceImpl.java:47 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobGroupServiceImpl.java:47-62 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobJdbcDatasourceServiceImpl.java:49-76 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:1122 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:1122-1137 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:1139-1154 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:695 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:695-710 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:713-728 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/TaskTreeView.java:440 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/TaskTreeView.java:440-455 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/TaskTreeView.java:457-473 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) REDACTED:582 — REDACTED:582-597 | REDACTED:602-617 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:862 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:862-877 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowExecutorListDialog.java:574-589 — 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) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobGroupSnapshotServiceImpl.java:47 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobGroupSnapshotServiceImpl.java:47-62 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobGroupSnapshotServiceImpl.java:65-80 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/NodeTemplateManager.java:150 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/NodeTemplateManager.java:150-165 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/NodeTemplateManager.java:170-185 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (12 corresponding lines) · ×8
  • Edited copy of a member (12 corresponding lines) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/LogPanel.java:571 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/LogPanel.java:571-582 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/TaskNavigationBar.java:215-226 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:2941 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:2941-2952 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:2971-2982 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:1022 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:1022-1033 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:1038-1049 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/LogPanel.java:555 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/LogPanel.java:555-566 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/TaskNavigationBar.java:199-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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/LogTabManager.java:31 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/LogTabManager.java:31-42 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/LogTabManager.java:113-129 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:1099 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:1099-1110 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:1112-1123 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DependencyNavigator.java:103 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DependencyNavigator.java:103-114 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DependencyNavigator.java:130-141 — 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) cc-job/cc-job-core/src/main/java/com/xxl/job/core/executor/impl/XxlJobSimpleExecutor.java:34 — cc-job/cc-job-core/src/main/java/com/xxl/job/core/executor/impl/XxlJobSimpleExecutor.java:34-45 | cc-job/cc-job-core/src/main/java/com/xxl/job/core/executor/impl/XxlJobSpringExecutor.java:32-49 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (8 corresponding lines) · ×8
  • Edited copy of a member (8 corresponding lines) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/NodeConnection.java:633 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/NodeConnection.java:633-641 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/NodeConnection.java:651-658 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasConnectionManager.java:362 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasConnectionManager.java:362-373 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:2673-2680 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobApprovalService.java:30 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobApprovalService.java:30-37 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobApprovalService.java:39-46 — 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) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/controller/DashboardController.java:115 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/controller/DashboardController.java:115-126 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/controller/DashboardController.java:135-142 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:1036 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:1036-1043 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1931-1938 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:219 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:219-226 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobLogListDialog.java:183-190 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/HttpClientUtil.java:42 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/HttpClientUtil.java:42-49 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/util/ApiUtil.java:71-78 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowExecutorListDialog.java:304 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowExecutorListDialog.java:304-311 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobLogListDialog.java: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.
D4 · Code Duplication · Duplicated block (17 lines × 2) · ×8
  • Duplicated block (17 lines × 2) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/datax/reader/MysqlReader.java:38 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/datax/reader/MysqlReader.java:38-54 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/datax/reader/OracleReader.java:39-55 — before extracting anything, compare `cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/datax/reader/MysqlReader.java` and `cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/datax/reader/OracleReader.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 67 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/datax/reader/MysqlReader.java: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.
  • Duplicated block (17 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/LogPanel.java:466 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/LogPanel.java:466-482 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/LogPanel.java:495-511 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/LogPanel.java:466` 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:101 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:101-117 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:109-125 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java` as WHOLE FILES: this scan already matched 46 separate duplicated blocks between them, totalling at least 798 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 (17 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:946 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:946-962 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:2803-2819 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (17 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:748 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:748-764 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1001-1017 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (17 lines × 2) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/controller/JobApprovalController.java:114 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/controller/JobApprovalController.java:114-130 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/controller/JobApprovalController.java:165-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.
  • Duplicated block (17 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/AddJobFromListDialog.java:358 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/AddJobFromListDialog.java:358-374 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:801-817 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/AddJobFromListDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 175 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/AddJobFromListDialog.java:358` 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobLogService.java:240 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobLogService.java:240-256 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobLogService.java:269-285 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobLogService.java:240` it begins part-way through the construct above it, so those 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, `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobLogService.java:238` calls `put`, `valueOf`, `getPageNum` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobLogService.java:268` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (8 lines × 3) · ×8
  • Duplicated block (8 lines × 3) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/cron/CronExpression.java:1357 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/cron/CronExpression.java:1357-1365 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/cron/CronExpression.java:1401-1408 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/cron/CronExpression.java:1446-1453 — 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 `cc-job/cc-job-admin/src/main/java/com/cc/job/admin/cron/CronExpression.java:1357` it begins part-way through the construct above it, so those 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) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/utils/JacksonUtil.java:40 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/utils/JacksonUtil.java:40-47 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/utils/JacksonUtil.java:61-68 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/utils/JacksonUtil.java:84-91 — 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 `cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/utils/JacksonUtil.java:40` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (8 lines × 3) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/AddJobFromListDialog.java:152 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/AddJobFromListDialog.java:152-159 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:195-204 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobLogListDialog.java:161-169 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/AddJobFromListDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 175 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 after the matched lines, `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/AddJobFromListDialog.java:160` calls `setPrefWidth` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobLogListDialog.java:170` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (8 lines × 3) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/AddJobFromListDialog.java:204 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/AddJobFromListDialog.java:204-211 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:264-271 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobLogListDialog.java:233-240 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/AddJobFromListDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 175 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 lines × 3) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:956 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:956-963 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java:504-511 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:1202-1209 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java` as WHOLE FILES: this scan already matched 31 separate duplicated blocks between them, totalling at least 451 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 lines × 3) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeDetailsDialog.java:66 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeDetailsDialog.java:66-73 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeDetailsDialog.java:128-135 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeDetailsDialog.java:171-178 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeDetailsDialog.java:123` calls `setStyle`, `linkPrimaryColor` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeDetailsDialog.java:166` 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 lines × 3) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/PermissionManageDialog.java:462 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/PermissionManageDialog.java:462-469 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/PermissionManageDialog.java:518-525 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/PermissionManageDialog.java:1013-1020 — 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 (8 lines × 3) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:412 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:412-419 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowExecutorListDialog.java:409-416 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobLogListDialog.java:511-518 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowExecutorListDialog.java` as WHOLE FILES: this scan already matched 26 separate duplicated blocks between them, totalling at least 339 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:412` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D6 · Cohesion (LCOM4) · Low cohesion · ×8
  • Low cohesion: DependencyNavigator (LCOM4 7) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DependencyNavigator.java:18 — DependencyNavigator's methods fall into 7 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 7 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: NodeSearchManager (LCOM4 7) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/NodeSearchManager.java:17 — NodeSearchManager's methods fall into 7 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 7 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: SmartParameterInput (LCOM4 6) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/component/SmartParameterInput.java:36 — SmartParameterInput's methods fall into 6 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 6 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: LogPanel (LCOM4 6) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/LogPanel.java:31 — LogPanel's methods fall into 6 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 6 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: ShowJobListDialog (LCOM4 5) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:36 — ShowJobListDialog'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: JobInfoController (LCOM4 4) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/controller/JobInfoController.java:45 — JobInfoController'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: WorkerWrapper (LCOM4 4) cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/engine/wrapper/WorkerWrapper.java:18 — WorkerWrapper'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: TopToolBar (LCOM4 4) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/TopToolBar.java:41 — TopToolBar'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.
D30 · Dependency Vulnerabilities · Medium CVE · ×7
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D35 · Change Coupling · Change coupling · ×7
  • Change coupling: JobPartService.java ↔ NodeCanvas.java cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobPartService.java:1 — `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobPartService.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java` change together 69% of the time (11 of the 16 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 11 shared commits counted here, the most recent 3 are `1545034c` fix: 优化条件节点处理逻辑和坐标计算; `10920262` 任务组节点; `bbe23398` 任务组节点 — run `git show` on any of them.
  • Change coupling: MysqlReader.java ↔ DataxHandler.java cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/datax/reader/MysqlReader.java:1 — `cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/datax/reader/MysqlReader.java` and `cc-job/cc-job-executor/src/main/java/com/cc/job/executor/handler/DataxHandler.java` change together 67% of the time (8 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `89d860a1` fix: 修复bug,更新文档 (at that commit the files were still `cc-job-admin/src/main/java/com/cc/job/admin/task/datax/reader/MysqlReader.java` and `cc-job-executor/src/main/java/com/cc/job/executor/handler/DataxHandler.java`); `701be737` fix: 修复任务组无法运行定时执行的bug (at that commit the files were still `cc-job-admin/src/main/java/com/cc/job/admin/task/datax/reader/MysqlReader.java` and `cc-job-executor/src/main/java/com/cc/job/executor/handler/DataxHandler.java`); `c34c2b00` feat: 增量同步功能开发... (at that commit the files were still `cc-job-admin/src/main/java/com/cc/job/admin/task/datax/reader/MysqlReader.java` and `cc-job-executor/src/main/java/com/cc/job/executor/handler/DataxHandler.java`) — run `git show` on any of them.
  • Change coupling: JobInfo.java ↔ JobInfoForm.java cc-job/cc-job-xo/src/main/java/com/cc/job/xo/model/entity/JobInfo.java:1 — `cc-job/cc-job-xo/src/main/java/com/cc/job/xo/model/entity/JobInfo.java` and `cc-job/cc-job-xo/src/main/java/com/cc/job/xo/model/form/JobInfoForm.java` change together 64% of the time (7 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `b77a0f67` feat: 优化日志配置和增量同步功能; `515fa2de` feat: 新增普通任务对话框和失败策略功能; `fa8d80a1` fix:支持暂停任务运行 (at that commit the files were still `cc-job-xo/src/main/java/com/cc/job/xo/model/entity/JobInfo.java` and `cc-job-xo/src/main/java/com/cc/job/xo/model/form/JobInfoForm.java`) — run `git show` on any of them.
  • Change coupling: MainView.java ↔ ShowJobListDialog.java cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:1 — `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java` change together 64% of the time (7 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `5040953d` feat: 优化datax数据同步页面; `73023a15` feat: 新增从任务列表添加节点到画布功能; `4bfcd289` feat: 新增任务组节点执行状态记录与历史查看功能 — run `git show` on any of them.
  • Change coupling: NodeConnection.java ↔ MainView.java cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/NodeConnection.java:1 — `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/NodeConnection.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java` change together 64% of the time (7 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `b75bd905` fix: 优化条件节点处理逻辑和坐标计算; `67adb3bb` feat: 优化节点状态显示和连接管理; `3eac06f3` 任务组节点 — run `git show` on any of them.
  • Change coupling: LogPanel.java ↔ MiniMapView.java cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/LogPanel.java:1 — `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/LogPanel.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MiniMapView.java` change together 55% of the time (6 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `1c4f0aec` refactor: 重构面板弹出窗口功能并优化日志面板恢复机制; `93474f99` 解决日志出错问题; `9703a59f` feat: 优化日志面板性能与交互体验 — run `git show` on any of them.
  • Change coupling: AdminApiClient.java ↔ JobGroupExecutorComplete.java cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/client/AdminApiClient.java:1 — `cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/client/AdminApiClient.java` and `cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/handler/JobGroupExecutorComplete.java` change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `6609283f` feat: 增强任务执行编排与节点结果管理功能; `0fa1ec60` feat: 添加任务组运行状态同步功能; `9bf48cad` 功能大改 — run `git show` on any of them.
D4 · Code Duplication · Duplicated block (16 lines × 2) · ×7
  • Duplicated block (16 lines × 2) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:418 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:418-433 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:495-510 — both copies are in the same file, so extract the 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 (16 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/CcJobGuiApplication.java:74 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/CcJobGuiApplication.java:74-89 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/CcJobGuiApplication.java:142-157 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (16 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/AddBookmarkDialog.java:47 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/AddBookmarkDialog.java:47-62 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/SaveNodeTemplateDialog.java:49-64 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/AddBookmarkDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/SaveNodeTemplateDialog.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:510 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:510-525 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1484-1499 — 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 (16 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:409 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:409-424 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:427-442 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:409` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note first that the copies are not typed on the same thing: the declarations holding them bind `item` to `String` in one and `Void` 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 (16 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/TaskNavigationBar.java:560 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/TaskNavigationBar.java:560-575 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/TopToolBar.java:1616-1631 — 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/TaskNavigationBar.java:560` it begins part-way through the construct above it, so those exact lines 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:959 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:959-974 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1861-1876 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (15 lines × 2) · ×7
  • Duplicated block (15 lines × 2) cc-job/cc-job-executor-samples/cc-job-executor-sample-frameless/src/main/java/com/cc/job/executor/sample/sample/frameless/jobhandler/SampleXxlJob.java:54 — cc-job/cc-job-executor-samples/cc-job-executor-sample-frameless/src/main/java/com/cc/job/executor/sample/sample/frameless/jobhandler/SampleXxlJob.java:54-68 | cc-job/cc-job-executor-samples/cc-job-executor-sample-springboot/src/main/java/com/cc/job/executor/sample/service/jobhandler/SampleXxlJob.java:387-401 — before extracting anything, compare `cc-job/cc-job-executor-samples/cc-job-executor-sample-frameless/src/main/java/com/cc/job/executor/sample/sample/frameless/jobhandler/SampleXxlJob.java` and `cc-job/cc-job-executor-samples/cc-job-executor-sample-springboot/src/main/java/com/cc/job/executor/sample/service/jobhandler/SampleXxlJob.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 168 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (15 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasSelectionManager.java:151 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasSelectionManager.java:151-165 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasSelectionManager.java:178-192 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasSelectionManager.java:151` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:137 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:137-151 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/GroupContainer.java:87-101 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/GroupContainer.java` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 569 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:385 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:385-399 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/GroupContainer.java:353-367 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/GroupContainer.java` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 569 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (15 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:810 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:810-824 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1065-1079 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (15 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowExecutorListDialog.java:411 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowExecutorListDialog.java:411-425 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobLogListDialog.java:513-527 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowExecutorListDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobLogListDialog.java` as WHOLE FILES: this scan already matched 21 separate duplicated blocks between them, totalling at least 257 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowExecutorListDialog.java:411` 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:939 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:939-953 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1841-1855 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (10 lines × 3) · ×7
  • Duplicated block (10 lines × 3) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/alarm/impl/DingTalkJobAlarm.java:72 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/alarm/impl/DingTalkJobAlarm.java:72-81 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/alarm/impl/FeishuJobAlarm.java:63-72 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/alarm/impl/WeComJobAlarm.java: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 `cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/alarm/impl/DingTalkJobAlarm.java: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 (10 lines × 3) cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/controller/JobCallbackController.java:80 — cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/controller/JobCallbackController.java:80-89 | cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/interfaces/api/TaskGroupControlApi.java:55-64 | cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/interfaces/api/TaskGroupControlApi.java:94-103 — 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 `cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/controller/JobCallbackController.java:80` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (10 lines × 3) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/CcJobGuiApplication.java:102 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/CcJobGuiApplication.java:102-111 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/CcJobGuiApplication.java:170-179 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/CcJobGuiApplication.java:196-205 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/CcJobGuiApplication.java:114` calls `Stage` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/CcJobGuiApplication.java:182` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (10 lines × 3) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:121 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:121-130 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java:65-75 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:129-139 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java` as WHOLE FILES: this scan already matched 31 separate duplicated blocks between them, totalling at least 451 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:121` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 3) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:134 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:134-143 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowExecutorListDialog.java:130-139 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobLogListDialog.java:206-215 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowExecutorListDialog.java` as WHOLE FILES: this scan already matched 26 separate duplicated blocks between them, totalling at least 339 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:134` it does not close everything it opens, so those 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, `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:145` calls `getSelectionModel`, `selectFirst` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowExecutorListDialog.java:141` 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 × 3) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/BatchEditDialog.java:70 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/BatchEditDialog.java:70-79 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/CanvasExportDialog.java:66-75 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeRemarkDialog.java:47-56 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/BatchEditDialog.java:70` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 3) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/LogPanel.java:1073 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/LogPanel.java:1073-1082 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MiniMapView.java:598-607 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/TaskTreeView.java:584-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 all 3 call sites, so a change lands once.
D4 · Code Duplication · Edited copy of a member (23 corresponding lines) · ×6
  • Edited copy of a member (23 corresponding lines) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:129 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:129-151 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:203-226 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/PermissionManageDialog.java:958 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/PermissionManageDialog.java:958-980 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/PermissionManageDialog.java:982-1010 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/LogPanel.java:460 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/LogPanel.java:460-482 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/LogPanel.java:488-511 — 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) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/thread/JobRegistryHelper.java:154 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/thread/JobRegistryHelper.java:154-178 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/thread/JobRegistryHelper.java:180-202 — 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) cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/client/AdminApiClient.java:55 — cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/client/AdminApiClient.java:55-77 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/infrastructure/client/ApiClient.java:67-91 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/NodeConnection.java:232 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/NodeConnection.java:232-254 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/NodeConnection.java:283-305 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (14 corresponding lines) · ×6
  • Edited copy of a member (14 corresponding lines) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/TreeDataManager.java:70 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/TreeDataManager.java:70-85 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/TreeDataManager.java:87-100 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:491 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:491-504 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:527-540 — 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) cc-job/cc-job-xo/src/main/java/com/cc/job/xo/common/IBaseEnum.java:47 — cc-job/cc-job-xo/src/main/java/com/cc/job/xo/common/IBaseEnum.java:47-60 | cc-job/cc-job-xo/src/main/java/com/cc/job/xo/common/IBaseEnum.java:71-85 — 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) cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/client/AdminApiClient.java:387 — cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/client/AdminApiClient.java:387-402 | cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/client/AdminApiClient.java:411-424 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/LogPanel.java:537 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/LogPanel.java:537-550 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/TaskNavigationBar.java:181-194 — 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) cc-job/cc-job-core/src/main/java/com/xxl/job/core/thread/ExecutorRegistryThread.java:114 — cc-job/cc-job-core/src/main/java/com/xxl/job/core/thread/ExecutorRegistryThread.java:114-127 | cc-job/cc-job-core/src/main/java/com/xxl/job/core/thread/JobLogFileCleanThread.java:108-122 — 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.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Edited copy of a member (24 corresponding lines) · ×5
  • Edited copy of a member (24 corresponding lines) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/LogPanel.java:587 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/LogPanel.java:587-610 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/TaskNavigationBar.java:231-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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:4672 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:4672-4695 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:4700-4723 — 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) cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/client/AdminApiClient.java:121 — cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/client/AdminApiClient.java:121-144 | cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/client/AdminApiClient.java:153-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) cc-job/cc-job-core/src/main/java/com/xxl/job/core/util/FileUtil.java:51 — cc-job/cc-job-core/src/main/java/com/xxl/job/core/util/FileUtil.java:51-76 | cc-job/cc-job-core/src/main/java/com/xxl/job/core/util/FileUtil.java:78-101 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MiniMapView.java:510 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MiniMapView.java:510-533 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MiniMapView.java:538-561 — 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 (11 corresponding lines) · ×5
  • Edited copy of a member (11 corresponding lines) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/controller/JobParamController.java:83 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/controller/JobParamController.java:83-94 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/param/ParamResolveService.java:24-34 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/DashboardBigScreenStage.java:95 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/DashboardBigScreenStage.java:95-105 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/TaskReportDialog.java:165-176 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:2188 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:2188-2198 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:2201-2211 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:1125 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:1125-1135 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:1137-1147 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobInfoService.java:337 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobInfoService.java:337-347 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobInfoService.java:453-463 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (18 corresponding lines) · ×5
  • Edited copy of a member (18 corresponding lines) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeHistoryView.java:84 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeHistoryView.java:84-105 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeHistoryView.java:107-124 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) REDACTED:23 — REDACTED:23-44 | REDACTED:53-70 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasSelectionManager.java:366 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasSelectionManager.java:366-383 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasSelectionManager.java:385-402 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/LoginView.java:164 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/LoginView.java:164-185 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/RegisterView.java:140-157 — 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) cc-job/cc-job-executor-samples/cc-job-executor-sample-frameless/src/main/java/com/cc/job/executor/sample/sample/frameless/jobhandler/SampleXxlJob.java:51 — cc-job/cc-job-executor-samples/cc-job-executor-sample-frameless/src/main/java/com/cc/job/executor/sample/sample/frameless/jobhandler/SampleXxlJob.java:51-68 | cc-job/cc-job-executor-samples/cc-job-executor-sample-springboot/src/main/java/com/cc/job/executor/sample/service/jobhandler/SampleXxlJob.java:384-401 — 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 (4 corresponding lines) · ×5
  • Edited copy of a member (4 corresponding lines) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/PermissionManageDialog.java:598 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/PermissionManageDialog.java:598-601 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/PermissionManageDialog.java:706-709 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/PermissionManageService.java:85 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/PermissionManageService.java:85-88 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/PermissionManageService.java:133-137 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/TreeContextMenuManager.java:198 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/TreeContextMenuManager.java:198-201 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/TaskTreeView.java:404-407 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/alarm/impl/WebhookJobAlarm.java:137 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/alarm/impl/WebhookJobAlarm.java:137-140 | cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/resolver/ParameterResolver.java:921-933 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:1428 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:1428-1431 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:1567-1570 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (22 lines × 2) · ×5
  • Duplicated block (22 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/HttpClientUtil.java:59 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/HttpClientUtil.java:59-80 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/util/ApiUtil.java:88-109 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/HttpClientUtil.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/util/ApiUtil.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 62 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (22 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ConditionNodeDialog.java:191 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ConditionNodeDialog.java:191-212 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ConditionNodeDialog.java:214-235 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ConditionNodeDialog.java:191` 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeHistoryView.java:173 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeHistoryView.java:173-194 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobLogListDialog.java:642-663 — 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeHistoryView.java:173` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeHistoryView.java:195` calls `getStyleClass`, `add` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobLogListDialog.java:664` 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 (22 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:831 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:831-852 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1603-1624 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java` as WHOLE FILES: this scan already matched 42 separate duplicated blocks between them, totalling at least 585 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 (22 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:1306 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:1306-1327 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/GroupContainer.java:874-895 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/GroupContainer.java` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 569 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (12–13 lines × 2) · ×5
  • Duplicated block (12–13 lines × 2) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:628 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:628-640 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:651-662 — both copies are in the same file, so extract the 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–13 lines × 2) REDACTED:693 — REDACTED:693-705 | REDACTED:814-825 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:693` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12–13 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:114 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:114-125 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/GroupContainer.java:73-85 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/GroupContainer.java` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 569 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–13 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:1246 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:1246-1257 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/GroupContainer.java:847-859 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/GroupContainer.java` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 569 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:1246` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12–13 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobPartService.java:398 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobPartService.java:398-410 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobPartService.java:422-433 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobPartService.java:398` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (10–11 lines × 2) · ×5
  • Duplicated block (10–11 lines × 2) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:523 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:523-533 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:809-818 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:523` it begins part-way through the construct above it, so those exact lines 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) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:1147 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:1147-1157 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:2017-2026 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (10–11 lines × 2) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/thread/JobRegistryHelper.java:216 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/thread/JobRegistryHelper.java:216-226 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/thread/JobRegistryHelper.java:251-260 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/thread/JobRegistryHelper.java:216` it does not close everything it opens, so those exact lines 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) cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/service/HistoricalDataLoader.java:118 — cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/service/HistoricalDataLoader.java:118-128 | cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/service/HistoricalDataLoader.java:193-202 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/service/HistoricalDataLoader.java: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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/service/HistoricalDataLoader.java:129` calls `debug` and `cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/service/HistoricalDataLoader.java:203` 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–11 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:834 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:834-844 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:1948-1957 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Edited copy of a member (50 corresponding lines) · ×4
  • Edited copy of a member (50 corresponding lines) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/PermissionManageDialog.java:461 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/PermissionManageDialog.java:461-510 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/PermissionManageDialog.java:512-563 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:541 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:541-590 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:563-614 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/CcJobGuiApplication.java:67 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/CcJobGuiApplication.java:67-130 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/CcJobGuiApplication.java:135-184 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/TopToolBar.java:1313 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/TopToolBar.java:1313-1362 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/TopToolBar.java:1368-1417 — These two members are one piece of code written twice and then edited apart: 50 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (22 corresponding lines) · ×4
  • Edited copy of a member (22 corresponding lines) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobLogService.java:235 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobLogService.java:235-258 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobLogService.java:266-287 — 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) REDACTED:30 — REDACTED:30-58 | REDACTED:504-525 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/TaskExecutionManager.java:436 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/TaskExecutionManager.java:436-457 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/TaskExecutionManager.java:463-484 — 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) cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/service/FileStorageService.java:227 — cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/service/FileStorageService.java:227-248 | cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/service/FileStorageService.java:256-281 — 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 (21 corresponding lines) · ×4
  • Edited copy of a member (21 corresponding lines) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MiniMapView.java:131 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MiniMapView.java:131-163 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/TaskTreeView.java:93-113 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (21 corresponding lines) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:923 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:923-943 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:2777-2797 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:2690 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:2690-2710 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:3060-3086 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/SSEService.java:253 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/SSEService.java:253-281 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/WebSocketService.java:110-130 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (15 corresponding lines) · ×4
  • Edited copy of a member (15 corresponding lines) REDACTED:60 — REDACTED:60-78 | REDACTED:485-499 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:4768 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:4768-4782 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:4829-4843 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/NodeOperationManager.java:541 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/NodeOperationManager.java:541-555 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:2541-2555 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeHistoryView.java:206 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeHistoryView.java:206-220 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeSearchDialog.java:85-102 — 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 (20 corresponding lines) · ×4
  • Edited copy of a member (20 corresponding lines) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/SettingsDialog.java:96 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/SettingsDialog.java:96-115 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/SettingsDialog.java:117-137 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:1236 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:1236-1257 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/GroupContainer.java:840-859 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasLayoutManager.java:325 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasLayoutManager.java:325-344 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DependencyNavigator.java:67-87 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/NodeOperationManager.java:648 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/NodeOperationManager.java:648-667 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/NodeOperationManager.java:717-739 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (10 corresponding lines) · ×4
  • Edited copy of a member (10 corresponding lines) cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/service/TaskExecutor.java:304 — cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/service/TaskExecutor.java:304-313 | cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/service/TaskExecutor.java:315-325 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeDetailsDialog.java:207 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeDetailsDialog.java:207-216 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/TaskReportDialog.java:84-93 — 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) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/controller/JobParamController.java:69 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/controller/JobParamController.java:69-78 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/controller/JobValidationController.java:67-76 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CycleDetectionManager.java:214 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CycleDetectionManager.java:214-223 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DataManager.java:343-352 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (15–16 lines × 2) · ×4
  • Duplicated block (15–16 lines × 2) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:583 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:583-598 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:892-906 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:583` it begins part-way through the construct above it, so those exact lines 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) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/thread/JobTriggerPoolHelper.java:32 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/thread/JobTriggerPoolHelper.java:32-47 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/thread/JobTriggerPoolHelper.java:53-67 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/thread/JobTriggerPoolHelper.java:32` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15–16 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:112 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:112-126 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:181-196 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java` as WHOLE FILES: this scan already matched 42 separate duplicated blocks between them, totalling at least 585 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–16 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/AddJobFromListDialog.java:247 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/AddJobFromListDialog.java:247-261 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:323-338 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/AddJobFromListDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 175 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.
D4 · Code Duplication · Duplicated block (13–14 lines × 2) · ×4
  • Duplicated block (13–14 lines × 2) REDACTED:65 — REDACTED:65-78 | REDACTED:487-499 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:65` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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–14 lines × 2) cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/resolver/ParameterResolver.java:509 — cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/resolver/ParameterResolver.java:509-521 | cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/resolver/ParameterResolver.java:556-569 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/resolver/ParameterResolver.java:509` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (13–14 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:593 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:593-606 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:642-654 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java` as WHOLE FILES: this scan already matched 46 separate duplicated blocks between them, totalling at least 798 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:593` it does not close everything it opens, so those exact lines 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:2691 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:2691-2703 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:3061-3074 — both copies are in the same file, so extract the 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:3077` calls `getManagedConditionNodes`, `removeConditionNode` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:2705` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (10 lines × 4) · ×4
  • Duplicated block (10 lines × 4) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:493 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:493-502 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:1076-1085 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/GroupContainer.java:472-481 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/GroupContainer.java:697-706 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/GroupContainer.java` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 569 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:493` it begins part-way through the construct above it, so those exact lines 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:1163 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:1163-1172 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:1922-1931 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:2988-2997 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:3057-3066 — 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:1163` it begins part-way through the construct above it, so those exact lines 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:325 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:325-334 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowExecutorListDialog.java:322-331 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:692-701 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobLogListDialog.java:398-407 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowExecutorListDialog.java` as WHOLE FILES: this scan already matched 26 separate duplicated blocks between them, totalling at least 339 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 after the matched lines, `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:335` calls `getStyleClass`, `add` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:702` 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 × 4) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:881 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:881-890 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowExecutorListDialog.java:659-668 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:1190-1199 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobLogListDialog.java:1189-1198 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowExecutorListDialog.java` as WHOLE FILES: this scan already matched 26 separate duplicated blocks between them, totalling at least 339 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:881` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (7 lines × 3) · ×4
  • Duplicated block (7 lines × 3) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/cron/CronExpression.java:1384 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/cron/CronExpression.java:1384-1391 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/cron/CronExpression.java:1438-1444 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/cron/CronExpression.java:1475-1481 — 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 `cc-job/cc-job-admin/src/main/java/com/cc/job/admin/cron/CronExpression.java:1384` it begins part-way through the construct above it, so those 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 (7 lines × 3) REDACTED:125 — REDACTED:125-131 | cc-job/cc-job-executor-samples/cc-job-executor-sample-frameless/src/main/java/com/cc/job/executor/sample/sample/frameless/jobhandler/SampleXxlJob.java:205-211 | cc-job/cc-job-executor-samples/cc-job-executor-sample-springboot/src/main/java/com/cc/job/executor/sample/service/jobhandler/SampleXxlJob.java:538-544 — before extracting anything, compare `cc-job/cc-job-executor-samples/cc-job-executor-sample-frameless/src/main/java/com/cc/job/executor/sample/sample/frameless/jobhandler/SampleXxlJob.java` and `cc-job/cc-job-executor-samples/cc-job-executor-sample-springboot/src/main/java/com/cc/job/executor/sample/service/jobhandler/SampleXxlJob.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 168 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (7 lines × 3) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasNodeManager.java:134 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasNodeManager.java:134-140 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:1367-1373 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/GroupContainer.java:920-926 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/GroupContainer.java` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 569 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasNodeManager.java:134` it does not close everything it opens, so those exact lines 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/PermissionManageDialog.java:453 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/PermissionManageDialog.java:453-459 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/PermissionManageDialog.java:800-806 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/PermissionManageDialog.java:904-910 — 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/PermissionManageDialog.java:453` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (6 lines × 5) · ×4
  • Duplicated block (6 lines × 5) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/BatchEditDialog.java:68 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/BatchEditDialog.java:68-73 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/CanvasExportDialog.java:64-69 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeApprovalSettingDialog.java:51-56 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeRemarkDialog.java:45-50 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/PermissionManageDialog.java:139-144 — 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 5 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/BatchEditDialog.java:68` it does not close everything it opens, so those exact lines 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 × 5) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/PermissionManageDialog.java:137 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/PermissionManageDialog.java:137-142 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:83-88 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowExecutorListDialog.java:77-82 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:143-148 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobLogListDialog.java:113-118 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowExecutorListDialog.java` as WHOLE FILES: this scan already matched 26 separate duplicated blocks between them, totalling at least 339 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (6 lines × 5) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:1279 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:1279-1284 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:2537-2542 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowExecutorListDialog.java:690-695 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:1218-1223 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobLogListDialog.java:1257-1262 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java` as WHOLE FILES: this scan already matched 42 separate duplicated blocks between them, totalling at least 585 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (6 lines × 5) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:1286 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:1286-1291 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:2544-2549 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowExecutorListDialog.java:697-702 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:1225-1230 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobLogListDialog.java:1264-1269 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java` as WHOLE FILES: this scan already matched 42 separate duplicated blocks between them, totalling at least 585 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.
D4 · Code Duplication · Duplicated block (6 lines × 3) · ×4
  • Duplicated block (6 lines × 3) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobDataxService.java:36 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobDataxService.java:36-41 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobJdbcDatasourceService.java:79-84 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobJdbcDatasourceService.java:96-101 — 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobDataxService.java: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 (6 lines × 3) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:864 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:864-869 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java:469-474 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:1131-1136 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java` as WHOLE FILES: this scan already matched 31 separate duplicated blocks between them, totalling at least 451 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (6 lines × 3) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:2475 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:2475-2480 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:2942-2947 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:2972-2977 — 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:2475` it does not close everything it opens, so those exact lines 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:173 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:173-178 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowExecutorListDialog.java:164-169 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:125-130 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowExecutorListDialog.java` as WHOLE FILES: this scan already matched 26 separate duplicated blocks between them, totalling at least 339 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, `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:123` calls `setPadding`, `Insets` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowExecutorListDialog.java:162` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (5 lines × 4) · ×4
  • Duplicated block (5 lines × 4) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/datax/reader/MysqlReader.java:27 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/datax/reader/MysqlReader.java:27-31 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/datax/reader/OracleReader.java:25-30 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/datax/writer/MysqlWriter.java:18-22 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/datax/writer/OracleWriter.java:19-23 — before extracting anything, compare `cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/datax/reader/MysqlReader.java` and `cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/datax/reader/OracleReader.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 67 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/datax/reader/MysqlReader.java:27` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 4) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobDataxService.java:37 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobDataxService.java:37-41 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobJdbcDatasourceService.java:41-46 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobJdbcDatasourceService.java:80-84 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobJdbcDatasourceService.java:97-101 — 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobDataxService.java:37` 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 (5 lines × 4) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobJdbcDatasourceService.java:125 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobJdbcDatasourceService.java:125-129 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobJdbcDatasourceService.java:144-148 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobJdbcDatasourceService.java:162-166 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobPartService.java:496-501 — 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobJdbcDatasourceService.java:125` 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 × 4) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:869 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:869-873 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1594-1598 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1634-1638 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1647-1651 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java` as WHOLE FILES: this scan already matched 42 separate duplicated blocks between them, totalling at least 585 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, `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1593` calls `accept` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:868` 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.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Edited copy of a member (32 corresponding lines) · ×3
  • Edited copy of a member (32 corresponding lines) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:924 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:924-957 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1665-1722 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java:216 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java:216-263 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:713-744 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasSelectionManager.java:143 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasSelectionManager.java:143-174 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasSelectionManager.java:176-208 — 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 (28 corresponding lines) · ×3
  • Edited copy of a member (28 corresponding lines) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/TaskReportDialog.java:222 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/TaskReportDialog.java:222-261 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/TaskReportDialog.java:292-338 — 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) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/route/strategy/ExecutorRouteBusyover.java:20 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/route/strategy/ExecutorRouteBusyover.java:20-47 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/route/strategy/ExecutorRouteFailover.java:18-47 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobLogListDialog.java:548 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobLogListDialog.java:548-575 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobLogListDialog.java:597-629 — 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 · Members sharing a duplicated core (5 members, 50+ identical tokens) · ×3
  • Members sharing a duplicated core (5 members, 50+ identical tokens) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/AddJobFromListDialog.java:321 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/AddJobFromListDialog.java:321-374 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:389-431 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowExecutorListDialog.java:386-425 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:755-817 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobLogListDialog.java:462-527 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:471 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:471-539 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java:297-366 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:483-548 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:760-809 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1445-1513 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:779 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:779-805 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java:371-398 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:1031-1058 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:613-629 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1237-1264 — 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 (39 corresponding lines) · ×3
  • Edited copy of a member (39 corresponding lines) REDACTED:543 — REDACTED:543-584 | REDACTED:836-874 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:587 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:587-637 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/GroupContainer.java:569-607 — These two members are one piece of code written twice and then edited apart: 39 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (39 corresponding lines) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:3183 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:3183-3231 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:3236-3274 — These two members are one piece of code written twice and then edited apart: 39 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (29 corresponding lines) · ×3
  • Edited copy of a member (29 corresponding lines) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/PermissionManageDialog.java:565 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/PermissionManageDialog.java:565-593 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/PermissionManageDialog.java:1060-1089 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DialogManager.java:375 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DialogManager.java:375-403 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DialogManager.java:414-443 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/CanvasRuler.java:135 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/CanvasRuler.java:135-163 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/CanvasRuler.java:168-200 — 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 (26 corresponding lines) · ×3
  • Edited copy of a member (26 corresponding lines) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasDataLoader.java:247 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasDataLoader.java:247-272 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/ParameterAutocompleteService.java:154-180 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:1647 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:1647-1672 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:2909-2942 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ProcessNode.java:1725 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ProcessNode.java:1725-1759 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ProcessNode.java:1765-1790 — 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 (19 corresponding lines) · ×3
  • Edited copy of a member (19 corresponding lines) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:224 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:224-242 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:299-331 — 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) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/controller/JobParamController.java:46 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/controller/JobParamController.java:46-64 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/controller/JobValidationController.java:41-62 — 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) cc-job/cc-job-executor/src/main/java/com/cc/job/executor/core/service/datax/IncrementalDataRefresher.java:247 — cc-job/cc-job-executor/src/main/java/com/cc/job/executor/core/service/datax/IncrementalDataRefresher.java:247-266 | cc-job/cc-job-executor/src/main/java/com/cc/job/executor/core/service/datax/IncrementalDataRefresher.java:285-303 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (17 corresponding lines) · ×3
  • Edited copy of a member (17 corresponding lines) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:1074 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:1074-1090 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:2477-2501 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/AddJobFromListDialog.java:382 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/AddJobFromListDialog.java:382-398 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:822-840 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:703 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:703-719 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:782-803 — 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 (13 corresponding lines) · ×3
  • Edited copy of a member (13 corresponding lines) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:818 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:818-830 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowExecutorListDialog.java:614-626 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/TreeDataManager.java:31 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/TreeDataManager.java:31-45 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/SelectTaskGroupDialog.java:162-174 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:1482 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:1482-1494 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:1496-1508 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (6 corresponding lines) · ×3
  • Edited copy of a member (6 corresponding lines) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:938 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:938-943 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:949-954 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/AddJobFromListDialog.java:143 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/AddJobFromListDialog.java:143-148 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:110-115 — 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) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/utils/JwtUtil.java:56 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/utils/JwtUtil.java:56-61 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobPartService.java:445-450 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (7 corresponding lines) · ×3
  • Edited copy of a member (7 corresponding lines) cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/service/ResultStorageService.java:331 — cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/service/ResultStorageService.java:331-344 | cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/service/HistoricalDataLoader.java:350-356 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:739 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:739-745 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:838-847 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/SSEService.java:399 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/SSEService.java:399-405 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/WebSocketService.java:246-252 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (23 lines × 2) · ×3
  • Duplicated block (23 lines × 2) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/cron/CronExpression.java:894 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/cron/CronExpression.java:894-916 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/cron/CronExpression.java:920-942 — both copies are in the same file, so extract the 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 (23 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:942 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:942-964 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java:490-512 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java` as WHOLE FILES: this scan already matched 31 separate duplicated blocks between them, totalling at least 451 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, `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java:487` calls `getScheduleConf`, `setText` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:939` 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:1005 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:1005-1027 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:1261-1283 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java` as WHOLE FILES: this scan already matched 46 separate duplicated blocks between them, totalling at least 798 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:1005` it begins part-way through the construct above it, so those 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, `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:1028` calls `setReqBody` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:1284` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (20 lines × 2) · ×3
  • Duplicated block (20 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:110 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:110-129 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java:54-73 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java` as WHOLE FILES: this scan already matched 31 separate duplicated blocks between them, totalling at least 451 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:110` it does not close everything it opens, so those exact lines 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:841 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:841-860 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java:443-462 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java` as WHOLE FILES: this scan already matched 31 separate duplicated blocks between them, totalling at least 451 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (20 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:206 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:206-225 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobLogListDialog.java:170-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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:206` it does not close everything it opens, so those 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, `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:205` calls `setPrefWidth` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobLogListDialog.java:169` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (19 lines × 2) · ×3
  • Duplicated block (19 lines × 2) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/cron/CronExpression.java:1372 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/cron/CronExpression.java:1372-1390 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/cron/CronExpression.java:1463-1481 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-admin/src/main/java/com/cc/job/admin/cron/CronExpression.java:1372` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (19 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/NodeOperationManager.java:93 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/NodeOperationManager.java:93-111 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/NodeOperationManager.java:152-170 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/NodeOperationManager.java:93` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (19 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:3213 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:3213-3231 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:3256-3274 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:3213` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (18 lines × 2) · ×3
  • Duplicated block (18 lines × 2) cc-job/cc-job-core/src/main/java/com/xxl/job/core/util/LocalDateTimeAdapter.java:26 — cc-job/cc-job-core/src/main/java/com/xxl/job/core/util/LocalDateTimeAdapter.java:26-43 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/util/LocalDateTimeAdapter.java:26-43 — before extracting anything, compare `cc-job/cc-job-core/src/main/java/com/xxl/job/core/util/LocalDateTimeAdapter.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/util/LocalDateTimeAdapter.java` as WHOLE FILES: 96% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (18 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:62 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:62-79 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowExecutorListDialog.java:53-70 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowExecutorListDialog.java` as WHOLE FILES: this scan already matched 26 separate duplicated blocks between them, totalling at least 339 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (18 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:981 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:981-998 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1149-1166 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:981` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
D4 · Code Duplication · Duplicated block (14–15 lines × 2) · ×3
  • Duplicated block (14–15 lines × 2) cc-job/cc-job-executor/src/main/java/com/cc/job/executor/core/service/JdbcTaskExecutor.java:159 — cc-job/cc-job-executor/src/main/java/com/cc/job/executor/core/service/JdbcTaskExecutor.java:159-173 | cc-job/cc-job-executor/src/main/java/com/cc/job/executor/core/service/JdbcTaskExecutor.java:249-262 — both copies are in the same file, so extract the 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, `cc-job/cc-job-executor/src/main/java/com/cc/job/executor/core/service/JdbcTaskExecutor.java:176` calls `currentTimeMillis` and `cc-job/cc-job-executor/src/main/java/com/cc/job/executor/core/service/JdbcTaskExecutor.java:264` 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 (14–15 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:143 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:143-156 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java:92-106 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java` as WHOLE FILES: this scan already matched 31 separate duplicated blocks between them, totalling at least 451 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:143` 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–15 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:2389 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:2389-2402 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:2440-2454 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:2389` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note first that the copies are not typed on the same thing: the declarations holding them bind `items` to `List<DataxTable>` in one and `List<String>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (14 lines × 3) · ×3
  • Duplicated block (14 lines × 3) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/thread/JobCompleteHelper.java:46 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/thread/JobCompleteHelper.java:46-59 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/thread/JobRegistryHelper.java:41-54 | cc-job/cc-job-core/src/main/java/com/xxl/job/core/server/EmbedServer.java:45-58 — 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 `cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/thread/JobCompleteHelper.java:46` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14 lines × 3) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:1110 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:1110-1123 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java:593-606 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:1364-1377 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java` as WHOLE FILES: this scan already matched 31 separate duplicated blocks between them, totalling at least 451 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:1110` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:1363` calls `getValue` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:1109` 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 (14 lines × 3) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:62 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:62-75 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowExecutorListDialog.java:53-66 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobLogListDialog.java:87-100 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowExecutorListDialog.java` as WHOLE FILES: this scan already matched 26 separate duplicated blocks between them, totalling at least 339 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 after the matched lines, `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobLogListDialog.java:103` calls `loadJobGroups` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:78` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (11 lines × 3) · ×3
  • Duplicated block (11 lines × 3) cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/service/FileStorageService.java:149 — cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/service/FileStorageService.java:149-159 | cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/service/FileStorageService.java:191-201 | cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/service/FileStorageService.java:261-271 — 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 `cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/service/FileStorageService.java: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 × 3) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:1064 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:1064-1074 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java:569-579 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:1318-1328 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java` as WHOLE FILES: this scan already matched 31 separate duplicated blocks between them, totalling at least 451 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 × 3) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:858 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:858-868 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1052-1062 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1112-1122 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
D4 · Code Duplication · Duplicated block (9 lines × 3) · ×3
  • Duplicated block (9 lines × 3) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:516 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:516-524 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java:343-351 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1490-1498 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java` as WHOLE FILES: this scan already matched 31 separate duplicated blocks between them, totalling at least 451 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, `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java:340` calls `setText` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:513` 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 × 3) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:1774 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:1774-1782 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:1786-1794 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:1798-1806 — 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:1774` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (9 lines × 3) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/controller/JobCanvasBookmarkController.java:65 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/controller/JobCanvasBookmarkController.java:65-73 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/controller/JobGroupSnapshotController.java:68-76 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/controller/JobNodeTemplateController.java:83-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 all 3 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/controller/JobGroupSnapshotController.java:64` calls `failed` and `cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/controller/JobCanvasBookmarkController.java:61` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (5 lines × 3) · ×3
  • Duplicated block (5 lines × 3) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:2881 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:2881-2885 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:2975-2979 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:3029-3033 — 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 (5 lines × 3) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/PermissionManageDialog.java:478 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/PermissionManageDialog.java:478-482 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/PermissionManageDialog.java:535-539 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/PermissionManageDialog.java:1026-1030 — 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 (5 lines × 3) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:701 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:701-705 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:2592-2596 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:3955-3959 — 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.
GD1 · Unfinished & placeholder code · Unfinished stub · ×3
  • Unfinished stub — returns a placeholder under a TODO marker cc-job/cc-job-admin/src/main/java/com/cc/job/admin/cron/CronExpression.java:1584 — `getTimeBefore` is a shipped method whose whole body returns a default value under a TODO/FIXME — a placeholder standing in for the implementation. Implement it or remove it.
  • Unfinished stub — returns a placeholder under a TODO marker cc-job/cc-job-admin/src/main/java/com/cc/job/admin/cron/CronExpression.java:1593 — `getFinalFireTime` is a shipped method whose whole body returns a default value under a TODO/FIXME — a placeholder standing in for the implementation. Implement it or remove it.
  • Unfinished stub — returns a placeholder under a TODO marker cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/ParameterAutocompleteService.java:474 — `getAttributesFromTaskGroup` is a shipped method whose whole body returns a default value under a TODO/FIXME — a placeholder standing in for the implementation. Implement it or remove it.
D1 · Cyclomatic Complexity · SampleXxlJob.httpJobHandler (cyclomatic 19) · ×2
  • SampleXxlJob.httpJobHandler (cyclomatic 19) cc-job/cc-job-executor-samples/cc-job-executor-sample-frameless/src/main/java/com/cc/job/executor/sample/sample/frameless/jobhandler/SampleXxlJob.java:126 — SampleXxlJob.httpJobHandler 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.
  • SampleXxlJob.httpJobHandler (cyclomatic 19) cc-job/cc-job-executor-samples/cc-job-executor-sample-springboot/src/main/java/com/cc/job/executor/sample/service/jobhandler/SampleXxlJob.java:459 — SampleXxlJob.httpJobHandler 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.
D1 · Cyclomatic Complexity · 1.run (cyclomatic 18) · ×2
  • 1.run (cyclomatic 18) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/thread/JobFailMonitorHelper.java:38 — 1.run 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.
  • 1.run (cyclomatic 18) cc-job/cc-job-core/src/main/java/com/xxl/job/core/thread/ExecutorRegistryThread.java:40 — 1.run 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.
D10 · Test Quality · No assertions · ×2
  • No assertions: test cc-job/cc-job-executor-samples/cc-job-executor-sample-frameless/src/test/java/com/cc/job/executor/sample/sample/frameless/test/FramelessApplicationTest.java:8 — This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: test cc-job/cc-job-executor-samples/cc-job-executor-sample-springboot/src/test/java/com/cc/job/executor/sample/test/XxlJobExecutorExampleBootApplicationTests.java:10 — This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
D10 · Test Quality · Test project verifies nothing · ×2
  • Test project verifies nothing: cc-job-executor-sample-frameless cc-job/cc-job-executor-samples/cc-job-executor-sample-frameless/src/test/java/com/cc/job/executor/sample/sample/frameless/test/FramelessApplicationTest.java:8 — No conventional assertion call was detected in 1 of 1 tests in `cc-job-executor-sample-frameless` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
  • Test project verifies nothing: cc-job-executor-sample-springboot cc-job/cc-job-executor-samples/cc-job-executor-sample-springboot/src/test/java/com/cc/job/executor/sample/test/XxlJobExecutorExampleBootApplicationTests.java:10 — No conventional assertion call was detected in 1 of 1 tests in `cc-job-executor-sample-springboot` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
D2 · Cognitive Complexity · SampleXxlJob.httpJobHandler (cognitive 21) · ×2
  • SampleXxlJob.httpJobHandler (cognitive 21) cc-job/cc-job-executor-samples/cc-job-executor-sample-frameless/src/main/java/com/cc/job/executor/sample/sample/frameless/jobhandler/SampleXxlJob.java:126 — SampleXxlJob.httpJobHandler has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 4, error handling 2, 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.
  • SampleXxlJob.httpJobHandler (cognitive 21) cc-job/cc-job-executor-samples/cc-job-executor-sample-springboot/src/main/java/com/cc/job/executor/sample/service/jobhandler/SampleXxlJob.java:459 — SampleXxlJob.httpJobHandler has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 4, error handling 2, 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.
D4 · Code Duplication · Near-duplicate member pair (43 shared lines) · ×2
  • Near-duplicate member pair (43 shared lines) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:968 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:968-1061 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:1225-1312 — These two members are variants of one another: 43 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 (43 shared lines) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:923 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:923-983 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1826-1883 — These two members are variants of one another: 43 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 (64 corresponding lines) · ×2
  • Edited copy of a member (64 corresponding lines) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:518 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:518-581 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/GroupContainer.java:498-563 — These two members are one piece of code written twice and then edited apart: 64 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (64 corresponding lines) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:1723 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:1723-1794 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:1820-1883 — These two members are one piece of code written twice and then edited apart: 64 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (45 corresponding lines) · ×2
  • Edited copy of a member (45 corresponding lines) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/TopToolBar.java:695 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/TopToolBar.java:695-743 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/TopToolBar.java:782-826 — These two members are one piece of code written twice and then edited apart: 45 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (45 corresponding lines) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:1915 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:1915-1959 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:1984-2032 — These two members are one piece of code written twice and then edited apart: 45 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (31 corresponding lines) · ×2
  • Edited copy of a member (31 corresponding lines) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:286 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:286-316 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/GroupContainer.java:234-268 — 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:747 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:747-777 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:852-904 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (36 corresponding lines) · ×2
  • Edited copy of a member (36 corresponding lines) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeHistoryView.java:165 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeHistoryView.java:165-201 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobLogListDialog.java:634-669 — 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.
  • Edited copy of a member (36 corresponding lines) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/TopToolBar.java:499 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/TopToolBar.java:499-535 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/TopToolBar.java:745-780 — 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, 9+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 9+ corresponding lines) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/DashboardService.java:41 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/DashboardService.java:41-55 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/DashboardService.java:60-68 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/DashboardService.java:74-84 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 9+ corresponding lines) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/PermissionManageDialog.java:595 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/PermissionManageDialog.java:595-603 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/PermissionManageDialog.java:703-711 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/PermissionManageDialog.java:713-721 — 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, 12+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 12+ corresponding lines) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/NodeSearchManager.java:187 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/NodeSearchManager.java:187-199 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/NodeSearchManager.java:242-253 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/NodeSearchManager.java:262-274 — 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) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/utils/JacksonUtil.java:36 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/utils/JacksonUtil.java:36-47 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/utils/JacksonUtil.java:57-68 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/utils/JacksonUtil.java:79-91 — 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, 11+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 11+ corresponding lines) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:3300 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:3300-3316 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:3321-3331 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:3372-3382 — 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.
  • Edited copies of one member (3 members, 11+ corresponding lines) cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/service/TaskExecutor.java:222 — cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/service/TaskExecutor.java:222-232 | cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/service/TaskExecutor.java:238-250 | cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/service/TaskExecutor.java:256-268 — 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 · Duplicated block (51–52 lines × 2) · ×2
  • Duplicated block (51–52 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasConnectionManager.java:195 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasConnectionManager.java:195-246 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasConnectionManager.java:271-321 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasConnectionManager.java:195` 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 (51–52 lines × 2) cc-job/cc-job-core/src/main/java/com/xxl/job/core/glue/CSharpGlueFactory.java:278 — cc-job/cc-job-core/src/main/java/com/xxl/job/core/glue/CSharpGlueFactory.java:278-329 | cc-job/cc-job-core/src/main/java/com/xxl/job/core/glue/CSharpGlueFactory.java:390-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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `cc-job/cc-job-core/src/main/java/com/xxl/job/core/glue/CSharpGlueFactory.java:443` calls `deleteDirectory`, `File` and `cc-job/cc-job-core/src/main/java/com/xxl/job/core/glue/CSharpGlueFactory.java:331` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (31 lines × 2) · ×2
  • Duplicated block (31 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeHistoryView.java:340 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeHistoryView.java:340-370 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobLogListDialog.java:1225-1255 — 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 (31 lines × 2) cc-job/cc-job-core/src/main/java/com/xxl/job/core/biz/client/AdminBizClient.java:18 — cc-job/cc-job-core/src/main/java/com/xxl/job/core/biz/client/AdminBizClient.java:18-48 | cc-job/cc-job-core/src/main/java/com/xxl/job/core/biz/client/ExecutorBizClient.java:14-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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (30 lines × 2) · ×2
  • Duplicated block (30 lines × 2) REDACTED:555 — REDACTED:555-584 | REDACTED:845-874 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:555` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `REDACTED:554` calls `setFailStrategy`, `getFailStrategy` and `REDACTED:844` 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 (30 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:1360 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:1360-1389 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/GroupContainer.java:913-942 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/GroupContainer.java` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 569 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:1360` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (23–27 lines × 2) · ×2
  • Duplicated block (23–27 lines × 2) REDACTED:97 — REDACTED:97-123 | REDACTED:134-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 (23–27 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:588 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:588-614 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/GroupContainer.java:570-592 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/GroupContainer.java` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 569 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:588` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (26 lines × 2) · ×2
  • Duplicated block (26 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:804 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:804-829 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:997-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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:804` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:799` calls `getPrefWidth`, `getPrefHeight` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:993` 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) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/controller/dto/DashboardExportTrendRow.java:1 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/controller/dto/DashboardExportTrendRow.java:1-26 | cc-job/cc-job-xo/src/main/java/com/cc/job/xo/model/vo/DashboardTrendItemVO.java:1-58 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/controller/dto/DashboardExportTrendRow.java:1` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (24 lines × 2) · ×2
  • Duplicated block (24 lines × 2) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/thread/JobCompleteHelper.java:102 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/thread/JobCompleteHelper.java:102-125 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/thread/JobFailMonitorHelper.java:88-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 `cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/thread/JobCompleteHelper.java:102` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/thread/JobCompleteHelper.java:131` calls `shutdownNow` and `cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/thread/JobFailMonitorHelper.java:116` 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 (24 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:199 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:199-222 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:274-297 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java` as WHOLE FILES: this scan already matched 42 separate duplicated blocks between them, totalling at least 585 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (20–21 lines × 2) · ×2
  • Duplicated block (20–21 lines × 2) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/route/strategy/ExecutorRouteBusyover.java:28 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/route/strategy/ExecutorRouteBusyover.java:28-47 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/route/strategy/ExecutorRouteFailover.java:27-47 — 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 `cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/route/strategy/ExecutorRouteBusyover.java:28` it begins part-way through the construct above it, so those 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 (20–21 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/TaskExecutionManager.java:203 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/TaskExecutionManager.java:203-222 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/TaskExecutionManager.java:354-374 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/TaskExecutionManager.java:203` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (17–20 lines × 2) · ×2
  • Duplicated block (17–20 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/LogPanel.java:113 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/LogPanel.java:113-129 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MiniMapView.java:142-161 — 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, `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MiniMapView.java:139` calls `setHgrow` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/LogPanel.java:111` 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–20 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:571 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:571-590 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:598-614 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java` as WHOLE FILES: this scan already matched 46 separate duplicated blocks between them, totalling at least 798 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:571` 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, `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:595` calls `setTaskGroupId` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:569` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (18–19 lines × 2) · ×2
  • Duplicated block (18–19 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:319 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:319-336 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/GroupContainer.java:271-289 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/GroupContainer.java` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 569 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (18–19 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:499 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:499-516 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/GroupContainer.java:478-496 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/GroupContainer.java` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 569 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:499` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
D4 · Code Duplication · Duplicated block (17–18 lines × 2) · ×2
  • Duplicated block (17–18 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:469 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:469-485 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowExecutorListDialog.java:443-460 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowExecutorListDialog.java` as WHOLE FILES: this scan already matched 26 separate duplicated blocks between them, totalling at least 339 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 (17–18 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobLogListDialog.java:484 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobLogListDialog.java:484-501 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobLogListDialog.java:1127-1143 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (16–17 lines × 2) · ×2
  • Duplicated block (16–17 lines × 2) cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/config/XxlJobConfig.java:111 — cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/config/XxlJobConfig.java:111-126 | cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/orchestrator/TaskGroupOrchestrator.java:128-144 — 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 `cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/config/XxlJobConfig.java:111` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (16–17 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:136 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:136-151 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:210-226 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java` as WHOLE FILES: this scan already matched 42 separate duplicated blocks between them, totalling at least 585 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:136` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (13–16 lines × 4) · ×2
  • Duplicated block (13–16 lines × 4) cc-job/cc-job-executor/src/main/java/com/cc/job/executor/core/service/datax/IncrementalDataRefresher.java:185 — cc-job/cc-job-executor/src/main/java/com/cc/job/executor/core/service/datax/IncrementalDataRefresher.java:185-197 | cc-job/cc-job-executor/src/main/java/com/cc/job/executor/core/service/datax/IncrementalDataRefresher.java:200-212 | cc-job/cc-job-executor/src/main/java/com/cc/job/executor/core/service/datax/IncrementalDataRefresher.java:251-266 | cc-job/cc-job-executor/src/main/java/com/cc/job/executor/core/service/datax/IncrementalDataRefresher.java:288-303 — 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 `cc-job/cc-job-executor/src/main/java/com/cc/job/executor/core/service/datax/IncrementalDataRefresher.java:251` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13–16 lines × 4) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:432 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:432-446 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java:245-260 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:433-448 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1409-1421 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java` as WHOLE FILES: this scan already matched 31 separate duplicated blocks between them, totalling at least 451 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, `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:429` calls `add` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java:242` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (12–14 lines × 2) · ×2
  • Duplicated block (12–14 lines × 2) REDACTED:598 — REDACTED:598-611 | REDACTED:742-753 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:722 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:722-733 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:809-822 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java` as WHOLE FILES: this scan already matched 46 separate duplicated blocks between them, totalling at least 798 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:722` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (13 lines × 3) · ×2
  • Duplicated block (13 lines × 3) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:603 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:603-615 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:912-924 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobInfoServiceImpl.java:999-1011 — 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 `cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:603` it does not close everything it opens, so those exact lines 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/infrastructure/client/ApiClient.java:73 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/infrastructure/client/ApiClient.java:73-85 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/HttpClientUtil.java:63-75 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/util/ApiUtil.java:92-104 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/HttpClientUtil.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/util/ApiUtil.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 62 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/infrastructure/client/ApiClient.java:73` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (12 lines × 3) · ×2
  • Duplicated block (12 lines × 3) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/GlueIdeDialog.java:76 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/GlueIdeDialog.java:76-87 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:117-128 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java:61-72 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/GlueIdeDialog.java:76` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 3) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowExecutorListDialog.java:656 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowExecutorListDialog.java:656-667 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:1187-1198 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobLogListDialog.java:1186-1197 — 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowExecutorListDialog.java:656` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (10–12 lines × 2) · ×2
  • Duplicated block (10–12 lines × 2) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:402 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:402-411 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:738-749 — both copies are in the same file, so extract the 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, `cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:399` calls `JobNode`, `setJobId`, `getId` and `cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:736` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (10–12 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/AddJobFromListDialog.java:151 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/AddJobFromListDialog.java:151-160 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:194-205 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/AddJobFromListDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 175 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.
D4 · Code Duplication · Duplicated block (11–12 lines × 2) · ×2
  • Duplicated block (11–12 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:683 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:683-694 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:1661-1671 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java: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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:679` calls `isBlank` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:1659` 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–12 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:988 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:988-998 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:1240-1251 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java` as WHOLE FILES: this scan already matched 46 separate duplicated blocks between them, totalling at least 798 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:988` it does not close everything it opens, so those 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, `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:1252` calls `setExecutorHandler` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:999` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (8–10 lines × 4) · ×2
  • Duplicated block (8–10 lines × 4) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java:195 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java:195-204 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:288-297 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:698-705 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1359-1368 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java` as WHOLE FILES: this scan already matched 25 separate duplicated blocks between them, totalling at least 367 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–10 lines × 4) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:96 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:96-103 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowExecutorListDialog.java:90-99 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:168-177 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobLogListDialog.java:126-134 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowExecutorListDialog.java` as WHOLE FILES: this scan already matched 26 separate duplicated blocks between them, totalling at least 339 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:96` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (9–10 lines × 2) · ×2
  • Duplicated block (9–10 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/EdgeStyleDialog.java:155 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/EdgeStyleDialog.java:155-164 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeStyleDialog.java:268-276 — 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 (9–10 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:112 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:112-120 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowExecutorListDialog.java:111-120 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowExecutorListDialog.java` as WHOLE FILES: this scan already matched 26 separate duplicated blocks between them, totalling at least 339 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.
D4 · Code Duplication · Duplicated block (9 lines × 4) · ×2
  • Duplicated block (9 lines × 4) REDACTED:383 — REDACTED:383-391 | REDACTED:489-497 | REDACTED:672-680 | REDACTED:797-805 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (9 lines × 4) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:4329 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:4329-4337 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:4342-4350 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:4366-4374 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:4379-4387 — 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:4329` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (8 lines × 4) · ×2
  • Duplicated block (8 lines × 4) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DialogManager.java:107 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DialogManager.java:107-114 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DialogManager.java:149-156 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DialogManager.java:194-201 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DialogManager.java:244-251 — 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DialogManager.java:107` 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 × 4) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/NodeCallbackConfigurator.java:156 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/NodeCallbackConfigurator.java:156-163 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/NodeCallbackConfigurator.java:232-239 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/NodeCallbackConfigurator.java:261-268 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/NodeCallbackConfigurator.java:287-294 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (7–8 lines × 3) · ×2
  • Duplicated block (7–8 lines × 3) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:1016 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:1016-1022 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1919-1925 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobLogListDialog.java:1094-1101 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobLogListDialog.java:1103` calls `debug` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:1025` 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–8 lines × 3) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:913 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:913-919 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:1003-1010 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1788-1795 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java` as WHOLE FILES: this scan already matched 42 separate duplicated blocks between them, totalling at least 585 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.
D4 · Code Duplication · Duplicated block (7–8 lines × 2) · ×2
  • Duplicated block (7–8 lines × 2) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/cron/CronExpression.java:533 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/cron/CronExpression.java:533-539 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/cron/CronExpression.java:549-556 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-admin/src/main/java/com/cc/job/admin/cron/CronExpression.java:533` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7–8 lines × 2) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/datax/reader/MysqlReader.java:27 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/datax/reader/MysqlReader.java:27-33 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/datax/reader/OracleReader.java:25-32 — before extracting anything, compare `cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/datax/reader/MysqlReader.java` and `cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/datax/reader/OracleReader.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 67 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/datax/reader/MysqlReader.java:27` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (7 lines × 4) · ×2
  • Duplicated block (7 lines × 4) cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/client/AdminApiClient.java:192 — cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/client/AdminApiClient.java:192-198 | cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/client/AdminApiClient.java:219-225 | cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/client/AdminApiClient.java:252-258 | cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/client/AdminApiClient.java:279-285 — 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 `cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/client/AdminApiClient.java:192` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 4) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:4788 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:4788-4794 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:4809-4815 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:4849-4855 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:4870-4876 — 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.
D4 · Code Duplication · Duplicated block (6 lines × 4) · ×2
  • Duplicated block (6 lines × 4) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/alarm/impl/DingTalkJobAlarm.java:44 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/alarm/impl/DingTalkJobAlarm.java:44-49 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/alarm/impl/FeishuJobAlarm.java:40-45 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/alarm/impl/WeComJobAlarm.java:40-45 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/alarm/impl/WebhookJobAlarm.java:65-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 all 4 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/alarm/impl/DingTalkJobAlarm.java: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.
  • Duplicated block (6 lines × 4) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:803 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:803-808 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:864-869 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1058-1063 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1118-1123 — 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.
D5 · Coupling · Off the main sequence · ×2
  • Off the main sequence: cc-job-core — cc-job-core: abstractness 0.07, instability 0.00, distance 0.93 — zone of pain — concrete and depended on by 5 project(s), so it's rigid to change.
  • Off the main sequence: cc-job-xo — cc-job-xo: abstractness 0.25, instability 0.00, distance 0.75 — zone of pain — concrete and depended on by 4 project(s), so it's rigid to change.
X13 · Undrained process stream · Redirected process stream is never drained (deadlock) · ×2
  • Redirected process stream is never drained (deadlock) cc-job/cc-job-core/src/main/java/com/xxl/job/core/glue/CSharpGlueFactory.java:455 — The JDK pipes both `stdout` and `stderr` of this child — no `redirectErrorStream`, `redirectError`, `redirectOutput` or `inheritIO` is set — and the parent waits on `process.waitFor()` while nothing in this scope ever reads stdout and stderr. The JDK's own `Process` documentation warns that failing to read a child's output promptly "may cause the process to block, or even deadlock": once the child writes more than the pipe holds (measured on OpenJDK 25 / Linux: 60,000 bytes finishes, 70,000 hangs forever), it blocks on the write, never exits, and the wait never returns. Nothing fails loudly. Read every piped stream before (or while) waiting — a thread or `CompletableFuture` per stream — merge them with `redirectErrorStream(true)` and read the one stream before `waitFor`, or discard what you do not want with `redirectOutput`/`redirectError(ProcessBuilder.Redirect.DISCARD)` (or a file).
  • Redirected process stream is never drained (deadlock) cc-job/cc-job-core/src/main/java/com/xxl/job/core/glue/CSharpGlueFactory.java:470 — The JDK pipes both `stdout` and `stderr` of this child — no `redirectErrorStream`, `redirectError`, `redirectOutput` or `inheritIO` is set — and the parent waits on `process.waitFor()` while nothing in this scope ever reads stderr. The JDK's own `Process` documentation warns that failing to read a child's output promptly "may cause the process to block, or even deadlock": once the child writes more than the pipe holds (measured on OpenJDK 25 / Linux: 60,000 bytes finishes, 70,000 hangs forever), it blocks on the write, never exits, and the wait never returns. Nothing fails loudly. Read every piped stream before (or while) waiting — a thread or `CompletableFuture` per stream — merge them with `redirectErrorStream(true)` and read the one stream before `waitFor`, or discard what you do not want with `redirectOutput`/`redirectError(ProcessBuilder.Redirect.DISCARD)` (or a file).
D1 · Cyclomatic Complexity · ShowDataxSyncDialog.applyEditData (cyclomatic 76) · ×1
  • ShowDataxSyncDialog.applyEditData (cyclomatic 76) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:434 — ShowDataxSyncDialog.applyEditData has cyclomatic complexity 76 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · NodeDetailsDialog.loadDetails (cyclomatic 69) · ×1
  • NodeDetailsDialog.loadDetails (cyclomatic 69) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeDetailsDialog.java:233 — NodeDetailsDialog.loadDetails has cyclomatic complexity 69 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · CronExpression.getTimeAfter (cyclomatic 67) · ×1
  • CronExpression.getTimeAfter (cyclomatic 67) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/cron/CronExpression.java:1162 — CronExpression.getTimeAfter has cyclomatic complexity 67 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · CronExpression.addToSet (cyclomatic 66) · ×1
  • CronExpression.addToSet (cyclomatic 66) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/cron/CronExpression.java:958 — CronExpression.addToSet has cyclomatic complexity 66 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · JobComposeServiceImpl.operateToSaveJobCompose (cyclomatic 63) · ×1
  • JobComposeServiceImpl.operateToSaveJobCompose (cyclomatic 63) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:321 — JobComposeServiceImpl.operateToSaveJobCompose has cyclomatic complexity 63 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · NodeCanvas.loadFromComposeData (cyclomatic 56) · ×1
  • NodeCanvas.loadFromComposeData (cyclomatic 56) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:2060 — NodeCanvas.loadFromComposeData has cyclomatic complexity 56 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · CronExpression.storeExpressionVals (cyclomatic 53) · ×1
  • CronExpression.storeExpressionVals (cyclomatic 53) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/cron/CronExpression.java:517 — CronExpression.storeExpressionVals has cyclomatic complexity 53 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · CanvasDataLoader.createNodeFromData (cyclomatic 48) · ×1
  • CanvasDataLoader.createNodeFromData (cyclomatic 48) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasDataLoader.java:47 — CanvasDataLoader.createNodeFromData has cyclomatic complexity 48 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · JobComposeServiceImpl.buildAllNodesAndEdgesRecursive (cyclomatic 47) · ×1
  • JobComposeServiceImpl.buildAllNodesAndEdgesRecursive (cyclomatic 47) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:1006 — JobComposeServiceImpl.buildAllNodesAndEdgesRecursive has cyclomatic complexity 47 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · ShowDataxSyncDialog.handleNext (cyclomatic 44) · ×1
  • ShowDataxSyncDialog.handleNext (cyclomatic 44) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1515 — ShowDataxSyncDialog.handleNext has cyclomatic complexity 44 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · ParameterResolver.resolveNestedAttribute (cyclomatic 42) · ×1
  • ParameterResolver.resolveNestedAttribute (cyclomatic 42) cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/resolver/ParameterResolver.java:489 — ParameterResolver.resolveNestedAttribute 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.
D1 · Cyclomatic Complexity · JobComposeServiceImpl.buildNodeVosRecursive (cyclomatic 41) · ×1
  • JobComposeServiceImpl.buildNodeVosRecursive (cyclomatic 41) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:1873 — JobComposeServiceImpl.buildNodeVosRecursive 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.
D1 · Cyclomatic Complexity · JobComposeServiceImpl.operateToUpdateJobCompose (cyclomatic 41) · ×1
  • JobComposeServiceImpl.operateToUpdateJobCompose (cyclomatic 41) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:702 — JobComposeServiceImpl.operateToUpdateJobCompose 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.
D1 · Cyclomatic Complexity · ParameterResolver.getValueFromContext (cyclomatic 41) · ×1
  • ParameterResolver.getValueFromContext (cyclomatic 41) cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/resolver/ParameterResolver.java:163 — ParameterResolver.getValueFromContext 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.
D1 · Cyclomatic Complexity · SmartParameterInput.handleSmartDelete (cyclomatic 40) · ×1
  • SmartParameterInput.handleSmartDelete (cyclomatic 40) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/component/SmartParameterInput.java:769 — SmartParameterInput.handleSmartDelete 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.
D1 · Cyclomatic Complexity · TaskGroupOrchestrator.prepareExecution (cyclomatic 38) · ×1
  • TaskGroupOrchestrator.prepareExecution (cyclomatic 38) cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/orchestrator/TaskGroupOrchestrator.java:199 — TaskGroupOrchestrator.prepareExecution 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.
D1 · Cyclomatic Complexity · NodeCallbackConfigurator.configureNodeCallbacks (cyclomatic 37) · ×1
  • NodeCallbackConfigurator.configureNodeCallbacks (cyclomatic 37) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/NodeCallbackConfigurator.java:59 — NodeCallbackConfigurator.configureNodeCallbacks has cyclomatic complexity 37 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · ConditionNode.bindCanvasNodes (cyclomatic 37) · ×1
  • ConditionNode.bindCanvasNodes (cyclomatic 37) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:663 — ConditionNode.bindCanvasNodes 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.
D1 · Cyclomatic Complexity · JobInfoServiceImpl.baseUpdateJobInfo (cyclomatic 36) · ×1
  • JobInfoServiceImpl.baseUpdateJobInfo (cyclomatic 36) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobInfoServiceImpl.java:1165 — JobInfoServiceImpl.baseUpdateJobInfo 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.
D1 · Cyclomatic Complexity · JobInfoServiceImpl.baseSaveJobInfo (cyclomatic 32) · ×1
  • JobInfoServiceImpl.baseSaveJobInfo (cyclomatic 32) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobInfoServiceImpl.java:789 — JobInfoServiceImpl.baseSaveJobInfo has cyclomatic complexity 32 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · ExecutorBizImpl.run (cyclomatic 32) · ×1
  • ExecutorBizImpl.run (cyclomatic 32) cc-job/cc-job-core/src/main/java/com/xxl/job/core/biz/impl/ExecutorBizImpl.java:51 — ExecutorBizImpl.run has cyclomatic complexity 32 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · DataManager.buildNodesData (cyclomatic 32) · ×1
  • DataManager.buildNodesData (cyclomatic 32) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DataManager.java:151 — DataManager.buildNodesData has cyclomatic complexity 32 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · JobPartService.parseJobComposeData (cyclomatic 31) · ×1
  • JobPartService.parseJobComposeData (cyclomatic 31) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobPartService.java:76 — JobPartService.parseJobComposeData 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.
D1 · Cyclomatic Complexity · NewJobDialog.fillFormData (cyclomatic 31) · ×1
  • NewJobDialog.fillFormData (cyclomatic 31) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:862 — NewJobDialog.fillFormData 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.
D1 · Cyclomatic Complexity · MainView.setupCallbacks (cyclomatic 30) · ×1
  • MainView.setupCallbacks (cyclomatic 30) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:261 — MainView.setupCallbacks 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.
D1 · Cyclomatic Complexity · NodeCanvas.performSmoothScroll (cyclomatic 30) · ×1
  • NodeCanvas.performSmoothScroll (cyclomatic 30) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:700 — NodeCanvas.performSmoothScroll 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.
D1 · Cyclomatic Complexity · CronExpression.checkNext (cyclomatic 29) · ×1
  • CronExpression.checkNext (cyclomatic 29) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/cron/CronExpression.java:711 — CronExpression.checkNext has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · 1.run (cyclomatic 29) · ×1
  • 1.run (cyclomatic 29) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/thread/JobScheduleHelper.java:44 — 1.run has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · HistoricalDataLoader.loadFromDatabase (cyclomatic 29) · ×1
  • HistoricalDataLoader.loadFromDatabase (cyclomatic 29) cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/service/HistoricalDataLoader.java:44 — HistoricalDataLoader.loadFromDatabase has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · ShowDataxSyncDialog.buildDataxJobInfoForm (cyclomatic 28) · ×1
  • ShowDataxSyncDialog.buildDataxJobInfoForm (cyclomatic 28) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1665 — ShowDataxSyncDialog.buildDataxJobInfoForm 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.
D1 · Cyclomatic Complexity · ProcessNode.setupDragHandlers (cyclomatic 27) · ×1
  • ProcessNode.setupDragHandlers (cyclomatic 27) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ProcessNode.java:532 — ProcessNode.setupDragHandlers 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.
D1 · Cyclomatic Complexity · SSEConnection.connectAndListen (cyclomatic 27) · ×1
  • SSEConnection.connectAndListen (cyclomatic 27) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/SSEService.java:140 — SSEConnection.connectAndListen 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.
D1 · Cyclomatic Complexity · NewJobNodeDialog.fillFormData (cyclomatic 27) · ×1
  • NewJobNodeDialog.fillFormData (cyclomatic 27) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:1130 — NewJobNodeDialog.fillFormData 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.
D1 · Cyclomatic Complexity · ShowDataxSyncDialog.parseRwParameter (cyclomatic 27) · ×1
  • ShowDataxSyncDialog.parseRwParameter (cyclomatic 27) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:381 — ShowDataxSyncDialog.parseRwParameter 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.
D1 · Cyclomatic Complexity · ResultStorageService.persistResultToDatabase (cyclomatic 26) · ×1
  • ResultStorageService.persistResultToDatabase (cyclomatic 26) cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/service/ResultStorageService.java:458 — ResultStorageService.persistResultToDatabase 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.
D1 · Cyclomatic Complexity · ProcessNode.setupContextMenu (cyclomatic 26) · ×1
  • ProcessNode.setupContextMenu (cyclomatic 26) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ProcessNode.java:689 — ProcessNode.setupContextMenu has cyclomatic complexity 26 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · NewJobDialog.collectFormData (cyclomatic 26) · ×1
  • NewJobDialog.collectFormData (cyclomatic 26) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:968 — NewJobDialog.collectFormData 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.
D1 · Cyclomatic Complexity · NodeCanvas.setupNodeCallbacks (cyclomatic 26) · ×1
  • NodeCanvas.setupNodeCallbacks (cyclomatic 26) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:387 — NodeCanvas.setupNodeCallbacks has cyclomatic complexity 26 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · CronExpression.buildExpression (cyclomatic 25) · ×1
  • CronExpression.buildExpression (cyclomatic 25) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/cron/CronExpression.java:431 — CronExpression.buildExpression 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.
D1 · Cyclomatic Complexity · JobComposeServiceImpl.saveJobNodeAndJobEdges (cyclomatic 25) · ×1
  • JobComposeServiceImpl.saveJobNodeAndJobEdges (cyclomatic 25) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:1424 — JobComposeServiceImpl.saveJobNodeAndJobEdges 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.
D1 · Cyclomatic Complexity · CanvasConnectionManager.configureConnectionInteractions (cyclomatic 25) · ×1
  • CanvasConnectionManager.configureConnectionInteractions (cyclomatic 25) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasConnectionManager.java:185 — CanvasConnectionManager.configureConnectionInteractions 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.
D1 · Cyclomatic Complexity · NodeCanvas.checkAndExpandCanvas (cyclomatic 25) · ×1
  • NodeCanvas.checkAndExpandCanvas (cyclomatic 25) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:3941 — NodeCanvas.checkAndExpandCanvas 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.
D1 · Cyclomatic Complexity · LifecycleWebhookSender.send (cyclomatic 24) · ×1
  • LifecycleWebhookSender.send (cyclomatic 24) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/lifecycle/LifecycleWebhookSender.java:37 — LifecycleWebhookSender.send 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.
D1 · Cyclomatic Complexity · CSharpGlueFactory.extractUserCode (cyclomatic 24) · ×1
  • CSharpGlueFactory.extractUserCode (cyclomatic 24) cc-job/cc-job-core/src/main/java/com/xxl/job/core/glue/CSharpGlueFactory.java:181 — CSharpGlueFactory.extractUserCode has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · LogContentManager.render (cyclomatic 24) · ×1
  • LogContentManager.render (cyclomatic 24) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/LogContentManager.java:253 — LogContentManager.render has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · TaskExecutionManager.handleSSEMessage (cyclomatic 24) · ×1
  • TaskExecutionManager.handleSSEMessage (cyclomatic 24) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/TaskExecutionManager.java:224 — TaskExecutionManager.handleSSEMessage has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · NewJobNodeDialog.validateForm (cyclomatic 24) · ×1
  • NewJobNodeDialog.validateForm (cyclomatic 24) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:1317 — NewJobNodeDialog.validateForm 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.
D1 · Cyclomatic Complexity · JobPartService.parseNodeData (cyclomatic 23) · ×1
  • JobPartService.parseNodeData (cyclomatic 23) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobPartService.java:264 — JobPartService.parseNodeData 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.
D1 · Cyclomatic Complexity · NewJobDialog.validateForm (cyclomatic 23) · ×1
  • NewJobDialog.validateForm (cyclomatic 23) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:1063 — NewJobDialog.validateForm 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.
D1 · Cyclomatic Complexity · NodeCanvas.createConditionNodeFromData (cyclomatic 23) · ×1
  • NodeCanvas.createConditionNodeFromData (cyclomatic 23) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:2317 — NodeCanvas.createConditionNodeFromData 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.
D1 · Cyclomatic Complexity · WebhookJobAlarm.doAlarm (cyclomatic 22) · ×1
  • WebhookJobAlarm.doAlarm (cyclomatic 22) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/alarm/impl/WebhookJobAlarm.java:55 — WebhookJobAlarm.doAlarm has cyclomatic complexity 22 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · JobInfoServiceImpl.triggerJob (cyclomatic 22) · ×1
  • JobInfoServiceImpl.triggerJob (cyclomatic 22) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobInfoServiceImpl.java:366 — JobInfoServiceImpl.triggerJob has cyclomatic complexity 22 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · XxlJobTrigger.processTrigger (cyclomatic 22) · ×1
  • XxlJobTrigger.processTrigger (cyclomatic 22) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/trigger/XxlJobTrigger.java:113 — XxlJobTrigger.processTrigger 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.
D1 · Cyclomatic Complexity · JobThread.run (cyclomatic 22) · ×1
  • JobThread.run (cyclomatic 22) cc-job/cc-job-core/src/main/java/com/xxl/job/core/thread/JobThread.java:98 — JobThread.run 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.
D1 · Cyclomatic Complexity · NodeSearchManager.search (cyclomatic 22) · ×1
  • NodeSearchManager.search (cyclomatic 22) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/NodeSearchManager.java:112 — NodeSearchManager.search 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.
D1 · Cyclomatic Complexity · ParameterResolver.getNodeResultAttribute (cyclomatic 21) · ×1
  • ParameterResolver.getNodeResultAttribute (cyclomatic 21) cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/resolver/ParameterResolver.java:418 — ParameterResolver.getNodeResultAttribute 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.
D1 · Cyclomatic Complexity · ConditionNode.<init> (cyclomatic 21) · ×1
  • ConditionNode.<init> (cyclomatic 21) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:109 — ConditionNode.<init> has cyclomatic complexity 21 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · NewJobNodeDialog.collectFormData (cyclomatic 21) · ×1
  • NewJobNodeDialog.collectFormData (cyclomatic 21) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:1225 — NewJobNodeDialog.collectFormData 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.
D1 · Cyclomatic Complexity · ShowDatasourceListDialog.showDatasourceFormDialog (cyclomatic 21) · ×1
  • ShowDatasourceListDialog.showDatasourceFormDialog (cyclomatic 21) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:466 — ShowDatasourceListDialog.showDatasourceFormDialog 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.
D1 · Cyclomatic Complexity · JobPartServiceImpl.getTree (cyclomatic 20) · ×1
  • JobPartServiceImpl.getTree (cyclomatic 20) REDACTED:74 — JobPartServiceImpl.getTree has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · TaskGroupOrchestrator.collectAndSaveNodeStatus (cyclomatic 20) · ×1
  • TaskGroupOrchestrator.collectAndSaveNodeStatus (cyclomatic 20) cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/orchestrator/TaskGroupOrchestrator.java:737 — TaskGroupOrchestrator.collectAndSaveNodeStatus has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · 1.run (cyclomatic 19) · ×1
  • 1.run (cyclomatic 19) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/thread/JobLogReportHelper.java:36 — 1.run has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · 3.run (cyclomatic 19) · ×1
  • 3.run (cyclomatic 19) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/thread/JobRegistryHelper.java:63 — 3.run has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · Async.doWorkWrappers (cyclomatic 19) · ×1
  • Async.doWorkWrappers (cyclomatic 19) cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/engine/Async.java:225 — Async.doWorkWrappers has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · JobTriggerService.createTriggerParam (cyclomatic 19) · ×1
  • JobTriggerService.createTriggerParam (cyclomatic 19) REDACTED:210 — JobTriggerService.createTriggerParam has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · 14741.updateItem (cyclomatic 19) · ×1
  • 14741.updateItem (cyclomatic 19) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/PermissionManageDialog.java:317 — 14741.updateItem 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.
D1 · Cyclomatic Complexity · ShowDataxGroupSyncDialog.handleNext (cyclomatic 19) · ×1
  • ShowDataxGroupSyncDialog.handleNext (cyclomatic 19) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:811 — ShowDataxGroupSyncDialog.handleNext has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · JobComposeServiceImpl.getMaxWidthHeight (cyclomatic 18) · ×1
  • JobComposeServiceImpl.getMaxWidthHeight (cyclomatic 18) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:1648 — JobComposeServiceImpl.getMaxWidthHeight has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · JobLogServiceImpl.updateJobNodeStatuses (cyclomatic 18) · ×1
  • JobLogServiceImpl.updateJobNodeStatuses (cyclomatic 18) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobLogServiceImpl.java:460 — JobLogServiceImpl.updateJobNodeStatuses has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · ParameterResolver.executeMethodByName (cyclomatic 18) · ×1
  • ParameterResolver.executeMethodByName (cyclomatic 18) cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/resolver/ParameterResolver.java:860 — ParameterResolver.executeMethodByName has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · HistoricalDataLoader.loadSingleNodeResult (cyclomatic 18) · ×1
  • HistoricalDataLoader.loadSingleNodeResult (cyclomatic 18) cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/service/HistoricalDataLoader.java:167 — HistoricalDataLoader.loadSingleNodeResult 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.
D1 · Cyclomatic Complexity · NodeCanvas.finishConnectionForConditionNode (cyclomatic 18) · ×1
  • NodeCanvas.finishConnectionForConditionNode (cyclomatic 18) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:2824 — NodeCanvas.finishConnectionForConditionNode has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · JobApprovalController.approve (cyclomatic 17) · ×1
  • JobApprovalController.approve (cyclomatic 17) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/controller/JobApprovalController.java:111 — JobApprovalController.approve has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · JobLogServiceImpl.getHealthStats (cyclomatic 17) · ×1
  • JobLogServiceImpl.getHealthStats (cyclomatic 17) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobLogServiceImpl.java:410 — JobLogServiceImpl.getHealthStats has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · JobPartService.parseComposeFromGuiSnapshot (cyclomatic 17) · ×1
  • JobPartService.parseComposeFromGuiSnapshot (cyclomatic 17) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobPartService.java:547 — JobPartService.parseComposeFromGuiSnapshot has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · LoginService.login (cyclomatic 17) · ×1
  • LoginService.login (cyclomatic 17) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/LoginService.java:52 — LoginService.login 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. This shape REPEATS in the file: one other method here (LoginService.register) 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.
D1 · Cyclomatic Complexity · LoginService.register (cyclomatic 17) · ×1
  • LoginService.register (cyclomatic 17) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/LoginService.java:159 — LoginService.register 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. This shape REPEATS in the file: one other method here (LoginService.login) 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.
D1 · Cyclomatic Complexity · ParameterAutocompleteService.getNestedAttributeSuggestions (cyclomatic 17) · ×1
  • ParameterAutocompleteService.getNestedAttributeSuggestions (cyclomatic 17) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/ParameterAutocompleteService.java:317 — ParameterAutocompleteService.getNestedAttributeSuggestions 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. This is NOT this file's highest cyclomatic complexity: ParameterAutocompleteService.normalizeNodeType (cyclomatic 37) 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 method is counted neither in this dimension's figures nor in its score.
D1 · Cyclomatic Complexity · SmartParameterInput.checkAutocompleteTrigger (cyclomatic 17) · ×1
  • SmartParameterInput.checkAutocompleteTrigger (cyclomatic 17) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/component/SmartParameterInput.java:298 — SmartParameterInput.checkAutocompleteTrigger 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.
D1 · Cyclomatic Complexity · MainView.showGoToPartitionDialog (cyclomatic 17) · ×1
  • MainView.showGoToPartitionDialog (cyclomatic 17) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:3002 — MainView.showGoToPartitionDialog has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · NewJobGroupDialog.fillFormData (cyclomatic 17) · ×1
  • NewJobGroupDialog.fillFormData (cyclomatic 17) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java:467 — NewJobGroupDialog.fillFormData 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.
D1 · Cyclomatic Complexity · NodeCanvas.appendTemplateToCanvas (cyclomatic 17) · ×1
  • NodeCanvas.appendTemplateToCanvas (cyclomatic 17) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:2269 — NodeCanvas.appendTemplateToCanvas has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · NodeCanvas.bindConditionNodeChildren (cyclomatic 17) · ×1
  • NodeCanvas.bindConditionNodeChildren (cyclomatic 17) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:2402 — NodeCanvas.bindConditionNodeChildren has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · NodeStyleDialog.createContent (cyclomatic 17) · ×1
  • NodeStyleDialog.createContent (cyclomatic 17) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeStyleDialog.java:66 — NodeStyleDialog.createContent 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.
D1 · Cyclomatic Complexity · ShowDataxGroupSyncDialog.buildDataxJobInfoForm (cyclomatic 17) · ×1
  • ShowDataxGroupSyncDialog.buildDataxJobInfoForm (cyclomatic 17) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:924 — ShowDataxGroupSyncDialog.buildDataxJobInfoForm 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.
D1 · Cyclomatic Complexity · ShowJobLogListDialog.loadPage (cyclomatic 17) · ×1
  • ShowJobLogListDialog.loadPage (cyclomatic 17) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobLogListDialog.java:462 — ShowJobLogListDialog.loadPage 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.
D1 · Cyclomatic Complexity · JobRoleManageController.updateRole (cyclomatic 16) · ×1
  • JobRoleManageController.updateRole (cyclomatic 16) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/controller/JobRoleManageController.java:77 — JobRoleManageController.updateRole has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · JobInfoServiceImpl.checkJobGroupRunningInExecutor (cyclomatic 16) · ×1
  • JobInfoServiceImpl.checkJobGroupRunningInExecutor (cyclomatic 16) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobInfoServiceImpl.java:1312 — JobInfoServiceImpl.checkJobGroupRunningInExecutor has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · JobCompleteHelper.callback (cyclomatic 16) · ×1
  • JobCompleteHelper.callback (cyclomatic 16) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/thread/JobCompleteHelper.java:161 — JobCompleteHelper.callback has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · SpringGlueFactory.injectService (cyclomatic 16) · ×1
  • SpringGlueFactory.injectService (cyclomatic 16) cc-job/cc-job-core/src/main/java/com/xxl/job/core/glue/impl/SpringGlueFactory.java:26 — SpringGlueFactory.injectService has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · ParameterResolver.resolve (cyclomatic 16) · ×1
  • ParameterResolver.resolve (cyclomatic 16) cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/resolver/ParameterResolver.java:46 — ParameterResolver.resolve has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · ConditionNode.bindConditionNodes (cyclomatic 16) · ×1
  • ConditionNode.bindConditionNodes (cyclomatic 16) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:894 — ConditionNode.bindConditionNodes has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · ConditionNode.checkAndExpandContainer (cyclomatic 16) · ×1
  • ConditionNode.checkAndExpandContainer (cyclomatic 16) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:1062 — ConditionNode.checkAndExpandContainer has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · MainView.showGoToTaskGroupDialog (cyclomatic 16) · ×1
  • MainView.showGoToTaskGroupDialog (cyclomatic 16) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:2948 — MainView.showGoToTaskGroupDialog has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · MainView.updateDetachedSidebarState (cyclomatic 16) · ×1
  • MainView.updateDetachedSidebarState (cyclomatic 16) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:2254 — MainView.updateDetachedSidebarState 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 shape REPEATS in the file: one other method here (MainView.updateLeftSidebar) 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.
D1 · Cyclomatic Complexity · MainView.updateLeftSidebar (cyclomatic 16) · ×1
  • MainView.updateLeftSidebar (cyclomatic 16) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:2013 — MainView.updateLeftSidebar 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 shape REPEATS in the file: one other method here (MainView.updateDetachedSidebarState) 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.
D1 · Cyclomatic Complexity · NodeCanvas.handleNodeStateChange (cyclomatic 16) · ×1
  • NodeCanvas.handleNodeStateChange (cyclomatic 16) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:3638 — NodeCanvas.handleNodeStateChange has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · NodeCanvas.showAlignmentGuides (cyclomatic 16) · ×1
  • NodeCanvas.showAlignmentGuides (cyclomatic 16) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:4556 — NodeCanvas.showAlignmentGuides 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.
D2 · Cognitive Complexity · ShowDataxSyncDialog.applyEditData (cognitive 189) · ×1
  • ShowDataxSyncDialog.applyEditData (cognitive 189) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:434 — ShowDataxSyncDialog.applyEditData has cognitive complexity 189 (threshold 15). Drivers by points: if/else 41 (107 pts), ternaries 12 (44 pts), error handling 6 (16 pts), boolean chains 15, loops 2 (7 pts) (nesting depth added 113). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · NodeCanvas.loadFromComposeData (cognitive 164) · ×1
  • NodeCanvas.loadFromComposeData (cognitive 164) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:2060 — NodeCanvas.loadFromComposeData has cognitive complexity 164 (threshold 15). Drivers by points: if/else 36 (122 pts), loops 9 (19 pts), boolean chains 15, error handling 1 (8 pts) (nesting depth added 103). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · CronExpression.getTimeAfter (cognitive 161) · ×1
  • CronExpression.getTimeAfter (cognitive 161) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/cron/CronExpression.java:1162 — CronExpression.getTimeAfter has cognitive complexity 161 (threshold 15). Drivers by points: if/else 57 (140 pts), boolean chains 16, loops 2 (5 pts) (nesting depth added 86). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · NodeDetailsDialog.loadDetails (cognitive 137) · ×1
  • NodeDetailsDialog.loadDetails (cognitive 137) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeDetailsDialog.java:233 — NodeDetailsDialog.loadDetails has cognitive complexity 137 (threshold 15). Drivers by points: if/else 28 (68 pts), ternaries 23 (24 pts), loops 4 (18 pts), error handling 5 (13 pts), boolean chains 12, match/switch 1 (2 pts) (nesting depth added 64). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CanvasDataLoader.createNodeFromData (cognitive 134) · ×1
  • CanvasDataLoader.createNodeFromData (cognitive 134) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasDataLoader.java:47 — CanvasDataLoader.createNodeFromData has cognitive complexity 134 (threshold 15). Drivers by points: if/else 35 (81 pts), error handling 8 (33 pts), loops 4 (17 pts), boolean chains 2, ternaries 1 (nesting depth added 84). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · JobComposeServiceImpl.operateToSaveJobCompose (cognitive 132) · ×1
  • JobComposeServiceImpl.operateToSaveJobCompose (cognitive 132) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:321 — JobComposeServiceImpl.operateToSaveJobCompose has cognitive complexity 132 (threshold 15). Drivers by points: if/else 37 (95 pts), loops 10 (18 pts), boolean chains 15, ternaries 1 (3 pts), error handling 1 (nesting depth added 68). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · JobComposeServiceImpl.buildNodeVosRecursive (cognitive 117) · ×1
  • JobComposeServiceImpl.buildNodeVosRecursive (cognitive 117) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:1873 — JobComposeServiceImpl.buildNodeVosRecursive has cognitive complexity 117 (threshold 15). Drivers by points: if/else 25 (82 pts), loops 6 (16 pts), error handling 2 (9 pts), boolean chains 8, ternaries 1 (2 pts) (nesting depth added 75). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · CronExpression.storeExpressionVals (cognitive 115) · ×1
  • CronExpression.storeExpressionVals (cognitive 115) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/cron/CronExpression.java:517 — CronExpression.storeExpressionVals has cognitive complexity 115 (threshold 15). Drivers by points: if/else 43 (98 pts), boolean chains 12, error handling 1 (5 pts) (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.
D2 · Cognitive Complexity · ParameterResolver.resolveNestedAttribute (cognitive 103) · ×1
  • ParameterResolver.resolveNestedAttribute (cognitive 103) cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/resolver/ParameterResolver.java:489 — ParameterResolver.resolveNestedAttribute has cognitive complexity 103 (threshold 15). Drivers by points: if/else 20 (52 pts), ternaries 4 (24 pts), match/switch 3 (15 pts), error handling 2 (7 pts), boolean chains 4, loops 1 (nesting depth added 69). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · ParameterResolver.getValueFromContext (cognitive 98) · ×1
  • ParameterResolver.getValueFromContext (cognitive 98) cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/resolver/ParameterResolver.java:163 — ParameterResolver.getValueFromContext has cognitive complexity 98 (threshold 15). Drivers by points: if/else 35 (87 pts), boolean chains 11 (nesting depth added 52). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · ShowDataxSyncDialog.handleNext (cognitive 91) · ×1
  • ShowDataxSyncDialog.handleNext (cognitive 91) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1515 — ShowDataxSyncDialog.handleNext has cognitive complexity 91 (threshold 15). Drivers by points: if/else 29 (62 pts), ternaries 5 (12 pts), boolean chains 9, loops 2 (7 pts), error handling 1 (nesting depth added 45). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · JobComposeServiceImpl.buildAllNodesAndEdgesRecursive (cognitive 90) · ×1
  • JobComposeServiceImpl.buildAllNodesAndEdgesRecursive (cognitive 90) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:1006 — JobComposeServiceImpl.buildAllNodesAndEdgesRecursive has cognitive complexity 90 (threshold 15). Drivers by points: if/else 27 (53 pts), loops 6 (10 pts), ternaries 4 (10 pts), error handling 3 (9 pts), boolean chains 8 (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.
D2 · Cognitive Complexity · JobPartService.parseJobComposeData (cognitive 89) · ×1
  • JobPartService.parseJobComposeData (cognitive 89) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobPartService.java:76 — JobPartService.parseJobComposeData has cognitive complexity 89 (threshold 15). Drivers by points: if/else 23 (59 pts), error handling 5 (20 pts), loops 3 (8 pts), boolean chains 2 (nesting depth added 56). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · CronExpression.addToSet (cognitive 83) · ×1
  • CronExpression.addToSet (cognitive 83) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/cron/CronExpression.java:958 — CronExpression.addToSet has cognitive complexity 83 (threshold 15). Drivers by points: if/else 36 (57 pts), boolean chains 23, match/switch 1 (2 pts), loops 1 (nesting depth added 22). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · JobComposeServiceImpl.operateToUpdateJobCompose (cognitive 82) · ×1
  • JobComposeServiceImpl.operateToUpdateJobCompose (cognitive 82) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:702 — JobComposeServiceImpl.operateToUpdateJobCompose has cognitive complexity 82 (threshold 15). Drivers by points: if/else 26 (64 pts), loops 7 (8 pts), boolean chains 6, ternaries 1 (3 pts), error handling 1 (nesting depth added 41). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · 1.run (cognitive 80) · ×1
  • 1.run (cognitive 80) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/thread/JobScheduleHelper.java:44 — 1.run has cognitive complexity 80 (threshold 15). Drivers by points: if/else 17 (50 pts), error handling 7 (18 pts), loops 3 (7 pts), ternaries 1 (3 pts), boolean chains 2 (nesting depth added 50). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SmartParameterInput.handleSmartDelete (cognitive 78) · ×1
  • SmartParameterInput.handleSmartDelete (cognitive 78) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/component/SmartParameterInput.java:769 — SmartParameterInput.handleSmartDelete has cognitive complexity 78 (threshold 15). Drivers by points: if/else 21 (50 pts), boolean chains 12, loops 4 (10 pts), ternaries 3 (6 pts) (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.
D2 · Cognitive Complexity · ConditionNode.bindCanvasNodes (cognitive 67) · ×1
  • ConditionNode.bindCanvasNodes (cognitive 67) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:663 — ConditionNode.bindCanvasNodes has cognitive complexity 67 (threshold 15). Drivers by points: if/else 24 (46 pts), loops 7 (11 pts), boolean chains 5, ternaries 3 (5 pts) (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.
D2 · Cognitive Complexity · TaskGroupOrchestrator.prepareExecution (cognitive 65) · ×1
  • TaskGroupOrchestrator.prepareExecution (cognitive 65) cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/orchestrator/TaskGroupOrchestrator.java:199 — TaskGroupOrchestrator.prepareExecution has cognitive complexity 65 (threshold 15). Drivers by points: if/else 25 (45 pts), boolean chains 13, loops 2 (5 pts), error handling 1 (2 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.
D2 · Cognitive Complexity · DataManager.buildNodesData (cognitive 63) · ×1
  • DataManager.buildNodesData (cognitive 63) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DataManager.java:151 — DataManager.buildNodesData has cognitive complexity 63 (threshold 15). Drivers by points: if/else 19 (44 pts), loops 6 (12 pts), boolean chains 5, ternaries 1 (2 pts) (nesting depth added 32). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CSharpGlueFactory.extractUserCode (cognitive 62) · ×1
  • CSharpGlueFactory.extractUserCode (cognitive 62) cc-job/cc-job-core/src/main/java/com/xxl/job/core/glue/CSharpGlueFactory.java:181 — CSharpGlueFactory.extractUserCode has cognitive complexity 62 (threshold 15). Drivers by points: if/else 15 (49 pts), loops 2 (7 pts), boolean chains 6 (nesting depth added 39). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · 3.run (cognitive 55) · ×1
  • 3.run (cognitive 55) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/thread/JobRegistryHelper.java:63 — 3.run has cognitive complexity 55 (threshold 15). Drivers by points: if/else 9 (35 pts), loops 4 (13 pts), error handling 2 (4 pts), boolean chains 3 (nesting depth added 37). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · JobPartServiceImpl.getTree (cognitive 53) · ×1
  • JobPartServiceImpl.getTree (cognitive 53) REDACTED:74 — JobPartServiceImpl.getTree has cognitive complexity 53 (threshold 15). Drivers by points: if/else 9 (22 pts), loops 5 (16 pts), ternaries 2 (12 pts), boolean chains 3 (nesting depth added 34). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · JobThread.run (cognitive 53) · ×1
  • JobThread.run (cognitive 53) cc-job/cc-job-core/src/main/java/com/xxl/job/core/thread/JobThread.java:98 — JobThread.run has cognitive complexity 53 (threshold 15). Drivers by points: if/else 16 (37 pts), error handling 4 (8 pts), ternaries 1 (4 pts), boolean chains 2, loops 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.
D2 · Cognitive Complexity · CronExpression.checkNext (cognitive 51) · ×1
  • CronExpression.checkNext (cognitive 51) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/cron/CronExpression.java:711 — CronExpression.checkNext has cognitive complexity 51 (threshold 15). Drivers by points: if/else 25 (42 pts), boolean chains 7, error handling 1 (2 pts) (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · 1.run (cognitive 51) · ×1
  • 1.run (cognitive 51) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/thread/JobFailMonitorHelper.java:38 — 1.run has cognitive complexity 51 (threshold 15). Drivers by points: if/else 11 (34 pts), ternaries 1 (6 pts), error handling 2 (4 pts), loops 2 (4 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.
D2 · Cognitive Complexity · ExecutorBizImpl.run (cognitive 51) · ×1
  • ExecutorBizImpl.run (cognitive 51) cc-job/cc-job-core/src/main/java/com/xxl/job/core/biz/impl/ExecutorBizImpl.java:51 — ExecutorBizImpl.run has cognitive complexity 51 (threshold 15). Drivers by points: if/else 20 (35 pts), boolean chains 9, error handling 2 (6 pts), ternaries 1 (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · LoginService.login (cognitive 50) · ×1
  • LoginService.login (cognitive 50) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/LoginService.java:52 — LoginService.login has cognitive complexity 50 (threshold 15). Drivers by points: if/else 14 (33 pts), ternaries 3 (13 pts), boolean chains 3, error handling 1 (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. This shape REPEATS in the file: one other method here (LoginService.register) 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.
D2 · Cognitive Complexity · LoginService.register (cognitive 50) · ×1
  • LoginService.register (cognitive 50) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/LoginService.java:159 — LoginService.register has cognitive complexity 50 (threshold 15). Drivers by points: if/else 14 (33 pts), ternaries 3 (13 pts), boolean chains 3, error handling 1 (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. This shape REPEATS in the file: one other method here (LoginService.login) 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.
D2 · Cognitive Complexity · JobInfoServiceImpl.baseUpdateJobInfo (cognitive 49) · ×1
  • JobInfoServiceImpl.baseUpdateJobInfo (cognitive 49) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobInfoServiceImpl.java:1165 — JobInfoServiceImpl.baseUpdateJobInfo has cognitive complexity 49 (threshold 15). Drivers by points: if/else 21 (30 pts), boolean chains 11, error handling 2 (4 pts), loops 2 (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.
D2 · Cognitive Complexity · JobInfoServiceImpl.baseSaveJobInfo (cognitive 48) · ×1
  • JobInfoServiceImpl.baseSaveJobInfo (cognitive 48) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobInfoServiceImpl.java:789 — JobInfoServiceImpl.baseSaveJobInfo has cognitive complexity 48 (threshold 15). Drivers by points: if/else 20 (31 pts), boolean chains 8, loops 3 (7 pts), error handling 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.
D2 · Cognitive Complexity · HistoricalDataLoader.loadFromDatabase (cognitive 48) · ×1
  • HistoricalDataLoader.loadFromDatabase (cognitive 48) cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/service/HistoricalDataLoader.java:44 — HistoricalDataLoader.loadFromDatabase has cognitive complexity 48 (threshold 15). Drivers by points: if/else 12 (19 pts), ternaries 5 (13 pts), boolean chains 9, error handling 3 (6 pts), loops 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.
D2 · Cognitive Complexity · ResultStorageService.persistResultToDatabase (cognitive 46) · ×1
  • ResultStorageService.persistResultToDatabase (cognitive 46) cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/service/ResultStorageService.java:458 — ResultStorageService.persistResultToDatabase has cognitive complexity 46 (threshold 15). Drivers by points: if/else 18 (32 pts), loops 3 (5 pts), boolean chains 4, ternaries 2 (4 pts), error handling 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.
D2 · Cognitive Complexity · ProcessNode.setupDragHandlers (cognitive 46) · ×1
  • ProcessNode.setupDragHandlers (cognitive 46) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ProcessNode.java:532 — ProcessNode.setupDragHandlers has cognitive complexity 46 (threshold 15). Drivers by points: if/else 20 (39 pts), boolean chains 7 (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.
D2 · Cognitive Complexity · 1.run (cognitive 44) · ×1
  • 1.run (cognitive 44) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/thread/JobLogReportHelper.java:36 — 1.run has cognitive complexity 44 (threshold 15). Drivers by points: if/else 6 (18 pts), ternaries 3 (12 pts), loops 3 (6 pts), boolean chains 4, error handling 2 (4 pts) (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.
D2 · Cognitive Complexity · LogContentManager.render (cognitive 44) · ×1
  • LogContentManager.render (cognitive 44) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/LogContentManager.java:253 — LogContentManager.render has cognitive complexity 44 (threshold 15). Drivers by points: if/else 13 (22 pts), ternaries 6 (15 pts), boolean chains 4, error handling 1 (2 pts), loops 1 (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · NodeCallbackConfigurator.configureNodeCallbacks (cognitive 42) · ×1
  • NodeCallbackConfigurator.configureNodeCallbacks (cognitive 42) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/NodeCallbackConfigurator.java:59 — NodeCallbackConfigurator.configureNodeCallbacks has cognitive complexity 42 (threshold 15). Drivers by points: if/else 31 (33 pts), boolean chains 7, loops 1 (2 pts) (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · SSEConnection.connectAndListen (cognitive 42) · ×1
  • SSEConnection.connectAndListen (cognitive 42) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/SSEService.java:140 — SSEConnection.connectAndListen has cognitive complexity 42 (threshold 15). Drivers by points: if/else 17 (30 pts), error handling 4 (7 pts), boolean chains 4, 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.
D2 · Cognitive Complexity · NodeSearchManager.search (cognitive 40) · ×1
  • NodeSearchManager.search (cognitive 40) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/NodeSearchManager.java:112 — NodeSearchManager.search has cognitive complexity 40 (threshold 15). Drivers by points: if/else 12 (29 pts), boolean chains 7, loops 2 (4 pts) (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · JobPartService.parseComposeFromGuiSnapshot (cognitive 40) · ×1
  • JobPartService.parseComposeFromGuiSnapshot (cognitive 40) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobPartService.java:547 — JobPartService.parseComposeFromGuiSnapshot has cognitive complexity 40 (threshold 15). Drivers by points: if/else 7 (15 pts), error handling 3 (9 pts), ternaries 2 (8 pts), loops 2 (6 pts), boolean chains 2 (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.
D2 · Cognitive Complexity · NewJobDialog.fillFormData (cognitive 40) · ×1
  • NewJobDialog.fillFormData (cognitive 40) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:862 — NewJobDialog.fillFormData has cognitive complexity 40 (threshold 15). Drivers by points: if/else 24 (29 pts), error handling 4 (8 pts), boolean chains 3 (nesting depth added 9). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · JobInfoServiceImpl.checkJobGroupRunningInExecutor (cognitive 39) · ×1
  • JobInfoServiceImpl.checkJobGroupRunningInExecutor (cognitive 39) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobInfoServiceImpl.java:1312 — JobInfoServiceImpl.checkJobGroupRunningInExecutor has cognitive complexity 39 (threshold 15). Drivers by points: if/else 8 (26 pts), loops 2 (7 pts), boolean chains 3, error handling 2 (3 pts) (nesting depth added 24). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · JobComposeServiceImpl.saveJobNodeAndJobEdges (cognitive 38) · ×1
  • JobComposeServiceImpl.saveJobNodeAndJobEdges (cognitive 38) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:1424 — JobComposeServiceImpl.saveJobNodeAndJobEdges has cognitive complexity 38 (threshold 15). Drivers by points: if/else 12 (22 pts), loops 7 (9 pts), ternaries 2 (4 pts), boolean chains 3 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · NewJobDialog.collectFormData (cognitive 38) · ×1
  • NewJobDialog.collectFormData (cognitive 38) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:968 — NewJobDialog.collectFormData has cognitive complexity 38 (threshold 15). Drivers by points: ternaries 11 (20 pts), if/else 9 (11 pts), boolean chains 4, error handling 2, match/switch 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ShowDataxSyncDialog.buildDataxJobInfoForm (cognitive 38) · ×1
  • ShowDataxSyncDialog.buildDataxJobInfoForm (cognitive 38) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1665 — ShowDataxSyncDialog.buildDataxJobInfoForm has cognitive complexity 38 (threshold 15). Drivers by points: ternaries 15 (22 pts), if/else 8 (9 pts), error handling 2 (4 pts), 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.
D2 · Cognitive Complexity · 1.run (cognitive 37) · ×1
  • 1.run (cognitive 37) cc-job/cc-job-core/src/main/java/com/xxl/job/core/thread/JobLogFileCleanThread.java:39 — 1.run has cognitive complexity 37 (threshold 15). Drivers by points: if/else 7 (24 pts), error handling 3 (8 pts), loops 2 (4 pts), boolean chains 1 (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.
D2 · Cognitive Complexity · CanvasConnectionManager.configureConnectionInteractions (cognitive 37) · ×1
  • CanvasConnectionManager.configureConnectionInteractions (cognitive 37) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasConnectionManager.java:185 — CanvasConnectionManager.configureConnectionInteractions has cognitive complexity 37 (threshold 15). Drivers by points: if/else 23 (31 pts), boolean chains 4, error handling 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.
D2 · Cognitive Complexity · NewJobNodeDialog.fillFormData (cognitive 37) · ×1
  • NewJobNodeDialog.fillFormData (cognitive 37) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:1130 — NewJobNodeDialog.fillFormData has cognitive complexity 37 (threshold 15). Drivers by points: if/else 22 (28 pts), error handling 3 (6 pts), boolean chains 3 (nesting depth added 9). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · NodeCanvas.createConditionNodeFromData (cognitive 37) · ×1
  • NodeCanvas.createConditionNodeFromData (cognitive 37) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:2317 — NodeCanvas.createConditionNodeFromData has cognitive complexity 37 (threshold 15). Drivers by points: if/else 11 (16 pts), error handling 4 (10 pts), ternaries 2 (6 pts), boolean chains 5 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · 1.run (cognitive 36) · ×1
  • 1.run (cognitive 36) cc-job/cc-job-core/src/main/java/com/xxl/job/core/thread/ExecutorRegistryThread.java:40 — 1.run has cognitive complexity 36 (threshold 15). Drivers by points: if/else 9 (20 pts), error handling 5 (10 pts), loops 3 (4 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.
D2 · Cognitive Complexity · TaskExecutionManager.handleSSEMessage (cognitive 36) · ×1
  • TaskExecutionManager.handleSSEMessage (cognitive 36) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/TaskExecutionManager.java:224 — TaskExecutionManager.handleSSEMessage has cognitive complexity 36 (threshold 15). Drivers by points: if/else 10 (18 pts), boolean chains 9, ternaries 2 (4 pts), loops 1 (3 pts), error handling 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.
D2 · Cognitive Complexity · ProcessNode.setupContextMenu (cognitive 36) · ×1
  • ProcessNode.setupContextMenu (cognitive 36) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ProcessNode.java:689 — ProcessNode.setupContextMenu has cognitive complexity 36 (threshold 15). Drivers by points: if/else 29 (33 pts), boolean chains 2, 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.
D2 · Cognitive Complexity · JobPartService.parseNodeData (cognitive 36) · ×1
  • JobPartService.parseNodeData (cognitive 36) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobPartService.java:264 — JobPartService.parseNodeData has cognitive complexity 36 (threshold 15). Drivers by points: if/else 17 (23 pts), error handling 5 (9 pts), boolean chains 2, loops 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.
D2 · Cognitive Complexity · XxlJobTrigger.processTrigger (cognitive 34) · ×1
  • XxlJobTrigger.processTrigger (cognitive 34) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/trigger/XxlJobTrigger.java:113 — XxlJobTrigger.processTrigger has cognitive complexity 34 (threshold 15). Drivers by points: if/else 17 (25 pts), boolean chains 5, ternaries 4 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ShowDataxSyncDialog.parseRwParameter (cognitive 34) · ×1
  • ShowDataxSyncDialog.parseRwParameter (cognitive 34) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:381 — ShowDataxSyncDialog.parseRwParameter has cognitive complexity 34 (threshold 15). Drivers by points: if/else 18 (23 pts), ternaries 4 (5 pts), boolean chains 3, loops 1 (3 pts) (nesting depth added 8). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · TaskGroupOrchestrator.collectAndSaveNodeStatus (cognitive 33) · ×1
  • TaskGroupOrchestrator.collectAndSaveNodeStatus (cognitive 33) cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/orchestrator/TaskGroupOrchestrator.java:737 — TaskGroupOrchestrator.collectAndSaveNodeStatus has cognitive complexity 33 (threshold 15). Drivers by points: if/else 13 (21 pts), boolean chains 4, error handling 2 (3 pts), loops 2 (3 pts), ternaries 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.
D2 · Cognitive Complexity · CycleDetectionManager.detectCycleDFS (cognitive 33) · ×1
  • CycleDetectionManager.detectCycleDFS (cognitive 33) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CycleDetectionManager.java:104 — CycleDetectionManager.detectCycleDFS has cognitive complexity 33 (threshold 15). Drivers by points: if/else 7 (21 pts), loops 3 (12 pts) (nesting depth added 23). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · MainView.setupCallbacks (cognitive 33) · ×1
  • MainView.setupCallbacks (cognitive 33) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:261 — MainView.setupCallbacks has cognitive complexity 33 (threshold 15). Drivers by points: if/else 18 (21 pts), boolean chains 8, ternaries 3, error handling 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · JobComposeServiceImpl.getMaxWidthHeight (cognitive 32) · ×1
  • JobComposeServiceImpl.getMaxWidthHeight (cognitive 32) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:1648 — JobComposeServiceImpl.getMaxWidthHeight has cognitive complexity 32 (threshold 15). Drivers by points: if/else 10 (18 pts), error handling 3 (9 pts), boolean chains 4, loops 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · JobLogServiceImpl.getHealthStats (cognitive 32) · ×1
  • JobLogServiceImpl.getHealthStats (cognitive 32) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobLogServiceImpl.java:410 — JobLogServiceImpl.getHealthStats has cognitive complexity 32 (threshold 15). Drivers by points: if/else 8 (18 pts), ternaries 5 (8 pts), loops 2 (4 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.
D2 · Cognitive Complexity · SpringGlueFactory.injectService (cognitive 32) · ×1
  • SpringGlueFactory.injectService (cognitive 32) cc-job/cc-job-core/src/main/java/com/xxl/job/core/glue/impl/SpringGlueFactory.java:26 — SpringGlueFactory.injectService has cognitive complexity 32 (threshold 15). Drivers by points: if/else 11 (20 pts), error handling 3 (9 pts), boolean chains 2, 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.
D2 · Cognitive Complexity · Async.doWorkWrappers (cognitive 32) · ×1
  • Async.doWorkWrappers (cognitive 32) cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/engine/Async.java:225 — Async.doWorkWrappers has cognitive complexity 32 (threshold 15). Drivers by points: if/else 13 (20 pts), loops 3 (5 pts), error handling 2 (3 pts), boolean chains 2, ternaries 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.
D2 · Cognitive Complexity · NewJobNodeDialog.collectFormData (cognitive 32) · ×1
  • NewJobNodeDialog.collectFormData (cognitive 32) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:1225 — NewJobNodeDialog.collectFormData has cognitive complexity 32 (threshold 15). Drivers by points: ternaries 8 (17 pts), if/else 8 (10 pts), boolean chains 3, error handling 1, match/switch 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ShowDataxGroupSyncDialog.handleNext (cognitive 32) · ×1
  • ShowDataxGroupSyncDialog.handleNext (cognitive 32) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:811 — ShowDataxGroupSyncDialog.handleNext has cognitive complexity 32 (threshold 15). Drivers by points: if/else 12 (21 pts), ternaries 3 (7 pts), boolean chains 2, error handling 1, loops 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · JobInfoServiceImpl.triggerJob (cognitive 31) · ×1
  • JobInfoServiceImpl.triggerJob (cognitive 31) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobInfoServiceImpl.java:366 — JobInfoServiceImpl.triggerJob has cognitive complexity 31 (threshold 15). Drivers by points: if/else 15 (19 pts), error handling 3 (6 pts), boolean chains 3, ternaries 2 (3 pts) (nesting depth added 8). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · NodeCanvas.performSmoothScroll (cognitive 31) · ×1
  • NodeCanvas.performSmoothScroll (cognitive 31) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:700 — NodeCanvas.performSmoothScroll has cognitive complexity 31 (threshold 15). Drivers by points: if/else 14 (16 pts), boolean chains 9, ternaries 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.
D2 · Cognitive Complexity · NodeCanvas.setupNodeCallbacks (cognitive 31) · ×1
  • NodeCanvas.setupNodeCallbacks (cognitive 31) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:387 — NodeCanvas.setupNodeCallbacks has cognitive complexity 31 (threshold 15). Drivers by points: if/else 21 (25 pts), boolean chains 6 (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.
D2 · Cognitive Complexity · JobRoleManageController.updateRole (cognitive 30) · ×1
  • JobRoleManageController.updateRole (cognitive 30) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/controller/JobRoleManageController.java:77 — JobRoleManageController.updateRole has cognitive complexity 30 (threshold 15). Drivers by points: if/else 8 (16 pts), ternaries 4 (10 pts), boolean chains 4 (nesting depth added 14). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · TreeSearchManager.filterNodeRecursive (cognitive 30) · ×1
  • TreeSearchManager.filterNodeRecursive (cognitive 30) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/TreeSearchManager.java:54 — TreeSearchManager.filterNodeRecursive has cognitive complexity 30 (threshold 15). Drivers by points: if/else 9 (22 pts), loops 2 (5 pts), boolean chains 3 (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.
D2 · Cognitive Complexity · NodeCanvas.checkAndExpandCanvas (cognitive 30) · ×1
  • NodeCanvas.checkAndExpandCanvas (cognitive 30) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:3941 — NodeCanvas.checkAndExpandCanvas has cognitive complexity 30 (threshold 15). Drivers by points: if/else 15 (21 pts), boolean chains 7, ternaries 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.
D2 · Cognitive Complexity · CronExpression.buildExpression (cognitive 29) · ×1
  • CronExpression.buildExpression (cognitive 29) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/cron/CronExpression.java:431 — CronExpression.buildExpression has cognitive complexity 29 (threshold 15). Drivers by points: if/else 14 (18 pts), boolean chains 6, loops 2 (3 pts), error handling 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.
D2 · Cognitive Complexity · JobLogServiceImpl.updateJobNodeStatuses (cognitive 29) · ×1
  • JobLogServiceImpl.updateJobNodeStatuses (cognitive 29) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobLogServiceImpl.java:460 — JobLogServiceImpl.updateJobNodeStatuses has cognitive complexity 29 (threshold 15). Drivers by points: if/else 11 (19 pts), boolean chains 4, error handling 2 (3 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.
D2 · Cognitive Complexity · JobPartServiceImpl.importData (cognitive 29) · ×1
  • JobPartServiceImpl.importData (cognitive 29) REDACTED:592 — JobPartServiceImpl.importData has cognitive complexity 29 (threshold 15). Drivers by points: if/else 6 (16 pts), loops 3 (10 pts), boolean chains 2, error handling 1 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · WebhookJobAlarm.doAlarm (cognitive 28) · ×1
  • WebhookJobAlarm.doAlarm (cognitive 28) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/alarm/impl/WebhookJobAlarm.java:55 — WebhookJobAlarm.doAlarm has cognitive complexity 28 (threshold 15). Drivers by points: ternaries 11 (15 pts), if/else 5 (6 pts), loops 2 (3 pts), boolean chains 2, error handling 1 (2 pts) (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.
D2 · Cognitive Complexity · CanvasLayoutManager.forceDirectedLayout (cognitive 28) · ×1
  • CanvasLayoutManager.forceDirectedLayout (cognitive 28) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasLayoutManager.java:174 — CanvasLayoutManager.forceDirectedLayout has cognitive complexity 28 (threshold 15). Drivers by points: loops 7 (13 pts), if/else 3 (10 pts), ternaries 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.
D2 · Cognitive Complexity · MainView.showGoToTaskGroupDialog (cognitive 28) · ×1
  • MainView.showGoToTaskGroupDialog (cognitive 28) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:2948 — MainView.showGoToTaskGroupDialog has cognitive complexity 28 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 4 (8 pts), ternaries 2 (4 pts), boolean chains 3, error handling 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · NodeCanvas.appendTemplateToCanvas (cognitive 28) · ×1
  • NodeCanvas.appendTemplateToCanvas (cognitive 28) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:2269 — NodeCanvas.appendTemplateToCanvas has cognitive complexity 28 (threshold 15). Drivers by points: if/else 8 (16 pts), ternaries 3 (6 pts), boolean chains 3, 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.
D2 · Cognitive Complexity · LifecycleWebhookSender.send (cognitive 27) · ×1
  • LifecycleWebhookSender.send (cognitive 27) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/lifecycle/LifecycleWebhookSender.java:37 — LifecycleWebhookSender.send has cognitive complexity 27 (threshold 15). Drivers by points: ternaries 12 (15 pts), boolean chains 6, if/else 3, error handling 1 (2 pts), loops 1 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · ParameterResolver.resolve (cognitive 27) · ×1
  • ParameterResolver.resolve (cognitive 27) cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/resolver/ParameterResolver.java:46 — ParameterResolver.resolve has cognitive complexity 27 (threshold 15). Drivers by points: if/else 8 (16 pts), boolean chains 6, ternaries 1 (4 pts), loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MainView.showGoToPartitionDialog (cognitive 27) · ×1
  • MainView.showGoToPartitionDialog (cognitive 27) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:3002 — MainView.showGoToPartitionDialog has cognitive complexity 27 (threshold 15). Drivers by points: if/else 7 (15 pts), loops 3 (4 pts), ternaries 2 (4 pts), boolean chains 3, error handling 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · NodeCanvas.finishConnectionForConditionNode (cognitive 27) · ×1
  • NodeCanvas.finishConnectionForConditionNode (cognitive 27) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:2824 — NodeCanvas.finishConnectionForConditionNode has cognitive complexity 27 (threshold 15). Drivers by points: if/else 10 (20 pts), boolean chains 6, 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.
D2 · Cognitive Complexity · ShowDatasourceListDialog.showDatasourceFormDialog (cognitive 27) · ×1
  • ShowDatasourceListDialog.showDatasourceFormDialog (cognitive 27) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:466 — ShowDatasourceListDialog.showDatasourceFormDialog has cognitive complexity 27 (threshold 15). Drivers by points: if/else 13 (17 pts), boolean chains 5, ternaries 3 (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.
D2 · Cognitive Complexity · IpUtil.getLocalAddress0 (cognitive 26) · ×1
  • IpUtil.getLocalAddress0 (cognitive 26) cc-job/cc-job-core/src/main/java/com/xxl/job/core/util/IpUtil.java:99 — IpUtil.getLocalAddress0 has cognitive complexity 26 (threshold 15). Drivers by points: error handling 5 (11 pts), if/else 5 (11 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.
D2 · Cognitive Complexity · NewJobNodeDialog.validateForm (cognitive 26) · ×1
  • NewJobNodeDialog.validateForm (cognitive 26) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:1317 — NewJobNodeDialog.validateForm has cognitive complexity 26 (threshold 15). Drivers by points: if/else 16 (19 pts), boolean chains 7 (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.
D2 · Cognitive Complexity · NodeCanvas.bindConditionNodeChildren (cognitive 26) · ×1
  • NodeCanvas.bindConditionNodeChildren (cognitive 26) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:2402 — NodeCanvas.bindConditionNodeChildren has cognitive complexity 26 (threshold 15). Drivers by points: if/else 13 (19 pts), loops 3 (4 pts), error handling 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.
D2 · Cognitive Complexity · TaskNavigationBar.updateButtonState (cognitive 26) · ×1
  • TaskNavigationBar.updateButtonState (cognitive 26) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/TaskNavigationBar.java:492 — TaskNavigationBar.updateButtonState has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (19 pts), loops 2 (4 pts), 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.
D2 · Cognitive Complexity · JobExecutionMonitor.call (cognitive 25) · ×1
  • JobExecutionMonitor.call (cognitive 25) cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/service/JobExecutionMonitor.java:72 — JobExecutionMonitor.call has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (15 pts), error handling 3 (6 pts), ternaries 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.
D2 · Cognitive Complexity · JobTriggerService.createTriggerParam (cognitive 25) · ×1
  • JobTriggerService.createTriggerParam (cognitive 25) REDACTED:210 — JobTriggerService.createTriggerParam has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 7, ternaries 2 (3 pts), error handling 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ConditionNode.updateFrameFromManagedNodes (cognitive 25) · ×1
  • ConditionNode.updateFrameFromManagedNodes (cognitive 25) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:1329 — ConditionNode.updateFrameFromManagedNodes has cognitive complexity 25 (threshold 15). Drivers by points: if/else 5 (14 pts), loops 4 (8 pts), boolean chains 3 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · NewJobDialog.updateFieldsForGlueType (cognitive 25) · ×1
  • NewJobDialog.updateFieldsForGlueType (cognitive 25) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:592 — NewJobDialog.updateFieldsForGlueType has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (21 pts), boolean chains 3, match/switch 1 (nesting depth added 12). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · JobPartServiceImpl.importTaskGroup (cognitive 24) · ×1
  • JobPartServiceImpl.importTaskGroup (cognitive 24) REDACTED:725 — JobPartServiceImpl.importTaskGroup has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (14 pts), loops 3 (7 pts), boolean chains 2, error handling 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · IncrementalDataRefresher.updateParamIncrementalMarkers (cognitive 24) · ×1
  • IncrementalDataRefresher.updateParamIncrementalMarkers (cognitive 24) cc-job/cc-job-executor/src/main/java/com/cc/job/executor/core/service/datax/IncrementalDataRefresher.java:166 — IncrementalDataRefresher.updateParamIncrementalMarkers has cognitive complexity 24 (threshold 15). Drivers by points: if/else 11 (18 pts), error handling 2 (4 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.
D2 · Cognitive Complexity · ConditionNode.setupResizeHandleDrag (cognitive 24) · ×1
  • ConditionNode.setupResizeHandleDrag (cognitive 24) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:401 — ConditionNode.setupResizeHandleDrag has cognitive complexity 24 (threshold 15). Drivers by points: if/else 12 (22 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.
D2 · Cognitive Complexity · ConditionNode.<init> (cognitive 24) · ×1
  • ConditionNode.<init> (cognitive 24) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:109 — ConditionNode.<init> has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (11 pts), ternaries 7 (8 pts), boolean chains 4, 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, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · LogPanel.exportLogsToFile (cognitive 24) · ×1
  • LogPanel.exportLogsToFile (cognitive 24) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/LogPanel.java:894 — LogPanel.exportLogsToFile has cognitive complexity 24 (threshold 15). Drivers by points: if/else 6 (13 pts), ternaries 1 (4 pts), boolean chains 3, loops 1 (2 pts), error handling 1, match/switch 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · NewJobDialog.validateForm (cognitive 24) · ×1
  • NewJobDialog.validateForm (cognitive 24) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:1063 — NewJobDialog.validateForm has cognitive complexity 24 (threshold 15). Drivers by points: if/else 16 (18 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.
D2 · Cognitive Complexity · SelectTaskGroupDialog.fillFromTree (cognitive 24) · ×1
  • SelectTaskGroupDialog.fillFromTree (cognitive 24) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/SelectTaskGroupDialog.java:176 — SelectTaskGroupDialog.fillFromTree has cognitive complexity 24 (threshold 15). Drivers by points: if/else 5 (15 pts), loops 2 (7 pts), boolean chains 2 (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.
D2 · Cognitive Complexity · XxlJobCompleter.finishJob (cognitive 23) · ×1
  • XxlJobCompleter.finishJob (cognitive 23) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/complete/XxlJobCompleter.java:47 — XxlJobCompleter.finishJob has cognitive complexity 23 (threshold 15). Drivers by points: if/else 5 (9 pts), ternaries 2 (9 pts), loops 1 (3 pts), boolean chains 2 (nesting depth added 13). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · JobApprovalController.approve (cognitive 23) · ×1
  • JobApprovalController.approve (cognitive 23) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/controller/JobApprovalController.java:111 — JobApprovalController.approve has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 6, error handling 2 (4 pts), ternaries 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ConditionNode.checkAndMoveContainerForNestedConditionNode (cognitive 23) · ×1
  • ConditionNode.checkAndMoveContainerForNestedConditionNode (cognitive 23) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:988 — ConditionNode.checkAndMoveContainerForNestedConditionNode has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 2 (4 pts), ternaries 2 (4 pts), 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.
D2 · Cognitive Complexity · ConditionNode.expand (cognitive 23) · ×1
  • ConditionNode.expand (cognitive 23) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:1196 — ConditionNode.expand has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (17 pts), loops 3 (6 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · GroupContainer.updateFrameFromManagedNodes (cognitive 23) · ×1
  • GroupContainer.updateFrameFromManagedNodes (cognitive 23) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/GroupContainer.java:898 — GroupContainer.updateFrameFromManagedNodes has cognitive complexity 23 (threshold 15). Drivers by points: if/else 5 (14 pts), loops 3 (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.
D2 · Cognitive Complexity · NodeCanvas.handleNodeStateChange (cognitive 23) · ×1
  • NodeCanvas.handleNodeStateChange (cognitive 23) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:3638 — NodeCanvas.handleNodeStateChange has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (13 pts), loops 4 (8 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.
D2 · Cognitive Complexity · NodeCanvas.setNodeTagsFromProperties (cognitive 23) · ×1
  • NodeCanvas.setNodeTagsFromProperties (cognitive 23) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:1323 — NodeCanvas.setNodeTagsFromProperties has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 2 (6 pts), error handling 1 (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.
D2 · Cognitive Complexity · CSharpGlueFactory.detectDotNetFramework (cognitive 22) · ×1
  • CSharpGlueFactory.detectDotNetFramework (cognitive 22) cc-job/cc-job-core/src/main/java/com/xxl/job/core/glue/CSharpGlueFactory.java:467 — CSharpGlueFactory.detectDotNetFramework has cognitive complexity 22 (threshold 15). Drivers by points: if/else 5 (15 pts), error handling 2 (6 pts), loops 1 (nesting depth added 14). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · CanvasConnectionManager.addConnectionInternal (cognitive 22) · ×1
  • CanvasConnectionManager.addConnectionInternal (cognitive 22) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasConnectionManager.java:104 — CanvasConnectionManager.addConnectionInternal has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (14 pts), loops 2 (5 pts), 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.
D2 · Cognitive Complexity · ConditionNode.bindConditionNodes (cognitive 22) · ×1
  • ConditionNode.bindConditionNodes (cognitive 22) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:894 — ConditionNode.bindConditionNodes has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 4, 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.
D2 · Cognitive Complexity · SmartParameterInput.updateAttributeAutocomplete (cognitive 22) · ×1
  • SmartParameterInput.updateAttributeAutocomplete (cognitive 22) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/component/SmartParameterInput.java:536 — SmartParameterInput.updateAttributeAutocomplete has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 4, ternaries 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.
D2 · Cognitive Complexity · 2.locateEdgeWithTaskGroupSwitch (cognitive 22) · ×1
  • 2.locateEdgeWithTaskGroupSwitch (cognitive 22) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:1820 — 2.locateEdgeWithTaskGroupSwitch has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (13 pts), ternaries 3 (7 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.
D2 · Cognitive Complexity · ShowDataxSyncDialog.createMultiColumnRadioButtons (cognitive 22) · ×1
  • ShowDataxSyncDialog.createMultiColumnRadioButtons (cognitive 22) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:2385 — ShowDataxSyncDialog.createMultiColumnRadioButtons has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 4 (12 pts), if/else 4 (6 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MysqlReader.buildJson (cognitive 21) · ×1
  • MysqlReader.buildJson (cognitive 21) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/datax/reader/MysqlReader.java:23 — MysqlReader.buildJson has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (16 pts), loops 1 (3 pts), boolean chains 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · OracleReader.buildJson (cognitive 21) · ×1
  • OracleReader.buildJson (cognitive 21) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/datax/reader/OracleReader.java:22 — OracleReader.buildJson has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (16 pts), loops 1 (3 pts), boolean chains 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · JobComposeServiceImpl.collectGroupNodeIdsRecursively (cognitive 21) · ×1
  • JobComposeServiceImpl.collectGroupNodeIdsRecursively (cognitive 21) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:227 — JobComposeServiceImpl.collectGroupNodeIdsRecursively has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 2 (4 pts), error handling 1 (3 pts), boolean chains 2 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · 2.run (cognitive 21) · ×1
  • 2.run (cognitive 21) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/thread/JobScheduleHelper.java:224 — 2.run has cognitive complexity 21 (threshold 15). Drivers by points: if/else 4 (11 pts), loops 3 (6 pts), error handling 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.
D2 · Cognitive Complexity · HttpClientUtil.executeRequestWithRetry (cognitive 21) · ×1
  • HttpClientUtil.executeRequestWithRetry (cognitive 21) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/HttpClientUtil.java:405 — HttpClientUtil.executeRequestWithRetry has cognitive complexity 21 (threshold 15). Drivers by points: if/else 4 (7 pts), ternaries 3 (7 pts), boolean chains 2, error handling 1 (2 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.
D2 · Cognitive Complexity · NewJobNodeDialog.updateFieldsForGlueType (cognitive 21) · ×1
  • NewJobNodeDialog.updateFieldsForGlueType (cognitive 21) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:641 — NewJobNodeDialog.updateFieldsForGlueType has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (18 pts), boolean chains 2, match/switch 1 (nesting depth added 11). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · NodeCanvas.handleNodeDrag (cognitive 21) · ×1
  • NodeCanvas.handleNodeDrag (cognitive 21) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:594 — NodeCanvas.handleNodeDrag has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (16 pts), loops 1 (3 pts), boolean chains 2 (nesting depth added 11). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · ShowJobLogListDialog.loadLogContentAsync (cognitive 21) · ×1
  • ShowJobLogListDialog.loadLogContentAsync (cognitive 21) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobLogListDialog.java:946 — ShowJobLogListDialog.loadLogContentAsync has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 4, error handling 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · JobInfoServiceImpl.addNode (cognitive 20) · ×1
  • JobInfoServiceImpl.addNode (cognitive 20) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobInfoServiceImpl.java:689 — JobInfoServiceImpl.addNode has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (14 pts), loops 4, 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.
D2 · Cognitive Complexity · JobCompleteHelper.callback (cognitive 20) · ×1
  • JobCompleteHelper.callback (cognitive 20) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/thread/JobCompleteHelper.java:161 — JobCompleteHelper.callback has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (15 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.
D2 · Cognitive Complexity · 3.run (cognitive 20) · ×1
  • 3.run (cognitive 20) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/thread/JobCompleteHelper.java:70 — 3.run has cognitive complexity 20 (threshold 15). Drivers by points: if/else 4 (10 pts), error handling 3 (5 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TriggerCallbackThread.appendFailCallbackFile (cognitive 20) · ×1
  • TriggerCallbackThread.appendFailCallbackFile (cognitive 20) cc-job/cc-job-core/src/main/java/com/xxl/job/core/thread/TriggerCallbackThread.java:209 — TriggerCallbackThread.appendFailCallbackFile has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (9 pts), error handling 3 (6 pts), boolean chains 3, loops 1 (2 pts) (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.
D2 · Cognitive Complexity · ParameterResolver.executeMethodByName (cognitive 20) · ×1
  • ParameterResolver.executeMethodByName (cognitive 20) cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/resolver/ParameterResolver.java:860 — ParameterResolver.executeMethodByName has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (15 pts), boolean chains 4, 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.
D2 · Cognitive Complexity · TaskExecutor.executeTask (cognitive 20) · ×1
  • TaskExecutor.executeTask (cognitive 20) cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/service/TaskExecutor.java:57 — TaskExecutor.executeTask has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 4, ternaries 1 (3 pts), error handling 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · GroupContainer.setupResizeHandleDrag (cognitive 20) · ×1
  • GroupContainer.setupResizeHandleDrag (cognitive 20) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/GroupContainer.java:375 — GroupContainer.setupResizeHandleDrag has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (18 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.
D2 · Cognitive Complexity · ProcessNode.updateGraphStateStyle (cognitive 20) · ×1
  • ProcessNode.updateGraphStateStyle (cognitive 20) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ProcessNode.java:1194 — ProcessNode.updateGraphStateStyle has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (19 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.
D2 · Cognitive Complexity · SmartParameterInput.checkAutocompleteTrigger (cognitive 20) · ×1
  • SmartParameterInput.checkAutocompleteTrigger (cognitive 20) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/component/SmartParameterInput.java:298 — SmartParameterInput.checkAutocompleteTrigger has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 6 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · MainView.updateDetachedSidebarState (cognitive 20) · ×1
  • MainView.updateDetachedSidebarState (cognitive 20) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:2254 — MainView.updateDetachedSidebarState has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 7 (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. This shape REPEATS in the file: one other method here (MainView.updateLeftSidebar) 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.
D2 · Cognitive Complexity · MainView.updateLeftSidebar (cognitive 20) · ×1
  • MainView.updateLeftSidebar (cognitive 20) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:2013 — MainView.updateLeftSidebar has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 7 (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. This shape REPEATS in the file: one other method here (MainView.updateDetachedSidebarState) 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.
D2 · Cognitive Complexity · NewJobGroupDialog.fillFormData (cognitive 20) · ×1
  • NewJobGroupDialog.fillFormData (cognitive 20) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java:467 — NewJobGroupDialog.fillFormData has cognitive complexity 20 (threshold 15). Drivers by points: if/else 12, error handling 4 (8 pts) (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.
D2 · Cognitive Complexity · NodeCanvas.updateConnectionStylesForNode (cognitive 20) · ×1
  • NodeCanvas.updateConnectionStylesForNode (cognitive 20) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:3712 — NodeCanvas.updateConnectionStylesForNode has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 4, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · NodeStyleDialog.createContent (cognitive 20) · ×1
  • NodeStyleDialog.createContent (cognitive 20) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeStyleDialog.java:66 — NodeStyleDialog.createContent has cognitive complexity 20 (threshold 15). Drivers by points: if/else 12 (13 pts), error handling 3 (4 pts), boolean chains 3 (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.
D2 · Cognitive Complexity · ShowExecutorListDialog.showExecutorFormDialog (cognitive 20) · ×1
  • ShowExecutorListDialog.showExecutorFormDialog (cognitive 20) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowExecutorListDialog.java:440 — ShowExecutorListDialog.showExecutorFormDialog has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (12 pts), ternaries 4 (7 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TopToolBar.updateButtonState (cognitive 20) · ×1
  • TopToolBar.updateButtonState (cognitive 20) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/TopToolBar.java:1544 — TopToolBar.updateButtonState has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 3, loops 2 (3 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.
D2 · Cognitive Complexity · SSEService.cleanupExpiredConnections (cognitive 19) · ×1
  • SSEService.cleanupExpiredConnections (cognitive 19) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/sse/SSEService.java:271 — SSEService.cleanupExpiredConnections has cognitive complexity 19 (threshold 15). Drivers by points: error handling 2 (7 pts), if/else 4 (7 pts), loops 3 (4 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · HistoricalDataLoader.loadSingleNodeResult (cognitive 19) · ×1
  • HistoricalDataLoader.loadSingleNodeResult (cognitive 19) cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/service/HistoricalDataLoader.java:167 — HistoricalDataLoader.loadSingleNodeResult has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8, boolean chains 5, error handling 2 (3 pts), ternaries 3 (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.
D2 · Cognitive Complexity · ApiHandler.getJobInfo (cognitive 19) · ×1
  • ApiHandler.getJobInfo (cognitive 19) cc-job/cc-job-executor/src/main/java/com/cc/job/executor/handler/ApiHandler.java:66 — ApiHandler.getJobInfo has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (19 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.
D2 · Cognitive Complexity · ConditionNode.checkAndExpandContainer (cognitive 19) · ×1
  • ConditionNode.checkAndExpandContainer (cognitive 19) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:1062 — ConditionNode.checkAndExpandContainer has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 4, loops 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.
D2 · Cognitive Complexity · NodeCanvas.getConnectorAnchorForNode (cognitive 19) · ×1
  • NodeCanvas.getConnectorAnchorForNode (cognitive 19) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:3001 — NodeCanvas.getConnectorAnchorForNode has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (19 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · 14741.updateItem (cognitive 19) · ×1
  • 14741.updateItem (cognitive 19) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/PermissionManageDialog.java:317 — 14741.updateItem has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 9 (10 pts), boolean chains 5, if/else 4 (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.
D2 · Cognitive Complexity · ShowDatasourceListDialog.buildFormFromInputs (cognitive 19) · ×1
  • ShowDatasourceListDialog.buildFormFromInputs (cognitive 19) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:688 — ShowDatasourceListDialog.buildFormFromInputs has cognitive complexity 19 (threshold 15). Drivers by points: if/else 13 (18 pts), ternaries 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · JobScheduleHelper.toStop (cognitive 18) · ×1
  • JobScheduleHelper.toStop (cognitive 18) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/thread/JobScheduleHelper.java:295 — JobScheduleHelper.toStop has cognitive complexity 18 (threshold 15). Drivers by points: error handling 5 (8 pts), if/else 5 (7 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.
D2 · Cognitive Complexity · DataContext.convertType (cognitive 18) · ×1
  • DataContext.convertType (cognitive 18) cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/context/DataContext.java:295 — DataContext.convertType has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 4 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Async.beginWork (cognitive 18) · ×1
  • Async.beginWork (cognitive 18) cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/engine/Async.java:62 — Async.beginWork has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (9 pts), loops 4 (6 pts), boolean chains 2, error handling 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · HttpTaskExecutor.executeHttpRequest (cognitive 18) · ×1
  • HttpTaskExecutor.executeHttpRequest (cognitive 18) cc-job/cc-job-executor/src/main/java/com/cc/job/executor/core/service/HttpTaskExecutor.java:110 — HttpTaskExecutor.executeHttpRequest has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (9 pts), boolean chains 4, error handling 2 (4 pts), ternaries 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.
D2 · Cognitive Complexity · ParameterAutocompleteService.getNestedAttributeSuggestions (cognitive 18) · ×1
  • ParameterAutocompleteService.getNestedAttributeSuggestions (cognitive 18) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/ParameterAutocompleteService.java:317 — ParameterAutocompleteService.getNestedAttributeSuggestions has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 4, match/switch 1 (2 pts), error handling 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · RecentFilesManager.loadRecentFiles (cognitive 18) · ×1
  • RecentFilesManager.loadRecentFiles (cognitive 18) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/util/RecentFilesManager.java:46 — RecentFilesManager.loadRecentFiles has cognitive complexity 18 (threshold 15). Drivers by points: if/else 3 (8 pts), error handling 2 (6 pts), boolean chains 2, 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.
D2 · Cognitive Complexity · SmartParameterInput.insertSuggestion (cognitive 18) · ×1
  • SmartParameterInput.insertSuggestion (cognitive 18) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/component/SmartParameterInput.java:634 — SmartParameterInput.insertSuggestion has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (18 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.
D2 · Cognitive Complexity · MainView.doRunTaskGroup (cognitive 18) · ×1
  • MainView.doRunTaskGroup (cognitive 18) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:3187 — MainView.doRunTaskGroup has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (10 pts), loops 2 (4 pts), ternaries 2 (3 pts), error handling 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · NodeCanvas.showAlignmentGuides (cognitive 18) · ×1
  • NodeCanvas.showAlignmentGuides (cognitive 18) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:4556 — NodeCanvas.showAlignmentGuides has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (13 pts), loops 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.
D2 · Cognitive Complexity · ShowDataxGroupSyncDialog.buildDataxJobInfoForm (cognitive 18) · ×1
  • ShowDataxGroupSyncDialog.buildDataxJobInfoForm (cognitive 18) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:924 — ShowDataxGroupSyncDialog.buildDataxJobInfoForm has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 11, error handling 2 (4 pts), if/else 3 (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.
D2 · Cognitive Complexity · TaskNavigationBar.setupTabDragReorder (cognitive 18) · ×1
  • TaskNavigationBar.setupTabDragReorder (cognitive 18) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/TaskNavigationBar.java:261 — TaskNavigationBar.setupTabDragReorder has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (17 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.
D2 · Cognitive Complexity · DataxServiceImpl.batchBuildJson (cognitive 17) · ×1
  • DataxServiceImpl.batchBuildJson (cognitive 17) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/DataxServiceImpl.java:93 — DataxServiceImpl.batchBuildJson has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (12 pts), loops 1 (3 pts), boolean chains 2 (nesting depth added 10). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · JobInfoServiceImpl.updateJobCompose (cognitive 17) · ×1
  • JobInfoServiceImpl.updateJobCompose (cognitive 17) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobInfoServiceImpl.java:901 — JobInfoServiceImpl.updateJobCompose has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (13 pts), loops 3 (4 pts) (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · JobLogServiceImpl.getLogDetailCat (cognitive 17) · ×1
  • JobLogServiceImpl.getLogDetailCat (cognitive 17) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobLogServiceImpl.java:132 — JobLogServiceImpl.getLogDetailCat has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 5, error handling 1 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SSEService.sendMessageToLocalOnly (cognitive 17) · ×1
  • SSEService.sendMessageToLocalOnly (cognitive 17) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/sse/SSEService.java:205 — SSEService.sendMessageToLocalOnly has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (9 pts), error handling 2 (5 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.
D2 · Cognitive Complexity · WebSocketServer.sendInfo (cognitive 17) · ×1
  • WebSocketServer.sendInfo (cognitive 17) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/websocket/WebSocketServer.java:129 — WebSocketServer.sendInfo has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (8 pts), error handling 2 (6 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TriggerCallbackThread.retryFailCallbackFile (cognitive 17) · ×1
  • TriggerCallbackThread.retryFailCallbackFile (cognitive 17) cc-job/cc-job-core/src/main/java/com/xxl/job/core/thread/TriggerCallbackThread.java:269 — TriggerCallbackThread.retryFailCallbackFile has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (8 pts), error handling 2 (5 pts), boolean chains 3, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · 1.run (cognitive 17) · ×1
  • 1.run (cognitive 17) cc-job/cc-job-core/src/main/java/com/xxl/job/core/thread/TriggerCallbackThread.java:63 — 1.run has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (11 pts), error handling 2 (3 pts), boolean chains 2, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TaskGroupOrchestrator.parseBatchIdFromParam (cognitive 17) · ×1
  • TaskGroupOrchestrator.parseBatchIdFromParam (cognitive 17) cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/orchestrator/TaskGroupOrchestrator.java:859 — TaskGroupOrchestrator.parseBatchIdFromParam has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 2, error handling 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · LogContentManager.renderIncremental (cognitive 17) · ×1
  • LogContentManager.renderIncremental (cognitive 17) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/LogContentManager.java:213 — LogContentManager.renderIncremental has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (10 pts), ternaries 2 (4 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.
D2 · Cognitive Complexity · NodeOperationManager.copyNodesToClipboard (cognitive 17) · ×1
  • NodeOperationManager.copyNodesToClipboard (cognitive 17) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/NodeOperationManager.java:192 — NodeOperationManager.copyNodesToClipboard has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (10 pts), boolean chains 4, loops 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.
D2 · Cognitive Complexity · GroupContainer.bindCanvasNodes (cognitive 17) · ×1
  • GroupContainer.bindCanvasNodes (cognitive 17) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/GroupContainer.java:635 — GroupContainer.bindCanvasNodes has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (11 pts), loops 4 (6 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · GroupContainer.<init> (cognitive 17) · ×1
  • GroupContainer.<init> (cognitive 17) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/GroupContainer.java:68 — GroupContainer.<init> has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8, ternaries 4 (5 pts), boolean chains 3, 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.
D2 · Cognitive Complexity · ProcessNode.updateStatus (cognitive 17) · ×1
  • ProcessNode.updateStatus (cognitive 17) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ProcessNode.java:1837 — ProcessNode.updateStatus has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (12 pts), match/switch 1 (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.
D2 · Cognitive Complexity · LogPanel.updateLastUpdateTime (cognitive 17) · ×1
  • LogPanel.updateLastUpdateTime (cognitive 17) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/LogPanel.java:301 — LogPanel.updateLastUpdateTime has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (12 pts), error handling 1 (4 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · 2.locateNodeWithTaskGroupSwitch (cognitive 17) · ×1
  • 2.locateNodeWithTaskGroupSwitch (cognitive 17) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:1723 — 2.locateNodeWithTaskGroupSwitch has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 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.
D2 · Cognitive Complexity · NodeCanvas.getContentBounds (cognitive 17) · ×1
  • NodeCanvas.getContentBounds (cognitive 17) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:1765 — NodeCanvas.getContentBounds has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (7 pts), ternaries 2 (4 pts), boolean chains 3, loops 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.
D2 · Cognitive Complexity · ShowDataxSyncDialog.applyParsedReaderConfig (cognitive 17) · ×1
  • ShowDataxSyncDialog.applyParsedReaderConfig (cognitive 17) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:622 — ShowDataxSyncDialog.applyParsedReaderConfig has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (13 pts), boolean chains 3, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ShowDataxSyncDialog.generateJson (cognitive 17) · ×1
  • ShowDataxSyncDialog.generateJson (cognitive 17) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1724 — ShowDataxSyncDialog.generateJson has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (9 pts), boolean chains 4, ternaries 2 (3 pts), error handling 1 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · XxlJobTrigger.trigger (cognitive 16) · ×1
  • XxlJobTrigger.trigger (cognitive 16) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/trigger/XxlJobTrigger.java:44 — XxlJobTrigger.trigger has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 3, loops 1 (2 pts), ternaries 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · CanvasLayoutManager.calculateLevels (cognitive 16) · ×1
  • CanvasLayoutManager.calculateLevels (cognitive 16) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasLayoutManager.java:349 — CanvasLayoutManager.calculateLevels has cognitive complexity 16 (threshold 15). Drivers by points: loops 7 (9 pts), if/else 3 (7 pts) (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.
D2 · Cognitive Complexity · NodeOperationManager.calculateDuplicatePosition (cognitive 16) · ×1
  • NodeOperationManager.calculateDuplicatePosition (cognitive 16) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/NodeOperationManager.java:476 — NodeOperationManager.calculateDuplicatePosition has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (9 pts), ternaries 2 (6 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · NodeOperationManager.pasteMultipleNodes (cognitive 16) · ×1
  • NodeOperationManager.pasteMultipleNodes (cognitive 16) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/NodeOperationManager.java:298 — NodeOperationManager.pasteMultipleNodes has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (10 pts), error handling 3, 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.
D2 · Cognitive Complexity · SmartParameterInput.applySyntaxHighlighting (cognitive 16) · ×1
  • SmartParameterInput.applySyntaxHighlighting (cognitive 16) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/component/SmartParameterInput.java:228 — SmartParameterInput.applySyntaxHighlighting has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (10 pts), error handling 2 (3 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.
D2 · Cognitive Complexity · MiniMapView.updateMiniMap (cognitive 16) · ×1
  • MiniMapView.updateMiniMap (cognitive 16) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MiniMapView.java:217 — MiniMapView.updateMiniMap has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11, ternaries 4, boolean chains 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.
D2 · Cognitive Complexity · NodeCanvas.locateConnectionByEdgeId (cognitive 16) · ×1
  • NodeCanvas.locateConnectionByEdgeId (cognitive 16) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:2631 — NodeCanvas.locateConnectionByEdgeId has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (14 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.
D2 · Cognitive Complexity · NodeCanvas.setupSelectionHandlers (cognitive 16) · ×1
  • NodeCanvas.setupSelectionHandlers (cognitive 16) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:1521 — NodeCanvas.setupSelectionHandlers has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (11 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.
D2 · Cognitive Complexity · PermissionManageDialog.getNodeTaskName (cognitive 16) · ×1
  • PermissionManageDialog.getNodeTaskName (cognitive 16) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/PermissionManageDialog.java:757 — PermissionManageDialog.getNodeTaskName has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 4, error handling 1 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PermissionManageDialog.grantResourcePermission (cognitive 16) · ×1
  • PermissionManageDialog.grantResourcePermission (cognitive 16) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/PermissionManageDialog.java:844 — PermissionManageDialog.grantResourcePermission has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 4, error handling 1 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ShowJobLogListDialog.loadPage (cognitive 16) · ×1
  • ShowJobLogListDialog.loadPage (cognitive 16) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobLogListDialog.java:462 — ShowJobLogListDialog.loadPage has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9, boolean chains 4, ternaries 2, error handling 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.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D31 · IaC & Container Security · Medium IaC · ×1
  • REDACTED
D4 · Code Duplication · Near-duplicate member family (5 members, 42 shared lines) · ×1
  • Near-duplicate member family (5 members, 42 shared lines) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/GlueIdeDialog.java:338 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/GlueIdeDialog.java:338-384 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:1125-1176 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java:621-673 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:1382-1434 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewPartitionDialog.java:127-182 — These 5 members are variants of one another: a block of 42 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 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 · Near-duplicate member family (5 members, 31 shared lines) · ×1
  • Near-duplicate member family (5 members, 31 shared lines) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:229 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:229-288 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java:152-211 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:245-305 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:658-711 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1307-1376 — These 5 members are variants of one another: a block of 31 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 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 · Near-duplicate member family (4 members, 20 shared lines) · ×1
  • Near-duplicate member family (4 members, 20 shared lines) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:81 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:81-109 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowExecutorListDialog.java:75-108 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:140-191 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobLogListDialog.java:111-141 — These 4 members are variants of one another: a block of 20 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication · Near-duplicate member family (4 members, 12 shared lines) · ×1
  • Near-duplicate member family (4 members, 12 shared lines) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/BatchEditDialog.java:49 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/BatchEditDialog.java:49-84 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/CanvasExportDialog.java:41-101 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeApprovalSettingDialog.java:33-71 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeRemarkDialog.java:26-61 — These 4 members are variants of one another: a block of 12 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication · Near-duplicate member family (3 members, 19 shared lines) · ×1
  • Near-duplicate member family (3 members, 19 shared lines) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:886 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:886-922 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:959-1024 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1724-1805 — These 3 members are variants of one another: a block of 19 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 3 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 3 times.
D4 · Code Duplication · Near-duplicate member pair (127 shared lines) · ×1
  • Near-duplicate member pair (127 shared lines) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:109 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:109-284 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/GroupContainer.java:68-232 — These two members are variants of one another: 127 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication · Near-duplicate member pair (70 shared lines) · ×1
  • Near-duplicate member pair (70 shared lines) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:321 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:321-621 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:702-930 — These two members are variants of one another: 70 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication · Near-duplicate member pair (69 shared lines) · ×1
  • Near-duplicate member pair (69 shared lines) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:350 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:350-449 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:310-451 — These two members are variants of one another: 69 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication · Near-duplicate member pair (60 shared lines) · ×1
  • Near-duplicate member pair (60 shared lines) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:862 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:862-966 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:1130-1220 — These two members are variants of one another: 60 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication · Near-duplicate member pair (51 shared lines) · ×1
  • Near-duplicate member pair (51 shared lines) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:592 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:592-679 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:641-777 — These two members are variants of one another: 51 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication · Near-duplicate member pair (33 shared lines) · ×1
  • Near-duplicate member pair (33 shared lines) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:111 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:111-186 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowExecutorListDialog.java:110-177 — These two members are variants of one another: 33 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) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DialogManager.java:91 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DialogManager.java:91-125 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DialogManager.java:133-167 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DialogManager.java:172-220 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DialogManager.java:225-270 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DialogManager.java:276-319 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:261-1636 — 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 (134 corresponding lines) · ×1
  • Edited copy of a member (134 corresponding lines) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:189 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:189-322 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowExecutorListDialog.java:180-319 — These two members are one piece of code written twice and then edited apart: 134 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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 (102 corresponding lines) · ×1
  • Edited copy of a member (102 corresponding lines) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobInfoServiceImpl.java:789 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobInfoServiceImpl.java:789-890 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobInfoServiceImpl.java:1165-1273 — These two members are one piece of code written twice and then edited apart: 102 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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 (89 corresponding lines) · ×1
  • Edited copy of a member (89 corresponding lines) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/LoginService.java:52 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/LoginService.java:52-140 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/LoginService.java:159-247 — 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 (75 corresponding lines) · ×1
  • Edited copy of a member (75 corresponding lines) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/AddJobFromListDialog.java:150 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/AddJobFromListDialog.java:150-224 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:193-292 — These two members are one piece of code written twice and then edited apart: 75 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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 (67 corresponding lines) · ×1
  • Edited copy of a member (67 corresponding lines) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/AddBookmarkDialog.java:41 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/AddBookmarkDialog.java:41-118 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/SaveNodeTemplateDialog.java:43-109 — These two members are one piece of code written twice and then edited apart: 67 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (51 corresponding lines) · ×1
  • Edited copy of a member (51 corresponding lines) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:1329 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:1329-1410 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/GroupContainer.java:898-948 — These two members are one piece of code written twice and then edited apart: 51 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (61 corresponding lines) · ×1
  • Edited copy of a member (61 corresponding lines) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:1063 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:1063-1123 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:1317-1377 — These two members are one piece of code written twice and then edited apart: 61 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (83 corresponding lines) · ×1
  • Edited copy of a member (83 corresponding lines) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:401 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:401-483 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/GroupContainer.java:375-458 — These two members are one piece of code written twice and then edited apart: 83 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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) · ×1
  • Edited copy of a member (56 corresponding lines) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasTemplateManager.java:207 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasTemplateManager.java:207-265 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasTemplateManager.java:271-326 — 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 copy of a member (95 corresponding lines) · ×1
  • Edited copy of a member (95 corresponding lines) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/TaskNavigationBar.java:492 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/TaskNavigationBar.java:492-586 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/TopToolBar.java:1544-1641 — 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 (52 corresponding lines) · ×1
  • Edited copy of a member (52 corresponding lines) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:949 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:949-1003 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:1045-1096 — These two members are one piece of code written twice and then edited apart: 52 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (43 corresponding lines) · ×1
  • Edited copy of a member (43 corresponding lines) cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/config/XxlJobConfig.java:100 — cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/config/XxlJobConfig.java:100-142 | cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/orchestrator/TaskGroupOrchestrator.java:112-160 — These two members are one piece of code written twice and then edited apart: 43 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (49 corresponding lines) · ×1
  • Edited copy of a member (49 corresponding lines) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:2013 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:2013-2063 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:2254-2302 — These two members are one piece of code written twice and then edited apart: 49 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (46 corresponding lines) · ×1
  • Edited copy of a member (46 corresponding lines) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/NodeConnection.java:211 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/NodeConnection.java:211-256 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/NodeConnection.java:262-307 — 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 (40 corresponding lines) · ×1
  • Edited copy of a member (40 corresponding lines) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:2071 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:2071-2110 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:2112-2151 — 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 (60 corresponding lines) · ×1
  • Edited copy of a member (60 corresponding lines) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/LoginView.java:264 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/LoginView.java:264-334 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/RegisterView.java:251-310 — These two members are one piece of code written twice and then edited apart: 60 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (37 corresponding lines) · ×1
  • Edited copy of a member (37 corresponding lines) cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/context/DataContextAccessor.java:209 — cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/context/DataContextAccessor.java:209-245 | cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/resolver/ParameterResolver.java:652-693 — 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 (5 members, 26+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 26+ corresponding lines) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:807 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:807-838 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java:403-436 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:1063-1096 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:631-656 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1269-1302 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 26 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 31+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 31+ corresponding lines) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasNodeManager.java:150 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasNodeManager.java:150-180 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:2895-2925 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:3028-3058 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 31 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (34 corresponding lines) · ×1
  • Edited copy of a member (34 corresponding lines) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:2001 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:2001-2034 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:2036-2069 — 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 (35 corresponding lines) · ×1
  • Edited copy of a member (35 corresponding lines) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/util/FileStorageUtil.java:45 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/util/FileStorageUtil.java:45-79 | cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/service/FileStorageService.java:185-219 — 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 (27 corresponding lines) · ×1
  • Edited copy of a member (27 corresponding lines) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:3851 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:3851-3877 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:3882-3908 — 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 (6 members, 22+ corresponding lines) · ×1
  • Edited copies of one member (6 members, 22+ corresponding lines) cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/controller/JobGroupControlController.java:43 — cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/controller/JobGroupControlController.java:43-66 | cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/controller/JobGroupControlController.java:77-102 | cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/controller/JobGroupControlController.java:110-131 | cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/interfaces/api/TaskGroupControlApi.java:40-64 | cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/interfaces/api/TaskGroupControlApi.java:76-103 | cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/interfaces/api/TaskGroupControlApi.java:111-134 — These 6 members are one piece of code written 6 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 6 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 14+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 14+ corresponding lines) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/PermissionManageDialog.java:446 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/PermissionManageDialog.java:446-459 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/PermissionManageDialog.java:792-806 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/PermissionManageDialog.java:897-910 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 18+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 18+ corresponding lines) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobNodeResultServiceImpl.java:144 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobNodeResultServiceImpl.java:144-161 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobNodeResultServiceImpl.java:164-185 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobNodeResultServiceImpl.java:188-211 — 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 (3 members, 16+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 16+ corresponding lines) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/TreeDataManager.java:141 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/TreeDataManager.java:141-158 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/TaskTreeView.java:484-499 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/TaskTreeView.java:501-516 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 9+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 9+ corresponding lines) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:1184 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:1184-1192 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:1194-1202 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:1204-1212 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:1214-1222 — 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 (4 members, 11+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 11+ corresponding lines) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/PermissionManageDialog.java:391 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/PermissionManageDialog.java:391-401 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:418-428 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:436-446 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:539-551 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 7+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 7+ corresponding lines) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:1106 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:1106-1112 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:1114-1120 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1983-1990 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1992-1999 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (7 members, 9+ corresponding lines) · ×1
  • Edited copies of one member (7 members, 9+ corresponding lines) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DialogManager.java:516 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DialogManager.java:516-530 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DialogManager.java:535-549 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DialogManager.java:554-568 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DialogManager.java:573-581 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DialogManager.java:594-608 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DialogManager.java:613-627 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DialogManager.java:632-646 — These 7 members are one piece of code written 7 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 7 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 8+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 8+ corresponding lines) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/controller/JobCanvasBookmarkController.java:40 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/controller/JobCanvasBookmarkController.java:40-47 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/controller/JobNodeTemplateController.java:42-49 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/controller/JobNodeTemplateController.java:57-65 — 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, 10+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 10+ corresponding lines) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/thread/JobCompleteHelper.java:127 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/thread/JobCompleteHelper.java:127-140 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/thread/JobFailMonitorHelper.java:113-122 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/thread/JobLogReportHelper.java:143-152 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/thread/JobRegistryHelper.java:136-149 — 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.
D4 · Code Duplication · Edited copies of one member (3 members, 7+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 7+ corresponding lines) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ConditionNodeDialog.java:407 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ConditionNodeDialog.java:407-413 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeHistoryView.java:372-378 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/TaskTreeView.java:409-415 — 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 copy of a member (5 corresponding lines) · ×1
  • Edited copy of a member (5 corresponding lines) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/SSEService.java:413 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/SSEService.java:413-417 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/WebSocketService.java:260-264 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (106 lines × 2) · ×1
  • Duplicated block (106 lines × 2) cc-job/cc-job-executor-samples/cc-job-executor-sample-frameless/src/main/java/com/cc/job/executor/sample/sample/frameless/jobhandler/SampleXxlJob.java:129 — cc-job/cc-job-executor-samples/cc-job-executor-sample-frameless/src/main/java/com/cc/job/executor/sample/sample/frameless/jobhandler/SampleXxlJob.java:129-234 | cc-job/cc-job-executor-samples/cc-job-executor-sample-springboot/src/main/java/com/cc/job/executor/sample/service/jobhandler/SampleXxlJob.java:462-567 — before extracting anything, compare `cc-job/cc-job-executor-samples/cc-job-executor-sample-frameless/src/main/java/com/cc/job/executor/sample/sample/frameless/jobhandler/SampleXxlJob.java` and `cc-job/cc-job-executor-samples/cc-job-executor-sample-springboot/src/main/java/com/cc/job/executor/sample/service/jobhandler/SampleXxlJob.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 168 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (100–103 lines × 2) · ×1
  • Duplicated block (100–103 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:185 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:185-284 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/GroupContainer.java:130-232 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/GroupContainer.java` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 569 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:185` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (65–76 lines × 2) · ×1
  • Duplicated block (65–76 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:402 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:402-466 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/GroupContainer.java:376-451 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/GroupContainer.java` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 569 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:402` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (74 lines × 2) · ×1
  • Duplicated block (74 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/LoginService.java:67 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/LoginService.java:67-140 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/LoginService.java:174-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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/LoginService.java:67` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (52 lines × 4) · ×1
  • Duplicated block (52 lines × 4) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:336 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:336-387 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowExecutorListDialog.java:333-384 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:702-753 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobLogListDialog.java:409-460 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowExecutorListDialog.java` as WHOLE FILES: this scan already matched 26 separate duplicated blocks between them, totalling at least 339 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:336` 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, `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:335` calls `getStyleClass`, `add` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:701` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (39–52 lines × 2) · ×1
  • Duplicated block (39–52 lines × 2) REDACTED:372 — REDACTED:372-423 | REDACTED:483-521 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:372` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (44–52 lines × 2) · ×1
  • Duplicated block (44–52 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:339 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:339-382 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/GroupContainer.java:296-347 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/GroupContainer.java` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 569 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (46–50 lines × 2) · ×1
  • Duplicated block (46–50 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:893 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:893-938 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:1141-1190 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java` as WHOLE FILES: this scan already matched 46 separate duplicated blocks between them, totalling at least 798 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:893` it does not close everything it opens, so those 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, `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:1191` calls `setData` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:939` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (76 lines × 2) · ×1
  • Duplicated block (76 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:1302 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:1302-1377 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:1441-1516 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java` as WHOLE FILES: this scan already matched 46 separate duplicated blocks between them, totalling at least 798 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (49 lines × 2) · ×1
  • Duplicated block (49 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobPartService.java:167 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobPartService.java:167-215 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobPartService.java:307-355 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobPartService.java:167` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (40–46 lines × 2) · ×1
  • Duplicated block (40–46 lines × 2) REDACTED:636 — REDACTED:636-681 | REDACTED:767-806 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:636` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (39–46 lines × 2) · ×1
  • Duplicated block (39–46 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/AddJobFromListDialog.java:174 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/AddJobFromListDialog.java:174-212 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:227-272 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/AddJobFromListDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 175 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/AddJobFromListDialog.java:174` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (42–44 lines × 2) · ×1
  • Duplicated block (42–44 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:368 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:368-409 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:328-371 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java` as WHOLE FILES: this scan already matched 46 separate duplicated blocks between them, totalling at least 798 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.
D4 · Code Duplication · Duplicated block (40 lines × 2) · ×1
  • Duplicated block (40 lines × 2) cc-job/cc-job-executor-samples/cc-job-executor-sample-frameless/src/main/java/com/cc/job/executor/sample/sample/frameless/jobhandler/SampleXxlJob.java:76 — cc-job/cc-job-executor-samples/cc-job-executor-sample-frameless/src/main/java/com/cc/job/executor/sample/sample/frameless/jobhandler/SampleXxlJob.java:76-115 | cc-job/cc-job-executor-samples/cc-job-executor-sample-springboot/src/main/java/com/cc/job/executor/sample/service/jobhandler/SampleXxlJob.java:409-448 — before extracting anything, compare `cc-job/cc-job-executor-samples/cc-job-executor-sample-frameless/src/main/java/com/cc/job/executor/sample/sample/frameless/jobhandler/SampleXxlJob.java` and `cc-job/cc-job-executor-samples/cc-job-executor-sample-springboot/src/main/java/com/cc/job/executor/sample/service/jobhandler/SampleXxlJob.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 168 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (29–39 lines × 3) · ×1
  • Duplicated block (29–39 lines × 3) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:267 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:267-305 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:683-711 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1338-1376 — 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:267` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
D4 · Code Duplication · Duplicated block (35–38 lines × 2) · ×1
  • Duplicated block (35–38 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:2029 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:2029-2063 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:2265-2302 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:2029` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (35–37 lines × 5) · ×1
  • Duplicated block (35–37 lines × 5) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/GlueIdeDialog.java:349 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/GlueIdeDialog.java:349-384 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:1142-1176 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java:638-673 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:1399-1434 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewPartitionDialog.java:146-182 — 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 5 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/GlueIdeDialog.java:349` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (27–37 lines × 2) · ×1
  • Duplicated block (27–37 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:764 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:764-790 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1450-1486 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java` as WHOLE FILES: this scan already matched 42 separate duplicated blocks between them, totalling at least 585 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 after the matched lines, `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1487` calls `setPromptText` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:791` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (35–36 lines × 2) · ×1
  • Duplicated block (35–36 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobPartService.java:131 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobPartService.java:131-165 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobPartService.java:270-305 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobPartService.java:131` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (35 lines × 2) · ×1
  • Duplicated block (35 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/NodeConnection.java:212 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/NodeConnection.java:212-246 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/NodeConnection.java:263-297 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/NodeConnection.java: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.
D4 · Code Duplication · Duplicated block (34 lines × 2) · ×1
  • Duplicated block (34 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:1738 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:1738-1771 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:1831-1864 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:1738` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (33 lines × 2) · ×1
  • Duplicated block (33 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java:66 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java:66-98 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:130-162 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java` as WHOLE FILES: this scan already matched 25 separate duplicated blocks between them, totalling at least 367 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java:66` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (25–31 lines × 2) · ×1
  • Duplicated block (25–31 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ProcessNode.java:1729 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ProcessNode.java:1729-1759 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ProcessNode.java:1766-1790 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ProcessNode.java:1729` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (22–31 lines × 2) · ×1
  • Duplicated block (22–31 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:717 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:717-738 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1383-1413 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java` as WHOLE FILES: this scan already matched 42 separate duplicated blocks between them, totalling at least 585 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1383` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (24–30 lines × 5) · ×1
  • Duplicated block (24–30 lines × 5) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:232 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:232-259 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java:155-182 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:248-275 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:666-689 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1317-1346 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java` as WHOLE FILES: this scan already matched 31 separate duplicated blocks between them, totalling at least 451 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.
D4 · Code Duplication · Duplicated block (22–30 lines × 5) · ×1
  • Duplicated block (22–30 lines × 5) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:811 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:811-838 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java:407-436 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:1067-1096 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:635-656 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1273-1302 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java` as WHOLE FILES: this scan already matched 31 separate duplicated blocks between them, totalling at least 451 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:811` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
D4 · Code Duplication · Duplicated block (27–30 lines × 2) · ×1
  • Duplicated block (27–30 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:555 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:555-581 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/GroupContainer.java:534-563 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/GroupContainer.java` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 569 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:555` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (28–29 lines × 2) · ×1
  • Duplicated block (28–29 lines × 2) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/cron/CronExpression.java:1274 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/cron/CronExpression.java:1274-1301 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/cron/CronExpression.java:1310-1338 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-admin/src/main/java/com/cc/job/admin/cron/CronExpression.java:1274` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (22–29 lines × 2) · ×1
  • Duplicated block (22–29 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:756 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:756-777 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:876-904 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java` as WHOLE FILES: this scan already matched 46 separate duplicated blocks between them, totalling at least 798 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:756` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (19–28 lines × 2) · ×1
  • Duplicated block (19–28 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:445 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:445-463 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1169-1196 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java` as WHOLE FILES: this scan already matched 42 separate duplicated blocks between them, totalling at least 585 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.
D4 · Code Duplication · Duplicated block (28 lines × 2) · ×1
  • Duplicated block (28 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:2277 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:2277-2304 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:2337-2364 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:2277` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (27 lines × 4) · ×1
  • Duplicated block (27 lines × 4) cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/client/AdminApiClient.java:87 — cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/client/AdminApiClient.java:87-113 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/infrastructure/client/ApiClient.java:101-127 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/HttpClientUtil.java:90-116 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/util/ApiUtil.java:119-145 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/HttpClientUtil.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/util/ApiUtil.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 62 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (2–27 lines × 5) · ×1
  • Duplicated block (2–27 lines × 5) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/AddJobFromListDialog.java:337 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/AddJobFromListDialog.java:337-357 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:411-412 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowExecutorListDialog.java:408-409 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:774-800 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobLogListDialog.java:510-511 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/AddJobFromListDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 175 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/AddJobFromListDialog.java:337` it does not close everything it opens, so those 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, `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/AddJobFromListDialog.java:357` calls `getData`, `getList`, `emptyList` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:412` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (26 lines × 4) · ×1
  • Duplicated block (26 lines × 4) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/infrastructure/client/ApiClient.java:180 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/infrastructure/client/ApiClient.java:180-205 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/infrastructure/client/ApiClient.java:246-271 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/infrastructure/client/ApiClient.java:303-328 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/infrastructure/client/ApiClient.java:357-382 — 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/infrastructure/client/ApiClient.java:180` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (18–26 lines × 2) · ×1
  • Duplicated block (18–26 lines × 2) cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/service/HistoricalDataLoader.java:466 — cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/service/HistoricalDataLoader.java:466-483 | cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/service/ResultStorageService.java:421-446 — 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.
D4 · Code Duplication · Duplicated block (27 lines × 2) · ×1
  • Duplicated block (27 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:197 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:197-223 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowExecutorListDialog.java:188-214 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowExecutorListDialog.java` as WHOLE FILES: this scan already matched 26 separate duplicated blocks between them, totalling at least 339 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.
D4 · Code Duplication · Duplicated block (25 lines × 2) · ×1
  • Duplicated block (25 lines × 2) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/datax/reader/MysqlReader.java:64 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/datax/reader/MysqlReader.java:64-88 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/datax/reader/OracleReader.java:79-103 — before extracting anything, compare `cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/datax/reader/MysqlReader.java` and `cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/datax/reader/OracleReader.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 67 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/datax/reader/MysqlReader.java:64` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (24–25 lines × 2) · ×1
  • Duplicated block (24–25 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:702 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:702-726 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:915-938 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:702` it does not close everything it opens, so those 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, `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:729` calls `setVisible`, `setManaged` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:939` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (20–25 lines × 2) · ×1
  • Duplicated block (20–25 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobPartService.java:464 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobPartService.java:464-488 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobPartService.java:513-532 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobPartService.java:464` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (4–24 lines × 4) · ×1
  • Duplicated block (4–24 lines × 4) cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/client/AdminApiClient.java:541 — cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/client/AdminApiClient.java:541-544 | cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/client/AdminApiClient.java:575-598 | cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/client/AdminApiClient.java:607-630 | cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/client/AdminApiClient.java:643-646 — 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 `cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/client/AdminApiClient.java:541` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (23–24 lines × 2) · ×1
  • Duplicated block (23–24 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:1079 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:1079-1102 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:1327-1349 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java` as WHOLE FILES: this scan already matched 46 separate duplicated blocks between them, totalling at least 798 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:1079` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (22–23 lines × 2) · ×1
  • Duplicated block (22–23 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:1417 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:1417-1438 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/GroupContainer.java:961-983 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/GroupContainer.java` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 569 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (21–22 lines × 4) · ×1
  • Duplicated block (21–22 lines × 4) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:785 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:785-805 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java:377-398 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:1037-1058 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1243-1264 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java` as WHOLE FILES: this scan already matched 31 separate duplicated blocks between them, totalling at least 451 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:785` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
D4 · Code Duplication · Duplicated block (21–22 lines × 2) · ×1
  • Duplicated block (21–22 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:935 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:935-955 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1678-1699 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java` as WHOLE FILES: this scan already matched 42 separate duplicated blocks between them, totalling at least 585 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.
D4 · Code Duplication · Duplicated block (21 lines × 3) · ×1
  • Duplicated block (21 lines × 3) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasNodeManager.java:151 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasNodeManager.java:151-171 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:2896-2916 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:3029-3049 — 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasNodeManager.java:151` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (4–21 lines × 3) · ×1
  • Duplicated block (4–21 lines × 3) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasDataLoader.java:142 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasDataLoader.java:142-162 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasDataLoader.java:190-193 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:1329-1349 — 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasDataLoader.java:190` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (21 lines × 2) · ×1
  • Duplicated block (21 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:542 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:542-562 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:564-584 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java` as WHOLE FILES: this scan already matched 46 separate duplicated blocks between them, totalling at least 798 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.
D4 · Code Duplication · Duplicated block (16–20 lines × 2) · ×1
  • Duplicated block (16–20 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:1156 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:1156-1171 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:1911-1930 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (17–19 lines × 2) · ×1
  • Duplicated block (17–19 lines × 2) cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/context/DataContextAccessor.java:210 — cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/context/DataContextAccessor.java:210-226 | cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/resolver/ParameterResolver.java:653-671 — 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 `cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/context/DataContextAccessor.java:210` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (38–41 lines × 2) · ×1
  • Duplicated block (38–41 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:989 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:989-1026 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1889-1929 — 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.
D4 · Code Duplication · Duplicated block (11–18 lines × 3) · ×1
  • Duplicated block (11–18 lines × 3) cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/context/DataContextAccessor.java:251 — cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/context/DataContextAccessor.java:251-261 | cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/orchestrator/TaskGroupOrchestrator.java:457-474 | cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/resolver/ParameterResolver.java:704-721 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (12–18 lines × 2) · ×1
  • Duplicated block (12–18 lines × 2) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:453 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:453-464 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:820-837 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:453` it begins part-way through the construct above it, so those 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, `cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:819` calls `add` and `cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:452` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (15–18 lines × 2) · ×1
  • Duplicated block (15–18 lines × 2) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobUserServiceImpl.java:65 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobUserServiceImpl.java:65-82 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobUserServiceImpl.java:165-179 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobUserServiceImpl.java:65` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (16–18 lines × 2) · ×1
  • Duplicated block (16–18 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:533 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:533-548 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/GroupContainer.java:506-523 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/GroupContainer.java` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 569 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:533` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (28–30 lines × 2) · ×1
  • Duplicated block (28–30 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:643 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:643-670 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:733-762 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java` as WHOLE FILES: this scan already matched 46 separate duplicated blocks between them, totalling at least 798 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, `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:731` calls `setVisible`, `setManaged` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:642` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (13–17 lines × 4) · ×1
  • Duplicated block (13–17 lines × 4) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:452 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:452-465 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java:269-285 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:457-473 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1427-1439 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java` as WHOLE FILES: this scan already matched 31 separate duplicated blocks between them, totalling at least 451 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:452` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (15–17 lines × 2) · ×1
  • Duplicated block (15–17 lines × 2) cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/context/DataContextAccessor.java:231 — cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/context/DataContextAccessor.java:231-245 | cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/resolver/ParameterResolver.java:677-693 — 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 `cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/context/DataContextAccessor.java:231` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (16 lines × 3) · ×1
  • Duplicated block (16 lines × 3) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DialogManager.java:204 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DialogManager.java:204-219 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DialogManager.java:254-269 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DialogManager.java:303-318 — 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DialogManager.java:204` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (15–16 lines × 3) · ×1
  • Duplicated block (15–16 lines × 3) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:491 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:491-505 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/GroupContainer.java:470-485 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/GroupContainer.java:695-710 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/GroupContainer.java` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 569 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.
D4 · Code Duplication · Duplicated block (10–16 lines × 2) · ×1
  • Duplicated block (10–16 lines × 2) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobUserServiceImpl.java:136 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobUserServiceImpl.java:136-151 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobUserServiceImpl.java:194-203 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobUserServiceImpl.java:136` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobUserServiceImpl.java:152` calls `warn` and `cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobUserServiceImpl.java:204` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (10–15 lines × 5) · ×1
  • Duplicated block (10–15 lines × 5) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:780 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:780-793 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java:372-386 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:1032-1046 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:614-623 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1238-1252 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java` as WHOLE FILES: this scan already matched 31 separate duplicated blocks between them, totalling at least 451 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java: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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (15 lines × 4) · ×1
  • Duplicated block (15 lines × 4) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DialogManager.java:110 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DialogManager.java:110-124 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DialogManager.java:152-166 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DialogManager.java:197-211 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DialogManager.java:296-310 — 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DialogManager.java:110` it begins part-way through the construct above it, so those 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, `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DialogManager.java:108` calls `error` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DialogManager.java:294` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (15 lines × 3) · ×1
  • Duplicated block (15 lines × 3) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:883 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:883-897 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowExecutorListDialog.java:661-675 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobLogListDialog.java:1191-1205 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowExecutorListDialog.java` as WHOLE FILES: this scan already matched 26 separate duplicated blocks between them, totalling at least 339 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:883` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (23–25 lines × 2) · ×1
  • Duplicated block (23–25 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:294 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:294-316 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/GroupContainer.java:244-268 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/GroupContainer.java` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 569 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:294` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (18–23 lines × 2) · ×1
  • Duplicated block (18–23 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:556 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:556-578 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:3195-3212 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:556` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (13–15 lines × 2) · ×1
  • Duplicated block (13–15 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:156 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:156-168 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:170-184 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java` as WHOLE FILES: this scan already matched 46 separate duplicated blocks between them, totalling at least 798 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:156` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:171` calls `valueProperty`, `addListener`, `updateScheduleConfLabel` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:187` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (32–34 lines × 2) · ×1
  • Duplicated block (32–34 lines × 2) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobInfoServiceImpl.java:807 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobInfoServiceImpl.java:807-840 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobInfoServiceImpl.java:1178-1209 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobInfoServiceImpl.java:807` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (10–13 lines × 6) · ×1
  • Duplicated block (10–13 lines × 6) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:808 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:808-819 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java:404-416 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:1064-1076 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/SelectTaskGroupDialog.java:210-219 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:632-641 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1270-1282 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java` as WHOLE FILES: this scan already matched 31 separate duplicated blocks between them, totalling at least 451 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:808` it does not close everything it opens, so those 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, `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:820` calls `setStyle` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/SelectTaskGroupDialog.java:220` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (13 lines × 4) · ×1
  • Duplicated block (13 lines × 4) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/EdgeStyleDialog.java:40 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/EdgeStyleDialog.java:40-52 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeLabelDialog.java:57-69 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeSearchDialog.java:60-72 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeStyleDialog.java:46-58 — 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/EdgeStyleDialog.java:40` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (11–13 lines × 4) · ×1
  • Duplicated block (11–13 lines × 4) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:527 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:527-539 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java:354-366 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:799-809 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1501-1513 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java` as WHOLE FILES: this scan already matched 31 separate duplicated blocks between them, totalling at least 451 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:527` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
D4 · Code Duplication · Duplicated block (10–13 lines × 2) · ×1
  • Duplicated block (10–13 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/HttpClientUtil.java:185 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/HttpClientUtil.java:185-194 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/HttpClientUtil.java:223-235 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/HttpClientUtil.java:185` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (3–13 lines × 4) · ×1
  • Duplicated block (3–13 lines × 4) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobDataxService.java:71 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobDataxService.java:71-73 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobDataxService.java:96-108 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobDataxService.java:119-131 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobJdbcDatasourceService.java:119-121 — 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobDataxService.java:71` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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, `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobDataxService.java:95` calls `Builder`, `url`, `post` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobDataxService.java:71` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (9–12 lines × 5) · ×1
  • Duplicated block (9–12 lines × 5) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:472 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:472-483 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java:298-309 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:484-495 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:761-769 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1446-1457 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java` as WHOLE FILES: this scan already matched 31 separate duplicated blocks between them, totalling at least 451 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.
D4 · Code Duplication · Duplicated block (12 lines × 4) · ×1
  • Duplicated block (12 lines × 4) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/CanvasExportDialog.java:44 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/CanvasExportDialog.java:44-55 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/EdgeStyleDialog.java:33-44 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeSearchDialog.java:53-64 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeStyleDialog.java:39-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 all 4 call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (11–12 lines × 4) · ×1
  • Duplicated block (11–12 lines × 4) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ConditionNodeDialog.java:134 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ConditionNodeDialog.java:134-144 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:183-193 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java:116-127 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:197-208 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java` as WHOLE FILES: this scan already matched 31 separate duplicated blocks between them, totalling at least 451 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 after the matched lines, `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:195` calls `Label`, `setStyle`, `getChildren` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java:128` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (7–12 lines × 4) · ×1
  • Duplicated block (7–12 lines × 4) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MiniMapView.java:243 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MiniMapView.java:243-253 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MiniMapView.java:328-338 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MiniMapView.java:385-396 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MiniMapView.java:463-469 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MiniMapView.java:341` calls `getViewportBounds` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MiniMapView.java:470` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (9–12 lines × 4) · ×1
  • Duplicated block (9–12 lines × 4) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:291 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:291-302 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java:217-228 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:714-722 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1379-1390 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java` as WHOLE FILES: this scan already matched 31 separate duplicated blocks between them, totalling at least 451 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.
D4 · Code Duplication · Duplicated block (10–12 lines × 3) · ×1
  • Duplicated block (10–12 lines × 3) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:307 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:307-318 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:725-734 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1395-1406 — 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.
D4 · Code Duplication · Duplicated block (11–12 lines × 3) · ×1
  • Duplicated block (11–12 lines × 3) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:845 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:845-855 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java:447-457 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:1104-1115 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java` as WHOLE FILES: this scan already matched 31 separate duplicated blocks between them, totalling at least 451 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java: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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:844` calls `getMisfireStrategy`, `equals` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:1103` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (10–11 lines × 8) · ×1
  • Duplicated block (10–11 lines × 8) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:1127 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:1127-1137 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java:624-633 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:1385-1394 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewPartitionDialog.java:130-139 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:84-93 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowExecutorListDialog.java:78-87 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:144-153 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobLogListDialog.java:114-123 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java` as WHOLE FILES: this scan already matched 31 separate duplicated blocks between them, totalling at least 451 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:1127` it does not close everything it opens, so those 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, `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:82` calls `getDialogPane`, `setPrefSize` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:1125` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (11 lines × 6) · ×1
  • Duplicated block (11 lines × 6) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:340 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:340-350 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:353-363 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:366-376 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:379-389 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:392-402 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:459-469 — 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:340` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note first that the copies are not typed on the same thing: the declarations holding them bind `item` to `Number` in one and `String` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (9–11 lines × 5) · ×1
  • Duplicated block (9–11 lines × 5) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:89 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:89-99 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:133-141 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:207-215 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowExecutorListDialog.java:83-93 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobLogListDialog.java:119-129 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowExecutorListDialog.java` as WHOLE FILES: this scan already matched 26 separate duplicated blocks between them, totalling at least 339 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:89` it does not close everything it opens, so those 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, `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:87` calls `getDialogPane`, `setMaxWidth`, `setMaxHeight` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:132` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (10–11 lines × 4) · ×1
  • Duplicated block (10–11 lines × 4) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:2278 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:2278-2287 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:2317-2327 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:2338-2347 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:2370-2380 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:2276` calls `equals` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:2369` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (10–11 lines × 3) · ×1
  • Duplicated block (10–11 lines × 3) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/datax/reader/MysqlReader.java:81 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/datax/reader/MysqlReader.java:81-90 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/datax/reader/OracleReader.java:96-105 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/datax/reader/PostgreSqlReader.java:31-41 — before extracting anything, compare `cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/datax/reader/MysqlReader.java` and `cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/datax/reader/OracleReader.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 67 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/datax/reader/MysqlReader.java:81` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Duplicated block (8–11 lines × 2) · ×1
  • Duplicated block (8–11 lines × 2) REDACTED:41 — REDACTED:41-51 | REDACTED:513-520 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication · Duplicated block (7–10 lines × 7) · ×1
  • Duplicated block (7–10 lines × 7) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:705 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:705-714 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:816-825 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java:413-422 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:787-796 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:1073-1082 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:639-645 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1279-1288 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java` as WHOLE FILES: this scan already matched 31 separate duplicated blocks between them, totalling at least 451 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, `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:784` calls `setText`, `equals` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:704` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (8–10 lines × 3) · ×1
  • Duplicated block (8–10 lines × 3) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:488 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:488-497 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:772-779 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1462-1471 — 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.
D4 · Code Duplication · Duplicated block (7–10 lines × 3) · ×1
  • Duplicated block (7–10 lines × 3) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:1014 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:1014-1020 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1917-1923 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/component/SmartParameterInput.java:277-286 — 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:1014` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (5–10 lines × 3) · ×1
  • Duplicated block (5–10 lines × 3) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/alarm/impl/DingTalkJobAlarm.java:57 — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/alarm/impl/DingTalkJobAlarm.java:57-61 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/alarm/impl/FeishuJobAlarm.java:53-62 | cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/alarm/impl/WeComJobAlarm.java:53-62 — 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 `cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/alarm/impl/DingTalkJobAlarm.java:57` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (7–10 lines × 2) · ×1
  • Duplicated block (7–10 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:706 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:706-712 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:2597-2606 — both copies are in the same file, so extract the 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.
D4 · Code Duplication · Duplicated block (21–23 lines × 2) · ×1
  • Duplicated block (21–23 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:900 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:900-920 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:989-1011 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (9 lines × 8) · ×1
  • Duplicated block (9 lines × 8) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:339 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:339-347 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:352-360 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:365-373 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:378-386 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:391-399 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:404-412 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:458-466 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:476-484 — all 8 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Note first that the copies are not typed on the same thing: the declarations holding them bind `item` to `Number` in one and `String` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (9 lines × 7) · ×1
  • Duplicated block (9 lines × 7) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/BatchEditDialog.java:59 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/BatchEditDialog.java:59-67 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/CanvasExportDialog.java:51-59 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/EdgeStyleDialog.java:40-48 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeLabelDialog.java:57-65 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeRemarkDialog.java:36-44 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeSearchDialog.java:60-68 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeStyleDialog.java:46-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 7 call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (9 lines × 5) · ×1
  • Duplicated block (9 lines × 5) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DialogManager.java:110 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DialogManager.java:110-118 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DialogManager.java:152-160 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DialogManager.java:197-205 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DialogManager.java:296-304 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:1546-1554 — there are 5 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 5 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DialogManager.java:110` it begins part-way through the construct above it, so those 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, `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DialogManager.java:108` calls `error` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DialogManager.java:294` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (6–9 lines × 3) · ×1
  • Duplicated block (6–9 lines × 3) cc-job/cc-job-executor/src/main/java/com/cc/job/executor/core/service/datax/IncrementalDataRefresher.java:227 — cc-job/cc-job-executor/src/main/java/com/cc/job/executor/core/service/datax/IncrementalDataRefresher.java:227-232 | cc-job/cc-job-executor/src/main/java/com/cc/job/executor/core/service/datax/IncrementalDataRefresher.java:272-277 | cc-job/cc-job-executor/src/main/java/com/cc/job/executor/core/service/datax/IncrementalDataRefresher.java:332-340 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `cc-job/cc-job-executor/src/main/java/com/cc/job/executor/core/service/datax/IncrementalDataRefresher.java:343` calls `buildWhereClause` and `cc-job/cc-job-executor/src/main/java/com/cc/job/executor/core/service/datax/IncrementalDataRefresher.java:278` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (14–17 lines × 2) · ×1
  • Duplicated block (14–17 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasTemplateManager.java:221 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasTemplateManager.java:221-237 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasTemplateManager.java:287-300 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasTemplateManager.java:221` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (7–9 lines × 2) · ×1
  • Duplicated block (7–9 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/PermissionManageDialog.java:153 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/PermissionManageDialog.java:153-161 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/PermissionManageDialog.java:358-364 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (26–27 lines × 2) · ×1
  • Duplicated block (26–27 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/TaskReportDialog.java:224 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/TaskReportDialog.java:224-250 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/TaskReportDialog.java: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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/TaskReportDialog.java:327` calls `toPath` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/TaskReportDialog.java:252` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (7–8 lines × 10) · ×1
  • Duplicated block (7–8 lines × 10) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/GlueIdeDialog.java:339 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/GlueIdeDialog.java:339-345 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:1126-1132 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java:622-629 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:1383-1390 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewPartitionDialog.java:129-135 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/SelectTaskGroupDialog.java:237-243 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:83-89 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowExecutorListDialog.java:77-83 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:143-149 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobLogListDialog.java:113-119 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 10 call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:82` calls `getDialogPane`, `setPrefSize` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/GlueIdeDialog.java:338` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (8 lines × 7) · ×1
  • Duplicated block (8 lines × 7) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DialogManager.java:110 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DialogManager.java:110-117 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DialogManager.java:152-159 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DialogManager.java:197-204 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DialogManager.java:212-220 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DialogManager.java:262-270 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DialogManager.java:296-303 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DialogManager.java:311-319 — all 7 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DialogManager.java:110` it begins part-way through the construct above it, so those 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, `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DialogManager.java:108` calls `error` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DialogManager.java:294` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (8 lines × 5) · ×1
  • Duplicated block (8 lines × 5) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DialogManager.java:117 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DialogManager.java:117-125 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DialogManager.java:159-167 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DialogManager.java:204-211 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DialogManager.java:254-261 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DialogManager.java:303-310 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DialogManager.java:117` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (7–8 lines × 5) · ×1
  • Duplicated block (7–8 lines × 5) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:271 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:271-278 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java:194-201 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:287-294 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:697-703 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1358-1365 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java` as WHOLE FILES: this scan already matched 31 separate duplicated blocks between them, totalling at least 451 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.
D4 · Code Duplication · Duplicated block (7–8 lines × 4) · ×1
  • Duplicated block (7–8 lines × 4) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobPartService.java:401 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobPartService.java:401-408 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobPartService.java:425-431 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobPartService.java:481-488 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobPartService.java:525-532 — 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobPartService.java:401` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (3–8 lines × 5) · ×1
  • Duplicated block (3–8 lines × 5) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/AddBookmarkDialog.java:94 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/AddBookmarkDialog.java:94-99 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/BookmarkListDialog.java:84-86 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/CreateNodeFromTemplateDialog.java:76-81 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/SaveNodeTemplateDialog.java:87-92 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/SettingsDialog.java:48-55 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/AddBookmarkDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/SaveNodeTemplateDialog.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/BookmarkListDialog.java:84` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (6–7 lines × 8) · ×1
  • Duplicated block (6–7 lines × 8) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/BatchEditDialog.java:58 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/BatchEditDialog.java:58-64 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/CanvasExportDialog.java:50-56 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/EdgeStyleDialog.java:39-45 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeApprovalSettingDialog.java:40-45 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeLabelDialog.java:56-62 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeRemarkDialog.java:35-41 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeSearchDialog.java:59-65 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeStyleDialog.java:45-51 — 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 8 call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (6–7 lines × 6) · ×1
  • Duplicated block (6–7 lines × 6) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/DependencyViewPanel.java:236 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/DependencyViewPanel.java:236-241 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:92-98 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:135-140 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:209-214 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowExecutorListDialog.java:86-92 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobLogListDialog.java:122-128 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowExecutorListDialog.java` as WHOLE FILES: this scan already matched 26 separate duplicated blocks between them, totalling at least 339 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/DependencyViewPanel.java:236` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (7 lines × 5) · ×1
  • Duplicated block (7 lines × 5) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/NodeCallbackConfigurator.java:154 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/NodeCallbackConfigurator.java:154-160 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/NodeCallbackConfigurator.java:230-236 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/NodeCallbackConfigurator.java:259-265 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/NodeCallbackConfigurator.java:285-291 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/NodeCallbackConfigurator.java:311-317 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/NodeCallbackConfigurator.java:154` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/NodeCallbackConfigurator.java:161` calls `warn` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/NodeCallbackConfigurator.java:318` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (6–7 lines × 4) · ×1
  • Duplicated block (6–7 lines × 4) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:849 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:849-854 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowExecutorListDialog.java:596-601 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:1029-1034 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobLogListDialog.java:1109-1115 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowExecutorListDialog.java` as WHOLE FILES: this scan already matched 26 separate duplicated blocks between them, totalling at least 339 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:849` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (8–9 lines × 2) · ×1
  • Duplicated block (8–9 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasTemplateManager.java:257 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasTemplateManager.java:257-265 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasTemplateManager.java:319-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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasTemplateManager.java: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. 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.
D4 · Code Duplication · Duplicated block (5–7 lines × 2) · ×1
  • Duplicated block (5–7 lines × 2) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:580 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:580-586 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1970-1974 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:580` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (6 lines × 8) · ×1
  • Duplicated block (6 lines × 8) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:266 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:266-271 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:273-278 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:394-399 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:401-406 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:778-783 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:785-790 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1031-1036 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1038-1043 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java` as WHOLE FILES: this scan already matched 42 separate duplicated blocks between them, totalling at least 585 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 `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:266` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:776` calls `setHgrow` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:264` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (6 lines × 6) · ×1
  • Duplicated block (6 lines × 6) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:894 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:894-899 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:906-911 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:983-988 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:996-1001 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1747-1752 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1780-1785 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java` as WHOLE FILES: this scan already matched 42 separate duplicated blocks between them, totalling at least 585 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.
D4 · Code Duplication · Duplicated block (3–6 lines × 3) · ×1
  • Duplicated block (3–6 lines × 3) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:977 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:977-982 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java:530-535 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:1234-1236 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java` as WHOLE FILES: this scan already matched 31 separate duplicated blocks between them, totalling at least 451 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, `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java:528` calls `setJobPartId`, `intValue` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:973` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (5 lines × 11) · ×1
  • Duplicated block (5 lines × 11) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:1132 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:1132-1138 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java:629-634 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:1390-1395 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewPartitionDialog.java:135-140 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeDetailsDialog.java:211-215 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:89-94 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:133-137 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:207-211 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowExecutorListDialog.java:83-88 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:149-154 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobLogListDialog.java:119-124 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java` as WHOLE FILES: this scan already matched 31 separate duplicated blocks between them, totalling at least 451 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, `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:1130` calls `getDialogPane`, `setMaxWidth`, `setMaxHeight` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeDetailsDialog.java:210` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (46 lines × 2) · ×1
  • Duplicated block (46 lines × 2) cc-job/cc-job-xo/src/main/java/com/cc/job/xo/model/dto/JobEdgeDto.java:1 — cc-job/cc-job-xo/src/main/java/com/cc/job/xo/model/dto/JobEdgeDto.java:1-46 | cc-job/cc-job-xo/src/main/java/com/cc/job/xo/model/entity/JobEdge.java:1-117 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-xo/src/main/java/com/cc/job/xo/model/dto/JobEdgeDto.java:1` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (78 lines × 2) · ×1
  • Duplicated block (78 lines × 2) cc-job/cc-job-xo/src/main/java/com/cc/job/xo/model/form/JobGroupForm.java:1 — cc-job/cc-job-xo/src/main/java/com/cc/job/xo/model/form/JobGroupForm.java:1-78 | cc-job/cc-job-xo/src/main/java/com/cc/job/xo/model/vo/JobGroupVO.java:1-88 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-xo/src/main/java/com/cc/job/xo/model/form/JobGroupForm.java:1` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (198 lines × 3) · ×1
  • Duplicated block (198 lines × 3) cc-job/cc-job-xo/src/main/java/com/cc/job/xo/model/entity/JobLog.java:1 — cc-job/cc-job-xo/src/main/java/com/cc/job/xo/model/entity/JobLog.java:1-225 | cc-job/cc-job-xo/src/main/java/com/cc/job/xo/model/form/JobLogForm.java:1-198 | cc-job/cc-job-xo/src/main/java/com/cc/job/xo/model/vo/JobLogVO.java:1-198 — 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 `cc-job/cc-job-xo/src/main/java/com/cc/job/xo/model/entity/JobLog.java:1` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (77 lines × 2) · ×1
  • Duplicated block (77 lines × 2) cc-job/cc-job-xo/src/main/java/com/cc/job/xo/model/form/JobLogReportForm.java:1 — cc-job/cc-job-xo/src/main/java/com/cc/job/xo/model/form/JobLogReportForm.java:1-85 | cc-job/cc-job-xo/src/main/java/com/cc/job/xo/model/vo/JobLogReportVO.java:1-77 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-xo/src/main/java/com/cc/job/xo/model/form/JobLogReportForm.java:1` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (86 lines × 2) · ×1
  • Duplicated block (86 lines × 2) cc-job/cc-job-xo/src/main/java/com/cc/job/xo/model/form/JobLogglueForm.java:1 — cc-job/cc-job-xo/src/main/java/com/cc/job/xo/model/form/JobLogglueForm.java:1-101 | cc-job/cc-job-xo/src/main/java/com/cc/job/xo/model/vo/JobLogglueVO.java:1-86 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `cc-job/cc-job-xo/src/main/java/com/cc/job/xo/model/form/JobLogglueForm.java:1` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (38 lines × 2) · ×1
  • Duplicated block (38 lines × 2) cc-job/cc-job-xo/src/main/java/com/cc/job/xo/model/entity/JobJdbcDatasource.java:1 — cc-job/cc-job-xo/src/main/java/com/cc/job/xo/model/entity/JobJdbcDatasource.java:1-119 | cc-job/cc-job-xo/src/main/java/com/cc/job/xo/model/query/JobJdbcDatasourceQuery.java:1-38 — 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 `cc-job/cc-job-xo/src/main/java/com/cc/job/xo/model/entity/JobJdbcDatasource.java:1` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (5 lines × 5) · ×1
  • Duplicated block (5 lines × 5) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/AddJobFromListDialog.java:376 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/AddJobFromListDialog.java:376-380 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:433-437 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowExecutorListDialog.java:427-431 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:842-846 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobLogListDialog.java:529-533 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/AddJobFromListDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 175 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.
D4 · Code Duplication · Duplicated block (6 lines × 7) · ×1
  • Duplicated block (6 lines × 7) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/BatchEditDialog.java:217 — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/BatchEditDialog.java:217-222 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ConditionNodeDialog.java:415-420 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/EdgeStyleDialog.java:166-171 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeLabelDialog.java:220-225 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeRemarkDialog.java:89-94 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeSearchDialog.java:297-302 | cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeStyleDialog.java:321-326 — before extracting anything, compare `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/BatchEditDialog.java` and `cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeRemarkDialog.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 52 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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.
P1 · CI/CD gates · No CI pipeline · ×1
  • No CI pipeline — No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
X25 · Inert configuration knob · Constructor parameter is stored and never read · ×1
  • Constructor parameter is stored and never read cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ConditionNodeDialog.java:393 — `ConditionNodeDialog` takes `editData` from the caller and stores it in `conditionData` on line 80, defaulting to `new ConditionData()` when none is supplied — but `conditionData` is never read anywhere in the type, and line 393 spells `new ConditionData()` out again where that field's value belongs. Every caller that passes `editData` therefore gets `new ConditionData()` regardless, and nothing in the type reports that its argument was ignored. Read `conditionData` at line 393 — or, if the value genuinely is fixed, delete `editData` and `conditionData` together so the signature stops advertising a knob that does nothing.
Minor — 404 finding(s)
D34 · Knowledge Freshness · Orphaned file · ×269
  • Orphaned file cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/TopToolBar.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ProcessNode.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobInfoServiceImpl.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file cc-job/cc-job-admin/src/main/java/com/cc/job/admin/cron/CronExpression.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/handler/JobGroupXxlJob.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/PermissionManageDialog.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobLogListDialog.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowJobListDialog.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/orchestrator/TaskGroupOrchestrator.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/LogPanel.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file REDACTED:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/component/SmartParameterInput.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/resolver/ParameterResolver.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/GroupContainer.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDatasourceListDialog.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/NodeOperationManager.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/TaskNavigationBar.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DialogManager.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/client/AdminApiClient.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • + 244 more in this group — see findings.md.
X10 · Duplicated predicate · Duplicated predicate · ×40
  • Duplicated predicate cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:1416 — `!item.getKey().trim().isEmpty() || !item.getValue().trim().isEmpty()` appears character-identically in 2 files — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java, cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:1426 — `!managedCanvasNodes.isEmpty() && !baseRelativePos.isEmpty()` appears character-identically in 2 files — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java, cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/GroupContainer.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/alarm/impl/DingTalkJobAlarm.java:43 — `!properties.isEnabled() || properties.getWebhookUrl() == null || properties.getWebhookUrl().trim().isEmpty()` appears character-identically in 3 files — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/alarm/impl/DingTalkJobAlarm.java, cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/alarm/impl/FeishuJobAlarm.java, cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/alarm/impl/WeComJobAlarm.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:692 — `"POST".equals(reqType) || "PUT".equals(reqType)` appears character-identically in 2 files — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java, cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasDataLoader.java:249 — `(candidate == null || candidate.isBlank()) && properties != null` appears character-identically in 2 files — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasDataLoader.java, cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/ParameterAutocompleteService.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/scheduler/XxlJobScheduler.java:90 — `address==null || address.trim().length()==0` appears character-identically in 2 files — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/scheduler/XxlJobScheduler.java, cc-job/cc-job-core/src/main/java/com/xxl/job/core/executor/XxlJobExecutor.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasDataLoader.java:255 — `candidate == null || candidate.isBlank()` appears character-identically in 2 files — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasDataLoader.java, cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/ParameterAutocompleteService.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasTemplateManager.java:375 — `category != null && !category.trim().isEmpty()` appears character-identically in 2 files — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/CanvasTemplateManager.java, cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/JobNodeTemplateApiService.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/TreeDataManager.java:77 — `child.getType() != null && child.getType() == 1` appears character-identically in 3 files — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/TreeDataManager.java, cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java, cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/SelectTaskGroupDialog.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/EdgeStyleDialog.java:155 — `colorPicker != null && colorPicker.getValue() != null` appears character-identically in 2 files — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/EdgeStyleDialog.java, cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeStyleDialog.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java:1079 — `columnType == 1 && incrTimeFormatCombo.getValue() != null` appears character-identically in 2 files — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxGroupSyncDialog.java, cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DataManager.java:355 — `composeData == null || composeData.getNodes() == null` appears character-identically in 2 files — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/manager/DataManager.java, cc-job/cc-job-gui/src/main/java/com/cc/job/gui/service/ParameterAutocompleteService.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java:1186 — `conn != null && conn.getParent() != null` appears character-identically in 2 files — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ConditionNode.java, cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/GroupContainer.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/sse/DatabaseSseBroadcastProvider.java:30 — `connectionKey == null || messageJson == null` appears character-identically in 2 files — cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/sse/DatabaseSseBroadcastProvider.java, cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/sse/SSEService.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/service/HistoricalDataLoader.java:45 — `context == null || context.getDataContext() == null` appears character-identically in 2 files — cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/service/HistoricalDataLoader.java, cc-job/cc-job-executor-compose/src/main/java/com/cc/job/executor/compose/core/service/ResultStorageService.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate cc-job/cc-job-core/src/main/java/com/xxl/job/core/glue/CSharpGlueFactory.java:285 — `contextData != null && !contextData.isEmpty()` appears character-identically in 2 files — cc-job/cc-job-core/src/main/java/com/xxl/job/core/glue/CSharpGlueFactory.java, cc-job/cc-job-core/src/main/java/com/xxl/job/core/handler/impl/ScriptJobHandler.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:653 — `currentCode == null || currentCode.trim().isEmpty()` appears character-identically in 2 files — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java, cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:750 — `currentGlueType == null || !currentGlueType.requiresGlueSource()` appears character-identically in 2 files — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java, cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/TaskNavigationBar.java:501 — `currentTaskGroupId != null && runningJobs.containsKey(currentTaskGroupId) && runningJobs.get(currentTaskGroupId).isRunning()` appears character-identically in 2 files — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/TaskNavigationBar.java, cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/TopToolBar.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:856 — `data.getChildJobId() != null && !data.getChildJobId().trim().isEmpty()` appears character-identically in 2 files — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java, cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:847 — `data.getExecutorBlockStrategy() != null && !data.getExecutorBlockStrategy().equals("SERIAL_EXECUTION")` appears character-identically in 3 files — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java, cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java, cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:853 — `data.getExecutorFailRetryCount() != null && data.getExecutorFailRetryCount() != 0` appears character-identically in 3 files — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java, cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java, cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:841 — `data.getExecutorRouteStrategy() != null && !data.getExecutorRouteStrategy().equals("FIRST")` appears character-identically in 3 files — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java, cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java, cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java:452 — `data.getExecutorTimeout() != null && data.getExecutorTimeout() != 300` appears character-identically in 2 files — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java, cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobNodeDialog.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java:844 — `data.getMisfireStrategy() != null && !data.getMisfireStrategy().equals("DO_NOTHING")` appears character-identically in 2 files — cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobDialog.java, cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NewJobGroupDialog.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • + 15 more in this group — see findings.md.
X4 · Structured logging · Interpolated log message defeats structured logging · ×40
  • Interpolated log message defeats structured logging cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:332 — `info` at line 332 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
  • Interpolated log message defeats structured logging cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:549 — `info` at line 549 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
  • Interpolated log message defeats structured logging cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:841 — `info` at line 841 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
  • Interpolated log message defeats structured logging cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:872 — `info` at line 872 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
  • Interpolated log message defeats structured logging cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:885 — `info` at line 885 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
  • Interpolated log message defeats structured logging cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:1048 — `info` at line 1048 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
  • Interpolated log message defeats structured logging cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:1380 — `warn` at line 1380 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
  • Interpolated log message defeats structured logging cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:1403 — `info` at line 1403 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
  • Interpolated log message defeats structured logging cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:1732 — `info` at line 1732 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
  • Interpolated log message defeats structured logging cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:1737 — `warn` at line 1737 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
  • Interpolated log message defeats structured logging cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:1745 — `info` at line 1745 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
  • Interpolated log message defeats structured logging cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:1775 — `info` at line 1775 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
  • Interpolated log message defeats structured logging cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:1778 — `warn` at line 1778 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
  • Interpolated log message defeats structured logging cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:1788 — `info` at line 1788 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
  • Interpolated log message defeats structured logging cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:1791 — `warn` at line 1791 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
  • Interpolated log message defeats structured logging cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:1838 — `info` at line 1838 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
  • Interpolated log message defeats structured logging cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:1954 — `info` at line 1954 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
  • Interpolated log message defeats structured logging cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:2363 — `info` at line 2363 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
  • Interpolated log message defeats structured logging cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:2409 — `info` at line 2409 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
  • Interpolated log message defeats structured logging cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:2517 — `info` at line 2517 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
  • Interpolated log message defeats structured logging cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:2602 — `info` at line 2602 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
  • Interpolated log message defeats structured logging cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:2852 — `info` at line 2852 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
  • Interpolated log message defeats structured logging cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:2891 — `info` at line 2891 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
  • Interpolated log message defeats structured logging cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:2894 — `warn` at line 2894 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
  • Interpolated log message defeats structured logging cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:3053 — `info` at line 3053 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
  • + 15 more in this group — see findings.md.
P10 · Library API & versioning · Implementation type on the public API · ×6
  • Implementation type on the public API cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/alarm/impl/DingTalkJobAlarm.java:29 — 5 public types in `com.cc.job.admin.task.alarm.impl` are marked as implementation by their own namespace, folder or name: `DingTalkJobAlarm` (cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/alarm/impl/DingTalkJobAlarm.java:29, `impl`), `EmailJobAlarm` (cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/alarm/impl/EmailJobAlarm.java:28, `impl`), `FeishuJobAlarm` (cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/alarm/impl/FeishuJobAlarm.java:25, `impl`), `WeComJobAlarm` (cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/alarm/impl/WeComJobAlarm.java:25, `impl`), `WebhookJobAlarm` (cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/alarm/impl/WebhookJobAlarm.java:32, `impl`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers.
  • Implementation type on the public API cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/AdminBizImpl.java:17 — 20 public types in `com.cc.job.admin.task.service.impl` are marked as implementation by their own namespace, folder or name: `AdminBizImpl` (cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/AdminBizImpl.java:17, `impl`), `DataxServiceImpl` (cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/DataxServiceImpl.java:22, `impl`), `JobCanvasBookmarkServiceImpl` (cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobCanvasBookmarkServiceImpl.java:13, `impl`), `JobComposeServiceImpl` (cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:39, `impl`), `LfNode` (cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:55, `impl`), `LfEdge` (cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobComposeServiceImpl.java:121, `impl`), `JobEdgeServiceImpl` (cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobEdgeServiceImpl.java:10, `impl`), `JobGroupServiceImpl` (cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/impl/JobGroupServiceImpl.java:32, `impl`), and 12 more. While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers.
  • Implementation type on the public API cc-job/cc-job-core/src/main/java/com/xxl/job/core/biz/impl/ExecutorBizImpl.java:26 — 1 public type in `com.xxl.job.core.biz.impl` is marked as implementation by its own namespace, folder or name: `ExecutorBizImpl` (cc-job/cc-job-core/src/main/java/com/xxl/job/core/biz/impl/ExecutorBizImpl.java:26, `impl`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers.
  • Implementation type on the public API cc-job/cc-job-core/src/main/java/com/xxl/job/core/executor/impl/XxlJobSimpleExecutor.java:20 — 2 public types in `com.xxl.job.core.executor.impl` are marked as implementation by their own namespace, folder or name: `XxlJobSimpleExecutor` (cc-job/cc-job-core/src/main/java/com/xxl/job/core/executor/impl/XxlJobSimpleExecutor.java:20, `impl`), `XxlJobSpringExecutor` (cc-job/cc-job-core/src/main/java/com/xxl/job/core/executor/impl/XxlJobSpringExecutor.java:26, `impl`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers.
  • Implementation type on the public API cc-job/cc-job-core/src/main/java/com/xxl/job/core/glue/impl/SpringGlueFactory.java:17 — 1 public type in `com.xxl.job.core.glue.impl` is marked as implementation by its own namespace, folder or name: `SpringGlueFactory` (cc-job/cc-job-core/src/main/java/com/xxl/job/core/glue/impl/SpringGlueFactory.java:17, `impl`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers.
  • Implementation type on the public API cc-job/cc-job-core/src/main/java/com/xxl/job/core/handler/impl/CSharpGlueJobHandler.java:13 — 4 public types in `com.xxl.job.core.handler.impl` are marked as implementation by their own namespace, folder or name: `CSharpGlueJobHandler` (cc-job/cc-job-core/src/main/java/com/xxl/job/core/handler/impl/CSharpGlueJobHandler.java:13, `impl`), `GlueJobHandler` (cc-job/cc-job-core/src/main/java/com/xxl/job/core/handler/impl/GlueJobHandler.java:11, `impl`), `MethodJobHandler` (cc-job/cc-job-core/src/main/java/com/xxl/job/core/handler/impl/MethodJobHandler.java:10, `impl`), `ScriptJobHandler` (cc-job/cc-job-core/src/main/java/com/xxl/job/core/handler/impl/ScriptJobHandler.java:15, `impl`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers.
D10 · Test Quality · No direct assertions · ×5
  • No direct assertions: test1 cc-job/cc-job-admin/src/test/java/com/cc/job/test/CcJobApplicationTest.java:56 — No conventional assertion call was detected, and 5 of 5 tests in `cc-job-admin` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: test2 cc-job/cc-job-admin/src/test/java/com/cc/job/test/CcJobApplicationTest.java:71 — No conventional assertion call was detected, and 5 of 5 tests in `cc-job-admin` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: test3 cc-job/cc-job-admin/src/test/java/com/cc/job/test/CcJobApplicationTest.java:144 — No conventional assertion call was detected, and 5 of 5 tests in `cc-job-admin` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: test4 cc-job/cc-job-admin/src/test/java/com/cc/job/test/CcJobApplicationTest.java:155 — No conventional assertion call was detected, and 5 of 5 tests in `cc-job-admin` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: test5 cc-job/cc-job-admin/src/test/java/com/cc/job/test/CcJobApplicationTest.java:166 — No conventional assertion call was detected, and 5 of 5 tests in `cc-job-admin` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
D13 · REDACTED Scanning · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D28 · Secrets (history) · REDACTED · ×5
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D26 · Project Cohesion · Projects may be oversized for their cohesion · ×4
  • Projects may be oversized for their cohesion cc-job/cc-job-gui/pom.xml:1 — `cc-job/cc-job-gui` (49724 LoC, 209 module-visible types across 13 directories) overshoots its size bounds. 4 of 8 build unit(s) (Maven) overshoot their size bounds, lowering Project Cohesion to 0.9/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
  • Projects may be oversized for their cohesion cc-job/cc-job-admin/pom.xml:1 — `cc-job/cc-job-admin` (17898 LoC, 159 module-visible types across 33 directories) overshoots its size bounds. 4 of 8 build unit(s) (Maven) overshoot their size bounds, lowering Project Cohesion to 0.9/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
  • Projects may be oversized for their cohesion REDACTED:1 — `cc-job/cc-job-executor-compose` (8288 LoC, 53 module-visible types across 25 directories) overshoots its size bounds. 4 of 8 build unit(s) (Maven) overshoot their size bounds, lowering Project Cohesion to 0.9/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
  • Projects may be oversized for their cohesion REDACTED:1 — `cc-job/cc-job-xo` (7132 LoC, 122 module-visible types across 12 directories) overshoots its size bounds. 4 of 8 build unit(s) (Maven) overshoot their size bounds, lowering Project Cohesion to 0.9/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
M4 · Documentation accuracy · README/code drift · ×4
  • README/code drift cc-job/cc-job-executor-compose/README.md:328 — cc-job/cc-job-executor-compose/README.md links to `./COMPLETE_IMPLEMENTATION.md`, but `cc-job/cc-job-executor-compose/COMPLETE_IMPLEMENTATION.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift cc-job/cc-job-executor-compose/README.md:474 — cc-job/cc-job-executor-compose/README.md links to `../doc/architecture-analysis.md`, but `cc-job/doc/architecture-analysis.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift cc-job/cc-job-executor-compose/README.md:475 — cc-job/cc-job-executor-compose/README.md links to `../doc/migration-guide.md`, but `cc-job/doc/migration-guide.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift cc-job/cc-job-executor-compose/README.md:476 — cc-job/cc-job-executor-compose/README.md links to `../doc/api-specification.md`, but `cc-job/doc/api-specification.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
D34 · Knowledge Freshness · Most significant orphaned file · ×3
  • Most significant orphaned file cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeCanvas.java:1 — One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
  • Most significant orphaned file cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/MainView.java:1 — One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
  • Most significant orphaned file cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:1 — One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
X7 · Silent fallback defaults · Silent fallback default on parse failure · ×3
  • Silent fallback default on parse failure cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/component/DateTimePicker.java:91 — `fromString` returns `0` when `NumberFormatException` is thrown, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment in the catch or in the Javadoc, and the row stops firing.
  • Silent fallback default on parse failure cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeStyleDialog.java:295 — `getNodeHeight` returns `80.0` when `NumberFormatException` is thrown, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment in the catch or in the Javadoc, and the row stops firing.
  • Silent fallback default on parse failure cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/NodeStyleDialog.java:284 — `getNodeWidth` returns `180.0` when `NumberFormatException` is thrown, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment in the catch or in the Javadoc, and the row stops firing.
AX6 · Interface segregation · Fat interface · ×2
  • Fat interface: JobInfoService (25 abstract methods) cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/service/JobInfoService.java:23 — `JobInfoService` declares 25 abstract methods: `baseSaveJobInfo`, `baseUpdateJobInfo`, `checkJobGroupRunningInExecutor`, `countJobs`, `countTaskGroups`, `delNodes`, `deleteJobInfos`, `getGlueList`, `getGlueList`, `getJobInfoForm`, `getJobInfoListWithPermission`, `getJobInfoPage`, `initData`, `nextTriggerTime`, `pauseJob`, `resetTriggerOneStatus`, `saveGlueSource`, `saveJobCompose`, `saveJobInfo`, `startJob`, `stopJob`, `stopJobCompose`, `triggerJob`, `updateJobCompose`, `updateJobInfo`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. Those 25 declarations carry 24 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 24 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: ToolBarCallback (43 abstract methods) cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/TopToolBar.java:46 — `ToolBarCallback` declares 43 abstract methods: `onAlignBottom`, `onAlignHorizontalCenter`, `onAlignLeft`, `onAlignRight`, `onAlignToCenter`, `onAlignToGroupBottom`, `onAlignToGroupHorizontalCenter`, `onAlignToGroupLeft`, `onAlignToGroupRight`, `onAlignToGroupTop`, `onAlignToGroupVerticalCenter`, `onAlignTop`, `onAlignVerticalCenter`, `onClear`, `onDashboardBigScreen`, `onDatasourceList`, `onDataxGroupSync`, `onDataxSync`, `onDetectCycles`, `onDistributeHorizontally`, `onDistributeVertically`, `onExportCanvas`, `onJobGroupList`, `onJobList`, `onJobLogList`, `onLayoutHorizontal`, `onLayoutVertical`, `onNew`, `onNewPart`, `onNodeHistory`, `onOpen`, `onRedo`, `onRun`, `onSave`, `onSelect`, `onSettings`, `onStop`, `onTaskReport`, `onToggleSnapToGrid`, `onUndo`, and 3 more. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
D29 · Static Analysis (SAST) · REDACTED · ×2
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×2
  • REDACTED
  • REDACTED
X7 · Silent fallback defaults · Silent fallback default in catch · ×2
  • Silent fallback default in catch cc-job/cc-job-admin/src/main/java/com/cc/job/admin/task/controller/JobApprovalController.java:63 — `listPending` swallows every exception into `return true` — a data error becomes a silent behavior change with no trail. Log the failure or let it propagate. 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 in the catch or in the Javadoc, and the row stops firing.
  • Silent fallback default in catch cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ProcessNode.java:527 — `lightenColor` swallows every exception into `return "#93C5FD"` — a data error becomes a silent behavior change with no trail. Log the failure or let it propagate. 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 in the catch or in the Javadoc, and the row stops firing.
D10 · Test Quality · Test project verifies nothing · ×1
  • Test project verifies nothing: cc-job-admin cc-job/cc-job-admin/src/test/java/com/cc/job/test/CcJobApplicationTest.java:56 — No conventional assertion call was detected in 5 of 5 tests in `cc-job-admin` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
D20 · ADR Quality · No ADRs found · ×1
  • No ADRs found cc-job/cc-job-gui/pom.xml:157 — 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 `cc-job/cc-job-gui/pom.xml` makes this repository a deployable product (line 157).
D21 · Naming Consistency · `applyWriterConfigToUi` spells `Ui` where 15 names in the project spell it `UI` · ×1
  • `applyWriterConfigToUi` spells `Ui` where 15 names in the project spell it `UI` cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/ShowDataxSyncDialog.java:667 — 15 of 16 names in project cc-job-gui spell the token `UI` (15 of 16; unit: names in project cc-job-gui containing `UI`). Peers: NodeConnection.initializeUI (cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/NodeConnection.java:120); ProcessNode.initializeUI (cc-job/cc-job-gui/src/main/java/com/cc/job/gui/model/ProcessNode.java:215); CanvasRuler.initializeUI (cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/CanvasRuler.java:40); CollapsedSidebar.initializeUI (cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/CollapsedSidebar.java:31); LogPanel.initializeUI (cc-job/cc-job-gui/src/main/java/com/cc/job/gui/view/LogPanel.java:74). Rename to `applyWriterConfigToUI`. [rule N6]
D28 · Secrets (history) · Rotate the exposed credentials · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D31 · IaC & Container Security · Low IaC · ×1
  • REDACTED
D34 · Knowledge Freshness · Dormant codebase · ×1
  • Dormant codebase — 272 of 272 significant files have no living knowledge — the codebase as a whole is dormant, not 272 separate risks. Counted over 272 of the 505 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over. Re-engage owners or document before change.
M2 · Architecture documentation · No ADRs · ×1
  • No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
M2 · Architecture documentation · No architecture diagram/doc · ×1
  • No architecture diagram/doc — No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
P3 · Security & performance tooling · No SAST · ×1
  • No SAST — No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
P3 · Security & performance tooling · No dependency-update automation · ×1
  • No dependency-update automation cc-job/cc-job-admin/pom.xml:17 — `cc-job/cc-job-admin/pom.xml` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`.
X5 · Nullable reference types · Java packages are not null-marked everywhere · ×1
  • Java packages are not null-marked everywhere — 0/118 of this repository's Java package directories are under a non-null default: a `package-info.java` declaring `@NullMarked` (JSpecify) or `@NonNullApi`, `@ParametersAreNonnullByDefault`, `@NonNullByDefault`, `@DefaultQualifier(NonNull.class)`; a `module-info.java` declaring `@NullMarked`; every type in it `@NullMarked`; or a build that runs NullAway with the package in `AnnotatedPackages`, or the Checker Framework's `NullnessChecker`. Elsewhere every reference admits null and no checker warns on the dereference that throws a `NullPointerException`.

Appendix B — Reproduction & audit trail

Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=0 --max-count=200" --report-format json --report-path /tmp/watchdog-gitleaks-daee6cf5420a4a8bb30ce0362e446877/history.json --exit-code 0 --source .9artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=200 --max-count=462" --report-format json --report-path /tmp/watchdog-gitleaks-daee6cf5420a4a8bb30ce0362e446877/history-1.json --exit-code 0 --source .18artifacts/raw/gitleaks-history-1.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-daee6cf5420a4a8bb30ce0362e446877/tree.json --exit-code 0 --source .5artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)semgrep—semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt .19artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiesosv-scanner—osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm .22artifacts/raw/osv-scanner.json
D31 · IaC & Container Securitytrivy—trivy config --format json --quiet .4artifacts/raw/trivy-config.json
D32 · Data Compliance (PII/GDPR)semgrep—semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.0—
D36 · Supply-chain Provenance & Signingprovenance—provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.0—
D37 · Vulnerability-disclosure Policydisclosure—disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.0—
D40 · Network Egress Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.0—
D41 · Kernel & Syscall Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.0—
D42 · Runtime Threat Enforcementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.0—
D43 · Malicious Dependenciesosv-scanner—osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm .0artifacts/raw/osv-scanner.json

Run 01a1e60f-e753-7dcc-8391-6f7cea159c1b · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Downloadable artifacts

Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.

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