Executive summary
databricks/dicer falls short of our standard for production because we found no automated security scanning of the code, its secrets or its dependencies. It scores 58 out of 100 and is rated Adequate, and its one critical finding is a security problem in its servers and containers.
Production Readiness, at 54, is the weakest lens, level with Code Health, and counts most in the score. The best first steps are serving traffic only over an encrypted connection and declaring which values may be missing, each worth about 3 points.
One setting leaves the servers or containers unsafe. Correcting the unsafe settings would close this risk.
The product code is 57,439 lines, about €140,000 to rebuild.
The weakest lenses score close to each other, so improving any of them moves the score.
New since the last survey: 6 findings
- Cyclomatic Complexity · SubscriberHandler.replyFromCell (cyclomatic 17) dicer/common/src/SubscriberHandler.scala
- Churn × Complexity Hotspots · Hotspot: dicer/common/src/SubscriberHandler.scala dicer/common/src/SubscriberHandler.scala
- Explicit Debt · TodoComment dicer/client/test/ClerkRetrySuiteBase.scala
- Explicit Debt · TodoComment dicer/client/test/ClerkRetrySuiteBase.scala
- Explicit Debt · HackComment caching/util/test/WatchCellSuite.scala
- Dependency Vulnerabilities · REDACTED
Fixed since the last survey: 3 findings
- Coupling · Unstable project //dicer/assigner:assigner_probe_source
- Coupling · Unstable project //dicer/assigner:dicer_tee_event
- Explicit Debt · TodoComment dicer/assigner/src/LoadWatcher.scala
Rebuild cost: about €140,000 · Estimate
| Cost to rebuild | €47,000 to €240,000, for 783 to 2,483 hours of work, about 1.0 person-years for 1 to 2 engineers |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 58. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 57,439 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 caching.util.EtcdWatcher.EtcdWatcherStateMachine | 2 caching.util.SafeCounter | 3 dicer.assigner.Store | 4 rpc | 5 caching.util.SequentialExecutionContext | 6 conf | 7 dicer.assigner.TargetMetrics.AssignmentDistributionSource | 8 dicer.common.SliceletData | 9 caching.util.WatchCell | 10 conf.trusted | 11 dicer.friend | 12 caching.util | 13 dicer.assigner.algorithm.MutableAssignment | 14 caching.util.EtcdClient | 15 caching.util.StateMachineOutput | 16 dicer.common.SubscriberHandler | 17 com.databricks | 18 rpc.tls | 19 dicer.common | 20 dicer.assigner.EtcdPreferredAssignerStore | 21 dicer.assigner.conf | 22 dicer.assigner.config.InternalTargetConfig | 23 dicer.client.SliceletLoadAccumulator | 24 dicer.common.testing.SliceTestUtils | 25 dicer.assigner.config | 26 dicer.client | 27 dicer.assigner.TargetMigratorStateMachine | 28 dicer.assigner.algorithm.Algorithm | 29 dicer.assigner.algorithm | 30 dicer.common.testing | 31 dicer.external | 32 dicer.assigner.HealthWatcher | 33 dicer.assigner.TargetMetrics | 34 dicer.assigner.Assigner | 35 dicer.assigner.AssignmentGenerator | 36 dicer.assigner.KubernetesMembershipChecker | 37 dicer.assigner | 38 dicer.assigner.EtcdPreferredAssignerStateMachine.RunState | 39 dicer.assigner.testing | 40 dicer.common.testing.TestAssigner |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 caching.util.EtcdWatcher.EtcdWatcherStateMachine | ||||||||||||||||||||||||||||||||||||||||
| 2 caching.util.SafeCounter | ||||||||||||||||||||||||||||||||||||||||
| 3 dicer.assigner.Store | ||||||||||||||||||||||||||||||||||||||||
| 4 rpc | ||||||||||||||||||||||||||||||||||||||||
| 5 caching.util.SequentialExecutionContext | 1 | 7 | ||||||||||||||||||||||||||||||||||||||
| 6 conf | 2 | 3 | ||||||||||||||||||||||||||||||||||||||
| 7 dicer.assigner.TargetMetrics.AssignmentDistributionSource | 3 | |||||||||||||||||||||||||||||||||||||||
| 8 dicer.common.SliceletData | 2 | |||||||||||||||||||||||||||||||||||||||
| 9 caching.util.WatchCell | 3 | 2 | ||||||||||||||||||||||||||||||||||||||
| 10 conf.trusted | 4 | 1 | ||||||||||||||||||||||||||||||||||||||
| 11 dicer.friend | 1 | 11 | ||||||||||||||||||||||||||||||||||||||
| 12 caching.util | 1 | 1 | 1 | 1 | 5 | 1 | 16 | 1 | ||||||||||||||||||||||||||||||||
| 13 dicer.assigner.algorithm.MutableAssignment | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 14 caching.util.EtcdClient | 2 | |||||||||||||||||||||||||||||||||||||||
| 15 caching.util.StateMachineOutput | 2 | |||||||||||||||||||||||||||||||||||||||
| 16 dicer.common.SubscriberHandler | 2 | 1 | 1 | 4 | 1 | |||||||||||||||||||||||||||||||||||
| 17 com.databricks | 2 | |||||||||||||||||||||||||||||||||||||||
| 18 rpc.tls | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 19 dicer.common | 2 | 2 | 2 | 1 | 1 | 15 | 13 | 2 | 7 | 1 | 1 | 28 | ||||||||||||||||||||||||||||
| 20 dicer.assigner.EtcdPreferredAssignerStore | 1 | 1 | 2 | 3 | ||||||||||||||||||||||||||||||||||||
| 21 dicer.assigner.conf | 5 | 2 | 2 | 1 | 3 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 22 dicer.assigner.config.InternalTargetConfig | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 23 dicer.client.SliceletLoadAccumulator | 1 | 1 | 2 | 1 | 2 | 4 | ||||||||||||||||||||||||||||||||||
| 24 dicer.common.testing.SliceTestUtils | 3 | 1 | 9 | 3 | ||||||||||||||||||||||||||||||||||||
| 25 dicer.assigner.config | 1 | 12 | 7 | 1 | 11 | 2 | ||||||||||||||||||||||||||||||||||
| 26 dicer.client | 3 | 2 | 1 | 1 | 9 | 12 | 1 | 1 | 1 | 31 | 1 | 20 | ||||||||||||||||||||||||||||
| 27 dicer.assigner.TargetMigratorStateMachine | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 28 dicer.assigner.algorithm.Algorithm | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 29 dicer.assigner.algorithm | 7 | 2 | 6 | 7 | 3 | 1 | 2 | 4 | ||||||||||||||||||||||||||||||||
| 30 dicer.common.testing | 1 | 2 | 4 | 5 | 7 | 1 | 4 | 26 | 1 | 2 | 2 | 2 | 15 | 1 | 3 | |||||||||||||||||||||||||
| 31 dicer.external | 1 | 2 | 2 | 1 | 1 | 3 | 3 | 1 | ||||||||||||||||||||||||||||||||
| 32 dicer.assigner.HealthWatcher | 1 | 3 | 2 | 2 | 2 | |||||||||||||||||||||||||||||||||||
| 33 dicer.assigner.TargetMetrics | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 34 dicer.assigner.Assigner | 1 | 1 | 4 | 1 | 1 | 1 | 6 | |||||||||||||||||||||||||||||||||
| 35 dicer.assigner.AssignmentGenerator | 1 | 1 | 1 | 2 | 1 | 1 | 3 | 1 | ||||||||||||||||||||||||||||||||
| 36 dicer.assigner.KubernetesMembershipChecker | 1 | 1 | 1 | 3 | ||||||||||||||||||||||||||||||||||||
| 37 dicer.assigner | 24 | 1 | 3 | 2 | 1 | 3 | 2 | 1 | 60 | 4 | 6 | 1 | 32 | 6 | 3 | 14 | 1 | 1 | 3 | 16 | 2 | 10 | 1 | 8 | 6 | |||||||||||||||
| 38 dicer.assigner.EtcdPreferredAssignerStateMachine.RunState | 4 | 1 | 4 | 1 | ||||||||||||||||||||||||||||||||||||
| 39 dicer.assigner.testing | 1 | 1 | 2 | 1 | 3 | 2 | 1 | 2 | 4 | |||||||||||||||||||||||||||||||
| 40 dicer.common.testing.TestAssigner | 1 | 1 | 1 | 1 | 1 | 3 | 1 | 2 |
5→2 caching.util.SequentialExecutionContext uses caching.util.SafeCounter✕
- Connections
- 1 pair of types, where a type in caching.util.SequentialExecutionContext uses a type in caching.util.SafeCounter.
- The types involved
com.databricks.caching.util.SequentialExecutionContext.Impl→com.databricks.caching.util.SafeCounter.Child
- Direction
- caching.util.SequentialExecutionContext uses caching.util.SafeCounter, so a change to caching.util.SafeCounter can break caching.util.SequentialExecutionContext, while a change to caching.util.SequentialExecutionContext can't break caching.util.SafeCounter.
- Position
- Below the diagonal: caching.util.SequentialExecutionContext uses a module listed above it, which is the healthy direction.
5→12 caching.util.SequentialExecutionContext uses caching.util part of a loop✕
- Connections
- 7 pairs of types, where a type in caching.util.SequentialExecutionContext uses a type in caching.util.
- The types involved
com.databricks.caching.util.SequentialExecutionContext.Command→com.databricks.caching.util.IntrusiveMinHeapElementcom.databricks.caching.util.SequentialExecutionContext.Command→com.databricks.caching.util.TickerTimecom.databricks.caching.util.SequentialExecutionContext.CommandQueue→com.databricks.caching.util.TickerTimecom.databricks.caching.util.SequentialExecutionContext.Impl→com.databricks.caching.util.Cancellablecom.databricks.caching.util.SequentialExecutionContext.Impl→com.databricks.caching.util.SequentialExecutionContextcom.databricks.caching.util.SequentialExecutionContext.Impl→com.databricks.caching.util.TickerTimecom.databricks.caching.util.SequentialExecutionContext.Impl→com.databricks.caching.util.TypedClock
- Direction
- caching.util.SequentialExecutionContext uses caching.util, so a change to caching.util can break caching.util.SequentialExecutionContext, while a change to caching.util.SequentialExecutionContext can't break caching.util.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→4 conf uses rpc✕
- Connections
- 2 pairs of types, where a type in conf uses a type in rpc.
- The types involved
com.databricks.conf.ConfigParser→com.databricks.rpc.DatabricksObjectMappercom.databricks.conf.DefaultParser→com.databricks.rpc.DatabricksObjectMapper
- Direction
- conf uses rpc, so a change to rpc can break conf, while a change to conf can't break rpc.
- Position
- Below the diagonal: conf uses a module listed above it, which is the healthy direction.
6→14 conf uses caching.util.EtcdClient part of a loop✕
- Connections
- 3 pairs of types, where a type in conf uses a type in caching.util.EtcdClient.
- The types involved
com.databricks.conf.Configs→com.databricks.caching.util.EtcdClient.Configcom.databricks.conf.RawConfigSingleton→com.databricks.caching.util.EtcdClient.Configcom.databricks.conf.RichConfig→com.databricks.caching.util.EtcdClient.Config
- Direction
- conf uses caching.util.EtcdClient, so a change to caching.util.EtcdClient can break conf, while a change to conf can't break caching.util.EtcdClient.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→33 dicer.assigner.TargetMetrics.AssignmentDistributionSource uses dicer.assigner.TargetMetrics part of a loop✕
- Connections
- 3 pairs of types, where a type in dicer.assigner.TargetMetrics.AssignmentDistributionSource uses a type in dicer.assigner.TargetMetrics.
- The types involved
com.databricks.dicer.assigner.TargetMetrics.AssignmentDistributionSource.Clerk→com.databricks.dicer.assigner.TargetMetrics.AssignmentDistributionSourcecom.databricks.dicer.assigner.TargetMetrics.AssignmentDistributionSource.Slicelet→com.databricks.dicer.assigner.TargetMetrics.AssignmentDistributionSourcecom.databricks.dicer.assigner.TargetMetrics.AssignmentDistributionSource.Store→com.databricks.dicer.assigner.TargetMetrics.AssignmentDistributionSource
- Direction
- dicer.assigner.TargetMetrics.AssignmentDistributionSource uses dicer.assigner.TargetMetrics, so a change to dicer.assigner.TargetMetrics can break dicer.assigner.TargetMetrics.AssignmentDistributionSource, while a change to dicer.assigner.TargetMetrics.AssignmentDistributionSource can't break dicer.assigner.TargetMetrics.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→31 dicer.common.SliceletData uses dicer.external part of a loop✕
- Connections
- 2 pairs of types, where a type in dicer.common.SliceletData uses a type in dicer.external.
- The types involved
com.databricks.dicer.common.SliceletData.KeyLoad→com.databricks.dicer.external.SliceKeycom.databricks.dicer.common.SliceletData.SliceLoad→com.databricks.dicer.external.Slice
- Direction
- dicer.common.SliceletData uses dicer.external, so a change to dicer.external can break dicer.common.SliceletData, while a change to dicer.common.SliceletData can't break dicer.external.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→5 caching.util.WatchCell uses caching.util.SequentialExecutionContext✕
- Connections
- 3 pairs of types, where a type in caching.util.WatchCell uses a type in caching.util.SequentialExecutionContext.
- The types involved
com.databricks.caching.util.WatchCell.Active→com.databricks.caching.util.SequentialExecutionContext.Statecom.databricks.caching.util.WatchCell.Initial→com.databricks.caching.util.SequentialExecutionContext.Statecom.databricks.caching.util.WatchCell.Terminal→com.databricks.caching.util.SequentialExecutionContext.State
- Direction
- caching.util.WatchCell uses caching.util.SequentialExecutionContext, so a change to caching.util.SequentialExecutionContext can break caching.util.WatchCell, while a change to caching.util.WatchCell can't break caching.util.SequentialExecutionContext.
- Position
- Below the diagonal: caching.util.WatchCell uses a module listed above it, which is the healthy direction.
9→12 caching.util.WatchCell uses caching.util part of a loop✕
- Connections
- 2 pairs of types, where a type in caching.util.WatchCell uses a type in caching.util.
- The types involved
com.databricks.caching.util.WatchCell.Consumer→com.databricks.caching.util.Cancellablecom.databricks.caching.util.WatchCell.Consumer→com.databricks.caching.util.StreamCallback
- Direction
- caching.util.WatchCell uses caching.util, so a change to caching.util can break caching.util.WatchCell, while a change to caching.util.WatchCell can't break caching.util.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→6 conf.trusted uses conf✕
- Connections
- 4 pairs of types, where a type in conf.trusted uses a type in conf.
- The types involved
com.databricks.conf.trusted.DatabricksServerConf→com.databricks.conf.DbConfcom.databricks.conf.trusted.LocationConf→com.databricks.conf.DbConfcom.databricks.conf.trusted.ProjectConf→com.databricks.conf.DbConfImplcom.databricks.conf.trusted.RPCPortConf→com.databricks.conf.DbConf
- Direction
- conf.trusted uses conf, so a change to conf can break conf.trusted, while a change to conf.trusted can't break conf.
- Position
- Below the diagonal: conf.trusted uses a module listed above it, which is the healthy direction.
10→14 conf.trusted uses caching.util.EtcdClient part of a loop✕
- Connections
- 1 pair of types, where a type in conf.trusted uses a type in caching.util.EtcdClient.
- The types involved
com.databricks.conf.trusted.ProjectConf→com.databricks.caching.util.EtcdClient.Config
- Direction
- conf.trusted uses caching.util.EtcdClient, so a change to caching.util.EtcdClient can break conf.trusted, while a change to conf.trusted can't break caching.util.EtcdClient.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→7 dicer.friend uses dicer.assigner.TargetMetrics.AssignmentDistributionSource✕
- Connections
- 1 pair of types, where a type in dicer.friend uses a type in dicer.assigner.TargetMetrics.AssignmentDistributionSource.
- The types involved
com.databricks.dicer.friend.SliceletAccessor→com.databricks.dicer.assigner.TargetMetrics.AssignmentDistributionSource.Slicelet
- Direction
- dicer.friend uses dicer.assigner.TargetMetrics.AssignmentDistributionSource, so a change to dicer.assigner.TargetMetrics.AssignmentDistributionSource can break dicer.friend, while a change to dicer.friend can't break dicer.assigner.TargetMetrics.AssignmentDistributionSource.
- Position
- Below the diagonal: dicer.friend uses a module listed above it, which is the healthy direction.
11→31 dicer.friend uses dicer.external part of a loop✕
- Connections
- 11 pairs of types, where a type in dicer.friend uses a type in dicer.external.
- The types involved
com.databricks.dicer.friend.MutableSliceMap→com.databricks.dicer.external.Slicecom.databricks.dicer.friend.MutableSliceMap→com.databricks.dicer.external.SliceKeycom.databricks.dicer.friend.ResourceAddressAccessor→com.databricks.dicer.external.ResourceAddresscom.databricks.dicer.friend.SliceAccessor→com.databricks.dicer.external.Slicecom.databricks.dicer.friend.SliceAccessor→com.databricks.dicer.external.SliceKeycom.databricks.dicer.friend.SliceMap→com.databricks.dicer.external.SliceKeycom.databricks.dicer.friend.SliceWithStateProvider→com.databricks.dicer.external.ResourceAddresscom.databricks.dicer.friend.SliceWithStateProvider→com.databricks.dicer.external.Slicecom.databricks.dicer.friend.SliceletAccessor→com.databricks.dicer.external.ResourceAddresscom.databricks.dicer.friend.SliceletAccessor→com.databricks.dicer.external.Targetcom.databricks.dicer.friend.Squid→com.databricks.dicer.external.ResourceAddress
- Direction
- dicer.friend uses dicer.external, so a change to dicer.external can break dicer.friend, while a change to dicer.friend can't break dicer.external.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→1 caching.util uses caching.util.EtcdWatcher.EtcdWatcherStateMachine✕
- Connections
- 1 pair of types, where a type in caching.util uses a type in caching.util.EtcdWatcher.EtcdWatcherStateMachine.
- The types involved
com.databricks.caching.util.EtcdWatcher→com.databricks.caching.util.EtcdWatcher.EtcdWatcherStateMachine.DriverAction
- Direction
- caching.util uses caching.util.EtcdWatcher.EtcdWatcherStateMachine, so a change to caching.util.EtcdWatcher.EtcdWatcherStateMachine can break caching.util, while a change to caching.util can't break caching.util.EtcdWatcher.EtcdWatcherStateMachine.
- Position
- Below the diagonal: caching.util uses a module listed above it, which is the healthy direction.
12→2 caching.util uses caching.util.SafeCounter✕
- Connections
- 1 pair of types, where a type in caching.util uses a type in caching.util.SafeCounter.
- The types involved
com.databricks.caching.util.SafeCounter→com.databricks.caching.util.SafeCounter.Child
- Direction
- caching.util uses caching.util.SafeCounter, so a change to caching.util.SafeCounter can break caching.util, while a change to caching.util can't break caching.util.SafeCounter.
- Position
- Below the diagonal: caching.util uses a module listed above it, which is the healthy direction.
12→4 caching.util uses rpc✕
- Connections
- 1 pair of types, where a type in caching.util uses a type in rpc.
- The types involved
com.databricks.caching.util.ServerConf→com.databricks.rpc.SslArguments
- Direction
- caching.util uses rpc, so a change to rpc can break caching.util, while a change to caching.util can't break rpc.
- Position
- Below the diagonal: caching.util uses a module listed above it, which is the healthy direction.
12→5 caching.util uses caching.util.SequentialExecutionContext✕
- Connections
- 1 pair of types, where a type in caching.util uses a type in caching.util.SequentialExecutionContext.
- The types involved
com.databricks.caching.util.WatchCell→com.databricks.caching.util.SequentialExecutionContext.State
- Direction
- caching.util uses caching.util.SequentialExecutionContext, so a change to caching.util.SequentialExecutionContext can break caching.util, while a change to caching.util can't break caching.util.SequentialExecutionContext.
- Position
- Below the diagonal: caching.util uses a module listed above it, which is the healthy direction.
12→9 caching.util uses caching.util.WatchCell✕
- Connections
- 5 pairs of types, where a type in caching.util uses a type in caching.util.WatchCell.
- The types involved
com.databricks.caching.util.WatchCell→com.databricks.caching.util.WatchCell.Consumercom.databricks.caching.util.WatchCell→com.databricks.caching.util.WatchCell.Producercom.databricks.caching.util.WatchValueCell→com.databricks.caching.util.WatchCell.Consumercom.databricks.caching.util.WatchValueCell→com.databricks.caching.util.WatchCell.Producercom.databricks.caching.util.WatchValueCellPollAdapter→com.databricks.caching.util.WatchCell.Consumer
- Direction
- caching.util uses caching.util.WatchCell, so a change to caching.util.WatchCell can break caching.util, while a change to caching.util can't break caching.util.WatchCell.
- Position
- Below the diagonal: caching.util uses a module listed above it, which is the healthy direction.
12→10 caching.util uses conf.trusted✕
- Connections
- 1 pair of types, where a type in caching.util uses a type in conf.trusted.
- The types involved
com.databricks.caching.util.ServerConf→com.databricks.conf.trusted.RPCPortConf
- Direction
- caching.util uses conf.trusted, so a change to conf.trusted can break caching.util, while a change to caching.util can't break conf.trusted.
- Position
- Below the diagonal: caching.util uses a module listed above it, which is the healthy direction.
12→14 caching.util uses caching.util.EtcdClient part of a loop✕
- Connections
- 16 pairs of types, where a type in caching.util uses a type in caching.util.EtcdClient.
- The types involved
com.databricks.caching.util.EtcdClient→com.databricks.caching.util.EtcdClient.Configcom.databricks.caching.util.EtcdClient→com.databricks.caching.util.EtcdClient.GlobalLogEntrycom.databricks.caching.util.EtcdClient→com.databricks.caching.util.EtcdClient.ReadResponsecom.databricks.caching.util.EtcdClient→com.databricks.caching.util.EtcdClient.ReadResumeTokencom.databricks.caching.util.EtcdClient→com.databricks.caching.util.EtcdClient.Versioncom.databricks.caching.util.EtcdClient→com.databricks.caching.util.EtcdClient.VersionedValuecom.databricks.caching.util.EtcdClient→com.databricks.caching.util.EtcdClient.WatchArgscom.databricks.caching.util.EtcdClient→com.databricks.caching.util.EtcdClient.WatchEventcom.databricks.caching.util.EtcdClient→com.databricks.caching.util.EtcdClient.WriteResponsecom.databricks.caching.util.EtcdKeyValueMapper→com.databricks.caching.util.EtcdClient.KeyNamespacecom.databricks.caching.util.EtcdKeyValueMapper→com.databricks.caching.util.EtcdClient.ScopedKeycom.databricks.caching.util.EtcdKeyValueMapper→com.databricks.caching.util.EtcdClient.Versioncom.databricks.caching.util.EtcdWatcher→com.databricks.caching.util.EtcdClient.Versioncom.databricks.caching.util.EtcdWatcher→com.databricks.caching.util.EtcdClient.WatchEventcom.databricks.caching.util.LossyEwmaCounter→com.databricks.caching.util.EtcdClient.Configcom.databricks.caching.util.SafeConfigProvider→com.databricks.caching.util.EtcdClient.Config
- Direction
- caching.util uses caching.util.EtcdClient, so a change to caching.util.EtcdClient can break caching.util, while a change to caching.util can't break caching.util.EtcdClient.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→17 caching.util uses com.databricks part of a loop✕
- Connections
- 1 pair of types, where a type in caching.util uses a type in com.databricks.
- The types involved
com.databricks.caching.util.CachingLatencyHistogram→com.databricks.ErrorCode
- Direction
- caching.util uses com.databricks, so a change to com.databricks can break caching.util, while a change to caching.util can't break com.databricks.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→11 dicer.assigner.algorithm.MutableAssignment uses dicer.friend✕
- Connections
- 2 pairs of types, where a type in dicer.assigner.algorithm.MutableAssignment uses a type in dicer.friend.
- The types involved
com.databricks.dicer.assigner.algorithm.MutableAssignment.MutableSliceAssignment→com.databricks.dicer.friend.Squidcom.databricks.dicer.assigner.algorithm.MutableAssignment.ResourceState→com.databricks.dicer.friend.Squid
- Direction
- dicer.assigner.algorithm.MutableAssignment uses dicer.friend, so a change to dicer.friend can break dicer.assigner.algorithm.MutableAssignment, while a change to dicer.assigner.algorithm.MutableAssignment can't break dicer.friend.
- Position
- Below the diagonal: dicer.assigner.algorithm.MutableAssignment uses a module listed above it, which is the healthy direction.
13→31 dicer.assigner.algorithm.MutableAssignment uses dicer.external part of a loop✕
- Connections
- 1 pair of types, where a type in dicer.assigner.algorithm.MutableAssignment uses a type in dicer.external.
- The types involved
com.databricks.dicer.assigner.algorithm.MutableAssignment.MutableSliceAssignment→com.databricks.dicer.external.Slice
- Direction
- dicer.assigner.algorithm.MutableAssignment uses dicer.external, so a change to dicer.external can break dicer.assigner.algorithm.MutableAssignment, while a change to dicer.assigner.algorithm.MutableAssignment can't break dicer.external.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→12 caching.util.EtcdClient uses caching.util✕
- Connections
- 2 pairs of types, where a type in caching.util.EtcdClient uses a type in caching.util.
- The types involved
com.databricks.caching.util.EtcdClient.Version→com.databricks.caching.util.UnixTimeVersioncom.databricks.caching.util.EtcdClient.forTest→com.databricks.caching.util.EtcdClient
- Direction
- caching.util.EtcdClient uses caching.util, so a change to caching.util can break caching.util.EtcdClient, while a change to caching.util.EtcdClient can't break caching.util.
- Position
- Below the diagonal: caching.util.EtcdClient uses a module listed above it, which is the healthy direction.
15→12 caching.util.StateMachineOutput uses caching.util✕
- Connections
- 2 pairs of types, where a type in caching.util.StateMachineOutput uses a type in caching.util.
- The types involved
com.databricks.caching.util.StateMachineOutput.Builder→com.databricks.caching.util.StateMachineOutputcom.databricks.caching.util.StateMachineOutput.Builder→com.databricks.caching.util.TickerTime
- Direction
- caching.util.StateMachineOutput uses caching.util, so a change to caching.util can break caching.util.StateMachineOutput, while a change to caching.util.StateMachineOutput can't break caching.util.
- Position
- Below the diagonal: caching.util.StateMachineOutput uses a module listed above it, which is the healthy direction.
16→2 dicer.common.SubscriberHandler uses caching.util.SafeCounter✕
- Connections
- 2 pairs of types, where a type in dicer.common.SubscriberHandler uses a type in caching.util.SafeCounter.
- The types involved
com.databricks.dicer.common.SubscriberHandler.AssignmentDistributionLatencyTracker→com.databricks.caching.util.SafeCounter.Childcom.databricks.dicer.common.SubscriberHandler.forTestStatic→com.databricks.caching.util.SafeCounter.Child
- Direction
- dicer.common.SubscriberHandler uses caching.util.SafeCounter, so a change to caching.util.SafeCounter can break dicer.common.SubscriberHandler, while a change to dicer.common.SubscriberHandler can't break caching.util.SafeCounter.
- Position
- Below the diagonal: dicer.common.SubscriberHandler uses a module listed above it, which is the healthy direction.
16→11 dicer.common.SubscriberHandler uses dicer.friend✕
- Connections
- 1 pair of types, where a type in dicer.common.SubscriberHandler uses a type in dicer.friend.
- The types involved
com.databricks.dicer.common.SubscriberHandler.AssignmentDistributionLatencyTracker→com.databricks.dicer.friend.Squid
- Direction
- dicer.common.SubscriberHandler uses dicer.friend, so a change to dicer.friend can break dicer.common.SubscriberHandler, while a change to dicer.common.SubscriberHandler can't break dicer.friend.
- Position
- Below the diagonal: dicer.common.SubscriberHandler uses a module listed above it, which is the healthy direction.
16→12 dicer.common.SubscriberHandler uses caching.util✕
- Connections
- 1 pair of types, where a type in dicer.common.SubscriberHandler uses a type in caching.util.
- The types involved
com.databricks.dicer.common.SubscriberHandler.AssignmentDistributionLatencyTracker→com.databricks.caching.util.TickerTime
- Direction
- dicer.common.SubscriberHandler uses caching.util, so a change to caching.util can break dicer.common.SubscriberHandler, while a change to dicer.common.SubscriberHandler can't break caching.util.
- Position
- Below the diagonal: dicer.common.SubscriberHandler uses a module listed above it, which is the healthy direction.
16→19 dicer.common.SubscriberHandler uses dicer.common part of a loop✕
- Connections
- 4 pairs of types, where a type in dicer.common.SubscriberHandler uses a type in dicer.common.
- The types involved
com.databricks.dicer.common.SubscriberHandler.AssignmentDistributionLatencyTracker→com.databricks.dicer.common.Assignmentcom.databricks.dicer.common.SubscriberHandler.AssignmentDistributionLatencyTracker→com.databricks.dicer.common.Generationcom.databricks.dicer.common.SubscriberHandler.AssignmentRecoveryState→com.databricks.dicer.common.Generationcom.databricks.dicer.common.SubscriberHandler.CachedSyncAssignmentState→com.databricks.dicer.common.Generation
- Direction
- dicer.common.SubscriberHandler uses dicer.common, so a change to dicer.common can break dicer.common.SubscriberHandler, while a change to dicer.common.SubscriberHandler can't break dicer.common.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→31 dicer.common.SubscriberHandler uses dicer.external part of a loop✕
- Connections
- 1 pair of types, where a type in dicer.common.SubscriberHandler uses a type in dicer.external.
- The types involved
com.databricks.dicer.common.SubscriberHandler.forTestStatic→com.databricks.dicer.external.Target
- Direction
- dicer.common.SubscriberHandler uses dicer.external, so a change to dicer.external can break dicer.common.SubscriberHandler, while a change to dicer.common.SubscriberHandler can't break dicer.external.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→14 com.databricks uses caching.util.EtcdClient✕
- Connections
- 2 pairs of types, where a type in com.databricks uses a type in caching.util.EtcdClient.
- The types involved
com.databricks.DatabricksMain→com.databricks.caching.util.EtcdClient.Configcom.databricks.conf→com.databricks.caching.util.EtcdClient.Config
- Direction
- com.databricks uses caching.util.EtcdClient, so a change to caching.util.EtcdClient can break com.databricks, while a change to com.databricks can't break caching.util.EtcdClient.
- Position
- Below the diagonal: com.databricks uses a module listed above it, which is the healthy direction.
18→4 rpc.tls uses rpc✕
- Connections
- 1 pair of types, where a type in rpc.tls uses a type in rpc.
- The types involved
com.databricks.rpc.tls.TLSOptionsMigration→com.databricks.rpc.SslArguments
- Direction
- rpc.tls uses rpc, so a change to rpc can break rpc.tls, while a change to rpc.tls can't break rpc.
- Position
- Below the diagonal: rpc.tls uses a module listed above it, which is the healthy direction.
18→15 rpc.tls uses caching.util.StateMachineOutput✕
- Connections
- 1 pair of types, where a type in rpc.tls uses a type in caching.util.StateMachineOutput.
- The types involved
com.databricks.rpc.tls.TLSOptionsMigration→com.databricks.caching.util.StateMachineOutput.Builder
- Direction
- rpc.tls uses caching.util.StateMachineOutput, so a change to caching.util.StateMachineOutput can break rpc.tls, while a change to rpc.tls can't break caching.util.StateMachineOutput.
- Position
- Below the diagonal: rpc.tls uses a module listed above it, which is the healthy direction.
19→2 dicer.common uses caching.util.SafeCounter✕
- Connections
- 2 pairs of types, where a type in dicer.common uses a type in caching.util.SafeCounter.
- The types involved
com.databricks.dicer.common.SubscriberHandler→com.databricks.caching.util.SafeCounter.Childcom.databricks.dicer.common.SubscriberHandlerMetrics→com.databricks.caching.util.SafeCounter.Child
- Direction
- dicer.common uses caching.util.SafeCounter, so a change to caching.util.SafeCounter can break dicer.common, while a change to dicer.common can't break caching.util.SafeCounter.
- Position
- Below the diagonal: dicer.common uses a module listed above it, which is the healthy direction.
19→4 dicer.common uses rpc✕
- Connections
- 2 pairs of types, where a type in dicer.common uses a type in rpc.
- The types involved
com.databricks.dicer.common.SubscriberHandler→com.databricks.rpc.RPCContextcom.databricks.dicer.common.WatchServerHelper→com.databricks.rpc.DatabricksServerWrapper
- Direction
- dicer.common uses rpc, so a change to rpc can break dicer.common, while a change to dicer.common can't break rpc.
- Position
- Below the diagonal: dicer.common uses a module listed above it, which is the healthy direction.
19→6 dicer.common uses conf✕
- Connections
- 2 pairs of types, where a type in dicer.common uses a type in conf.
- The types involved
com.databricks.dicer.common.CommonSslConf→com.databricks.conf.DbConfcom.databricks.dicer.common.InternalClientConf→com.databricks.conf.DbConf
- Direction
- dicer.common uses conf, so a change to conf can break dicer.common, while a change to dicer.common can't break conf.
- Position
- Below the diagonal: dicer.common uses a module listed above it, which is the healthy direction.
19→8 dicer.common uses dicer.common.SliceletData✕
- Connections
- 1 pair of types, where a type in dicer.common uses a type in dicer.common.SliceletData.
- The types involved
com.databricks.dicer.common.SliceletData→com.databricks.dicer.common.SliceletData.SliceLoad
- Direction
- dicer.common uses dicer.common.SliceletData, so a change to dicer.common.SliceletData can break dicer.common, while a change to dicer.common can't break dicer.common.SliceletData.
- Position
- Below the diagonal: dicer.common uses a module listed above it, which is the healthy direction.
19→10 dicer.common uses conf.trusted✕
- Connections
- 1 pair of types, where a type in dicer.common uses a type in conf.trusted.
- The types involved
com.databricks.dicer.common.WatchServerConf→com.databricks.conf.trusted.DatabricksServerConf
- Direction
- dicer.common uses conf.trusted, so a change to conf.trusted can break dicer.common, while a change to dicer.common can't break conf.trusted.
- Position
- Below the diagonal: dicer.common uses a module listed above it, which is the healthy direction.
19→11 dicer.common uses dicer.friend✕
- Connections
- 15 pairs of types, where a type in dicer.common uses a type in dicer.friend.
- The types involved
com.databricks.dicer.common.Assignment→com.databricks.dicer.friend.SliceMapcom.databricks.dicer.common.Assignment→com.databricks.dicer.friend.Squidcom.databricks.dicer.common.AssignmentFormatter→com.databricks.dicer.friend.Squidcom.databricks.dicer.common.CommonSlicez→com.databricks.dicer.friend.Squidcom.databricks.dicer.common.DPageViewHelpers→com.databricks.dicer.friend.Squidcom.databricks.dicer.common.DiffAssignment→com.databricks.dicer.friend.Squidcom.databricks.dicer.common.ProposedAssignment→com.databricks.dicer.friend.SliceMapcom.databricks.dicer.common.ProposedSliceAssignment→com.databricks.dicer.friend.Squidcom.databricks.dicer.common.SliceAssignment→com.databricks.dicer.friend.Squidcom.databricks.dicer.common.SliceMapHelper→com.databricks.dicer.friend.SliceMapcom.databricks.dicer.common.SliceWithResources→com.databricks.dicer.friend.Squidcom.databricks.dicer.common.SliceletData→com.databricks.dicer.friend.Squidcom.databricks.dicer.common.SubsliceAnnotation→com.databricks.dicer.friend.Squidcom.databricks.dicer.common.SubsliceAnnotationsMap→com.databricks.dicer.friend.SliceMapcom.databricks.dicer.common.Transfer→com.databricks.dicer.friend.Squid
- Direction
- dicer.common uses dicer.friend, so a change to dicer.friend can break dicer.common, while a change to dicer.common can't break dicer.friend.
- Position
- Below the diagonal: dicer.common uses a module listed above it, which is the healthy direction.
19→12 dicer.common uses caching.util✕
- Connections
- 13 pairs of types, where a type in dicer.common uses a type in caching.util.
- The types involved
com.databricks.dicer.common.AssignmentFormatter→com.databricks.caching.util.AsciiTablecom.databricks.dicer.common.AssignmentFormatter→com.databricks.caching.util.UnixTimeVersioncom.databricks.dicer.common.ClientRequest→com.databricks.caching.util.KubernetesClusterUricom.databricks.dicer.common.ClientRequest→com.databricks.caching.util.RegionUricom.databricks.dicer.common.EtcdBootstrapper→com.databricks.caching.util.Pipelinecom.databricks.dicer.common.Generation→com.databricks.caching.util.UnixTimeVersioncom.databricks.dicer.common.SliceletData→com.databricks.caching.util.HyperLogLogcom.databricks.dicer.common.SubscriberHandler→com.databricks.caching.util.Cancellablecom.databricks.dicer.common.SubscriberHandler→com.databricks.caching.util.TickerTimecom.databricks.dicer.common.SubscriberHandlerMetrics→com.databricks.caching.util.KubernetesClusterUricom.databricks.dicer.common.SubsliceAnnotation→com.databricks.caching.util.UnixTimeVersioncom.databricks.dicer.common.SubsliceAnnotationsMap→com.databricks.caching.util.UnixTimeVersioncom.databricks.dicer.common.WatchServerHelper→com.databricks.caching.util.GenericRpcServiceBuilder
- Direction
- dicer.common uses caching.util, so a change to caching.util can break dicer.common, while a change to dicer.common can't break caching.util.
- Position
- Below the diagonal: dicer.common uses a module listed above it, which is the healthy direction.
19→14 dicer.common uses caching.util.EtcdClient✕
- Connections
- 2 pairs of types, where a type in dicer.common uses a type in caching.util.EtcdClient.
- The types involved
com.databricks.dicer.common.EtcdBootstrapper→com.databricks.caching.util.EtcdClient.KeyNamespacecom.databricks.dicer.common.EtcdBootstrapper→com.databricks.caching.util.EtcdClient.Version
- Direction
- dicer.common uses caching.util.EtcdClient, so a change to caching.util.EtcdClient can break dicer.common, while a change to dicer.common can't break caching.util.EtcdClient.
- Position
- Below the diagonal: dicer.common uses a module listed above it, which is the healthy direction.
19→16 dicer.common uses dicer.common.SubscriberHandler✕
- Connections
- 7 pairs of types, where a type in dicer.common uses a type in dicer.common.SubscriberHandler.
- The types involved
com.databricks.dicer.common.SubscriberHandler→com.databricks.dicer.common.SubscriberHandler.AssignmentDistributionLatencyTrackercom.databricks.dicer.common.SubscriberHandler→com.databricks.dicer.common.SubscriberHandler.AssignmentRecoveryStatecom.databricks.dicer.common.SubscriberHandler→com.databricks.dicer.common.SubscriberHandler.CachedSyncAssignmentStatecom.databricks.dicer.common.SubscriberHandler→com.databricks.dicer.common.SubscriberHandler.MetricsKeycom.databricks.dicer.common.SubscriberHandler→com.databricks.dicer.common.SubscriberHandler.SubscriberInfocom.databricks.dicer.common.SubscriberHandlerMetrics→com.databricks.dicer.common.SubscriberHandler.Locationcom.databricks.dicer.common.SubscriberHandlerMetrics→com.databricks.dicer.common.SubscriberHandler.MetricsKey
- Direction
- dicer.common uses dicer.common.SubscriberHandler, so a change to dicer.common.SubscriberHandler can break dicer.common, while a change to dicer.common can't break dicer.common.SubscriberHandler.
- Position
- Below the diagonal: dicer.common uses a module listed above it, which is the healthy direction.
19→17 dicer.common uses com.databricks✕
- Connections
- 1 pair of types, where a type in dicer.common uses a type in com.databricks.
- The types involved
com.databricks.dicer.common.WatchServerHelper→com.databricks.ErrorCode
- Direction
- dicer.common uses com.databricks, so a change to com.databricks can break dicer.common, while a change to dicer.common can't break com.databricks.
- Position
- Below the diagonal: dicer.common uses a module listed above it, which is the healthy direction.
19→18 dicer.common uses rpc.tls✕
- Connections
- 1 pair of types, where a type in dicer.common uses a type in rpc.tls.
- The types involved
com.databricks.dicer.common.CommonSslConf→com.databricks.rpc.tls.TLSOptions
- Direction
- dicer.common uses rpc.tls, so a change to rpc.tls can break dicer.common, while a change to dicer.common can't break rpc.tls.
- Position
- Below the diagonal: dicer.common uses a module listed above it, which is the healthy direction.
19→31 dicer.common uses dicer.external part of a loop✕
- Connections
- 28 pairs of types, where a type in dicer.common uses a type in dicer.external. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.databricks.dicer.common.Assignment→com.databricks.dicer.external.SliceKeycom.databricks.dicer.common.AssignmentFormatter→com.databricks.dicer.external.HighSliceKeycom.databricks.dicer.common.AssignmentFormatter→com.databricks.dicer.external.Slicecom.databricks.dicer.common.AssignmentFormatter→com.databricks.dicer.external.SliceKeycom.databricks.dicer.common.ClientRequest→com.databricks.dicer.external.AppTargetcom.databricks.dicer.common.ClientRequest→com.databricks.dicer.external.Targetcom.databricks.dicer.common.CommonSlicez→com.databricks.dicer.external.Slicecom.databricks.dicer.common.CommonSlicez→com.databricks.dicer.external.SliceKeycom.databricks.dicer.common.DPageViewHelpers→com.databricks.dicer.external.Slicecom.databricks.dicer.common.DPageViewHelpers→com.databricks.dicer.external.SliceKeycom.databricks.dicer.common.ProposedSliceAssignment→com.databricks.dicer.external.Slicecom.databricks.dicer.common.SliceAssignment→com.databricks.dicer.external.Slicecom.databricks.dicer.common.SliceHelper→com.databricks.dicer.external.Slicecom.databricks.dicer.common.SliceKeyHelper→com.databricks.dicer.external.SliceKeycom.databricks.dicer.common.SliceSetImpl→com.databricks.dicer.external.Slicecom.databricks.dicer.common.SliceSetImpl→com.databricks.dicer.external.SliceKeycom.databricks.dicer.common.SliceSetImplBuilder→com.databricks.dicer.external.Slicecom.databricks.dicer.common.SliceWithResources→com.databricks.dicer.external.Slicecom.databricks.dicer.common.SubscriberHandlerMetrics→com.databricks.dicer.external.AppTargetcom.databricks.dicer.common.SubscriberHandlerMetrics→com.databricks.dicer.external.Targetcom.databricks.dicer.common.SubsliceAnnotation→com.databricks.dicer.external.Slicecom.databricks.dicer.common.SubsliceAnnotationsMap→com.databricks.dicer.external.SliceKeycom.databricks.dicer.common.TargetHelper→com.databricks.dicer.external.Targetcom.databricks.dicer.common.TargetName→com.databricks.dicer.external.Targetcom.databricks.dicer.common.TargetSlicezData→com.databricks.dicer.external.SliceKey
- Direction
- dicer.common uses dicer.external, so a change to dicer.external can break dicer.common, while a change to dicer.common can't break dicer.external.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→1 dicer.assigner.EtcdPreferredAssignerStore uses caching.util.EtcdWatcher.EtcdWatcherStateMachine✕
- Connections
- 1 pair of types, where a type in dicer.assigner.EtcdPreferredAssignerStore uses a type in caching.util.EtcdWatcher.EtcdWatcherStateMachine.
- The types involved
com.databricks.dicer.assigner.EtcdPreferredAssignerStore.Impl→com.databricks.caching.util.EtcdWatcher.EtcdWatcherStateMachine.DriverAction
- Direction
- dicer.assigner.EtcdPreferredAssignerStore uses caching.util.EtcdWatcher.EtcdWatcherStateMachine, so a change to caching.util.EtcdWatcher.EtcdWatcherStateMachine can break dicer.assigner.EtcdPreferredAssignerStore, while a change to dicer.assigner.EtcdPreferredAssignerStore can't break caching.util.EtcdWatcher.EtcdWatcherStateMachine.
- Position
- Below the diagonal: dicer.assigner.EtcdPreferredAssignerStore uses a module listed above it, which is the healthy direction.
20→12 dicer.assigner.EtcdPreferredAssignerStore uses caching.util✕
- Connections
- 1 pair of types, where a type in dicer.assigner.EtcdPreferredAssignerStore uses a type in caching.util.
- The types involved
com.databricks.dicer.assigner.EtcdPreferredAssignerStore.Impl→com.databricks.caching.util.Cancellable
- Direction
- dicer.assigner.EtcdPreferredAssignerStore uses caching.util, so a change to caching.util can break dicer.assigner.EtcdPreferredAssignerStore, while a change to dicer.assigner.EtcdPreferredAssignerStore can't break caching.util.
- Position
- Below the diagonal: dicer.assigner.EtcdPreferredAssignerStore uses a module listed above it, which is the healthy direction.
20→19 dicer.assigner.EtcdPreferredAssignerStore uses dicer.common✕
- Connections
- 2 pairs of types, where a type in dicer.assigner.EtcdPreferredAssignerStore uses a type in dicer.common.
- The types involved
com.databricks.dicer.assigner.EtcdPreferredAssignerStore.Impl→com.databricks.dicer.common.Incarnationcom.databricks.dicer.assigner.EtcdPreferredAssignerStore.PreferredAssignerProposal→com.databricks.dicer.common.Generation
- Direction
- dicer.assigner.EtcdPreferredAssignerStore uses dicer.common, so a change to dicer.common can break dicer.assigner.EtcdPreferredAssignerStore, while a change to dicer.assigner.EtcdPreferredAssignerStore can't break dicer.common.
- Position
- Below the diagonal: dicer.assigner.EtcdPreferredAssignerStore uses a module listed above it, which is the healthy direction.
20→37 dicer.assigner.EtcdPreferredAssignerStore uses dicer.assigner part of a loop✕
- Connections
- 3 pairs of types, where a type in dicer.assigner.EtcdPreferredAssignerStore uses a type in dicer.assigner.
- The types involved
com.databricks.dicer.assigner.EtcdPreferredAssignerStore.Impl→com.databricks.dicer.assigner.EtcdPreferredAssignerStorecom.databricks.dicer.assigner.EtcdPreferredAssignerStore.Impl→com.databricks.dicer.assigner.PreferredAssignerValuecom.databricks.dicer.assigner.EtcdPreferredAssignerStore.PreferredAssignerProposal→com.databricks.dicer.assigner.AssignerInfo
- Direction
- dicer.assigner.EtcdPreferredAssignerStore uses dicer.assigner, so a change to dicer.assigner can break dicer.assigner.EtcdPreferredAssignerStore, while a change to dicer.assigner.EtcdPreferredAssignerStore can't break dicer.assigner.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→6 dicer.assigner.conf uses conf✕
- Connections
- 5 pairs of types, where a type in dicer.assigner.conf uses a type in conf.
- The types involved
com.databricks.dicer.assigner.conf.GeneratorConf→com.databricks.conf.DbConfcom.databricks.dicer.assigner.conf.HealthConf→com.databricks.conf.DbConfcom.databricks.dicer.assigner.conf.LoadWatcherConf→com.databricks.conf.DbConfcom.databricks.dicer.assigner.conf.PreferredAssignerConf→com.databricks.conf.DbConfcom.databricks.dicer.assigner.conf.RemoteMembershipCheckerConf→com.databricks.conf.DbConf
- Direction
- dicer.assigner.conf uses conf, so a change to conf can break dicer.assigner.conf, while a change to dicer.assigner.conf can't break conf.
- Position
- Below the diagonal: dicer.assigner.conf uses a module listed above it, which is the healthy direction.
21→10 dicer.assigner.conf uses conf.trusted✕
- Connections
- 2 pairs of types, where a type in dicer.assigner.conf uses a type in conf.trusted.
- The types involved
com.databricks.dicer.assigner.conf.DicerAssignerConf→com.databricks.conf.trusted.LocationConfcom.databricks.dicer.assigner.conf.DicerAssignerConf→com.databricks.conf.trusted.ProjectConfByName
- Direction
- dicer.assigner.conf uses conf.trusted, so a change to conf.trusted can break dicer.assigner.conf, while a change to dicer.assigner.conf can't break conf.trusted.
- Position
- Below the diagonal: dicer.assigner.conf uses a module listed above it, which is the healthy direction.
21→12 dicer.assigner.conf uses caching.util✕
- Connections
- 2 pairs of types, where a type in dicer.assigner.conf uses a type in caching.util.
- The types involved
com.databricks.dicer.assigner.conf.DicerAssignerConf→com.databricks.caching.util.ClusterConfigScopecom.databricks.dicer.assigner.conf.DicerAssignerConf→com.databricks.caching.util.ServerConf
- Direction
- dicer.assigner.conf uses caching.util, so a change to caching.util can break dicer.assigner.conf, while a change to dicer.assigner.conf can't break caching.util.
- Position
- Below the diagonal: dicer.assigner.conf uses a module listed above it, which is the healthy direction.
21→18 dicer.assigner.conf uses rpc.tls✕
- Connections
- 1 pair of types, where a type in dicer.assigner.conf uses a type in rpc.tls.
- The types involved
com.databricks.dicer.assigner.conf.DicerAssignerConf→com.databricks.rpc.tls.TLSOptions
- Direction
- dicer.assigner.conf uses rpc.tls, so a change to rpc.tls can break dicer.assigner.conf, while a change to dicer.assigner.conf can't break rpc.tls.
- Position
- Below the diagonal: dicer.assigner.conf uses a module listed above it, which is the healthy direction.
21→19 dicer.assigner.conf uses dicer.common✕
- Connections
- 3 pairs of types, where a type in dicer.assigner.conf uses a type in dicer.common.
- The types involved
com.databricks.dicer.assigner.conf.DicerAssignerConf→com.databricks.dicer.common.CommonSslConfcom.databricks.dicer.assigner.conf.DicerAssignerConf→com.databricks.dicer.common.WatchServerConfcom.databricks.dicer.assigner.conf.GeneratorConf→com.databricks.dicer.common.Incarnation
- Direction
- dicer.assigner.conf uses dicer.common, so a change to dicer.common can break dicer.assigner.conf, while a change to dicer.assigner.conf can't break dicer.common.
- Position
- Below the diagonal: dicer.assigner.conf uses a module listed above it, which is the healthy direction.
21→25 dicer.assigner.conf uses dicer.assigner.config part of a loop✕
- Connections
- 1 pair of types, where a type in dicer.assigner.conf uses a type in dicer.assigner.config.
- The types involved
com.databricks.dicer.assigner.conf.DicerAssignerConf→com.databricks.dicer.assigner.config.TargetMigrationConfig
- Direction
- dicer.assigner.conf uses dicer.assigner.config, so a change to dicer.assigner.config can break dicer.assigner.conf, while a change to dicer.assigner.conf can't break dicer.assigner.config.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→37 dicer.assigner.conf uses dicer.assigner part of a loop✕
- Connections
- 1 pair of types, where a type in dicer.assigner.conf uses a type in dicer.assigner.
- The types involved
com.databricks.dicer.assigner.conf.PreferredAssignerConf→com.databricks.dicer.assigner.MigrationMode
- Direction
- dicer.assigner.conf uses dicer.assigner, so a change to dicer.assigner can break dicer.assigner.conf, while a change to dicer.assigner.conf can't break dicer.assigner.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
22→19 dicer.assigner.config.InternalTargetConfig uses dicer.common✕
- Connections
- 1 pair of types, where a type in dicer.assigner.config.InternalTargetConfig uses a type in dicer.common.
- The types involved
com.databricks.dicer.assigner.config.InternalTargetConfig.KeySensitivityConfig→com.databricks.dicer.common.SliceKeySensitivity
- Direction
- dicer.assigner.config.InternalTargetConfig uses dicer.common, so a change to dicer.common can break dicer.assigner.config.InternalTargetConfig, while a change to dicer.assigner.config.InternalTargetConfig can't break dicer.common.
- Position
- Below the diagonal: dicer.assigner.config.InternalTargetConfig uses a module listed above it, which is the healthy direction.
22→25 dicer.assigner.config.InternalTargetConfig uses dicer.assigner.config part of a loop✕
- Connections
- 2 pairs of types, where a type in dicer.assigner.config.InternalTargetConfig uses a type in dicer.assigner.config.
- The types involved
com.databricks.dicer.assigner.config.InternalTargetConfig.LoadBalancingConfig→com.databricks.dicer.assigner.config.ChurnConfigcom.databricks.dicer.assigner.config.InternalTargetConfig.forTest→com.databricks.dicer.assigner.config.InternalTargetConfig
- Direction
- dicer.assigner.config.InternalTargetConfig uses dicer.assigner.config, so a change to dicer.assigner.config can break dicer.assigner.config.InternalTargetConfig, while a change to dicer.assigner.config.InternalTargetConfig can't break dicer.assigner.config.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→2 dicer.client.SliceletLoadAccumulator uses caching.util.SafeCounter✕
- Connections
- 1 pair of types, where a type in dicer.client.SliceletLoadAccumulator uses a type in caching.util.SafeCounter.
- The types involved
com.databricks.dicer.client.SliceletLoadAccumulator.SliceKeyLoadDistributionHistogram→com.databricks.caching.util.SafeCounter.Child
- Direction
- dicer.client.SliceletLoadAccumulator uses caching.util.SafeCounter, so a change to caching.util.SafeCounter can break dicer.client.SliceletLoadAccumulator, while a change to dicer.client.SliceletLoadAccumulator can't break caching.util.SafeCounter.
- Position
- Below the diagonal: dicer.client.SliceletLoadAccumulator uses a module listed above it, which is the healthy direction.
23→8 dicer.client.SliceletLoadAccumulator uses dicer.common.SliceletData✕
- Connections
- 1 pair of types, where a type in dicer.client.SliceletLoadAccumulator uses a type in dicer.common.SliceletData.
- The types involved
com.databricks.dicer.client.SliceletLoadAccumulator.SliceAccumulator→com.databricks.dicer.common.SliceletData.SliceLoad
- Direction
- dicer.client.SliceletLoadAccumulator uses dicer.common.SliceletData, so a change to dicer.common.SliceletData can break dicer.client.SliceletLoadAccumulator, while a change to dicer.client.SliceletLoadAccumulator can't break dicer.common.SliceletData.
- Position
- Below the diagonal: dicer.client.SliceletLoadAccumulator uses a module listed above it, which is the healthy direction.
23→11 dicer.client.SliceletLoadAccumulator uses dicer.friend✕
- Connections
- 2 pairs of types, where a type in dicer.client.SliceletLoadAccumulator uses a type in dicer.friend.
- The types involved
com.databricks.dicer.client.SliceletLoadAccumulator.AssignmentAccumulator→com.databricks.dicer.friend.SliceMapcom.databricks.dicer.client.SliceletLoadAccumulator.AssignmentAccumulator→com.databricks.dicer.friend.Squid
- Direction
- dicer.client.SliceletLoadAccumulator uses dicer.friend, so a change to dicer.friend can break dicer.client.SliceletLoadAccumulator, while a change to dicer.client.SliceletLoadAccumulator can't break dicer.friend.
- Position
- Below the diagonal: dicer.client.SliceletLoadAccumulator uses a module listed above it, which is the healthy direction.
23→12 dicer.client.SliceletLoadAccumulator uses caching.util✕
- Connections
- 1 pair of types, where a type in dicer.client.SliceletLoadAccumulator uses a type in caching.util.
- The types involved
com.databricks.dicer.client.SliceletLoadAccumulator.AssignmentAccumulator→com.databricks.caching.util.TypedClock
- Direction
- dicer.client.SliceletLoadAccumulator uses caching.util, so a change to caching.util can break dicer.client.SliceletLoadAccumulator, while a change to dicer.client.SliceletLoadAccumulator can't break caching.util.
- Position
- Below the diagonal: dicer.client.SliceletLoadAccumulator uses a module listed above it, which is the healthy direction.
23→19 dicer.client.SliceletLoadAccumulator uses dicer.common✕
- Connections
- 2 pairs of types, where a type in dicer.client.SliceletLoadAccumulator uses a type in dicer.common.
- The types involved
com.databricks.dicer.client.SliceletLoadAccumulator.AssignmentAccumulator→com.databricks.dicer.common.Assignmentcom.databricks.dicer.client.SliceletLoadAccumulator.AssignmentAccumulator→com.databricks.dicer.common.Generation
- Direction
- dicer.client.SliceletLoadAccumulator uses dicer.common, so a change to dicer.common can break dicer.client.SliceletLoadAccumulator, while a change to dicer.client.SliceletLoadAccumulator can't break dicer.common.
- Position
- Below the diagonal: dicer.client.SliceletLoadAccumulator uses a module listed above it, which is the healthy direction.
23→31 dicer.client.SliceletLoadAccumulator uses dicer.external part of a loop✕
- Connections
- 4 pairs of types, where a type in dicer.client.SliceletLoadAccumulator uses a type in dicer.external.
- The types involved
com.databricks.dicer.client.SliceletLoadAccumulator.SliceAccumulator→com.databricks.dicer.external.Slicecom.databricks.dicer.client.SliceletLoadAccumulator.SliceAccumulator→com.databricks.dicer.external.SliceKeycom.databricks.dicer.client.SliceletLoadAccumulator.SliceKeyLoadDistributionHistogram→com.databricks.dicer.external.SliceKeycom.databricks.dicer.client.SliceletLoadAccumulator.forTest→com.databricks.dicer.external.Target
- Direction
- dicer.client.SliceletLoadAccumulator uses dicer.external, so a change to dicer.external can break dicer.client.SliceletLoadAccumulator, while a change to dicer.client.SliceletLoadAccumulator can't break dicer.external.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
24→11 dicer.common.testing.SliceTestUtils uses dicer.friend✕
- Connections
- 3 pairs of types, where a type in dicer.common.testing.SliceTestUtils uses a type in dicer.friend.
- The types involved
com.databricks.dicer.common.testing.SliceTestUtils.SliceAssignmentFluet→com.databricks.dicer.friend.Squidcom.databricks.dicer.common.testing.SliceTestUtils.SliceAssignmentSliceAndGenerationFluent→com.databricks.dicer.friend.Squidcom.databricks.dicer.common.testing.SliceTestUtils.SliceAssignmentSliceFluent→com.databricks.dicer.friend.Squid
- Direction
- dicer.common.testing.SliceTestUtils uses dicer.friend, so a change to dicer.friend can break dicer.common.testing.SliceTestUtils, while a change to dicer.common.testing.SliceTestUtils can't break dicer.friend.
- Position
- Below the diagonal: dicer.common.testing.SliceTestUtils uses a module listed above it, which is the healthy direction.
24→12 dicer.common.testing.SliceTestUtils uses caching.util✕
- Connections
- 1 pair of types, where a type in dicer.common.testing.SliceTestUtils uses a type in caching.util.
- The types involved
com.databricks.dicer.common.testing.SliceTestUtils.SubsliceAnnotationSliceFluent→com.databricks.caching.util.UnixTimeVersion
- Direction
- dicer.common.testing.SliceTestUtils uses caching.util, so a change to caching.util can break dicer.common.testing.SliceTestUtils, while a change to dicer.common.testing.SliceTestUtils can't break caching.util.
- Position
- Below the diagonal: dicer.common.testing.SliceTestUtils uses a module listed above it, which is the healthy direction.
24→19 dicer.common.testing.SliceTestUtils uses dicer.common✕
- Connections
- 9 pairs of types, where a type in dicer.common.testing.SliceTestUtils uses a type in dicer.common.
- The types involved
com.databricks.dicer.common.testing.SliceTestUtils.GenerationIncarnationFluent→com.databricks.dicer.common.Generationcom.databricks.dicer.common.testing.SliceTestUtils.ProposedAssignmentEntry→com.databricks.dicer.common.ProposedSliceAssignmentcom.databricks.dicer.common.testing.SliceTestUtils.ProposedSliceAssignmentFluent→com.databricks.dicer.common.ProposedSliceAssignmentcom.databricks.dicer.common.testing.SliceTestUtils.SliceAssignmentFluet→com.databricks.dicer.common.SliceAssignmentcom.databricks.dicer.common.testing.SliceTestUtils.SliceAssignmentFluet→com.databricks.dicer.common.SubsliceAnnotationcom.databricks.dicer.common.testing.SliceTestUtils.SliceAssignmentSliceAndGenerationFluent→com.databricks.dicer.common.Generationcom.databricks.dicer.common.testing.SliceTestUtils.SliceAssignmentSliceAndGenerationFluent→com.databricks.dicer.common.SliceAssignmentcom.databricks.dicer.common.testing.SliceTestUtils.SliceAssignmentSliceFluent→com.databricks.dicer.common.Generationcom.databricks.dicer.common.testing.SliceTestUtils.SliceAssignmentSliceFluent→com.databricks.dicer.common.ProposedSliceAssignment
- Direction
- dicer.common.testing.SliceTestUtils uses dicer.common, so a change to dicer.common can break dicer.common.testing.SliceTestUtils, while a change to dicer.common.testing.SliceTestUtils can't break dicer.common.
- Position
- Below the diagonal: dicer.common.testing.SliceTestUtils uses a module listed above it, which is the healthy direction.
24→31 dicer.common.testing.SliceTestUtils uses dicer.external part of a loop✕
- Connections
- 3 pairs of types, where a type in dicer.common.testing.SliceTestUtils uses a type in dicer.external.
- The types involved
com.databricks.dicer.common.testing.SliceTestUtils.LowInclusiveSliceKeyFluent→com.databricks.dicer.external.HighSliceKeycom.databricks.dicer.common.testing.SliceTestUtils.LowInclusiveSliceKeyFluent→com.databricks.dicer.external.Slicecom.databricks.dicer.common.testing.SliceTestUtils.SliceAssignmentSliceAndGenerationFluent→com.databricks.dicer.external.Slice
- Direction
- dicer.common.testing.SliceTestUtils uses dicer.external, so a change to dicer.external can break dicer.common.testing.SliceTestUtils, while a change to dicer.common.testing.SliceTestUtils can't break dicer.external.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
25→4 dicer.assigner.config uses rpc✕
- Connections
- 1 pair of types, where a type in dicer.assigner.config uses a type in rpc.
- The types involved
com.databricks.dicer.assigner.config.Authorizer→com.databricks.rpc.RPCContext
- Direction
- dicer.assigner.config uses rpc, so a change to rpc can break dicer.assigner.config, while a change to dicer.assigner.config can't break rpc.
- Position
- Below the diagonal: dicer.assigner.config uses a module listed above it, which is the healthy direction.
25→12 dicer.assigner.config uses caching.util✕
- Connections
- 12 pairs of types, where a type in dicer.assigner.config uses a type in caching.util.
- The types involved
com.databricks.dicer.assigner.config.DicerSafeConfigProvider→com.databricks.caching.util.ClusterConfigScopecom.databricks.dicer.assigner.config.DicerSafeConfigProvider→com.databricks.caching.util.SafeConfigProvidercom.databricks.dicer.assigner.config.InternalTargetConfigMap→com.databricks.caching.util.ClusterConfigScopecom.databricks.dicer.assigner.config.NamedInternalTargetConfig→com.databricks.caching.util.JsonSerializableConfigcom.databricks.dicer.assigner.config.StaticTargetConfigProvider→com.databricks.caching.util.Cancellablecom.databricks.dicer.assigner.config.StaticTargetConfigProvider→com.databricks.caching.util.ValueStreamCallbackcom.databricks.dicer.assigner.config.StaticTargetMigrationConfigProvider→com.databricks.caching.util.Cancellablecom.databricks.dicer.assigner.config.StaticTargetMigrationConfigProvider→com.databricks.caching.util.ValueStreamCallbackcom.databricks.dicer.assigner.config.TargetConfigProvider→com.databricks.caching.util.Cancellablecom.databricks.dicer.assigner.config.TargetConfigProvider→com.databricks.caching.util.ValueStreamCallbackcom.databricks.dicer.assigner.config.TargetConfigReader→com.databricks.caching.util.ClusterConfigScopecom.databricks.dicer.assigner.config.TargetConfigReader→com.databricks.caching.util.ConfigScope
- Direction
- dicer.assigner.config uses caching.util, so a change to caching.util can break dicer.assigner.config, while a change to dicer.assigner.config can't break caching.util.
- Position
- Below the diagonal: dicer.assigner.config uses a module listed above it, which is the healthy direction.
25→19 dicer.assigner.config uses dicer.common✕
- Connections
- 7 pairs of types, where a type in dicer.assigner.config uses a type in dicer.common.
- The types involved
com.databricks.dicer.assigner.config.Authorizer→com.databricks.dicer.common.ClientTypecom.databricks.dicer.assigner.config.DicerSafeConfigProvider→com.databricks.dicer.common.TargetNamecom.databricks.dicer.assigner.config.InternalTargetConfigMap→com.databricks.dicer.common.TargetNamecom.databricks.dicer.assigner.config.InternalTargetConfigMetrics→com.databricks.dicer.common.TargetNamecom.databricks.dicer.assigner.config.NamedInternalTargetConfig→com.databricks.dicer.common.TargetNamecom.databricks.dicer.assigner.config.TargetConfigReader→com.databricks.dicer.common.TargetNamecom.databricks.dicer.assigner.config.TargetMigrationConfig→com.databricks.dicer.common.TargetName
- Direction
- dicer.assigner.config uses dicer.common, so a change to dicer.common can break dicer.assigner.config, while a change to dicer.assigner.config can't break dicer.common.
- Position
- Below the diagonal: dicer.assigner.config uses a module listed above it, which is the healthy direction.
25→21 dicer.assigner.config uses dicer.assigner.conf✕
- Connections
- 1 pair of types, where a type in dicer.assigner.config uses a type in dicer.assigner.conf.
- The types involved
com.databricks.dicer.assigner.config.TargetConfigProviderFactory→com.databricks.dicer.assigner.conf.DicerAssignerConf
- Direction
- dicer.assigner.config uses dicer.assigner.conf, so a change to dicer.assigner.conf can break dicer.assigner.config, while a change to dicer.assigner.config can't break dicer.assigner.conf.
- Position
- Below the diagonal: dicer.assigner.config uses a module listed above it, which is the healthy direction.
25→22 dicer.assigner.config uses dicer.assigner.config.InternalTargetConfig✕
- Connections
- 11 pairs of types, where a type in dicer.assigner.config uses a type in dicer.assigner.config.InternalTargetConfig.
- The types involved
com.databricks.dicer.assigner.config.InternalTargetConfig→com.databricks.dicer.assigner.config.InternalTargetConfig.HealthWatcherTargetConfigcom.databricks.dicer.assigner.config.InternalTargetConfig→com.databricks.dicer.assigner.config.InternalTargetConfig.KeyOfDeathProtectionConfigcom.databricks.dicer.assigner.config.InternalTargetConfig→com.databricks.dicer.assigner.config.InternalTargetConfig.KeyReplicationConfigcom.databricks.dicer.assigner.config.InternalTargetConfig→com.databricks.dicer.assigner.config.InternalTargetConfig.KeySensitivityConfigcom.databricks.dicer.assigner.config.InternalTargetConfig→com.databricks.dicer.assigner.config.InternalTargetConfig.LoadBalancingConfigcom.databricks.dicer.assigner.config.InternalTargetConfig→com.databricks.dicer.assigner.config.InternalTargetConfig.LoadWatcherTargetConfigcom.databricks.dicer.assigner.config.InternalTargetConfig→com.databricks.dicer.assigner.config.InternalTargetConfig.TargetWatchRequestRateLimitConfigcom.databricks.dicer.assigner.config.InternalTargetConfigMetrics→com.databricks.dicer.assigner.config.InternalTargetConfig.KeyReplicationConfigcom.databricks.dicer.assigner.config.InternalTargetConfigMetrics→com.databricks.dicer.assigner.config.InternalTargetConfig.LoadBalancingConfigcom.databricks.dicer.assigner.config.InternalTargetConfigMetrics→com.databricks.dicer.assigner.config.InternalTargetConfig.LoadWatcherTargetConfigcom.databricks.dicer.assigner.config.InternalTargetConfigMetrics→com.databricks.dicer.assigner.config.InternalTargetConfig.TargetWatchRequestRateLimitConfig
- Direction
- dicer.assigner.config uses dicer.assigner.config.InternalTargetConfig, so a change to dicer.assigner.config.InternalTargetConfig can break dicer.assigner.config, while a change to dicer.assigner.config can't break dicer.assigner.config.InternalTargetConfig.
- Position
- Below the diagonal: dicer.assigner.config uses a module listed above it, which is the healthy direction.
25→31 dicer.assigner.config uses dicer.external part of a loop✕
- Connections
- 2 pairs of types, where a type in dicer.assigner.config uses a type in dicer.external.
- The types involved
com.databricks.dicer.assigner.config.Authorizer→com.databricks.dicer.external.Targetcom.databricks.dicer.assigner.config.AuthorizerMetrics→com.databricks.dicer.external.Target
- Direction
- dicer.assigner.config uses dicer.external, so a change to dicer.external can break dicer.assigner.config, while a change to dicer.assigner.config can't break dicer.external.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
26→1 dicer.client uses caching.util.EtcdWatcher.EtcdWatcherStateMachine✕
- Connections
- 3 pairs of types, where a type in dicer.client uses a type in caching.util.EtcdWatcher.EtcdWatcherStateMachine.
- The types involved
com.databricks.dicer.client.AssignmentSyncStateMachine→com.databricks.caching.util.EtcdWatcher.EtcdWatcherStateMachine.DriverActioncom.databricks.dicer.client.AssignmentSyncStateMachine→com.databricks.caching.util.EtcdWatcher.EtcdWatcherStateMachine.Eventcom.databricks.dicer.client.SliceLookup→com.databricks.caching.util.EtcdWatcher.EtcdWatcherStateMachine.DriverAction
- Direction
- dicer.client uses caching.util.EtcdWatcher.EtcdWatcherStateMachine, so a change to caching.util.EtcdWatcher.EtcdWatcherStateMachine can break dicer.client, while a change to dicer.client can't break caching.util.EtcdWatcher.EtcdWatcherStateMachine.
- Position
- Below the diagonal: dicer.client uses a module listed above it, which is the healthy direction.
26→2 dicer.client uses caching.util.SafeCounter✕
- Connections
- 2 pairs of types, where a type in dicer.client uses a type in caching.util.SafeCounter.
- The types involved
com.databricks.dicer.client.ClerkMetrics→com.databricks.caching.util.SafeCounter.Childcom.databricks.dicer.client.SliceletMetrics→com.databricks.caching.util.SafeCounter.Child
- Direction
- dicer.client uses caching.util.SafeCounter, so a change to caching.util.SafeCounter can break dicer.client, while a change to dicer.client can't break caching.util.SafeCounter.
- Position
- Below the diagonal: dicer.client uses a module listed above it, which is the healthy direction.
26→4 dicer.client uses rpc✕
- Connections
- 1 pair of types, where a type in dicer.client uses a type in rpc.
- The types involved
com.databricks.dicer.client.SliceLookup→com.databricks.rpc.RPCContext
- Direction
- dicer.client uses rpc, so a change to rpc can break dicer.client, while a change to dicer.client can't break rpc.
- Position
- Below the diagonal: dicer.client uses a module listed above it, which is the healthy direction.
26→5 dicer.client uses caching.util.SequentialExecutionContext✕
- Connections
- 1 pair of types, where a type in dicer.client uses a type in caching.util.SequentialExecutionContext.
- The types involved
com.databricks.dicer.client.SliceletMetrics→com.databricks.caching.util.SequentialExecutionContext.State
- Direction
- dicer.client uses caching.util.SequentialExecutionContext, so a change to caching.util.SequentialExecutionContext can break dicer.client, while a change to dicer.client can't break caching.util.SequentialExecutionContext.
- Position
- Below the diagonal: dicer.client uses a module listed above it, which is the healthy direction.
26→11 dicer.client uses dicer.friend✕
- Connections
- 9 pairs of types, where a type in dicer.client uses a type in dicer.friend.
- The types involved
com.databricks.dicer.client.ClerkAssignment→com.databricks.dicer.friend.SliceMapcom.databricks.dicer.client.ClientTargetSlicezData→com.databricks.dicer.friend.Squidcom.databricks.dicer.client.ResourceRouter→com.databricks.dicer.friend.Squidcom.databricks.dicer.client.SliceInfo→com.databricks.dicer.friend.Squidcom.databricks.dicer.client.SliceletAssignment→com.databricks.dicer.friend.Squidcom.databricks.dicer.client.SliceletImpl→com.databricks.dicer.friend.SliceWithStateProvidercom.databricks.dicer.client.SliceletImpl→com.databricks.dicer.friend.Squidcom.databricks.dicer.client.SliceletLoadAccumulator→com.databricks.dicer.friend.Squidcom.databricks.dicer.client.SliceletSliceLookup→com.databricks.dicer.friend.Squid
- Direction
- dicer.client uses dicer.friend, so a change to dicer.friend can break dicer.client, while a change to dicer.client can't break dicer.friend.
- Position
- Below the diagonal: dicer.client uses a module listed above it, which is the healthy direction.
26→12 dicer.client uses caching.util✕
- Connections
- 12 pairs of types, where a type in dicer.client uses a type in caching.util.
- The types involved
com.databricks.dicer.client.AssignmentSyncStateMachine→com.databricks.caching.util.StateMachinecom.databricks.dicer.client.AssignmentSyncStateMachine→com.databricks.caching.util.StateMachineOutputcom.databricks.dicer.client.AssignmentSyncStateMachine→com.databricks.caching.util.TickerTimecom.databricks.dicer.client.ClerkImpl→com.databricks.caching.util.WatchValueCellcom.databricks.dicer.client.SliceInfo→com.databricks.caching.util.ConsistentHashRingcom.databricks.dicer.client.SliceLookupConfig→com.databricks.caching.util.KubernetesClusterUricom.databricks.dicer.client.SliceLookupConfig→com.databricks.caching.util.RegionUricom.databricks.dicer.client.SliceletImpl→com.databricks.caching.util.Cancellablecom.databricks.dicer.client.SliceletKeyCardinalityEstimator→com.databricks.caching.util.HyperLogLogcom.databricks.dicer.client.SliceletSliceLookup→com.databricks.caching.util.Cancellablecom.databricks.dicer.client.SliceletSliceLookup→com.databricks.caching.util.ValueStreamCallbackcom.databricks.dicer.client.SliceletSliceLookup→com.databricks.caching.util.WatchValueCell
- Direction
- dicer.client uses caching.util, so a change to caching.util can break dicer.client, while a change to dicer.client can't break caching.util.
- Position
- Below the diagonal: dicer.client uses a module listed above it, which is the healthy direction.
26→15 dicer.client uses caching.util.StateMachineOutput✕
- Connections
- 1 pair of types, where a type in dicer.client uses a type in caching.util.StateMachineOutput.
- The types involved
com.databricks.dicer.client.AssignmentSyncStateMachine→com.databricks.caching.util.StateMachineOutput.Builder
- Direction
- dicer.client uses caching.util.StateMachineOutput, so a change to caching.util.StateMachineOutput can break dicer.client, while a change to dicer.client can't break caching.util.StateMachineOutput.
- Position
- Below the diagonal: dicer.client uses a module listed above it, which is the healthy direction.
26→16 dicer.client uses dicer.common.SubscriberHandler✕
- Connections
- 1 pair of types, where a type in dicer.client uses a type in dicer.common.SubscriberHandler.
- The types involved
com.databricks.dicer.client.SliceLookup→com.databricks.dicer.common.SubscriberHandler.Location
- Direction
- dicer.client uses dicer.common.SubscriberHandler, so a change to dicer.common.SubscriberHandler can break dicer.client, while a change to dicer.client can't break dicer.common.SubscriberHandler.
- Position
- Below the diagonal: dicer.client uses a module listed above it, which is the healthy direction.
26→18 dicer.client uses rpc.tls✕
- Connections
- 1 pair of types, where a type in dicer.client uses a type in rpc.tls.
- The types involved
com.databricks.dicer.client.SliceLookupConfig→com.databricks.rpc.tls.TLSOptions
- Direction
- dicer.client uses rpc.tls, so a change to rpc.tls can break dicer.client, while a change to dicer.client can't break rpc.tls.
- Position
- Below the diagonal: dicer.client uses a module listed above it, which is the healthy direction.
26→19 dicer.client uses dicer.common✕
- Connections
- 31 pairs of types, where a type in dicer.client uses a type in dicer.common. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.databricks.dicer.client.AssignmentSyncStateMachine→com.databricks.dicer.common.Assignmentcom.databricks.dicer.client.AssignmentSyncStateMachine→com.databricks.dicer.common.ClientRequestcom.databricks.dicer.client.AssignmentSyncStateMachine→com.databricks.dicer.common.ClientResponsecom.databricks.dicer.client.AssignmentSyncStateMachine→com.databricks.dicer.common.Redirectcom.databricks.dicer.client.AssignmentSyncStateMachine→com.databricks.dicer.common.SyncAssignmentStatecom.databricks.dicer.client.ClerkAssignment→com.databricks.dicer.common.Assignmentcom.databricks.dicer.client.ClientMetrics→com.databricks.dicer.common.AssignerServiceInfocom.databricks.dicer.client.ClientMetrics→com.databricks.dicer.common.AssignmentMetricsSourcecom.databricks.dicer.client.ClientMetrics→com.databricks.dicer.common.ClientTypecom.databricks.dicer.client.ClientMetrics→com.databricks.dicer.common.Generationcom.databricks.dicer.client.ClientSlicez→com.databricks.dicer.common.TargetSlicezDatacom.databricks.dicer.client.ClientTargetSlicezData→com.databricks.dicer.common.Assignmentcom.databricks.dicer.client.ClientTargetSlicezData→com.databricks.dicer.common.ClerkSubscriberSlicezDatacom.databricks.dicer.client.ClientTargetSlicezData→com.databricks.dicer.common.SliceletSubscriberSlicezDatacom.databricks.dicer.client.ClientTargetSlicezData→com.databricks.dicer.common.TargetSlicezDatacom.databricks.dicer.client.DicerClientProtoLogger→com.databricks.dicer.common.Generationcom.databricks.dicer.client.RetryTokenImpl→com.databricks.dicer.common.Generationcom.databricks.dicer.client.SliceLookup→com.databricks.dicer.common.Assignmentcom.databricks.dicer.client.SliceLookup→com.databricks.dicer.common.ClientRequestcom.databricks.dicer.client.SliceLookup→com.databricks.dicer.common.ClientResponsecom.databricks.dicer.client.SliceLookup→com.databricks.dicer.common.Redirectcom.databricks.dicer.client.SliceLookup→com.databricks.dicer.common.SyncAssignmentStatecom.databricks.dicer.client.SliceLookupConfig→com.databricks.dicer.common.ClientTypecom.databricks.dicer.client.SliceletAssignment→com.databricks.dicer.common.Assignmentcom.databricks.dicer.client.SliceletAssignment→com.databricks.dicer.common.Generation
- Direction
- dicer.client uses dicer.common, so a change to dicer.common can break dicer.client, while a change to dicer.client can't break dicer.common.
- Position
- Below the diagonal: dicer.client uses a module listed above it, which is the healthy direction.
26→23 dicer.client uses dicer.client.SliceletLoadAccumulator✕
- Connections
- 1 pair of types, where a type in dicer.client uses a type in dicer.client.SliceletLoadAccumulator.
- The types involved
com.databricks.dicer.client.SliceletLoadAccumulator→com.databricks.dicer.client.SliceletLoadAccumulator.SliceAccumulator
- Direction
- dicer.client uses dicer.client.SliceletLoadAccumulator, so a change to dicer.client.SliceletLoadAccumulator can break dicer.client, while a change to dicer.client can't break dicer.client.SliceletLoadAccumulator.
- Position
- Below the diagonal: dicer.client uses a module listed above it, which is the healthy direction.
26→31 dicer.client uses dicer.external part of a loop✕
- Connections
- 20 pairs of types, where a type in dicer.client uses a type in dicer.external.
- The types involved
com.databricks.dicer.client.ClerkImpl→com.databricks.dicer.external.SliceKeycom.databricks.dicer.client.ClientMetrics→com.databricks.dicer.external.Targetcom.databricks.dicer.client.ClientTargetSlicezData→com.databricks.dicer.external.Slicecom.databricks.dicer.client.ClientTargetSlicezData→com.databricks.dicer.external.SliceKeycom.databricks.dicer.client.ClientTargetSlicezData→com.databricks.dicer.external.Targetcom.databricks.dicer.client.ResourceRouter→com.databricks.dicer.external.SliceKeycom.databricks.dicer.client.SliceInfo→com.databricks.dicer.external.Slicecom.databricks.dicer.client.SliceInfo→com.databricks.dicer.external.SliceKeycom.databricks.dicer.client.SliceKeyHandleImpl→com.databricks.dicer.external.SliceKeycom.databricks.dicer.client.SliceLookupCache→com.databricks.dicer.external.Targetcom.databricks.dicer.client.SliceLookupConfig→com.databricks.dicer.external.AppTargetcom.databricks.dicer.client.SliceLookupConfig→com.databricks.dicer.external.Targetcom.databricks.dicer.client.SliceletImpl→com.databricks.dicer.external.ResourceAddresscom.databricks.dicer.client.SliceletImpl→com.databricks.dicer.external.SliceKeycom.databricks.dicer.client.SliceletImpl→com.databricks.dicer.external.SliceletListenercom.databricks.dicer.client.SliceletImpl→com.databricks.dicer.external.Targetcom.databricks.dicer.client.SliceletKeyCardinalityEstimator→com.databricks.dicer.external.SliceKeycom.databricks.dicer.client.SliceletLoadAccumulator→com.databricks.dicer.external.SliceKeycom.databricks.dicer.client.SliceletSliceLookup→com.databricks.dicer.external.ResourceAddresscom.databricks.dicer.client.WatchStubManager→com.databricks.dicer.external.Target
- Direction
- dicer.client uses dicer.external, so a change to dicer.external can break dicer.client, while a change to dicer.client can't break dicer.external.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
27→25 dicer.assigner.TargetMigratorStateMachine uses dicer.assigner.config✕
- Connections
- 1 pair of types, where a type in dicer.assigner.TargetMigratorStateMachine uses a type in dicer.assigner.config.
- The types involved
com.databricks.dicer.assigner.TargetMigratorStateMachine.MigratorState→com.databricks.dicer.assigner.config.TargetMigrationConfig
- Direction
- dicer.assigner.TargetMigratorStateMachine uses dicer.assigner.config, so a change to dicer.assigner.config can break dicer.assigner.TargetMigratorStateMachine, while a change to dicer.assigner.TargetMigratorStateMachine can't break dicer.assigner.config.
- Position
- Below the diagonal: dicer.assigner.TargetMigratorStateMachine uses a module listed above it, which is the healthy direction.
27→37 dicer.assigner.TargetMigratorStateMachine uses dicer.assigner part of a loop✕
- Connections
- 1 pair of types, where a type in dicer.assigner.TargetMigratorStateMachine uses a type in dicer.assigner.
- The types involved
com.databricks.dicer.assigner.TargetMigratorStateMachine.MigratorState→com.databricks.dicer.assigner.TargetMigrationSnapshot
- Direction
- dicer.assigner.TargetMigratorStateMachine uses dicer.assigner, so a change to dicer.assigner can break dicer.assigner.TargetMigratorStateMachine, while a change to dicer.assigner.TargetMigratorStateMachine can't break dicer.assigner.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
28→11 dicer.assigner.algorithm.Algorithm uses dicer.friend✕
- Connections
- 1 pair of types, where a type in dicer.assigner.algorithm.Algorithm uses a type in dicer.friend.
- The types involved
com.databricks.dicer.assigner.algorithm.Algorithm.AssignmentGenerationResult→com.databricks.dicer.friend.SliceMap
- Direction
- dicer.assigner.algorithm.Algorithm uses dicer.friend, so a change to dicer.friend can break dicer.assigner.algorithm.Algorithm, while a change to dicer.assigner.algorithm.Algorithm can't break dicer.friend.
- Position
- Below the diagonal: dicer.assigner.algorithm.Algorithm uses a module listed above it, which is the healthy direction.
28→19 dicer.assigner.algorithm.Algorithm uses dicer.common✕
- Connections
- 1 pair of types, where a type in dicer.assigner.algorithm.Algorithm uses a type in dicer.common.
- The types involved
com.databricks.dicer.assigner.algorithm.Algorithm.AssignmentGenerationResult→com.databricks.dicer.common.ProposedSliceAssignment
- Direction
- dicer.assigner.algorithm.Algorithm uses dicer.common, so a change to dicer.common can break dicer.assigner.algorithm.Algorithm, while a change to dicer.assigner.algorithm.Algorithm can't break dicer.common.
- Position
- Below the diagonal: dicer.assigner.algorithm.Algorithm uses a module listed above it, which is the healthy direction.
28→22 dicer.assigner.algorithm.Algorithm uses dicer.assigner.config.InternalTargetConfig✕
- Connections
- 1 pair of types, where a type in dicer.assigner.algorithm.Algorithm uses a type in dicer.assigner.config.InternalTargetConfig.
- The types involved
com.databricks.dicer.assigner.algorithm.Algorithm.Config→com.databricks.dicer.assigner.config.InternalTargetConfig.KeyReplicationConfig
- Direction
- dicer.assigner.algorithm.Algorithm uses dicer.assigner.config.InternalTargetConfig, so a change to dicer.assigner.config.InternalTargetConfig can break dicer.assigner.algorithm.Algorithm, while a change to dicer.assigner.algorithm.Algorithm can't break dicer.assigner.config.InternalTargetConfig.
- Position
- Below the diagonal: dicer.assigner.algorithm.Algorithm uses a module listed above it, which is the healthy direction.
28→25 dicer.assigner.algorithm.Algorithm uses dicer.assigner.config✕
- Connections
- 1 pair of types, where a type in dicer.assigner.algorithm.Algorithm uses a type in dicer.assigner.config.
- The types involved
com.databricks.dicer.assigner.algorithm.Algorithm.Config→com.databricks.dicer.assigner.config.ChurnConfig
- Direction
- dicer.assigner.algorithm.Algorithm uses dicer.assigner.config, so a change to dicer.assigner.config can break dicer.assigner.algorithm.Algorithm, while a change to dicer.assigner.algorithm.Algorithm can't break dicer.assigner.config.
- Position
- Below the diagonal: dicer.assigner.algorithm.Algorithm uses a module listed above it, which is the healthy direction.
28→31 dicer.assigner.algorithm.Algorithm uses dicer.external part of a loop✕
- Connections
- 1 pair of types, where a type in dicer.assigner.algorithm.Algorithm uses a type in dicer.external.
- The types involved
com.databricks.dicer.assigner.algorithm.Algorithm.Config→com.databricks.dicer.external.Target
- Direction
- dicer.assigner.algorithm.Algorithm uses dicer.external, so a change to dicer.external can break dicer.assigner.algorithm.Algorithm, while a change to dicer.assigner.algorithm.Algorithm can't break dicer.external.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
29→11 dicer.assigner.algorithm uses dicer.friend✕
- Connections
- 7 pairs of types, where a type in dicer.assigner.algorithm uses a type in dicer.friend.
- The types involved
com.databricks.dicer.assigner.algorithm.Algorithm→com.databricks.dicer.friend.SliceMapcom.databricks.dicer.assigner.algorithm.HomomorphicAssignmentAlgorithm→com.databricks.dicer.friend.SliceMapcom.databricks.dicer.assigner.algorithm.InitialAssignmentAlgorithm→com.databricks.dicer.friend.SliceMapcom.databricks.dicer.assigner.algorithm.LoadMap→com.databricks.dicer.friend.SliceMapcom.databricks.dicer.assigner.algorithm.MutableAssignment→com.databricks.dicer.friend.SliceMapcom.databricks.dicer.assigner.algorithm.MutableAssignment→com.databricks.dicer.friend.Squidcom.databricks.dicer.assigner.algorithm.Resources→com.databricks.dicer.friend.Squid
- Direction
- dicer.assigner.algorithm uses dicer.friend, so a change to dicer.friend can break dicer.assigner.algorithm, while a change to dicer.assigner.algorithm can't break dicer.friend.
- Position
- Below the diagonal: dicer.assigner.algorithm uses a module listed above it, which is the healthy direction.
29→13 dicer.assigner.algorithm uses dicer.assigner.algorithm.MutableAssignment✕
- Connections
- 2 pairs of types, where a type in dicer.assigner.algorithm uses a type in dicer.assigner.algorithm.MutableAssignment.
- The types involved
com.databricks.dicer.assigner.algorithm.MutableAssignment→com.databricks.dicer.assigner.algorithm.MutableAssignment.MutableSliceAssignmentcom.databricks.dicer.assigner.algorithm.MutableAssignment→com.databricks.dicer.assigner.algorithm.MutableAssignment.ResourceState
- Direction
- dicer.assigner.algorithm uses dicer.assigner.algorithm.MutableAssignment, so a change to dicer.assigner.algorithm.MutableAssignment can break dicer.assigner.algorithm, while a change to dicer.assigner.algorithm can't break dicer.assigner.algorithm.MutableAssignment.
- Position
- Below the diagonal: dicer.assigner.algorithm uses a module listed above it, which is the healthy direction.
29→14 dicer.assigner.algorithm uses caching.util.EtcdClient✕
- Connections
- 6 pairs of types, where a type in dicer.assigner.algorithm uses a type in caching.util.EtcdClient.
- The types involved
com.databricks.dicer.assigner.algorithm.Algorithm→com.databricks.caching.util.EtcdClient.Configcom.databricks.dicer.assigner.algorithm.AlgorithmExecutor→com.databricks.caching.util.EtcdClient.Configcom.databricks.dicer.assigner.algorithm.ConstraintPhase→com.databricks.caching.util.EtcdClient.Configcom.databricks.dicer.assigner.algorithm.MergePhase→com.databricks.caching.util.EtcdClient.Configcom.databricks.dicer.assigner.algorithm.PlacementPhase→com.databricks.caching.util.EtcdClient.Configcom.databricks.dicer.assigner.algorithm.Splitter→com.databricks.caching.util.EtcdClient.Config
- Direction
- dicer.assigner.algorithm uses caching.util.EtcdClient, so a change to caching.util.EtcdClient can break dicer.assigner.algorithm, while a change to dicer.assigner.algorithm can't break caching.util.EtcdClient.
- Position
- Below the diagonal: dicer.assigner.algorithm uses a module listed above it, which is the healthy direction.
29→19 dicer.assigner.algorithm uses dicer.common✕
- Connections
- 7 pairs of types, where a type in dicer.assigner.algorithm uses a type in dicer.common.
- The types involved
com.databricks.dicer.assigner.algorithm.Algorithm→com.databricks.dicer.common.ProposedSliceAssignmentcom.databricks.dicer.assigner.algorithm.Algorithm→com.databricks.dicer.common.SliceAssignmentcom.databricks.dicer.assigner.algorithm.HomomorphicAssignmentAlgorithm→com.databricks.dicer.common.ProposedSliceAssignmentcom.databricks.dicer.assigner.algorithm.HomomorphicAssignmentAlgorithm→com.databricks.dicer.common.SliceAssignmentcom.databricks.dicer.assigner.algorithm.HomomorphicAssignmentAlgorithm→com.databricks.dicer.common.SliceWithResourcescom.databricks.dicer.assigner.algorithm.InitialAssignmentAlgorithm→com.databricks.dicer.common.ProposedSliceAssignmentcom.databricks.dicer.assigner.algorithm.MutableAssignment→com.databricks.dicer.common.SliceWithResources
- Direction
- dicer.assigner.algorithm uses dicer.common, so a change to dicer.common can break dicer.assigner.algorithm, while a change to dicer.assigner.algorithm can't break dicer.common.
- Position
- Below the diagonal: dicer.assigner.algorithm uses a module listed above it, which is the healthy direction.
29→22 dicer.assigner.algorithm uses dicer.assigner.config.InternalTargetConfig✕
- Connections
- 3 pairs of types, where a type in dicer.assigner.algorithm uses a type in dicer.assigner.config.InternalTargetConfig.
- The types involved
com.databricks.dicer.assigner.algorithm.Algorithm→com.databricks.dicer.assigner.config.InternalTargetConfig.KeyReplicationConfigcom.databricks.dicer.assigner.algorithm.Algorithm→com.databricks.dicer.assigner.config.InternalTargetConfig.LoadBalancingConfigcom.databricks.dicer.assigner.algorithm.InitialAssignmentAlgorithm→com.databricks.dicer.assigner.config.InternalTargetConfig.KeyReplicationConfig
- Direction
- dicer.assigner.algorithm uses dicer.assigner.config.InternalTargetConfig, so a change to dicer.assigner.config.InternalTargetConfig can break dicer.assigner.algorithm, while a change to dicer.assigner.algorithm can't break dicer.assigner.config.InternalTargetConfig.
- Position
- Below the diagonal: dicer.assigner.algorithm uses a module listed above it, which is the healthy direction.
29→25 dicer.assigner.algorithm uses dicer.assigner.config✕
- Connections
- 1 pair of types, where a type in dicer.assigner.algorithm uses a type in dicer.assigner.config.
- The types involved
com.databricks.dicer.assigner.algorithm.Algorithm→com.databricks.dicer.assigner.config.InternalTargetConfig
- Direction
- dicer.assigner.algorithm uses dicer.assigner.config, so a change to dicer.assigner.config can break dicer.assigner.algorithm, while a change to dicer.assigner.algorithm can't break dicer.assigner.config.
- Position
- Below the diagonal: dicer.assigner.algorithm uses a module listed above it, which is the healthy direction.
29→28 dicer.assigner.algorithm uses dicer.assigner.algorithm.Algorithm✕
- Connections
- 2 pairs of types, where a type in dicer.assigner.algorithm uses a type in dicer.assigner.algorithm.Algorithm.
- The types involved
com.databricks.dicer.assigner.algorithm.Algorithm→com.databricks.dicer.assigner.algorithm.Algorithm.AssignmentGenerationResultcom.databricks.dicer.assigner.algorithm.Algorithm→com.databricks.dicer.assigner.algorithm.Algorithm.DesiredLoadRange
- Direction
- dicer.assigner.algorithm uses dicer.assigner.algorithm.Algorithm, so a change to dicer.assigner.algorithm.Algorithm can break dicer.assigner.algorithm, while a change to dicer.assigner.algorithm can't break dicer.assigner.algorithm.Algorithm.
- Position
- Below the diagonal: dicer.assigner.algorithm uses a module listed above it, which is the healthy direction.
29→31 dicer.assigner.algorithm uses dicer.external part of a loop✕
- Connections
- 4 pairs of types, where a type in dicer.assigner.algorithm uses a type in dicer.external.
- The types involved
com.databricks.dicer.assigner.algorithm.Algorithm→com.databricks.dicer.external.Targetcom.databricks.dicer.assigner.algorithm.HomomorphicAssignmentAlgorithm→com.databricks.dicer.external.Targetcom.databricks.dicer.assigner.algorithm.InitialAssignmentAlgorithm→com.databricks.dicer.external.Targetcom.databricks.dicer.assigner.algorithm.LoadMap→com.databricks.dicer.external.Slice
- Direction
- dicer.assigner.algorithm uses dicer.external, so a change to dicer.external can break dicer.assigner.algorithm, while a change to dicer.assigner.algorithm can't break dicer.external.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
30→3 dicer.common.testing uses dicer.assigner.Store✕
- Connections
- 1 pair of types, where a type in dicer.common.testing uses a type in dicer.assigner.Store.
- The types involved
com.databricks.dicer.common.testing.InterceptableStore→com.databricks.dicer.assigner.Store.WriteAssignmentResult
- Direction
- dicer.common.testing uses dicer.assigner.Store, so a change to dicer.assigner.Store can break dicer.common.testing, while a change to dicer.common.testing can't break dicer.assigner.Store.
- Position
- Below the diagonal: dicer.common.testing uses a module listed above it, which is the healthy direction.
30→4 dicer.common.testing uses rpc✕
- Connections
- 2 pairs of types, where a type in dicer.common.testing uses a type in rpc.
- The types involved
com.databricks.dicer.common.testing.TestAssigner→com.databricks.rpc.RPCContextcom.databricks.dicer.common.testing.TestAssigner→com.databricks.rpc.RequestHeaders
- Direction
- dicer.common.testing uses rpc, so a change to rpc can break dicer.common.testing, while a change to dicer.common.testing can't break rpc.
- Position
- Below the diagonal: dicer.common.testing uses a module listed above it, which is the healthy direction.
30→7 dicer.common.testing uses dicer.assigner.TargetMetrics.AssignmentDistributionSource✕
- Connections
- 4 pairs of types, where a type in dicer.common.testing uses a type in dicer.assigner.TargetMetrics.AssignmentDistributionSource.
- The types involved
com.databricks.dicer.common.testing.InternalDicerTestEnvironment→com.databricks.dicer.assigner.TargetMetrics.AssignmentDistributionSource.Clerkcom.databricks.dicer.common.testing.InternalDicerTestEnvironment→com.databricks.dicer.assigner.TargetMetrics.AssignmentDistributionSource.Sliceletcom.databricks.dicer.common.testing.SliceTestUtils→com.databricks.dicer.assigner.TargetMetrics.AssignmentDistributionSource.Clerkcom.databricks.dicer.common.testing.SliceTestUtils→com.databricks.dicer.assigner.TargetMetrics.AssignmentDistributionSource.Slicelet
- Direction
- dicer.common.testing uses dicer.assigner.TargetMetrics.AssignmentDistributionSource, so a change to dicer.assigner.TargetMetrics.AssignmentDistributionSource can break dicer.common.testing, while a change to dicer.common.testing can't break dicer.assigner.TargetMetrics.AssignmentDistributionSource.
- Position
- Below the diagonal: dicer.common.testing uses a module listed above it, which is the healthy direction.
30→11 dicer.common.testing uses dicer.friend✕
- Connections
- 5 pairs of types, where a type in dicer.common.testing uses a type in dicer.friend.
- The types involved
com.databricks.dicer.common.testing.InternalDicerTestEnvironment→com.databricks.dicer.friend.SliceMapcom.databricks.dicer.common.testing.SliceTestUtils→com.databricks.dicer.friend.SliceMapcom.databricks.dicer.common.testing.SliceTestUtils→com.databricks.dicer.friend.Squidcom.databricks.dicer.common.testing.TestAssigner→com.databricks.dicer.friend.SliceMapcom.databricks.dicer.common.testing.TestAssigner→com.databricks.dicer.friend.Squid
- Direction
- dicer.common.testing uses dicer.friend, so a change to dicer.friend can break dicer.common.testing, while a change to dicer.common.testing can't break dicer.friend.
- Position
- Below the diagonal: dicer.common.testing uses a module listed above it, which is the healthy direction.
30→12 dicer.common.testing uses caching.util✕
- Connections
- 7 pairs of types, where a type in dicer.common.testing uses a type in caching.util.
- The types involved
com.databricks.dicer.common.testing.InterceptableStore→com.databricks.caching.util.Cancellablecom.databricks.dicer.common.testing.InterceptableStore→com.databricks.caching.util.SequentialExecutionContextcom.databricks.dicer.common.testing.InterceptableStore→com.databricks.caching.util.ValueStreamCallbackcom.databricks.dicer.common.testing.InternalDicerTestEnvironment→com.databricks.caching.util.SequentialExecutionContextcom.databricks.dicer.common.testing.SubscriberHandlerMetricTestUtils→com.databricks.caching.util.KubernetesClusterUricom.databricks.dicer.common.testing.SubscriberHandlerSuiteBase→com.databricks.caching.util.KubernetesClusterUricom.databricks.dicer.common.testing.TestAssigner→com.databricks.caching.util.PrefixLogger
- Direction
- dicer.common.testing uses caching.util, so a change to caching.util can break dicer.common.testing, while a change to dicer.common.testing can't break caching.util.
- Position
- Below the diagonal: dicer.common.testing uses a module listed above it, which is the healthy direction.
30→14 dicer.common.testing uses caching.util.EtcdClient✕
- Connections
- 1 pair of types, where a type in dicer.common.testing uses a type in caching.util.EtcdClient.
- The types involved
com.databricks.dicer.common.testing.InternalDicerTestEnvironment→com.databricks.caching.util.EtcdClient.Config
- Direction
- dicer.common.testing uses caching.util.EtcdClient, so a change to caching.util.EtcdClient can break dicer.common.testing, while a change to dicer.common.testing can't break caching.util.EtcdClient.
- Position
- Below the diagonal: dicer.common.testing uses a module listed above it, which is the healthy direction.
30→16 dicer.common.testing uses dicer.common.SubscriberHandler✕
- Connections
- 4 pairs of types, where a type in dicer.common.testing uses a type in dicer.common.SubscriberHandler.
- The types involved
com.databricks.dicer.common.testing.SubscriberHandlerMetricTestUtils→com.databricks.dicer.common.SubscriberHandler.Locationcom.databricks.dicer.common.testing.SubscriberHandlerMetricTestUtils→com.databricks.dicer.common.SubscriberHandler.MetricsKeycom.databricks.dicer.common.testing.SubscriberHandlerSuiteBase→com.databricks.dicer.common.SubscriberHandler.Locationcom.databricks.dicer.common.testing.SubscriberHandlerSuiteBase→com.databricks.dicer.common.SubscriberHandler.MetricsKey
- Direction
- dicer.common.testing uses dicer.common.SubscriberHandler, so a change to dicer.common.SubscriberHandler can break dicer.common.testing, while a change to dicer.common.testing can't break dicer.common.SubscriberHandler.
- Position
- Below the diagonal: dicer.common.testing uses a module listed above it, which is the healthy direction.
30→19 dicer.common.testing uses dicer.common✕
- Connections
- 26 pairs of types, where a type in dicer.common.testing uses a type in dicer.common. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.databricks.dicer.common.testing.InterceptableStore→com.databricks.dicer.common.Assignmentcom.databricks.dicer.common.testing.InterceptableStore→com.databricks.dicer.common.Incarnationcom.databricks.dicer.common.testing.InterceptableStore→com.databricks.dicer.common.ProposedAssignmentcom.databricks.dicer.common.testing.InternalDicerTestEnvironment→com.databricks.dicer.common.Assignmentcom.databricks.dicer.common.testing.InternalDicerTestEnvironment→com.databricks.dicer.common.ProposedSliceAssignmentcom.databricks.dicer.common.testing.InternalDicerTestEnvironment→com.databricks.dicer.common.TargetNamecom.databricks.dicer.common.testing.SliceTestUtils→com.databricks.dicer.common.AssignerServiceInfocom.databricks.dicer.common.testing.SliceTestUtils→com.databricks.dicer.common.Assignmentcom.databricks.dicer.common.testing.SliceTestUtils→com.databricks.dicer.common.AssignmentConsistencyModecom.databricks.dicer.common.testing.SliceTestUtils→com.databricks.dicer.common.DiffAssignmentcom.databricks.dicer.common.testing.SliceTestUtils→com.databricks.dicer.common.Generationcom.databricks.dicer.common.testing.SliceTestUtils→com.databricks.dicer.common.Incarnationcom.databricks.dicer.common.testing.SliceTestUtils→com.databricks.dicer.common.ProposedSliceAssignmentcom.databricks.dicer.common.testing.SliceTestUtils→com.databricks.dicer.common.SliceAssignmentcom.databricks.dicer.common.testing.SliceTestUtils→com.databricks.dicer.common.SubsliceAnnotationcom.databricks.dicer.common.testing.SubscriberHandlerHarness→com.databricks.dicer.common.Assignmentcom.databricks.dicer.common.testing.SubscriberHandlerHarness→com.databricks.dicer.common.ClientRequestcom.databricks.dicer.common.testing.SubscriberHandlerHarness→com.databricks.dicer.common.Redirectcom.databricks.dicer.common.testing.SubscriberHandlerSuiteBase→com.databricks.dicer.common.Assignmentcom.databricks.dicer.common.testing.SubscriberHandlerSuiteBase→com.databricks.dicer.common.ClientRequestcom.databricks.dicer.common.testing.SubscriberHandlerSuiteBase→com.databricks.dicer.common.Generationcom.databricks.dicer.common.testing.SubscriberHandlerSuiteBase→com.databricks.dicer.common.SliceletDatacom.databricks.dicer.common.testing.SubscriberHandlerSuiteBase→com.databricks.dicer.common.SubscriberDatacom.databricks.dicer.common.testing.TestAssigner→com.databricks.dicer.common.Assignmentcom.databricks.dicer.common.testing.TestAssigner→com.databricks.dicer.common.Incarnation
- Direction
- dicer.common.testing uses dicer.common, so a change to dicer.common can break dicer.common.testing, while a change to dicer.common.testing can't break dicer.common.
- Position
- Below the diagonal: dicer.common.testing uses a module listed above it, which is the healthy direction.
30→24 dicer.common.testing uses dicer.common.testing.SliceTestUtils✕
- Connections
- 1 pair of types, where a type in dicer.common.testing uses a type in dicer.common.testing.SliceTestUtils.
- The types involved
com.databricks.dicer.common.testing.SliceTestUtils→com.databricks.dicer.common.testing.SliceTestUtils.ProposedAssignmentEntry
- Direction
- dicer.common.testing uses dicer.common.testing.SliceTestUtils, so a change to dicer.common.testing.SliceTestUtils can break dicer.common.testing, while a change to dicer.common.testing can't break dicer.common.testing.SliceTestUtils.
- Position
- Below the diagonal: dicer.common.testing uses a module listed above it, which is the healthy direction.
30→25 dicer.common.testing uses dicer.assigner.config✕
- Connections
- 2 pairs of types, where a type in dicer.common.testing uses a type in dicer.assigner.config.
- The types involved
com.databricks.dicer.common.testing.InternalDicerTestEnvironment→com.databricks.dicer.assigner.config.InternalTargetConfigcom.databricks.dicer.common.testing.SliceTestUtils→com.databricks.dicer.assigner.config.InternalTargetConfig
- Direction
- dicer.common.testing uses dicer.assigner.config, so a change to dicer.assigner.config can break dicer.common.testing, while a change to dicer.common.testing can't break dicer.assigner.config.
- Position
- Below the diagonal: dicer.common.testing uses a module listed above it, which is the healthy direction.
30→26 dicer.common.testing uses dicer.client✕
- Connections
- 2 pairs of types, where a type in dicer.common.testing uses a type in dicer.client.
- The types involved
com.databricks.dicer.common.testing.SliceTestUtils→com.databricks.dicer.client.ClerkImplcom.databricks.dicer.common.testing.SliceTestUtils→com.databricks.dicer.client.SliceletImpl
- Direction
- dicer.common.testing uses dicer.client, so a change to dicer.client can break dicer.common.testing, while a change to dicer.common.testing can't break dicer.client.
- Position
- Below the diagonal: dicer.common.testing uses a module listed above it, which is the healthy direction.
30→29 dicer.common.testing uses dicer.assigner.algorithm✕
- Connections
- 2 pairs of types, where a type in dicer.common.testing uses a type in dicer.assigner.algorithm.
- The types involved
com.databricks.dicer.common.testing.SliceTestUtils→com.databricks.dicer.assigner.algorithm.LoadMapcom.databricks.dicer.common.testing.SliceTestUtils→com.databricks.dicer.assigner.algorithm.Resources
- Direction
- dicer.common.testing uses dicer.assigner.algorithm, so a change to dicer.assigner.algorithm can break dicer.common.testing, while a change to dicer.common.testing can't break dicer.assigner.algorithm.
- Position
- Below the diagonal: dicer.common.testing uses a module listed above it, which is the healthy direction.
30→31 dicer.common.testing uses dicer.external part of a loop✕
- Connections
- 15 pairs of types, where a type in dicer.common.testing uses a type in dicer.external.
- The types involved
com.databricks.dicer.common.testing.InterceptableStore→com.databricks.dicer.external.Targetcom.databricks.dicer.common.testing.InternalDicerTestEnvironment→com.databricks.dicer.external.ResourceAddresscom.databricks.dicer.common.testing.InternalDicerTestEnvironment→com.databricks.dicer.external.Targetcom.databricks.dicer.common.testing.SliceTestUtils→com.databricks.dicer.external.HighSliceKeycom.databricks.dicer.common.testing.SliceTestUtils→com.databricks.dicer.external.ResourceAddresscom.databricks.dicer.common.testing.SliceTestUtils→com.databricks.dicer.external.Slicecom.databricks.dicer.common.testing.SliceTestUtils→com.databricks.dicer.external.SliceKeycom.databricks.dicer.common.testing.SliceTestUtils→com.databricks.dicer.external.Targetcom.databricks.dicer.common.testing.SubscriberHandlerHarness→com.databricks.dicer.external.Targetcom.databricks.dicer.common.testing.SubscriberHandlerMetricTestUtils→com.databricks.dicer.external.AppTargetcom.databricks.dicer.common.testing.SubscriberHandlerMetricTestUtils→com.databricks.dicer.external.Targetcom.databricks.dicer.common.testing.SubscriberHandlerSuiteBase→com.databricks.dicer.external.AppTargetcom.databricks.dicer.common.testing.SubscriberHandlerSuiteBase→com.databricks.dicer.external.Targetcom.databricks.dicer.common.testing.TestAssigner→com.databricks.dicer.external.Targetcom.databricks.dicer.common.testing.TestEnvironmentMain→com.databricks.dicer.external.DicerTestEnvironment
- Direction
- dicer.common.testing uses dicer.external, so a change to dicer.external can break dicer.common.testing, while a change to dicer.common.testing can't break dicer.external.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
30→34 dicer.common.testing uses dicer.assigner.Assigner part of a loop✕
- Connections
- 1 pair of types, where a type in dicer.common.testing uses a type in dicer.assigner.Assigner.
- The types involved
com.databricks.dicer.common.testing.TestAssigner→com.databricks.dicer.assigner.Assigner.BaseForTest
- Direction
- dicer.common.testing uses dicer.assigner.Assigner, so a change to dicer.assigner.Assigner can break dicer.common.testing, while a change to dicer.common.testing can't break dicer.assigner.Assigner.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
30→37 dicer.common.testing uses dicer.assigner part of a loop✕
- Connections
- 3 pairs of types, where a type in dicer.common.testing uses a type in dicer.assigner.
- The types involved
com.databricks.dicer.common.testing.InterceptableStore→com.databricks.dicer.assigner.Storecom.databricks.dicer.common.testing.TestAssigner→com.databricks.dicer.assigner.AssignerInfocom.databricks.dicer.common.testing.TestAssigner→com.databricks.dicer.assigner.FakeKubernetesTargetWatcherFactory
- Direction
- dicer.common.testing uses dicer.assigner, so a change to dicer.assigner can break dicer.common.testing, while a change to dicer.common.testing can't break dicer.assigner.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
31→6 dicer.external uses conf✕
- Connections
- 1 pair of types, where a type in dicer.external uses a type in conf.
- The types involved
com.databricks.dicer.external.DicerClientConf→com.databricks.conf.DbConf
- Direction
- dicer.external uses conf, so a change to conf can break dicer.external, while a change to dicer.external can't break conf.
- Position
- Below the diagonal: dicer.external uses a module listed above it, which is the healthy direction.
31→7 dicer.external uses dicer.assigner.TargetMetrics.AssignmentDistributionSource✕
- Connections
- 2 pairs of types, where a type in dicer.external uses a type in dicer.assigner.TargetMetrics.AssignmentDistributionSource.
- The types involved
com.databricks.dicer.external.DicerTestEnvironment→com.databricks.dicer.assigner.TargetMetrics.AssignmentDistributionSource.Clerkcom.databricks.dicer.external.DicerTestEnvironment→com.databricks.dicer.assigner.TargetMetrics.AssignmentDistributionSource.Slicelet
- Direction
- dicer.external uses dicer.assigner.TargetMetrics.AssignmentDistributionSource, so a change to dicer.assigner.TargetMetrics.AssignmentDistributionSource can break dicer.external, while a change to dicer.external can't break dicer.assigner.TargetMetrics.AssignmentDistributionSource.
- Position
- Below the diagonal: dicer.external uses a module listed above it, which is the healthy direction.
31→10 dicer.external uses conf.trusted✕
- Connections
- 2 pairs of types, where a type in dicer.external uses a type in conf.trusted.
- The types involved
com.databricks.dicer.external.DicerClientConf→com.databricks.conf.trusted.LocationConfcom.databricks.dicer.external.DicerClientConf→com.databricks.conf.trusted.RPCPortConf
- Direction
- dicer.external uses conf.trusted, so a change to conf.trusted can break dicer.external, while a change to dicer.external can't break conf.trusted.
- Position
- Below the diagonal: dicer.external uses a module listed above it, which is the healthy direction.
31→14 dicer.external uses caching.util.EtcdClient✕
- Connections
- 1 pair of types, where a type in dicer.external uses a type in caching.util.EtcdClient.
- The types involved
com.databricks.dicer.external.DicerTestEnvironment→com.databricks.caching.util.EtcdClient.Config
- Direction
- dicer.external uses caching.util.EtcdClient, so a change to caching.util.EtcdClient can break dicer.external, while a change to dicer.external can't break caching.util.EtcdClient.
- Position
- Below the diagonal: dicer.external uses a module listed above it, which is the healthy direction.
31→18 dicer.external uses rpc.tls✕
- Connections
- 1 pair of types, where a type in dicer.external uses a type in rpc.tls.
- The types involved
com.databricks.dicer.external.DicerClientConf→com.databricks.rpc.tls.TLSOptions
- Direction
- dicer.external uses rpc.tls, so a change to rpc.tls can break dicer.external, while a change to dicer.external can't break rpc.tls.
- Position
- Below the diagonal: dicer.external uses a module listed above it, which is the healthy direction.
31→19 dicer.external uses dicer.common✕
- Connections
- 3 pairs of types, where a type in dicer.external uses a type in dicer.common.
- The types involved
com.databricks.dicer.external.DicerClientConf→com.databricks.dicer.common.CommonSslConfcom.databricks.dicer.external.DicerClientConf→com.databricks.dicer.common.InternalClientConfcom.databricks.dicer.external.SliceletConf→com.databricks.dicer.common.WatchServerConf
- Direction
- dicer.external uses dicer.common, so a change to dicer.common can break dicer.external, while a change to dicer.external can't break dicer.common.
- Position
- Below the diagonal: dicer.external uses a module listed above it, which is the healthy direction.
31→26 dicer.external uses dicer.client✕
- Connections
- 3 pairs of types, where a type in dicer.external uses a type in dicer.client.
- The types involved
com.databricks.dicer.external.Clerk→com.databricks.dicer.client.ClerkImplcom.databricks.dicer.external.DicerClientConf→com.databricks.dicer.client.DicerClientProtoLoggerConfcom.databricks.dicer.external.Slicelet→com.databricks.dicer.client.SliceletImpl
- Direction
- dicer.external uses dicer.client, so a change to dicer.client can break dicer.external, while a change to dicer.external can't break dicer.client.
- Position
- Below the diagonal: dicer.external uses a module listed above it, which is the healthy direction.
31→30 dicer.external uses dicer.common.testing✕
- Connections
- 1 pair of types, where a type in dicer.external uses a type in dicer.common.testing.
- The types involved
com.databricks.dicer.external.DicerTestEnvironment→com.databricks.dicer.common.testing.InternalDicerTestEnvironment
- Direction
- dicer.external uses dicer.common.testing, so a change to dicer.common.testing can break dicer.external, while a change to dicer.external can't break dicer.common.testing.
- Position
- Below the diagonal: dicer.external uses a module listed above it, which is the healthy direction.
32→11 dicer.assigner.HealthWatcher uses dicer.friend✕
- Connections
- 1 pair of types, where a type in dicer.assigner.HealthWatcher uses a type in dicer.friend.
- The types involved
com.databricks.dicer.assigner.HealthWatcher.ResourceHealth→com.databricks.dicer.friend.Squid
- Direction
- dicer.assigner.HealthWatcher uses dicer.friend, so a change to dicer.friend can break dicer.assigner.HealthWatcher, while a change to dicer.assigner.HealthWatcher can't break dicer.friend.
- Position
- Below the diagonal: dicer.assigner.HealthWatcher uses a module listed above it, which is the healthy direction.
32→12 dicer.assigner.HealthWatcher uses caching.util✕
- Connections
- 3 pairs of types, where a type in dicer.assigner.HealthWatcher uses a type in caching.util.
- The types involved
com.databricks.dicer.assigner.HealthWatcher.ResourceHealth→com.databricks.caching.util.IntrusiveMinHeapElementcom.databricks.dicer.assigner.HealthWatcher.ResourceHealth→com.databricks.caching.util.TickerTimecom.databricks.dicer.assigner.HealthWatcher.forTest→com.databricks.caching.util.TickerTime
- Direction
- dicer.assigner.HealthWatcher uses caching.util, so a change to caching.util can break dicer.assigner.HealthWatcher, while a change to dicer.assigner.HealthWatcher can't break caching.util.
- Position
- Below the diagonal: dicer.assigner.HealthWatcher uses a module listed above it, which is the healthy direction.
32→22 dicer.assigner.HealthWatcher uses dicer.assigner.config.InternalTargetConfig✕
- Connections
- 2 pairs of types, where a type in dicer.assigner.HealthWatcher uses a type in dicer.assigner.config.InternalTargetConfig.
- The types involved
com.databricks.dicer.assigner.HealthWatcher.DefaultFactory→com.databricks.dicer.assigner.config.InternalTargetConfig.HealthWatcherTargetConfigcom.databricks.dicer.assigner.HealthWatcher.Factory→com.databricks.dicer.assigner.config.InternalTargetConfig.HealthWatcherTargetConfig
- Direction
- dicer.assigner.HealthWatcher uses dicer.assigner.config.InternalTargetConfig, so a change to dicer.assigner.config.InternalTargetConfig can break dicer.assigner.HealthWatcher, while a change to dicer.assigner.HealthWatcher can't break dicer.assigner.config.InternalTargetConfig.
- Position
- Below the diagonal: dicer.assigner.HealthWatcher uses a module listed above it, which is the healthy direction.
32→31 dicer.assigner.HealthWatcher uses dicer.external✕
- Connections
- 2 pairs of types, where a type in dicer.assigner.HealthWatcher uses a type in dicer.external.
- The types involved
com.databricks.dicer.assigner.HealthWatcher.DefaultFactory→com.databricks.dicer.external.Targetcom.databricks.dicer.assigner.HealthWatcher.Factory→com.databricks.dicer.external.Target
- Direction
- dicer.assigner.HealthWatcher uses dicer.external, so a change to dicer.external can break dicer.assigner.HealthWatcher, while a change to dicer.assigner.HealthWatcher can't break dicer.external.
- Position
- Below the diagonal: dicer.assigner.HealthWatcher uses a module listed above it, which is the healthy direction.
32→37 dicer.assigner.HealthWatcher uses dicer.assigner part of a loop✕
- Connections
- 2 pairs of types, where a type in dicer.assigner.HealthWatcher uses a type in dicer.assigner.
- The types involved
com.databricks.dicer.assigner.HealthWatcher.DefaultFactory→com.databricks.dicer.assigner.HealthWatchercom.databricks.dicer.assigner.HealthWatcher.Factory→com.databricks.dicer.assigner.HealthWatcher
- Direction
- dicer.assigner.HealthWatcher uses dicer.assigner, so a change to dicer.assigner can break dicer.assigner.HealthWatcher, while a change to dicer.assigner.HealthWatcher can't break dicer.assigner.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
33→11 dicer.assigner.TargetMetrics uses dicer.friend✕
- Connections
- 1 pair of types, where a type in dicer.assigner.TargetMetrics uses a type in dicer.friend.
- The types involved
com.databricks.dicer.assigner.TargetMetrics.forTest→com.databricks.dicer.friend.Squid
- Direction
- dicer.assigner.TargetMetrics uses dicer.friend, so a change to dicer.friend can break dicer.assigner.TargetMetrics, while a change to dicer.assigner.TargetMetrics can't break dicer.friend.
- Position
- Below the diagonal: dicer.assigner.TargetMetrics uses a module listed above it, which is the healthy direction.
33→31 dicer.assigner.TargetMetrics uses dicer.external✕
- Connections
- 2 pairs of types, where a type in dicer.assigner.TargetMetrics uses a type in dicer.external.
- The types involved
com.databricks.dicer.assigner.TargetMetrics.ChurnRatioMetric→com.databricks.dicer.external.Targetcom.databricks.dicer.assigner.TargetMetrics.LoadDistributionHistogramBucket→com.databricks.dicer.external.Slice
- Direction
- dicer.assigner.TargetMetrics uses dicer.external, so a change to dicer.external can break dicer.assigner.TargetMetrics, while a change to dicer.assigner.TargetMetrics can't break dicer.external.
- Position
- Below the diagonal: dicer.assigner.TargetMetrics uses a module listed above it, which is the healthy direction.
34→4 dicer.assigner.Assigner uses rpc✕
- Connections
- 1 pair of types, where a type in dicer.assigner.Assigner uses a type in rpc.
- The types involved
com.databricks.dicer.assigner.Assigner.TargetManager→com.databricks.rpc.RPCContext
- Direction
- dicer.assigner.Assigner uses rpc, so a change to rpc can break dicer.assigner.Assigner, while a change to dicer.assigner.Assigner can't break rpc.
- Position
- Below the diagonal: dicer.assigner.Assigner uses a module listed above it, which is the healthy direction.
34→12 dicer.assigner.Assigner uses caching.util✕
- Connections
- 1 pair of types, where a type in dicer.assigner.Assigner uses a type in caching.util.
- The types involved
com.databricks.dicer.assigner.Assigner.TargetManager→com.databricks.caching.util.TickerTime
- Direction
- dicer.assigner.Assigner uses caching.util, so a change to caching.util can break dicer.assigner.Assigner, while a change to dicer.assigner.Assigner can't break caching.util.
- Position
- Below the diagonal: dicer.assigner.Assigner uses a module listed above it, which is the healthy direction.
34→19 dicer.assigner.Assigner uses dicer.common✕
- Connections
- 4 pairs of types, where a type in dicer.assigner.Assigner uses a type in dicer.common.
- The types involved
com.databricks.dicer.assigner.Assigner.TargetManager→com.databricks.dicer.common.ClientRequestcom.databricks.dicer.assigner.Assigner.TargetManager→com.databricks.dicer.common.Redirectcom.databricks.dicer.assigner.Assigner.TargetManager→com.databricks.dicer.common.SubscriberHandlercom.databricks.dicer.assigner.Assigner.forTest→com.databricks.dicer.common.TargetUnmarshaller
- Direction
- dicer.assigner.Assigner uses dicer.common, so a change to dicer.common can break dicer.assigner.Assigner, while a change to dicer.assigner.Assigner can't break dicer.common.
- Position
- Below the diagonal: dicer.assigner.Assigner uses a module listed above it, which is the healthy direction.
34→25 dicer.assigner.Assigner uses dicer.assigner.config✕
- Connections
- 1 pair of types, where a type in dicer.assigner.Assigner uses a type in dicer.assigner.config.
- The types involved
com.databricks.dicer.assigner.Assigner.TargetManager→com.databricks.dicer.assigner.config.InternalTargetConfig
- Direction
- dicer.assigner.Assigner uses dicer.assigner.config, so a change to dicer.assigner.config can break dicer.assigner.Assigner, while a change to dicer.assigner.Assigner can't break dicer.assigner.config.
- Position
- Below the diagonal: dicer.assigner.Assigner uses a module listed above it, which is the healthy direction.
34→31 dicer.assigner.Assigner uses dicer.external✕
- Connections
- 1 pair of types, where a type in dicer.assigner.Assigner uses a type in dicer.external.
- The types involved
com.databricks.dicer.assigner.Assigner.forTest→com.databricks.dicer.external.Target
- Direction
- dicer.assigner.Assigner uses dicer.external, so a change to dicer.external can break dicer.assigner.Assigner, while a change to dicer.assigner.Assigner can't break dicer.external.
- Position
- Below the diagonal: dicer.assigner.Assigner uses a module listed above it, which is the healthy direction.
34→33 dicer.assigner.Assigner uses dicer.assigner.TargetMetrics✕
- Connections
- 1 pair of types, where a type in dicer.assigner.Assigner uses a type in dicer.assigner.TargetMetrics.
- The types involved
com.databricks.dicer.assigner.Assigner.TargetManager→com.databricks.dicer.assigner.TargetMetrics.GeneratorShutdownReason
- Direction
- dicer.assigner.Assigner uses dicer.assigner.TargetMetrics, so a change to dicer.assigner.TargetMetrics can break dicer.assigner.Assigner, while a change to dicer.assigner.Assigner can't break dicer.assigner.TargetMetrics.
- Position
- Below the diagonal: dicer.assigner.Assigner uses a module listed above it, which is the healthy direction.
34→37 dicer.assigner.Assigner uses dicer.assigner part of a loop✕
- Connections
- 6 pairs of types, where a type in dicer.assigner.Assigner uses a type in dicer.assigner.
- The types involved
com.databricks.dicer.assigner.Assigner.BaseForTest→com.databricks.dicer.assigner.Assignercom.databricks.dicer.assigner.Assigner.StoreFactory→com.databricks.dicer.assigner.Storecom.databricks.dicer.assigner.Assigner.TargetManager→com.databricks.dicer.assigner.AssignerTargetSlicezDatacom.databricks.dicer.assigner.Assigner.TargetManager→com.databricks.dicer.assigner.AssignmentGeneratorDrivercom.databricks.dicer.assigner.Assigner.forTest→com.databricks.dicer.assigner.AssignmentGeneratorDrivercom.databricks.dicer.assigner.Assigner.forTest→com.databricks.dicer.assigner.PreferredAssignerConfig
- Direction
- dicer.assigner.Assigner uses dicer.assigner, so a change to dicer.assigner can break dicer.assigner.Assigner, while a change to dicer.assigner.Assigner can't break dicer.assigner.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
35→1 dicer.assigner.AssignmentGenerator uses caching.util.EtcdWatcher.EtcdWatcherStateMachine✕
- Connections
- 1 pair of types, where a type in dicer.assigner.AssignmentGenerator uses a type in caching.util.EtcdWatcher.EtcdWatcherStateMachine.
- The types involved
com.databricks.dicer.assigner.AssignmentGenerator.forTest→com.databricks.caching.util.EtcdWatcher.EtcdWatcherStateMachine.Event
- Direction
- dicer.assigner.AssignmentGenerator uses caching.util.EtcdWatcher.EtcdWatcherStateMachine, so a change to caching.util.EtcdWatcher.EtcdWatcherStateMachine can break dicer.assigner.AssignmentGenerator, while a change to dicer.assigner.AssignmentGenerator can't break caching.util.EtcdWatcher.EtcdWatcherStateMachine.
- Position
- Below the diagonal: dicer.assigner.AssignmentGenerator uses a module listed above it, which is the healthy direction.
35→11 dicer.assigner.AssignmentGenerator uses dicer.friend✕
- Connections
- 1 pair of types, where a type in dicer.assigner.AssignmentGenerator uses a type in dicer.friend.
- The types involved
com.databricks.dicer.assigner.AssignmentGenerator.GeneratorTargetSlicezData→com.databricks.dicer.friend.Squid
- Direction
- dicer.assigner.AssignmentGenerator uses dicer.friend, so a change to dicer.friend can break dicer.assigner.AssignmentGenerator, while a change to dicer.assigner.AssignmentGenerator can't break dicer.friend.
- Position
- Below the diagonal: dicer.assigner.AssignmentGenerator uses a module listed above it, which is the healthy direction.
35→12 dicer.assigner.AssignmentGenerator uses caching.util✕
- Connections
- 1 pair of types, where a type in dicer.assigner.AssignmentGenerator uses a type in caching.util.
- The types involved
com.databricks.dicer.assigner.AssignmentGenerator.forTest→com.databricks.caching.util.TickerTime
- Direction
- dicer.assigner.AssignmentGenerator uses caching.util, so a change to caching.util can break dicer.assigner.AssignmentGenerator, while a change to dicer.assigner.AssignmentGenerator can't break caching.util.
- Position
- Below the diagonal: dicer.assigner.AssignmentGenerator uses a module listed above it, which is the healthy direction.
35→19 dicer.assigner.AssignmentGenerator uses dicer.common✕
- Connections
- 2 pairs of types, where a type in dicer.assigner.AssignmentGenerator uses a type in dicer.common.
- The types involved
com.databricks.dicer.assigner.AssignmentGenerator.AssignmentGenerationContext→com.databricks.dicer.common.Assignmentcom.databricks.dicer.assigner.AssignmentGenerator.Config→com.databricks.dicer.common.Incarnation
- Direction
- dicer.assigner.AssignmentGenerator uses dicer.common, so a change to dicer.common can break dicer.assigner.AssignmentGenerator, while a change to dicer.assigner.AssignmentGenerator can't break dicer.common.
- Position
- Below the diagonal: dicer.assigner.AssignmentGenerator uses a module listed above it, which is the healthy direction.
35→28 dicer.assigner.AssignmentGenerator uses dicer.assigner.algorithm.Algorithm✕
- Connections
- 1 pair of types, where a type in dicer.assigner.AssignmentGenerator uses a type in dicer.assigner.algorithm.Algorithm.
- The types involved
com.databricks.dicer.assigner.AssignmentGenerator.AssignmentGenerationContext→com.databricks.dicer.assigner.algorithm.Algorithm.DesiredLoadRange
- Direction
- dicer.assigner.AssignmentGenerator uses dicer.assigner.algorithm.Algorithm, so a change to dicer.assigner.algorithm.Algorithm can break dicer.assigner.AssignmentGenerator, while a change to dicer.assigner.AssignmentGenerator can't break dicer.assigner.algorithm.Algorithm.
- Position
- Below the diagonal: dicer.assigner.AssignmentGenerator uses a module listed above it, which is the healthy direction.
35→29 dicer.assigner.AssignmentGenerator uses dicer.assigner.algorithm✕
- Connections
- 1 pair of types, where a type in dicer.assigner.AssignmentGenerator uses a type in dicer.assigner.algorithm.
- The types involved
com.databricks.dicer.assigner.AssignmentGenerator.AssignmentGenerationContext→com.databricks.dicer.assigner.algorithm.LoadMap
- Direction
- dicer.assigner.AssignmentGenerator uses dicer.assigner.algorithm, so a change to dicer.assigner.algorithm can break dicer.assigner.AssignmentGenerator, while a change to dicer.assigner.AssignmentGenerator can't break dicer.assigner.algorithm.
- Position
- Below the diagonal: dicer.assigner.AssignmentGenerator uses a module listed above it, which is the healthy direction.
35→31 dicer.assigner.AssignmentGenerator uses dicer.external✕
- Connections
- 3 pairs of types, where a type in dicer.assigner.AssignmentGenerator uses a type in dicer.external.
- The types involved
com.databricks.dicer.assigner.AssignmentGenerator.AssignmentGenerationContext→com.databricks.dicer.external.Targetcom.databricks.dicer.assigner.AssignmentGenerator.GeneratorTargetSlicezData→com.databricks.dicer.external.Slicecom.databricks.dicer.assigner.AssignmentGenerator.GeneratorTargetSlicezData→com.databricks.dicer.external.SliceKey
- Direction
- dicer.assigner.AssignmentGenerator uses dicer.external, so a change to dicer.external can break dicer.assigner.AssignmentGenerator, while a change to dicer.assigner.AssignmentGenerator can't break dicer.external.
- Position
- Below the diagonal: dicer.assigner.AssignmentGenerator uses a module listed above it, which is the healthy direction.
35→32 dicer.assigner.AssignmentGenerator uses dicer.assigner.HealthWatcher✕
- Connections
- 1 pair of types, where a type in dicer.assigner.AssignmentGenerator uses a type in dicer.assigner.HealthWatcher.
- The types involved
com.databricks.dicer.assigner.AssignmentGenerator.Config→com.databricks.dicer.assigner.HealthWatcher.StaticConfig
- Direction
- dicer.assigner.AssignmentGenerator uses dicer.assigner.HealthWatcher, so a change to dicer.assigner.HealthWatcher can break dicer.assigner.AssignmentGenerator, while a change to dicer.assigner.AssignmentGenerator can't break dicer.assigner.HealthWatcher.
- Position
- Below the diagonal: dicer.assigner.AssignmentGenerator uses a module listed above it, which is the healthy direction.
36→12 dicer.assigner.KubernetesMembershipChecker uses caching.util✕
- Connections
- 1 pair of types, where a type in dicer.assigner.KubernetesMembershipChecker uses a type in caching.util.
- The types involved
com.databricks.dicer.assigner.KubernetesMembershipChecker.KubernetesConnectionHealthMonitor→com.databricks.caching.util.PrefixLogger
- Direction
- dicer.assigner.KubernetesMembershipChecker uses caching.util, so a change to caching.util can break dicer.assigner.KubernetesMembershipChecker, while a change to dicer.assigner.KubernetesMembershipChecker can't break caching.util.
- Position
- Below the diagonal: dicer.assigner.KubernetesMembershipChecker uses a module listed above it, which is the healthy direction.
36→31 dicer.assigner.KubernetesMembershipChecker uses dicer.external✕
- Connections
- 1 pair of types, where a type in dicer.assigner.KubernetesMembershipChecker uses a type in dicer.external.
- The types involved
com.databricks.dicer.assigner.KubernetesMembershipChecker.VersionedResourceSet→com.databricks.dicer.external.ResourceAddress
- Direction
- dicer.assigner.KubernetesMembershipChecker uses dicer.external, so a change to dicer.external can break dicer.assigner.KubernetesMembershipChecker, while a change to dicer.assigner.KubernetesMembershipChecker can't break dicer.external.
- Position
- Below the diagonal: dicer.assigner.KubernetesMembershipChecker uses a module listed above it, which is the healthy direction.
36→32 dicer.assigner.KubernetesMembershipChecker uses dicer.assigner.HealthWatcher✕
- Connections
- 1 pair of types, where a type in dicer.assigner.KubernetesMembershipChecker uses a type in dicer.assigner.HealthWatcher.
- The types involved
com.databricks.dicer.assigner.KubernetesMembershipChecker.DefaultFactory→com.databricks.dicer.assigner.HealthWatcher.Factory
- Direction
- dicer.assigner.KubernetesMembershipChecker uses dicer.assigner.HealthWatcher, so a change to dicer.assigner.HealthWatcher can break dicer.assigner.KubernetesMembershipChecker, while a change to dicer.assigner.KubernetesMembershipChecker can't break dicer.assigner.HealthWatcher.
- Position
- Below the diagonal: dicer.assigner.KubernetesMembershipChecker uses a module listed above it, which is the healthy direction.
36→37 dicer.assigner.KubernetesMembershipChecker uses dicer.assigner part of a loop✕
- Connections
- 3 pairs of types, where a type in dicer.assigner.KubernetesMembershipChecker uses a type in dicer.assigner.
- The types involved
com.databricks.dicer.assigner.KubernetesMembershipChecker.DefaultFactory→com.databricks.dicer.assigner.KubernetesMembershipCheckercom.databricks.dicer.assigner.KubernetesMembershipChecker.ExtractedPod→com.databricks.dicer.assigner.AssignerUricom.databricks.dicer.assigner.KubernetesMembershipChecker.Factory→com.databricks.dicer.assigner.KubernetesMembershipChecker
- Direction
- dicer.assigner.KubernetesMembershipChecker uses dicer.assigner, so a change to dicer.assigner can break dicer.assigner.KubernetesMembershipChecker, while a change to dicer.assigner.KubernetesMembershipChecker can't break dicer.assigner.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
37→1 dicer.assigner uses caching.util.EtcdWatcher.EtcdWatcherStateMachine✕
- Connections
- 24 pairs of types, where a type in dicer.assigner uses a type in caching.util.EtcdWatcher.EtcdWatcherStateMachine.
- The types involved
com.databricks.dicer.assigner.AssignmentGenerator→com.databricks.caching.util.EtcdWatcher.EtcdWatcherStateMachine.DriverActioncom.databricks.dicer.assigner.AssignmentGenerator→com.databricks.caching.util.EtcdWatcher.EtcdWatcherStateMachine.Eventcom.databricks.dicer.assigner.AssignmentGenerator→com.databricks.caching.util.EtcdWatcher.EtcdWatcherStateMachine.RunStatecom.databricks.dicer.assigner.AssignmentGeneratorDriver→com.databricks.caching.util.EtcdWatcher.EtcdWatcherStateMachine.DriverActioncom.databricks.dicer.assigner.AssignmentGeneratorDriver→com.databricks.caching.util.EtcdWatcher.EtcdWatcherStateMachine.Eventcom.databricks.dicer.assigner.ConsistentHashingPreferredAssignerDriver→com.databricks.caching.util.EtcdWatcher.EtcdWatcherStateMachine.DriverActioncom.databricks.dicer.assigner.ConsistentHashingPreferredAssignerDriver→com.databricks.caching.util.EtcdWatcher.EtcdWatcherStateMachine.Eventcom.databricks.dicer.assigner.ConsistentHashingPreferredAssignerStateMachine→com.databricks.caching.util.EtcdWatcher.EtcdWatcherStateMachine.DriverActioncom.databricks.dicer.assigner.ConsistentHashingPreferredAssignerStateMachine→com.databricks.caching.util.EtcdWatcher.EtcdWatcherStateMachine.Eventcom.databricks.dicer.assigner.ConsistentHashingPreferredAssignerStateMachine→com.databricks.caching.util.EtcdWatcher.EtcdWatcherStateMachine.RunStatecom.databricks.dicer.assigner.DicerSimulatorEventEmitter→com.databricks.caching.util.EtcdWatcher.EtcdWatcherStateMachine.Eventcom.databricks.dicer.assigner.EtcdPreferredAssignerDriver→com.databricks.caching.util.EtcdWatcher.EtcdWatcherStateMachine.DriverActioncom.databricks.dicer.assigner.EtcdPreferredAssignerDriver→com.databricks.caching.util.EtcdWatcher.EtcdWatcherStateMachine.Eventcom.databricks.dicer.assigner.EtcdPreferredAssignerStateMachine→com.databricks.caching.util.EtcdWatcher.EtcdWatcherStateMachine.DriverActioncom.databricks.dicer.assigner.EtcdPreferredAssignerStateMachine→com.databricks.caching.util.EtcdWatcher.EtcdWatcherStateMachine.Eventcom.databricks.dicer.assigner.EtcdPreferredAssignerStateMachine→com.databricks.caching.util.EtcdWatcher.EtcdWatcherStateMachine.RunStatecom.databricks.dicer.assigner.EtcdPreferredAssignerStoreStateMachine→com.databricks.caching.util.EtcdWatcher.EtcdWatcherStateMachine.DriverActioncom.databricks.dicer.assigner.EtcdPreferredAssignerStoreStateMachine→com.databricks.caching.util.EtcdWatcher.EtcdWatcherStateMachine.Eventcom.databricks.dicer.assigner.KeyOfDeathDetector→com.databricks.caching.util.EtcdWatcher.EtcdWatcherStateMachine.DriverActioncom.databricks.dicer.assigner.KeyOfDeathDetector→com.databricks.caching.util.EtcdWatcher.EtcdWatcherStateMachine.Eventcom.databricks.dicer.assigner.TargetMigratorImpl→com.databricks.caching.util.EtcdWatcher.EtcdWatcherStateMachine.DriverActioncom.databricks.dicer.assigner.TargetMigratorImpl→com.databricks.caching.util.EtcdWatcher.EtcdWatcherStateMachine.Eventcom.databricks.dicer.assigner.TargetMigratorStateMachine→com.databricks.caching.util.EtcdWatcher.EtcdWatcherStateMachine.DriverActioncom.databricks.dicer.assigner.TargetMigratorStateMachine→com.databricks.caching.util.EtcdWatcher.EtcdWatcherStateMachine.Event
- Direction
- dicer.assigner uses caching.util.EtcdWatcher.EtcdWatcherStateMachine, so a change to caching.util.EtcdWatcher.EtcdWatcherStateMachine can break dicer.assigner, while a change to dicer.assigner can't break caching.util.EtcdWatcher.EtcdWatcherStateMachine.
- Position
- Below the diagonal: dicer.assigner uses a module listed above it, which is the healthy direction.
37→2 dicer.assigner uses caching.util.SafeCounter✕
- Connections
- 1 pair of types, where a type in dicer.assigner uses a type in caching.util.SafeCounter.
- The types involved
com.databricks.dicer.assigner.KubernetesMembershipChecker→com.databricks.caching.util.SafeCounter.Child
- Direction
- dicer.assigner uses caching.util.SafeCounter, so a change to caching.util.SafeCounter can break dicer.assigner, while a change to dicer.assigner can't break caching.util.SafeCounter.
- Position
- Below the diagonal: dicer.assigner uses a module listed above it, which is the healthy direction.
37→3 dicer.assigner uses dicer.assigner.Store✕
- Connections
- 3 pairs of types, where a type in dicer.assigner uses a type in dicer.assigner.Store.
- The types involved
com.databricks.dicer.assigner.AssignmentGenerator→com.databricks.dicer.assigner.Store.WriteAssignmentResultcom.databricks.dicer.assigner.InMemoryStore→com.databricks.dicer.assigner.Store.WriteAssignmentResultcom.databricks.dicer.assigner.Store→com.databricks.dicer.assigner.Store.WriteAssignmentResult
- Direction
- dicer.assigner uses dicer.assigner.Store, so a change to dicer.assigner.Store can break dicer.assigner, while a change to dicer.assigner can't break dicer.assigner.Store.
- Position
- Below the diagonal: dicer.assigner uses a module listed above it, which is the healthy direction.
37→4 dicer.assigner uses rpc✕
- Connections
- 2 pairs of types, where a type in dicer.assigner uses a type in rpc.
- The types involved
com.databricks.dicer.assigner.Assigner→com.databricks.rpc.DatabricksServerWrappercom.databricks.dicer.assigner.Assigner→com.databricks.rpc.RPCContext
- Direction
- dicer.assigner uses rpc, so a change to rpc can break dicer.assigner, while a change to dicer.assigner can't break rpc.
- Position
- Below the diagonal: dicer.assigner uses a module listed above it, which is the healthy direction.
37→5 dicer.assigner uses caching.util.SequentialExecutionContext✕
- Connections
- 1 pair of types, where a type in dicer.assigner uses a type in caching.util.SequentialExecutionContext.
- The types involved
com.databricks.dicer.assigner.KeyOfDeathDetector→com.databricks.caching.util.SequentialExecutionContext.State
- Direction
- dicer.assigner uses caching.util.SequentialExecutionContext, so a change to caching.util.SequentialExecutionContext can break dicer.assigner, while a change to dicer.assigner can't break caching.util.SequentialExecutionContext.
- Position
- Below the diagonal: dicer.assigner uses a module listed above it, which is the healthy direction.
37→8 dicer.assigner uses dicer.common.SliceletData✕
- Connections
- 3 pairs of types, where a type in dicer.assigner uses a type in dicer.common.SliceletData.
- The types involved
com.databricks.dicer.assigner.LoadWatcher→com.databricks.dicer.common.SliceletData.KeyLoadcom.databricks.dicer.assigner.LoadWatcher→com.databricks.dicer.common.SliceletData.LoadDistributioncom.databricks.dicer.assigner.WeightedLoadDistributionAggregator→com.databricks.dicer.common.SliceletData.LoadDistribution
- Direction
- dicer.assigner uses dicer.common.SliceletData, so a change to dicer.common.SliceletData can break dicer.assigner, while a change to dicer.assigner can't break dicer.common.SliceletData.
- Position
- Below the diagonal: dicer.assigner uses a module listed above it, which is the healthy direction.
37→9 dicer.assigner uses caching.util.WatchCell✕
- Connections
- 2 pairs of types, where a type in dicer.assigner uses a type in caching.util.WatchCell.
- The types involved
com.databricks.dicer.assigner.ConsistentHashingPreferredAssignerDriver→com.databricks.caching.util.WatchCell.Consumercom.databricks.dicer.assigner.KubernetesMembershipChecker→com.databricks.caching.util.WatchCell.Consumer
- Direction
- dicer.assigner uses caching.util.WatchCell, so a change to caching.util.WatchCell can break dicer.assigner, while a change to dicer.assigner can't break caching.util.WatchCell.
- Position
- Below the diagonal: dicer.assigner uses a module listed above it, which is the healthy direction.
37→11 dicer.assigner uses dicer.friend✕
- Connections
- 1 pair of types, where a type in dicer.assigner uses a type in dicer.friend.
- The types involved
com.databricks.dicer.assigner.TargetMetrics→com.databricks.dicer.friend.Squid
- Direction
- dicer.assigner uses dicer.friend, so a change to dicer.friend can break dicer.assigner, while a change to dicer.assigner can't break dicer.friend.
- Position
- Below the diagonal: dicer.assigner uses a module listed above it, which is the healthy direction.
37→12 dicer.assigner uses caching.util✕
- Connections
- 60 pairs of types, where a type in dicer.assigner uses a type in caching.util. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.databricks.dicer.assigner.Assigner→com.databricks.caching.util.SequentialExecutionContextPoolcom.databricks.dicer.assigner.AssignmentGenerator→com.databricks.caching.util.StateMachinecom.databricks.dicer.assigner.AssignmentGenerator→com.databricks.caching.util.StateMachineOutputcom.databricks.dicer.assigner.AssignmentGenerator→com.databricks.caching.util.TickerTimecom.databricks.dicer.assigner.AssignmentGeneratorDriver→com.databricks.caching.util.Cancellablecom.databricks.dicer.assigner.ConsistentHashingPreferredAssignerDriver→com.databricks.caching.util.Cancellablecom.databricks.dicer.assigner.ConsistentHashingPreferredAssignerDriver→com.databricks.caching.util.PrefixLoggercom.databricks.dicer.assigner.ConsistentHashingPreferredAssignerDriver→com.databricks.caching.util.StateMachineDrivercom.databricks.dicer.assigner.ConsistentHashingPreferredAssignerDriver→com.databricks.caching.util.ValueStreamCallbackcom.databricks.dicer.assigner.ConsistentHashingPreferredAssignerDriver→com.databricks.caching.util.WatchValueCellcom.databricks.dicer.assigner.ConsistentHashingPreferredAssignerStateMachine→com.databricks.caching.util.ConsistentHashRingcom.databricks.dicer.assigner.ConsistentHashingPreferredAssignerStateMachine→com.databricks.caching.util.PrefixLoggercom.databricks.dicer.assigner.ConsistentHashingPreferredAssignerStateMachine→com.databricks.caching.util.StateMachinecom.databricks.dicer.assigner.ConsistentHashingPreferredAssignerStateMachine→com.databricks.caching.util.StateMachineOutputcom.databricks.dicer.assigner.ConsistentHashingPreferredAssignerStateMachine→com.databricks.caching.util.TickerTimecom.databricks.dicer.assigner.DicerSimulatorEventLogEmitter→com.databricks.caching.util.SequentialExecutionContextcom.databricks.dicer.assigner.DisabledPreferredAssignerDriver→com.databricks.caching.util.Cancellablecom.databricks.dicer.assigner.DisabledPreferredAssignerDriver→com.databricks.caching.util.ValueStreamCallbackcom.databricks.dicer.assigner.DisabledPreferredAssignerDriver→com.databricks.caching.util.WatchValueCellcom.databricks.dicer.assigner.EtcdPreferredAssignerDriver→com.databricks.caching.util.Cancellablecom.databricks.dicer.assigner.EtcdPreferredAssignerDriver→com.databricks.caching.util.StateMachineDrivercom.databricks.dicer.assigner.EtcdPreferredAssignerDriver→com.databricks.caching.util.ValueStreamCallbackcom.databricks.dicer.assigner.EtcdPreferredAssignerStateMachine→com.databricks.caching.util.StateMachinecom.databricks.dicer.assigner.EtcdPreferredAssignerStateMachine→com.databricks.caching.util.StateMachineOutputcom.databricks.dicer.assigner.EtcdPreferredAssignerStateMachine→com.databricks.caching.util.TickerTime
- Direction
- dicer.assigner uses caching.util, so a change to caching.util can break dicer.assigner, while a change to dicer.assigner can't break caching.util.
- Position
- Below the diagonal: dicer.assigner uses a module listed above it, which is the healthy direction.
37→14 dicer.assigner uses caching.util.EtcdClient✕
- Connections
- 4 pairs of types, where a type in dicer.assigner uses a type in caching.util.EtcdClient.
- The types involved
com.databricks.dicer.assigner.EtcdPreferredAssignerStoreStateMachine→com.databricks.caching.util.EtcdClient.Versioncom.databricks.dicer.assigner.EtcdPreferredAssignerStoreStateMachine→com.databricks.caching.util.EtcdClient.WatchEventcom.databricks.dicer.assigner.EtcdPreferredAssignerStoreStateMachine→com.databricks.caching.util.EtcdClient.WriteResponsecom.databricks.dicer.assigner.KeyOfDeathDetector→com.databricks.caching.util.EtcdClient.Config
- Direction
- dicer.assigner uses caching.util.EtcdClient, so a change to caching.util.EtcdClient can break dicer.assigner, while a change to dicer.assigner can't break caching.util.EtcdClient.
- Position
- Below the diagonal: dicer.assigner uses a module listed above it, which is the healthy direction.
37→15 dicer.assigner uses caching.util.StateMachineOutput✕
- Connections
- 6 pairs of types, where a type in dicer.assigner uses a type in caching.util.StateMachineOutput.
- The types involved
com.databricks.dicer.assigner.AssignmentGenerator→com.databricks.caching.util.StateMachineOutput.Buildercom.databricks.dicer.assigner.ConsistentHashingPreferredAssignerStateMachine→com.databricks.caching.util.StateMachineOutput.Buildercom.databricks.dicer.assigner.EtcdPreferredAssignerStateMachine→com.databricks.caching.util.StateMachineOutput.Buildercom.databricks.dicer.assigner.EtcdPreferredAssignerStoreStateMachine→com.databricks.caching.util.StateMachineOutput.Buildercom.databricks.dicer.assigner.KeyOfDeathDetector→com.databricks.caching.util.StateMachineOutput.Buildercom.databricks.dicer.assigner.TargetMigratorStateMachine→com.databricks.caching.util.StateMachineOutput.Builder
- Direction
- dicer.assigner uses caching.util.StateMachineOutput, so a change to caching.util.StateMachineOutput can break dicer.assigner, while a change to dicer.assigner can't break caching.util.StateMachineOutput.
- Position
- Below the diagonal: dicer.assigner uses a module listed above it, which is the healthy direction.
37→17 dicer.assigner uses com.databricks✕
- Connections
- 1 pair of types, where a type in dicer.assigner uses a type in com.databricks.
- The types involved
com.databricks.dicer.assigner.AssignerMainBase→com.databricks.DatabricksMain
- Direction
- dicer.assigner uses com.databricks, so a change to com.databricks can break dicer.assigner, while a change to dicer.assigner can't break com.databricks.
- Position
- Below the diagonal: dicer.assigner uses a module listed above it, which is the healthy direction.
37→19 dicer.assigner uses dicer.common✕
- Connections
- 32 pairs of types, where a type in dicer.assigner uses a type in dicer.common. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.databricks.dicer.assigner.Assigner→com.databricks.dicer.common.ClientRequestcom.databricks.dicer.assigner.Assigner→com.databricks.dicer.common.ClientTypecom.databricks.dicer.assigner.Assigner→com.databricks.dicer.common.Redirectcom.databricks.dicer.assigner.AssignerProtoLogger→com.databricks.dicer.common.Assignmentcom.databricks.dicer.assigner.AssignerProtoLogger→com.databricks.dicer.common.SliceKeySensitivitycom.databricks.dicer.assigner.AssignerSlicezData→com.databricks.dicer.common.SlicezDatacom.databricks.dicer.assigner.AssignerTargetSlicezData→com.databricks.dicer.common.Assignmentcom.databricks.dicer.assigner.AssignerTargetSlicezData→com.databricks.dicer.common.ClerkSubscriberSlicezDatacom.databricks.dicer.assigner.AssignerTargetSlicezData→com.databricks.dicer.common.SliceletSubscriberSlicezDatacom.databricks.dicer.assigner.AssignerTargetSlicezData→com.databricks.dicer.common.TargetSlicezDatacom.databricks.dicer.assigner.AssignmentGenerator→com.databricks.dicer.common.Assignmentcom.databricks.dicer.assigner.AssignmentGenerator→com.databricks.dicer.common.ClientRequestcom.databricks.dicer.assigner.AssignmentGenerator→com.databricks.dicer.common.SyncAssignmentStatecom.databricks.dicer.assigner.AssignmentGeneratorDriver→com.databricks.dicer.common.ClientRequestcom.databricks.dicer.assigner.DicerSimulatorEventEmitter→com.databricks.dicer.common.SliceKeySensitivitycom.databricks.dicer.assigner.EtcdPreferredAssignerStore→com.databricks.dicer.common.Incarnationcom.databricks.dicer.assigner.EtcdPreferredAssignerStoreStateMachine→com.databricks.dicer.common.Generationcom.databricks.dicer.assigner.InMemoryStore→com.databricks.dicer.common.Assignmentcom.databricks.dicer.assigner.InMemoryStore→com.databricks.dicer.common.Generationcom.databricks.dicer.assigner.InMemoryStore→com.databricks.dicer.common.Incarnationcom.databricks.dicer.assigner.InMemoryStore→com.databricks.dicer.common.ProposedAssignmentcom.databricks.dicer.assigner.LoadWatcher→com.databricks.dicer.common.Assignmentcom.databricks.dicer.assigner.NoopAssignerProtoLogger→com.databricks.dicer.common.Assignmentcom.databricks.dicer.assigner.NoopAssignerProtoLogger→com.databricks.dicer.common.SliceKeySensitivitycom.databricks.dicer.assigner.PreferredAssignerMetrics→com.databricks.dicer.common.Generation
- Direction
- dicer.assigner uses dicer.common, so a change to dicer.common can break dicer.assigner, while a change to dicer.assigner can't break dicer.common.
- Position
- Below the diagonal: dicer.assigner uses a module listed above it, which is the healthy direction.
37→20 dicer.assigner uses dicer.assigner.EtcdPreferredAssignerStore✕
- Connections
- 6 pairs of types, where a type in dicer.assigner uses a type in dicer.assigner.EtcdPreferredAssignerStore.
- The types involved
com.databricks.dicer.assigner.EtcdPreferredAssignerStateMachine→com.databricks.dicer.assigner.EtcdPreferredAssignerStore.PreferredAssignerProposalcom.databricks.dicer.assigner.EtcdPreferredAssignerStateMachine→com.databricks.dicer.assigner.EtcdPreferredAssignerStore.WriteResultcom.databricks.dicer.assigner.EtcdPreferredAssignerStore→com.databricks.dicer.assigner.EtcdPreferredAssignerStore.PreferredAssignerProposalcom.databricks.dicer.assigner.EtcdPreferredAssignerStore→com.databricks.dicer.assigner.EtcdPreferredAssignerStore.WriteResultcom.databricks.dicer.assigner.EtcdPreferredAssignerStoreStateMachine→com.databricks.dicer.assigner.EtcdPreferredAssignerStore.PreferredAssignerProposalcom.databricks.dicer.assigner.EtcdPreferredAssignerStoreStateMachine→com.databricks.dicer.assigner.EtcdPreferredAssignerStore.WriteResult
- Direction
- dicer.assigner uses dicer.assigner.EtcdPreferredAssignerStore, so a change to dicer.assigner.EtcdPreferredAssignerStore can break dicer.assigner, while a change to dicer.assigner can't break dicer.assigner.EtcdPreferredAssignerStore.
- Position
- Below the diagonal: dicer.assigner uses a module listed above it, which is the healthy direction.
37→21 dicer.assigner uses dicer.assigner.conf✕
- Connections
- 3 pairs of types, where a type in dicer.assigner uses a type in dicer.assigner.conf.
- The types involved
com.databricks.dicer.assigner.Assigner→com.databricks.dicer.assigner.conf.DicerAssignerConfcom.databricks.dicer.assigner.AssignerMainBase→com.databricks.dicer.assigner.conf.DicerAssignerConfcom.databricks.dicer.assigner.RemoteMembershipCheckerFactory→com.databricks.dicer.assigner.conf.DicerAssignerConf
- Direction
- dicer.assigner uses dicer.assigner.conf, so a change to dicer.assigner.conf can break dicer.assigner, while a change to dicer.assigner can't break dicer.assigner.conf.
- Position
- Below the diagonal: dicer.assigner uses a module listed above it, which is the healthy direction.
37→25 dicer.assigner uses dicer.assigner.config✕
- Connections
- 14 pairs of types, where a type in dicer.assigner uses a type in dicer.assigner.config.
- The types involved
com.databricks.dicer.assigner.Assigner→com.databricks.dicer.assigner.config.TargetConfigProvidercom.databricks.dicer.assigner.AssignerTargetSlicezData→com.databricks.dicer.assigner.config.NamedInternalTargetConfigcom.databricks.dicer.assigner.AssignmentGeneratorDriver→com.databricks.dicer.assigner.config.InternalTargetConfigcom.databricks.dicer.assigner.GossipRequest→com.databricks.dicer.assigner.config.TargetMigrationConfigcom.databricks.dicer.assigner.GossipResponse→com.databricks.dicer.assigner.config.TargetMigrationConfigcom.databricks.dicer.assigner.GossipValues→com.databricks.dicer.assigner.config.TargetMigrationConfigcom.databricks.dicer.assigner.TargetMigrationRoleResolver→com.databricks.dicer.assigner.config.TargetMigrationRolecom.databricks.dicer.assigner.TargetMigrationRoleResolver→com.databricks.dicer.assigner.config.TargetMigrationTypecom.databricks.dicer.assigner.TargetMigrator→com.databricks.dicer.assigner.config.TargetMigrationConfigcom.databricks.dicer.assigner.TargetMigratorImpl→com.databricks.dicer.assigner.config.TargetMigrationConfigcom.databricks.dicer.assigner.TargetMigratorStateMachine→com.databricks.dicer.assigner.config.TargetMigrationConfigcom.databricks.dicer.assigner.TargetOwnershipResolver→com.databricks.dicer.assigner.config.TargetMigrationConfigcom.databricks.dicer.assigner.TargetOwnershipResolver→com.databricks.dicer.assigner.config.TargetMigrationRolecom.databricks.dicer.assigner.WatchRequestRateLimitingStrategy→com.databricks.dicer.assigner.config.InternalTargetConfigMap
- Direction
- dicer.assigner uses dicer.assigner.config, so a change to dicer.assigner.config can break dicer.assigner, while a change to dicer.assigner can't break dicer.assigner.config.
- Position
- Below the diagonal: dicer.assigner uses a module listed above it, which is the healthy direction.
37→27 dicer.assigner uses dicer.assigner.TargetMigratorStateMachine✕
- Connections
- 1 pair of types, where a type in dicer.assigner uses a type in dicer.assigner.TargetMigratorStateMachine.
- The types involved
com.databricks.dicer.assigner.TargetMigratorStateMachine→com.databricks.dicer.assigner.TargetMigratorStateMachine.MigratorState
- Direction
- dicer.assigner uses dicer.assigner.TargetMigratorStateMachine, so a change to dicer.assigner.TargetMigratorStateMachine can break dicer.assigner, while a change to dicer.assigner can't break dicer.assigner.TargetMigratorStateMachine.
- Position
- Below the diagonal: dicer.assigner uses a module listed above it, which is the healthy direction.
37→28 dicer.assigner uses dicer.assigner.algorithm.Algorithm✕
- Connections
- 1 pair of types, where a type in dicer.assigner uses a type in dicer.assigner.algorithm.Algorithm.
- The types involved
com.databricks.dicer.assigner.TargetMetrics→com.databricks.dicer.assigner.algorithm.Algorithm.DesiredLoadRange
- Direction
- dicer.assigner uses dicer.assigner.algorithm.Algorithm, so a change to dicer.assigner.algorithm.Algorithm can break dicer.assigner, while a change to dicer.assigner can't break dicer.assigner.algorithm.Algorithm.
- Position
- Below the diagonal: dicer.assigner uses a module listed above it, which is the healthy direction.
37→29 dicer.assigner uses dicer.assigner.algorithm✕
- Connections
- 3 pairs of types, where a type in dicer.assigner uses a type in dicer.assigner.algorithm.
- The types involved
com.databricks.dicer.assigner.AssignmentGenerator→com.databricks.dicer.assigner.algorithm.Resourcescom.databricks.dicer.assigner.TargetMetrics→com.databricks.dicer.assigner.algorithm.LoadMapcom.databricks.dicer.assigner.TargetMetrics→com.databricks.dicer.assigner.algorithm.Resources
- Direction
- dicer.assigner uses dicer.assigner.algorithm, so a change to dicer.assigner.algorithm can break dicer.assigner, while a change to dicer.assigner can't break dicer.assigner.algorithm.
- Position
- Below the diagonal: dicer.assigner uses a module listed above it, which is the healthy direction.
37→31 dicer.assigner uses dicer.external✕
- Connections
- 16 pairs of types, where a type in dicer.assigner uses a type in dicer.external.
- The types involved
com.databricks.dicer.assigner.Assigner→com.databricks.dicer.external.Targetcom.databricks.dicer.assigner.AssignerProtoLogger→com.databricks.dicer.external.Targetcom.databricks.dicer.assigner.AssignerTargetSlicezData→com.databricks.dicer.external.Targetcom.databricks.dicer.assigner.DicerSimulatorEventEmitter→com.databricks.dicer.external.Targetcom.databricks.dicer.assigner.InMemoryStore→com.databricks.dicer.external.Targetcom.databricks.dicer.assigner.KeyOfDeathDetector→com.databricks.dicer.external.Targetcom.databricks.dicer.assigner.LoadWatcher→com.databricks.dicer.external.ResourceAddresscom.databricks.dicer.assigner.LoadWatcher→com.databricks.dicer.external.Slicecom.databricks.dicer.assigner.NoopAssignerProtoLogger→com.databricks.dicer.external.Targetcom.databricks.dicer.assigner.SliceKeyMath→com.databricks.dicer.external.HighSliceKeycom.databricks.dicer.assigner.Store→com.databricks.dicer.external.Targetcom.databricks.dicer.assigner.TargetMetrics→com.databricks.dicer.external.AppTargetcom.databricks.dicer.assigner.TargetMetrics→com.databricks.dicer.external.Targetcom.databricks.dicer.assigner.TargetOwnershipResolver→com.databricks.dicer.external.Targetcom.databricks.dicer.assigner.WeightedLoadDistributionAggregator→com.databricks.dicer.external.HighSliceKeycom.databricks.dicer.assigner.WeightedLoadDistributionAggregator→com.databricks.dicer.external.SliceKey
- Direction
- dicer.assigner uses dicer.external, so a change to dicer.external can break dicer.assigner, while a change to dicer.assigner can't break dicer.external.
- Position
- Below the diagonal: dicer.assigner uses a module listed above it, which is the healthy direction.
37→32 dicer.assigner uses dicer.assigner.HealthWatcher✕
- Connections
- 2 pairs of types, where a type in dicer.assigner uses a type in dicer.assigner.HealthWatcher.
- The types involved
com.databricks.dicer.assigner.FakeKubernetesTargetWatcherFactory→com.databricks.dicer.assigner.HealthWatcher.Factorycom.databricks.dicer.assigner.RemoteMembershipCheckerFactory→com.databricks.dicer.assigner.HealthWatcher.Factory
- Direction
- dicer.assigner uses dicer.assigner.HealthWatcher, so a change to dicer.assigner.HealthWatcher can break dicer.assigner, while a change to dicer.assigner can't break dicer.assigner.HealthWatcher.
- Position
- Below the diagonal: dicer.assigner uses a module listed above it, which is the healthy direction.
37→33 dicer.assigner uses dicer.assigner.TargetMetrics✕
- Connections
- 10 pairs of types, where a type in dicer.assigner uses a type in dicer.assigner.TargetMetrics.
- The types involved
com.databricks.dicer.assigner.Assigner→com.databricks.dicer.assigner.TargetMetrics.GeneratorShutdownReasoncom.databricks.dicer.assigner.AssignmentGenerator→com.databricks.dicer.assigner.TargetMetrics.AssignmentDistributionSourcecom.databricks.dicer.assigner.HealthWatcher→com.databricks.dicer.assigner.TargetMetrics.AssignmentDistributionSourcecom.databricks.dicer.assigner.TargetMetrics→com.databricks.dicer.assigner.TargetMetrics.AssignmentDistributionSourcecom.databricks.dicer.assigner.TargetMetrics→com.databricks.dicer.assigner.TargetMetrics.AssignmentGeneratorOpTypecom.databricks.dicer.assigner.TargetMetrics→com.databricks.dicer.assigner.TargetMetrics.ChurnRatioMetriccom.databricks.dicer.assigner.TargetMetrics→com.databricks.dicer.assigner.TargetMetrics.GeneratorShutdownReasoncom.databricks.dicer.assigner.TargetMetrics→com.databricks.dicer.assigner.TargetMetrics.IncarnationMismatchTypecom.databricks.dicer.assigner.TargetMetrics→com.databricks.dicer.assigner.TargetMetrics.KeyOfDeathTransitionTypecom.databricks.dicer.assigner.TargetMetrics→com.databricks.dicer.assigner.TargetMetrics.LoadDistributionHistogramBucket
- Direction
- dicer.assigner uses dicer.assigner.TargetMetrics, so a change to dicer.assigner.TargetMetrics can break dicer.assigner, while a change to dicer.assigner can't break dicer.assigner.TargetMetrics.
- Position
- Below the diagonal: dicer.assigner uses a module listed above it, which is the healthy direction.
37→34 dicer.assigner uses dicer.assigner.Assigner✕
- Connections
- 1 pair of types, where a type in dicer.assigner uses a type in dicer.assigner.Assigner.
- The types involved
com.databricks.dicer.assigner.Assigner→com.databricks.dicer.assigner.Assigner.TargetManager
- Direction
- dicer.assigner uses dicer.assigner.Assigner, so a change to dicer.assigner.Assigner can break dicer.assigner, while a change to dicer.assigner can't break dicer.assigner.Assigner.
- Position
- Below the diagonal: dicer.assigner uses a module listed above it, which is the healthy direction.
37→35 dicer.assigner uses dicer.assigner.AssignmentGenerator✕
- Connections
- 8 pairs of types, where a type in dicer.assigner uses a type in dicer.assigner.AssignmentGenerator.
- The types involved
com.databricks.dicer.assigner.AssignerProtoLogger→com.databricks.dicer.assigner.AssignmentGenerator.AssignmentGenerationContextcom.databricks.dicer.assigner.AssignerTargetSlicezData→com.databricks.dicer.assigner.AssignmentGenerator.GeneratorTargetSlicezDatacom.databricks.dicer.assigner.AssignmentGenerator→com.databricks.dicer.assigner.AssignmentGenerator.AssignmentGenerationContextcom.databricks.dicer.assigner.AssignmentGenerator→com.databricks.dicer.assigner.AssignmentGenerator.AssignmentGenerationDecisioncom.databricks.dicer.assigner.AssignmentGenerator→com.databricks.dicer.assigner.AssignmentGenerator.GeneratorTargetSlicezDatacom.databricks.dicer.assigner.AssignmentGeneratorDriver→com.databricks.dicer.assigner.AssignmentGenerator.GeneratorTargetSlicezDatacom.databricks.dicer.assigner.NoopAssignerProtoLogger→com.databricks.dicer.assigner.AssignmentGenerator.AssignmentGenerationContextcom.databricks.dicer.assigner.TargetMetrics→com.databricks.dicer.assigner.AssignmentGenerator.AssignmentGenerationDecision
- Direction
- dicer.assigner uses dicer.assigner.AssignmentGenerator, so a change to dicer.assigner.AssignmentGenerator can break dicer.assigner, while a change to dicer.assigner can't break dicer.assigner.AssignmentGenerator.
- Position
- Below the diagonal: dicer.assigner uses a module listed above it, which is the healthy direction.
37→36 dicer.assigner uses dicer.assigner.KubernetesMembershipChecker✕
- Connections
- 6 pairs of types, where a type in dicer.assigner uses a type in dicer.assigner.KubernetesMembershipChecker.
- The types involved
com.databricks.dicer.assigner.ConsistentHashingPreferredAssignerStateMachine→com.databricks.dicer.assigner.KubernetesMembershipChecker.ResourceVersioncom.databricks.dicer.assigner.KubernetesMembershipChecker→com.databricks.dicer.assigner.KubernetesMembershipChecker.CheckerStatecom.databricks.dicer.assigner.KubernetesMembershipChecker→com.databricks.dicer.assigner.KubernetesMembershipChecker.KubernetesConnectionHealthMonitorcom.databricks.dicer.assigner.KubernetesMembershipChecker→com.databricks.dicer.assigner.KubernetesMembershipChecker.PollOutcomecom.databricks.dicer.assigner.KubernetesMembershipChecker→com.databricks.dicer.assigner.KubernetesMembershipChecker.VersionedResourceSetcom.databricks.dicer.assigner.TargetMigratorStateMachine→com.databricks.dicer.assigner.KubernetesMembershipChecker.VersionedResourceSet
- Direction
- dicer.assigner uses dicer.assigner.KubernetesMembershipChecker, so a change to dicer.assigner.KubernetesMembershipChecker can break dicer.assigner, while a change to dicer.assigner can't break dicer.assigner.KubernetesMembershipChecker.
- Position
- Below the diagonal: dicer.assigner uses a module listed above it, which is the healthy direction.
38→1 dicer.assigner.EtcdPreferredAssignerStateMachine.RunState uses caching.util.EtcdWatcher.EtcdWatcherStateMachine✕
- Connections
- 4 pairs of types, where a type in dicer.assigner.EtcdPreferredAssignerStateMachine.RunState uses a type in caching.util.EtcdWatcher.EtcdWatcherStateMachine.
- The types involved
com.databricks.dicer.assigner.EtcdPreferredAssignerStateMachine.RunState.Preferred→com.databricks.caching.util.EtcdWatcher.EtcdWatcherStateMachine.RunStatecom.databricks.dicer.assigner.EtcdPreferredAssignerStateMachine.RunState.Standby→com.databricks.caching.util.EtcdWatcher.EtcdWatcherStateMachine.RunStatecom.databricks.dicer.assigner.EtcdPreferredAssignerStateMachine.RunState.StandbyWithoutPreferred→com.databricks.caching.util.EtcdWatcher.EtcdWatcherStateMachine.RunStatecom.databricks.dicer.assigner.EtcdPreferredAssignerStateMachine.RunState.Startup→com.databricks.caching.util.EtcdWatcher.EtcdWatcherStateMachine.RunState
- Direction
- dicer.assigner.EtcdPreferredAssignerStateMachine.RunState uses caching.util.EtcdWatcher.EtcdWatcherStateMachine, so a change to caching.util.EtcdWatcher.EtcdWatcherStateMachine can break dicer.assigner.EtcdPreferredAssignerStateMachine.RunState, while a change to dicer.assigner.EtcdPreferredAssignerStateMachine.RunState can't break caching.util.EtcdWatcher.EtcdWatcherStateMachine.
- Position
- Below the diagonal: dicer.assigner.EtcdPreferredAssignerStateMachine.RunState uses a module listed above it, which is the healthy direction.
38→12 dicer.assigner.EtcdPreferredAssignerStateMachine.RunState uses caching.util✕
- Connections
- 1 pair of types, where a type in dicer.assigner.EtcdPreferredAssignerStateMachine.RunState uses a type in caching.util.
- The types involved
com.databricks.dicer.assigner.EtcdPreferredAssignerStateMachine.RunState.Startup→com.databricks.caching.util.TickerTime
- Direction
- dicer.assigner.EtcdPreferredAssignerStateMachine.RunState uses caching.util, so a change to caching.util can break dicer.assigner.EtcdPreferredAssignerStateMachine.RunState, while a change to dicer.assigner.EtcdPreferredAssignerStateMachine.RunState can't break caching.util.
- Position
- Below the diagonal: dicer.assigner.EtcdPreferredAssignerStateMachine.RunState uses a module listed above it, which is the healthy direction.
38→19 dicer.assigner.EtcdPreferredAssignerStateMachine.RunState uses dicer.common✕
- Connections
- 4 pairs of types, where a type in dicer.assigner.EtcdPreferredAssignerStateMachine.RunState uses a type in dicer.common.
- The types involved
com.databricks.dicer.assigner.EtcdPreferredAssignerStateMachine.RunState.Preferred→com.databricks.dicer.common.Generationcom.databricks.dicer.assigner.EtcdPreferredAssignerStateMachine.RunState.Standby→com.databricks.dicer.common.Generationcom.databricks.dicer.assigner.EtcdPreferredAssignerStateMachine.RunState.StandbyWithoutPreferred→com.databricks.dicer.common.Generationcom.databricks.dicer.assigner.EtcdPreferredAssignerStateMachine.RunState.Startup→com.databricks.dicer.common.Generation
- Direction
- dicer.assigner.EtcdPreferredAssignerStateMachine.RunState uses dicer.common, so a change to dicer.common can break dicer.assigner.EtcdPreferredAssignerStateMachine.RunState, while a change to dicer.assigner.EtcdPreferredAssignerStateMachine.RunState can't break dicer.common.
- Position
- Below the diagonal: dicer.assigner.EtcdPreferredAssignerStateMachine.RunState uses a module listed above it, which is the healthy direction.
38→37 dicer.assigner.EtcdPreferredAssignerStateMachine.RunState uses dicer.assigner✕
- Connections
- 1 pair of types, where a type in dicer.assigner.EtcdPreferredAssignerStateMachine.RunState uses a type in dicer.assigner.
- The types involved
com.databricks.dicer.assigner.EtcdPreferredAssignerStateMachine.RunState.Standby→com.databricks.dicer.assigner.AssignerInfo
- Direction
- dicer.assigner.EtcdPreferredAssignerStateMachine.RunState uses dicer.assigner, so a change to dicer.assigner can break dicer.assigner.EtcdPreferredAssignerStateMachine.RunState, while a change to dicer.assigner.EtcdPreferredAssignerStateMachine.RunState can't break dicer.assigner.
- Position
- Below the diagonal: dicer.assigner.EtcdPreferredAssignerStateMachine.RunState uses a module listed above it, which is the healthy direction.
39→4 dicer.assigner.testing uses rpc✕
- Connections
- 1 pair of types, where a type in dicer.assigner.testing uses a type in rpc.
- The types involved
com.databricks.dicer.assigner.testing.PreferredAssignerTestUtils→com.databricks.rpc.RPCContext
- Direction
- dicer.assigner.testing uses rpc, so a change to rpc can break dicer.assigner.testing, while a change to dicer.assigner.testing can't break rpc.
- Position
- Below the diagonal: dicer.assigner.testing uses a module listed above it, which is the healthy direction.
39→11 dicer.assigner.testing uses dicer.friend✕
- Connections
- 1 pair of types, where a type in dicer.assigner.testing uses a type in dicer.friend.
- The types involved
com.databricks.dicer.assigner.testing.PreferredAssignerTestUtils→com.databricks.dicer.friend.Squid
- Direction
- dicer.assigner.testing uses dicer.friend, so a change to dicer.friend can break dicer.assigner.testing, while a change to dicer.assigner.testing can't break dicer.friend.
- Position
- Below the diagonal: dicer.assigner.testing uses a module listed above it, which is the healthy direction.
39→12 dicer.assigner.testing uses caching.util✕
- Connections
- 2 pairs of types, where a type in dicer.assigner.testing uses a type in caching.util.
- The types involved
com.databricks.dicer.assigner.testing.FakeKubernetesServer→com.databricks.caching.util.WatchValueCellcom.databricks.dicer.assigner.testing.PreferredAssignerTestUtils→com.databricks.caching.util.SequentialExecutionContext
- Direction
- dicer.assigner.testing uses caching.util, so a change to caching.util can break dicer.assigner.testing, while a change to dicer.assigner.testing can't break caching.util.
- Position
- Below the diagonal: dicer.assigner.testing uses a module listed above it, which is the healthy direction.
39→14 dicer.assigner.testing uses caching.util.EtcdClient✕
- Connections
- 1 pair of types, where a type in dicer.assigner.testing uses a type in caching.util.EtcdClient.
- The types involved
com.databricks.dicer.assigner.testing.PreferredAssignerTestUtils→com.databricks.caching.util.EtcdClient.Config
- Direction
- dicer.assigner.testing uses caching.util.EtcdClient, so a change to caching.util.EtcdClient can break dicer.assigner.testing, while a change to dicer.assigner.testing can't break caching.util.EtcdClient.
- Position
- Below the diagonal: dicer.assigner.testing uses a module listed above it, which is the healthy direction.
39→19 dicer.assigner.testing uses dicer.common✕
- Connections
- 3 pairs of types, where a type in dicer.assigner.testing uses a type in dicer.common.
- The types involved
com.databricks.dicer.assigner.testing.PreferredAssignerTestUtils→com.databricks.dicer.common.ClientRequestcom.databricks.dicer.assigner.testing.PreferredAssignerTestUtils→com.databricks.dicer.common.Incarnationcom.databricks.dicer.assigner.testing.PreferredAssignerTestUtils→com.databricks.dicer.common.Redirect
- Direction
- dicer.assigner.testing uses dicer.common, so a change to dicer.common can break dicer.assigner.testing, while a change to dicer.assigner.testing can't break dicer.common.
- Position
- Below the diagonal: dicer.assigner.testing uses a module listed above it, which is the healthy direction.
39→30 dicer.assigner.testing uses dicer.common.testing✕
- Connections
- 2 pairs of types, where a type in dicer.assigner.testing uses a type in dicer.common.testing.
- The types involved
com.databricks.dicer.assigner.testing.PreferredAssignerTestUtils→com.databricks.dicer.common.testing.InternalDicerTestEnvironmentcom.databricks.dicer.assigner.testing.PreferredAssignerTestUtils→com.databricks.dicer.common.testing.TestAssigner
- Direction
- dicer.assigner.testing uses dicer.common.testing, so a change to dicer.common.testing can break dicer.assigner.testing, while a change to dicer.assigner.testing can't break dicer.common.testing.
- Position
- Below the diagonal: dicer.assigner.testing uses a module listed above it, which is the healthy direction.
39→31 dicer.assigner.testing uses dicer.external✕
- Connections
- 1 pair of types, where a type in dicer.assigner.testing uses a type in dicer.external.
- The types involved
com.databricks.dicer.assigner.testing.PreferredAssignerTestUtils→com.databricks.dicer.external.Target
- Direction
- dicer.assigner.testing uses dicer.external, so a change to dicer.external can break dicer.assigner.testing, while a change to dicer.assigner.testing can't break dicer.external.
- Position
- Below the diagonal: dicer.assigner.testing uses a module listed above it, which is the healthy direction.
39→32 dicer.assigner.testing uses dicer.assigner.HealthWatcher✕
- Connections
- 2 pairs of types, where a type in dicer.assigner.testing uses a type in dicer.assigner.HealthWatcher.
- The types involved
com.databricks.dicer.assigner.testing.KubernetesTestUtils→com.databricks.dicer.assigner.HealthWatcher.Factorycom.databricks.dicer.assigner.testing.PreferredAssignerTestUtils→com.databricks.dicer.assigner.HealthWatcher.Factory
- Direction
- dicer.assigner.testing uses dicer.assigner.HealthWatcher, so a change to dicer.assigner.HealthWatcher can break dicer.assigner.testing, while a change to dicer.assigner.testing can't break dicer.assigner.HealthWatcher.
- Position
- Below the diagonal: dicer.assigner.testing uses a module listed above it, which is the healthy direction.
39→37 dicer.assigner.testing uses dicer.assigner✕
- Connections
- 4 pairs of types, where a type in dicer.assigner.testing uses a type in dicer.assigner.
- The types involved
com.databricks.dicer.assigner.testing.PreferredAssignerTestUtils→com.databricks.dicer.assigner.MigrationModecom.databricks.dicer.assigner.testing.PreferredAssignerTestUtils→com.databricks.dicer.assigner.PreferredAssignerDrivercom.databricks.dicer.assigner.testing.PreferredAssignerTestUtils→com.databricks.dicer.assigner.PreferredAssignerValuecom.databricks.dicer.assigner.testing.PreferredAssignerTestUtils→com.databricks.dicer.assigner.TargetMigrator
- Direction
- dicer.assigner.testing uses dicer.assigner, so a change to dicer.assigner can break dicer.assigner.testing, while a change to dicer.assigner.testing can't break dicer.assigner.
- Position
- Below the diagonal: dicer.assigner.testing uses a module listed above it, which is the healthy direction.
40→14 dicer.common.testing.TestAssigner uses caching.util.EtcdClient✕
- Connections
- 1 pair of types, where a type in dicer.common.testing.TestAssigner uses a type in caching.util.EtcdClient.
- The types involved
com.databricks.dicer.common.testing.TestAssigner.Config→com.databricks.caching.util.EtcdClient.Config
- Direction
- dicer.common.testing.TestAssigner uses caching.util.EtcdClient, so a change to caching.util.EtcdClient can break dicer.common.testing.TestAssigner, while a change to dicer.common.testing.TestAssigner can't break caching.util.EtcdClient.
- Position
- Below the diagonal: dicer.common.testing.TestAssigner uses a module listed above it, which is the healthy direction.
40→19 dicer.common.testing.TestAssigner uses dicer.common✕
- Connections
- 1 pair of types, where a type in dicer.common.testing.TestAssigner uses a type in dicer.common.
- The types involved
com.databricks.dicer.common.testing.TestAssigner.Config→com.databricks.dicer.common.AssignerServiceInfo
- Direction
- dicer.common.testing.TestAssigner uses dicer.common, so a change to dicer.common can break dicer.common.testing.TestAssigner, while a change to dicer.common.testing.TestAssigner can't break dicer.common.
- Position
- Below the diagonal: dicer.common.testing.TestAssigner uses a module listed above it, which is the healthy direction.
40→22 dicer.common.testing.TestAssigner uses dicer.assigner.config.InternalTargetConfig✕
- Connections
- 1 pair of types, where a type in dicer.common.testing.TestAssigner uses a type in dicer.assigner.config.InternalTargetConfig.
- The types involved
com.databricks.dicer.common.testing.TestAssigner.TestHealthWatcherFactory→com.databricks.dicer.assigner.config.InternalTargetConfig.HealthWatcherTargetConfig
- Direction
- dicer.common.testing.TestAssigner uses dicer.assigner.config.InternalTargetConfig, so a change to dicer.assigner.config.InternalTargetConfig can break dicer.common.testing.TestAssigner, while a change to dicer.common.testing.TestAssigner can't break dicer.assigner.config.InternalTargetConfig.
- Position
- Below the diagonal: dicer.common.testing.TestAssigner uses a module listed above it, which is the healthy direction.
40→30 dicer.common.testing.TestAssigner uses dicer.common.testing✕
- Connections
- 1 pair of types, where a type in dicer.common.testing.TestAssigner uses a type in dicer.common.testing.
- The types involved
com.databricks.dicer.common.testing.TestAssigner.InterceptableStoreFactory→com.databricks.dicer.common.testing.InterceptableStore
- Direction
- dicer.common.testing.TestAssigner uses dicer.common.testing, so a change to dicer.common.testing can break dicer.common.testing.TestAssigner, while a change to dicer.common.testing.TestAssigner can't break dicer.common.testing.
- Position
- Below the diagonal: dicer.common.testing.TestAssigner uses a module listed above it, which is the healthy direction.
40→31 dicer.common.testing.TestAssigner uses dicer.external✕
- Connections
- 1 pair of types, where a type in dicer.common.testing.TestAssigner uses a type in dicer.external.
- The types involved
com.databricks.dicer.common.testing.TestAssigner.TestHealthWatcherFactory→com.databricks.dicer.external.Target
- Direction
- dicer.common.testing.TestAssigner uses dicer.external, so a change to dicer.external can break dicer.common.testing.TestAssigner, while a change to dicer.common.testing.TestAssigner can't break dicer.external.
- Position
- Below the diagonal: dicer.common.testing.TestAssigner uses a module listed above it, which is the healthy direction.
40→32 dicer.common.testing.TestAssigner uses dicer.assigner.HealthWatcher✕
- Connections
- 3 pairs of types, where a type in dicer.common.testing.TestAssigner uses a type in dicer.assigner.HealthWatcher.
- The types involved
com.databricks.dicer.common.testing.TestAssigner.Config→com.databricks.dicer.assigner.HealthWatcher.Factorycom.databricks.dicer.common.testing.TestAssigner.TestHealthWatcherFactory→com.databricks.dicer.assigner.HealthWatcher.Factorycom.databricks.dicer.common.testing.TestAssigner.TestHealthWatcherFactory→com.databricks.dicer.assigner.HealthWatcher.StaticConfig
- Direction
- dicer.common.testing.TestAssigner uses dicer.assigner.HealthWatcher, so a change to dicer.assigner.HealthWatcher can break dicer.common.testing.TestAssigner, while a change to dicer.common.testing.TestAssigner can't break dicer.assigner.HealthWatcher.
- Position
- Below the diagonal: dicer.common.testing.TestAssigner uses a module listed above it, which is the healthy direction.
40→34 dicer.common.testing.TestAssigner uses dicer.assigner.Assigner✕
- Connections
- 1 pair of types, where a type in dicer.common.testing.TestAssigner uses a type in dicer.assigner.Assigner.
- The types involved
com.databricks.dicer.common.testing.TestAssigner.InterceptableStoreFactory→com.databricks.dicer.assigner.Assigner.StoreFactory
- Direction
- dicer.common.testing.TestAssigner uses dicer.assigner.Assigner, so a change to dicer.assigner.Assigner can break dicer.common.testing.TestAssigner, while a change to dicer.common.testing.TestAssigner can't break dicer.assigner.Assigner.
- Position
- Below the diagonal: dicer.common.testing.TestAssigner uses a module listed above it, which is the healthy direction.
40→37 dicer.common.testing.TestAssigner uses dicer.assigner✕
- Connections
- 2 pairs of types, where a type in dicer.common.testing.TestAssigner uses a type in dicer.assigner.
- The types involved
com.databricks.dicer.common.testing.TestAssigner.Config→com.databricks.dicer.assigner.TargetMigratorcom.databricks.dicer.common.testing.TestAssigner.TestHealthWatcherFactory→com.databricks.dicer.assigner.HealthWatcher
- Direction
- dicer.common.testing.TestAssigner uses dicer.assigner, so a change to dicer.assigner can break dicer.common.testing.TestAssigner, while a change to dicer.common.testing.TestAssigner can't break dicer.assigner.
- Position
- Below the diagonal: dicer.common.testing.TestAssigner uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A02:2025 — Security Misconfiguration | 6 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 2 | Medium |
Roadmap
Top priorities: Secure the server's transport: serve TLS itself (akka/pekko-http `ConnectionContext.httpsServer(sslContext)` with `newServerAt(…).enableHttps(…)`, an http4s server builder's `withTLS(…)`, Play's `https.port`), or run it behind a TLS-terminating proxy and trust it (`X-Forwarded-Proto`; Play `play.http.forwarded.trustedProxies`); send `Strict-Transport-Security` once it is HTTPS-only (http4s `HSTS(…)`, Play `RedirectHttpsFilter`); On Scala 3, add `-Yexplicit-nulls` to `scalacOptions` so `String` and `String | Null` mean different things, and type each Java API's result as nullable where it can return null; on Scala 2 (or as a first step), enable WartRemover's `Null` wart (`wartremoverErrors += Wart.Null`) or Scalafix's `DisableSyntax.noNulls = true` so the code holds absence in `Option`. Then pay the assertions down rather than adding to them: each `.nn` is a null the compiler could not rule out — wrap the Java value in `Option(…)` at the boundary, pattern-match on `null` once there, or change the API so the null cannot arrive; an `unsafeNulls` import switches the checking off for everything after it; Interpolated log message defeats structured logging.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Secure the server's transport: serve TLS itself (akka/pekko-http `ConnectionContext.httpsServer(sslContext)` with `newServerAt(…).enableHttps(…)`, an http4s server builder's `withTLS(…)`, Play's `https.port`), or run it behind a TLS-terminating proxy and trust it (`X-Forwarded-Proto`; Play `play.http.forwarded.trustedProxies`); send `Strict-Transport-Security` once it is HTTPS-only (http4s `HSTS(…)`, Play `RedirectHttpsFilter`). | +2.8 pts | Medium | Web-Security Posture |
| On Scala 3, add `-Yexplicit-nulls` to `scalacOptions` so `String` and `String | Null` mean different things, and type each Java API's result as nullable where it can return null; on Scala 2 (or as a first step), enable WartRemover's `Null` wart (`wartremoverErrors += Wart.Null`) or Scalafix's `DisableSyntax.noNulls = true` so the code holds absence in `Option`. Then pay the assertions down rather than adding to them: each `.nn` is a null the compiler could not rule out — wrap the Java value in `Option(…)` at the boundary, pattern-match on `null` once there, or change the API so the null cannot arrive; an `unsafeNulls` import switches the checking off for everything after it. | +2.6 pts | Medium | Nullable reference types |
| Interpolated log message defeats structured logging | +2.0 pts | Medium | Structured logging |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +1.8 pts | Medium | Release Hygiene |
| Resolve the 1 No network policy finding(s) in Network Egress Confinement. | +0.8 pts | Low | Network Egress Confinement |
| Resolve the 88 TodoComment finding(s) in Explicit Debt — start with ClerkImpl.scala (7), SliceletSuiteBase.scala (6), SliceletImpl.scala (5). | +0.8 pts | Medium | Explicit Debt |
| Raise allocation-aware density on the hot paths — currently 19 use(s) across 56,931 production line(s) (~0.3/1k). More of the idioms below on the allocation-heavy paths climbs this toward 10. | +0.9 pts | Medium | Allocation hygiene |
| Swallowed exception (caught, then discarded) | +0.8 pts | Medium | Exception handling |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.6 | Slop | IaC & Container Security: High IaC: REDACTED |
| dicer/assigner/src/HealthWatcher.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| dicer/common/src/SubscriberHandler.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| dicer/assigner/src/AssignmentGenerator.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| dicer/assigner/src/EtcdPreferredAssignerStoreStateMachine.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| dicer/assigner/src/Assigner.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| caching/util/src/EtcdClient.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| dicer/client/src/ClerkImpl.scala | 6.4 | Mixed | Explicit Debt: TodoComment |
| dicer/external/test/SliceletSuiteBase.scala | 6.5 | Mixed | Explicit Debt: TodoComment |
| dicer/client/src/SliceletImpl.scala | 6.5 | Mixed | Explicit Debt: TodoComment |
| dicer/assigner/config/src/InternalTargetConfig.scala | 6.5 | Mixed | Explicit Debt: TodoComment |
| dicer/common/src/ProposedAssignment.scala | 6.7 | Mixed | Explicit Debt: TodoComment |
| caching/util/src/Pipeline.scala | 6.7 | Mixed | Explicit Debt: TodoComment |
| dicer/assigner/src/TargetMetrics.scala | 6.7 | Mixed | Explicit Debt: TodoComment |
| dicer/assigner/src/AssignerSlicez.scala | 6.7 | Mixed | Explicit Debt: TodoComment |
| dicer/common/testing/src/InternalDicerTestEnvironment.scala | 6.9 | Mixed | Explicit Debt: TodoComment |
| dicer/common/testing/src/TestAssigner.scala | 6.9 | Mixed | Explicit Debt: TodoComment |
| dicer/client/test/SliceLookupSuiteBase.scala | 6.9 | Mixed | Explicit Debt: TodoComment |
| dicer/client/src/SliceLookup.scala | 6.9 | Mixed | Explicit Debt: TodoComment |
| REDACTED | 6.9 | Mixed | Dependency Vulnerabilities: Medium advisory (unsound): REDACTED |
How the grades work
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.
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.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
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 61 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.7, the weighted average across measured dimensions.
What we checked — 61 dimensions across the health lenses
- 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, 145 of 182 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- 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 (.scala, .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. To have real coverage read, produce a coverage report in a standard format (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`, or JaCoCo XML — `mvn jacoco:report` or the Gradle `jacocoTestReport` task) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`, or JaCoCo XML — `mvn jacoco:report` or the Gradle `jacocoTestReport` task) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- 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 (.scala, .java) but the built-in reliability runner does not support this repository's ecosystem, so flakiness couldn't be assessed. 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. No dependency manifest this pass reads for hygiene (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems)) was found in this repository, so no package was assessed. Zero packages read is NOT a clean dependency tree, so this is NOT SCORED — a gap in the analyzer, not a verdict about this repository. This row is about dependency HYGIENE — outdated, deprecated or unmaintained direct dependencies; known CVEs in the same dependency graph are a separate question, reported under D30 wherever the manifest is OSV-readable.
- D14 License Compliance — 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 — no dependency manifest this pass reads for licence data (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems)) was found in this repository, so it declares no third-party dependency closure to grade. A gap in the analyzer, NOT a finding that this repository's licences are compliant: a manifest in an ecosystem outside that list, or third-party code copied into the tree, is not read — so this dimension asserts nothing about this repository's licensing in either direction.
- D15 Churn × Complexity Hotspots — measured, with a gap in what it reached — 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. Git history depth insufficient — this repository has 12 commit(s), too few for a reliable trend signal. The clone is complete, so there is no deeper history to fetch: the signal returns as the project accumulates history.
- 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. Too few commits for a meaningful bus factor (12 commit(s) sampled, fewer than the 50 this dimension needs before a bus factor means anything).
- D20 ADR Quality — 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. The ADR expectation is gated on whether a repository ships a deployable product. Our repo-kind classifier reads .NET project files and the host and package markers of the other ecosystems it knows (a Go `package main`, a Cargo binary, a package.json `bin`, `start` script or application dev server such as Vite or Next, Python console scripts or a Django/WSGI entry point, a Spring Boot / WAR / Gradle application build, a Rack or Rails app, a Composer project, an OTP release or escript, a Dockerfile, a Procfile, a Platform.sh `.platform/routes.yaml`, and the corresponding published-package manifests, including an OTP `*.app.src`, a Drupal module's `*.info` and a Claude Code `.claude-plugin/plugin.json`), and found none here, so we could not tell what kind of repository this is and did not assess its ADR log. This is a gap in our analyzer, not a finding about this repository.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its 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: 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.
- D26 Project Cohesion — 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. Project size and spread are measured over build units (a .NET project, a Maven or Gradle module, an npm, Deno or JSR package, a Go module, a Cargo crate, a Python, Composer, Bundler, RubyGems, Mix, rebar3, sbt, SwiftPM or pub package, an OTP application, an Xcode project or XcodeGen spec, or a checkout that declares no build at all) whose source a code model reads. This repository's production source is in a language no model reads, or in units whose build tool D26 does not recognise. That is a gap in this analyzer's language reach — not a finding that the repository's projects are cohesive.
- D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- D34 Knowledge Freshness — 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. Too few commits to judge knowledge freshness (12 commit(s) sampled).
- D35 Change Coupling — measured, with a gap in what it reached — 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. Git history depth insufficient — this repository has 12 commit(s), too few for a reliable change-coupling signal. The clone is complete, so there is no deeper history to fetch: the signal returns as the project accumulates history.
- D41 Kernel & Syscall Confinement — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Dicer/production/assigner/templates/deployment.yaml:4 did not read as a pod spec (a templated manifest such as Helm's that is not YAML until rendered, or a workload whose pod spec this check does not locate), so the seccomp/AppArmor profile in force there was not judged and no row about them can appear on this card.
- D44 Platform End-of-Life — 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 dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
- 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 Dockerfile (dicer/demo/deploy/docker/Dockerfile.assigner). docker build failed (exit 1) — 10 | 11 | # Expose the Assigner watch gRPC port. -------------------- ERROR: failed to solve: failed to compute cache key: failed to calculate checksum of ref e2d29302-ad18-43b4-91f5-1e047207bf04::w70t7of8xoqx10b968ydnkck1: "/dicer/assigner/advanced_config/dev/demo-cache-app.textproto": not found; runtime evidence skipped.
- 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.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
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
- 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.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- 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.
- 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.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D40 Network Egress Confinement: Egress confinement is read from committed Kubernetes manifests — a policy applied out-of-band (cluster-default deny, a service mesh, or a cloud firewall/security group off-repo) is invisible, and a present NetworkPolicy is declared config, not proof the cluster admission-controller actually enforces it at runtime.
- D41 Kernel & Syscall Confinement: Syscall/MAC confinement is read from committed manifests — a profile applied by a cluster-wide PodSecurity default or a mutating webhook off-repo isn't seen, and a declared seccomp/AppArmor profile is config presence, not proof the node's kernel actually loaded and enforced it.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
4 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was ResourceHealth.updateHealthStatus at 25.
What to do
- Bring the 4 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with ResourceHealth.updateHealthStatus (cyclomatic 25), AssignmentFormatter.appendSliceAssignmentRows (cyclomatic 21), SubscriberHandler.replyFromCell (cyclomatic 17). — 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 4 together lifts Cyclomatic Complexity from 9.1 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
16 method(s) exceeded the cognitive complexity threshold of 15; the worst was AssignmentFormatter.appendSliceAssignmentRows at 45.
What to do
- Bring the 2 bodies over 30 down to 30 or less in Cognitive Complexity — start with AssignmentFormatter.appendSliceAssignmentRows (cognitive 45), HealthWatcher.onAdvance (cognitive 32). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cognitive Complexity from 7.6 to about 8.0/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
8 god class(es) detected.
What to do
- Resolve the 7 FileTooLong finding(s) in God Classes — start with TargetMetrics.scala, Assigner.scala, SubscriberHandlerSuiteBase.scala. — One of this dimension's main actionable groups (7 warning-level).
- Resolve the 1 ClassTooLong finding(s) in God Classes — start with SubscriberHandlerSuiteBase.scala. — One of this dimension's main actionable groups (1 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
5 duplicated block group(s) detected. 1 of the 5 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
What to do
- Resolve the 1 Duplicated block (26–30 lines × 2) finding(s) in Code Duplication — start with EtcdClient.scala. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (23–24 lines × 2) finding(s) in Code Duplication — start with EtcdClient.scala. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with SliceTestUtils.scala. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
215 production modules (Bazel), 0 dependency cycle(s), 27 unstable depended-on module(s). Read from the build's own module declarations, and main-sequence distance (abstractness) is not computed for these modules yet.
What to do
- Resolve the 13 Unstable project //dicer/assigner finding(s) in Coupling. — One of this dimension's main actionable groups (13 warning-level).
- Resolve the 4 Unstable project //dicer/client finding(s) in Coupling. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 2 Unstable project //dicer/common finding(s) in Coupling. — One of this dimension's main actionable groups (2 warning-level).
- Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
1 of 95 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with DicerAssignerConf.scala. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D9 · Test Distribution
1336 test methods: 1317 unit, 19 integration, 0 BDD, 0 e2e. The Rust suite contributes 26 `#[test]` function(s) across 4 file(s) declaring at least one; its unit/integration split is Cargo's own — 0 of those file(s) are integration-test targets under a crate's tests/ directory, and the rest are #[test] functions compiled into the crate they test. The Scala suite contributes 1268 test case(s) across 164 file(s) in a test source set declaring at least one — every `test("…")`, `it("…")`, `property("…")` and `"…" in {…}` registration and every JUnit `@Test`, which is how munit, ScalaTest, utest, ZIO Test and specs2 declare a case; a case registered under a computed name is not counted, so this is a floor. Its tier split is INFERRED from paths and file names, except sbt's src/it source set, which the build declares.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D15 · Churn × Complexity Hotspots
Top hotspots: dicer/common/src/SubscriberHandler.scala (4×17=68); dicer/assigner/src/HealthWatcher.scala (2×25=50)
What to do
- Resolve the 2 Hotspot finding(s) in Churn × Complexity Hotspots — start with SubscriberHandler.scala, HealthWatcher.scala. — One of this dimension's main actionable groups (2 warning-level).
D17 · Explicit Debt
89 deducted task-comment markers across 57439 LoC (0.1/KLoC) → score 9.7. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 88 TodoComment finding(s) in Explicit Debt — start with ClerkImpl.scala (7), SliceletSuiteBase.scala (6), SliceletImpl.scala (5). — One of this dimension's main actionable groups (88 warning-level).
- Resolve the 1 HackComment finding(s) in Explicit Debt — start with WatchCellSuite.scala. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
semgrep found no security issues. semgrep hit a parse error in 11 file(s) — `dicer/demo/deploy/helm/demo-client/templates/configmap.yaml`, `dicer/demo/deploy/helm/demo-client/templates/deployment.yaml`, `dicer/demo/deploy/helm/demo-server/templates/configmap.yaml`, `dicer/demo/deploy/helm/demo-server/templates/deployment.yaml`, `dicer/demo/deploy/helm/demo-server/templates/service.yaml`, … (+6 more) — so no absence of findings in them is evidence of anything, and nothing in them was analysed. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
D30 · Dependency Vulnerabilities
2 finding(s): 0 critical, 0 high, 2 medium, 0 low.
What to do
- Resolve the 2 Medium advisory (unsound) finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
D31 · IaC & Container Security
6 finding(s): 0 critical, 1 high, 4 medium, 1 low.
What to do
- Resolve the 1 High IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 4 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (4). — One of this dimension's main actionable groups (4 warning-level).
- 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).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D40 · Network Egress Confinement
0/2 network-egress controls present (network policy, egress restriction).
What to do
- Resolve the 1 No network policy finding(s) in Network Egress Confinement. — One of this dimension's main actionable groups (1 recommendation-level).
D41 · Kernel & Syscall Confinement
No workload manifest could be read as a pod spec, so no confinement was judged.
What to do
- Improve Kernel & Syscall Confinement — currently 6.0/10. — No workload manifest could be read as a pod spec, so no confinement was judged.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
Frontend & cross-cutting dimensions
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
AX8 · Test isolation
AX9 · CQS / query purity
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
- `parseSubFlag` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — caching/util/src/SafeBatchFlagHelper.scala:10
- `tryCreate` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — dicer/assigner/src/RemoteMembershipCheckerFactory.scala:11
- `getSubFlagValues` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — wrappers/feature-flag/src/BaseDynamicConf.scala:40
- `getHeader` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — wrappers/rpc/src/HttpRequestInfo.scala:5
- `configureClient` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — wrappers/rpc/src/JetcdTLS.scala:7
- `contains` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — wrappers/rpc/src/RequestHeaders.scala:5
What to do
- Finish or delete the unfinished stubs (functions that throw "not implemented", or whose body is empty or a bare constant) — they are dead surface that looks live.
M1 · Documentation (README)
- 235 code files changed in the last 6 months but the README was not touched — it may no longer reflect the system.
What to do
- Review the README against recent changes; refresh the parts that drifted.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
- Production code isn't grouped under a src/ folder — it's spread across several top-level directories, so there's no one place that says 'this is the product'.
What to do
- Group production code under src/ (or split deliberately, e.g. backend/ + frontend/) so production and tooling code aren't mixed at the root.
M4 · Documentation accuracy
- dicer/demo/deploy/helm/README.md links to `../../../caching/util/src/ServerConf.scala`, but `dicer/caching/util/src/ServerConf.scala` 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. — dicer/demo/deploy/helm/README.md:323
What to do
- Reconcile the README with reality: dicer/demo/deploy/helm/README.md links to `../../../caching/util/src/ServerConf.scala`, but `dicer/caching/util/src/ServerConf.scala` does not exist.
P1 · CI/CD gates
- A CI pipeline exists but no build step was matched — changes may merge without the build ever running. A build step may be invoked directly as a command, or declared as a task that a runner named in the pipeline resolves.
What to do
- Add an explicit build step to your CI pipeline — your stack's own build command, or, if the pipeline delegates to a task runner, a build task that runner executes in CI — so every change is built before merge.
P2 · Observability
What to do
- Add a health-check endpoint (Spring Boot Actuator's /actuator/health, or a /health route) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add scalafix or scapegoat (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 851 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. — .github/workflows/ci.yml:10
What to do
- Add a SAST step to CI running what this repository's stack ships: scalafix or scapegoat — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
What to do
- Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
PF2 · Allocation hygiene
What to do
- Raise allocation-aware density on the hot paths — currently 19 use(s) across 56,931 production line(s) (~0.3/1k). More of the idioms below on the allocation-heavy paths climbs this toward 10.
- Java: on hot paths, work through buffer views (ByteBuffer/LongBuffer slices, MemorySegment) instead of copies, avoid boxing with primitive collections (fastutil, Eclipse Collections, HPPC, Trove), presize collections and StringBuilders, and pool expensive buffers (Netty's pooled allocator, commons-pool).
- Scala: on hot paths, make small wrappers value classes (extends AnyVal), @specialized generic code over primitives, use primitive collections, and presize builders.
PF3 · Async & latency hygiene
S1 · Web-Security Posture
- This repository runs an HTTP server and nothing in its Scala source or committed configuration secures the transport: no HTTPS served (akka/pekko-http `ConnectionContext.httpsServer`/`enableHttps`, an http4s builder's `withTLS`, Jetty's `SslContextFactory`, zio-http's `SSLConfig`, Play's `https.port`), no `Strict-Transport-Security` header, HSTS middleware or Play `RedirectHttpsFilter`, no `X-Forwarded-Proto` read or Play `play.http.forwarded.trustedProxies` for a TLS-terminating proxy — so its traffic may cross the network in clear text. (−2.0 on this card.) The server: wrappers/instrumentation/src/InfoService.scala:90 — `HttpServer.create`.
- None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is set on a response this repository's Scala server sends — defense in depth, even when a proxy could set them. (−2.0 on this card.) The server: wrappers/instrumentation/src/InfoService.scala:90 — `HttpServer.create`.
- No handler of this repository's Scala server answers 400, 413 or 422 (`BadRequest`, `StatusCodes.BadRequest`, `Status.BadRequest`, `UnprocessableEntity`), and nothing declares validation — no Play `Form(mapping(…))` or `validate[T]`, no tapir `Validator`, no akka/pekko-http `validate(…)` or `withSizeLimit`, no validation library (refined, iron, accord, cats `Validated`, Jakarta Bean Validation) — nothing shows inbound requests being checked, and refused, before a handler acts on them. A check that answers its failure with 200 and an error body is not seen. (−2.0 on this card.) The server: wrappers/instrumentation/src/InfoService.scala:90 — `HttpServer.create`.
What to do
- Secure the server's transport: serve TLS itself (akka/pekko-http `ConnectionContext.httpsServer(sslContext)` with `newServerAt(…).enableHttps(…)`, an http4s server builder's `withTLS(…)`, Play's `https.port`), or run it behind a TLS-terminating proxy and trust it (`X-Forwarded-Proto`; Play `play.http.forwarded.trustedProxies`); send `Strict-Transport-Security` once it is HTTPS-only (http4s `HSTS(…)`, Play `RedirectHttpsFilter`).
- Set security response headers on what the server sends — keep Play's `SecurityHeadersFilter` enabled, wrap akka/pekko-http routes in `respondWithHeaders(RawHeader("X-Content-Type-Options", "nosniff"), …)`, or add an http4s middleware that sets `Content-Security-Policy`, `X-Content-Type-Options` and a frame policy on every response.
- Validate what the server reads from a request — path, query, headers, body size and shape — and answer what fails with 400 (413 for an oversized body) before a handler acts on it: a Play form or `validate[T]` answered with `BadRequest`, tapir `Validator`s on the endpoint's inputs, or akka/pekko-http's `validate(…)` and `withSizeLimit` directives.
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
- `case NonFatal(_)` 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. — caching/util/src/WhereAmIHelper.scala:53
What to do
- Swallowed exception (caught, then discarded)
X30 · Support guard that admits what it rejects
X4 · Structured logging
- `event!` at line 20 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `event!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — wrappers/rust/throttled_logger/src/lib.rs:20
What to do
- Interpolated log message defeats structured logging
X5 · Nullable reference types
- No build over this repository's 279 Scala product file(s) passes `-Yexplicit-nulls`, enables WartRemover's `Null` wart or runs Scalafix's `DisableSyntax.noNulls`, so every reference type admits null and nothing reports a `null` written into the code or returned from a Java API — the first one to reach a method call is a `NullPointerException`. `Option` by convention is a habit no tool here holds the code to.
What to do
- On Scala 3, add `-Yexplicit-nulls` to `scalacOptions` so `String` and `String | Null` mean different things, and type each Java API's result as nullable where it can return null; on Scala 2 (or as a first step), enable WartRemover's `Null` wart (`wartremoverErrors += Wart.Null`) or Scalafix's `DisableSyntax.noNulls = true` so the code holds absence in `Option`. Then pay the assertions down rather than adding to them: each `.nn` is a null the compiler could not rule out — wrap the Java value in `Option(…)` at the boundary, pattern-match on `null` once there, or change the API so the null cannot arrive; an `unsafeNulls` import switches the checking off for everything after it.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 54% | Adequate — gated by X4, X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 97% | Exemplary | Strongest area. |
| Maturity | 70% | Adequate | Acceptable, with room to improve. |
| Readiness | 54% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 58% | Adequate | Acceptable, with room to improve. |
| Performance | 78% | Strong | Solid. |
Unscored — 1 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 56 check(s) not relevant to this codebase
- 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.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: this repository's Java imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one; this repository's Scala imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Java code is a Spring, JSR-330 or CDI singleton bean. No class in this Scala code is a Play controller, a Cask routes object, a Scalatra servlet, a Finatra controller, an Akka/Pekko HTTP routes holder or a JSR-330/Spring singleton, so no instance is shared between request threads. Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — docker build failed (exit 1) — 10 | 11 | # Expose the Assigner watch gRPC port. -------------------- ERROR: failed to solve: failed to compute cache key: failed to calculate checksum of ref e2d29302-ad18-43b4-91f5-1e047207bf04::w70t7of8xoqx10b968ydnkck1: "/dicer/assigner/advanced_config/dev/demo-cache-app.textproto": not found; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — 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.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named column (email, first_name, date_of_birth, phone_number, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, a MongoDB or Cassandra driver, JDBC) imported either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database or data-store client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, JDBC, MongoDB, Cassandra, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database or data-store client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, JDBC, MongoDB, Cassandra, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~78632 lines of test source are present (.scala, .java) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — no .scala test runner
- D12 Dependency Hygiene — Dependency hygiene not measured — no supported dependency manifest was read
- D14 License Compliance — No dependency manifest found — no declared dependency closure to grade for licences
- D16 Bus Factor — too few commits for a meaningful bus factor
- 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.
- D19 Documentation Quality — No runnable or published unit to look for an example in, and no multi-project root README to look for a map in; the other documentation kinds are withheld (see the gaps), so documentation quality is not applicable here.
- D20 ADR Quality — Repository kind not determined
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; Java, Rust, Scala not measured.
- 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, .rs, .scala, 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
- D26 Project Cohesion — D26 measured no build unit over this repository's .java, .rs, .scala source. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.scala), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D34 Knowledge Freshness — too few commits to judge knowledge freshness
- D36 Supply-chain Provenance & Signing — The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release).
- 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.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D42 Runtime Threat Enforcement — The repository ships application workloads but no cluster-governance resources (CRDs, admission webhooks, or a committed policy engine). Runtime threat-detection (Falco/Tetragon) and admission control (Kyverno/OPA-Gatekeeper/PodSecurity) are cluster-OPERATOR controls owned by the platform, not shipped by an application repo/chart — nothing for this repo to assess.
- D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — applicable but not scored (2 signals for this style, 2 needed — the count is met but a required primary signal is absent): 287 value object(s); 19 domain event(s); its domain events are published by services or handlers — no domain entity raises one
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM, Rust source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- 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 pom.xml, 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.
- X2 Cancellation propagation — no C# was loaded; this repository's Scala, Java and Rust were read, and no request in it can be cancelled by a caller — a Scala request takes no token: a Future cannot be cancelled, and cats-effect, ZIO and Monix interrupt the fiber that made the request from outside the call, not through a parameter; 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; a Rust request takes no token: a future is cancelled by dropping it, from outside the call (select!, a timeout, an aborted task), and reqwest, hyper and tonic take none
- 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.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 1 finding(s)
- REDACTED
Serious — 166 finding(s)
- TodoComment dicer/external/test/ClerkSuiteBase.scala:1204
- TodoComment dicer/external/test/ScalaSingletonSliceLookupSuite.scala:74
- TodoComment dicer/external/test/SliceletSuiteBase.scala:167
- TodoComment dicer/external/test/SliceletSuiteBase.scala:1700
- TodoComment dicer/external/test/SliceletSuiteBase.scala:2511
- TodoComment dicer/external/test/SliceletSuiteBase.scala:2646
- TodoComment dicer/external/test/SliceletSuiteBase.scala:2989
- TodoComment dicer/external/test/SliceletSuiteBase.scala:3011
- TodoComment dicer/external/src/Clerk.scala:87
- TodoComment dicer/external/src/Slicelet.scala:70
- TodoComment dicer/external/src/Target.scala:78
- TodoComment dicer/common/testing/src/InternalDicerTestEnvironment.scala:503
- TodoComment dicer/common/testing/src/InternalDicerTestEnvironment.scala:591
- TodoComment dicer/common/testing/src/InternalDicerTestEnvironment.scala:700
- TodoComment dicer/common/testing/src/TestAssigner.scala:684
- TodoComment dicer/common/testing/src/TestAssigner.scala:822
- TodoComment dicer/common/testing/src/TestAssigner.scala:824
- TodoComment dicer/common/test/AppIdentifierSuite.scala:10
- TodoComment dicer/common/test/GossipSuite.scala:343
- TodoComment dicer/common/test/SlicezSuite.scala:45
- TodoComment dicer/common/test/SlicezSuite.scala:67
- TodoComment dicer/common/src/ClientRequest.scala:623
- TodoComment dicer/common/src/DiffAssignment.scala:166
- TodoComment dicer/common/src/DiffAssignment.scala:311
- TodoComment dicer/common/src/ProposedAssignment.scala:296
- Unstable project //dicer/assigner:assigner
- Unstable project //dicer/assigner:assignment_generator_driver
- Unstable project //dicer/assigner:assignment_stats
- Unstable project //dicer/assigner:consistent_hashing_preferred_assigner_driver
- Unstable project //dicer/assigner:disabled_preferred_assigner_driver
- Unstable project //dicer/assigner:etcd_preferred_assigner_driver
- Unstable project //dicer/assigner:etcd_preferred_assigner_store
- Unstable project //dicer/assigner:generator
- Unstable project //dicer/assigner:in_memory_store
- Unstable project //dicer/assigner:load_watcher
- Unstable project //dicer/assigner:migration_preferred_assigner_driver
- Unstable project //dicer/assigner:remote_membership_checker_factory
- Unstable project //dicer/assigner:target_migrator
- FileTooLong: src/TargetMetrics.scala dicer/assigner/src/TargetMetrics.scala
- FileTooLong: src/Assigner.scala dicer/assigner/src/Assigner.scala
- FileTooLong: src/SubscriberHandlerSuiteBase.scala dicer/common/testing/src/SubscriberHandlerSuiteBase.scala
- FileTooLong: src/AssignmentGenerator.scala dicer/assigner/src/AssignmentGenerator.scala
- FileTooLong: src/EtcdClient.scala caching/util/src/EtcdClient.scala
- FileTooLong: src/SubscriberHandler.scala dicer/common/src/SubscriberHandler.scala
- FileTooLong: src/KubernetesMembershipChecker.scala dicer/assigner/src/KubernetesMembershipChecker.scala
- Hollow method — returns a constant without doing the work caching/util/src/SafeBatchFlagHelper.scala:10
- Hollow method — returns a constant without doing the work dicer/assigner/src/RemoteMembershipCheckerFactory.scala:11
- Hollow method — returns a constant without doing the work wrappers/feature-flag/src/BaseDynamicConf.scala:40
- Hollow method — returns a constant without doing the work wrappers/rpc/src/HttpRequestInfo.scala:5
- Hollow method — returns a constant without doing the work wrappers/rpc/src/RequestHeaders.scala:5
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Unstable project //dicer/client:clerk_impl
- Unstable project //dicer/client:lookup
- Unstable project //dicer/client:slicelet_impl
- Unstable project //dicer/client:sync
- Hotspot: dicer/common/src/SubscriberHandler.scala dicer/common/src/SubscriberHandler.scala:328
- Hotspot: dicer/assigner/src/HealthWatcher.scala dicer/assigner/src/HealthWatcher.scala:549
- REDACTED
- REDACTED
- Unstable project //dicer/common:etcd_bootstrapper
- Unstable project //dicer/common:subscriber_handler
- Unstable project //dicer/external/javaapi:clerk
- Unstable project //dicer/external/javaapi:impl_friend
- ResourceHealth.updateHealthStatus (cyclomatic 25) dicer/assigner/src/HealthWatcher.scala:549
- AssignmentFormatter.appendSliceAssignmentRows (cyclomatic 21) dicer/common/src/AssignmentFormatter.scala:645
- SubscriberHandler.replyFromCell (cyclomatic 17) dicer/common/src/SubscriberHandler.scala:328
- Assignment.fromDiff (cyclomatic 16) dicer/common/src/Assignment.scala:270
- HackComment caching/util/test/WatchCellSuite.scala:67
- AssignmentFormatter.appendSliceAssignmentRows (cognitive 45) dicer/common/src/AssignmentFormatter.scala:645
- HealthWatcher.onAdvance (cognitive 32) dicer/assigner/src/HealthWatcher.scala:725
- PlacementPhase.generateCandidateOperations (cognitive 29) dicer/assigner/algorithm/src/PlacementPhase.scala:389
- Assignment.fromDiff (cognitive 29) dicer/common/src/Assignment.scala:270
- SubscriberHandler.replyFromCell (cognitive 26) dicer/common/src/SubscriberHandler.scala:328
- ProposedAssignment.commitWithPredecessor (cognitive 25) dicer/common/src/ProposedAssignment.scala:223
- AssignmentGenerator.shouldGenerateNewAssignment (cognitive 20) dicer/assigner/src/AssignmentGenerator.scala:306
- EtcdPreferredAssignerStoreStateMachine.onEtcdWriteResponse (cognitive 20) dicer/assigner/src/EtcdPreferredAssignerStoreStateMachine.scala:267
- AssignmentSyncStateMachine.onAdvanceInternal (cognitive 19) dicer/client/src/AssignmentSyncStateMachine.scala:375
- EtcdPreferredAssignerStateMachine.onAdvanceInternal (cognitive 18) dicer/assigner/src/EtcdPreferredAssignerStateMachine.scala:168
- ResourceHealth.update (cognitive 18) dicer/assigner/src/HealthWatcher.scala:442
- AssignmentFormatter.createSliceAssignmentTable (cognitive 18) dicer/common/src/AssignmentFormatter.scala:471
- EtcdWatcherStateMachine.onKeyValue (cognitive 16) caching/util/src/EtcdWatcher.scala:582
- Pipeline.sequence (cognitive 16) caching/util/src/Pipeline.scala:230
- ResourceHealth.updateHealthStatus (cognitive 16) dicer/assigner/src/HealthWatcher.scala:549
- KeyOfDeathDetector.onAdvanceInternal (cognitive 16) dicer/assigner/src/KeyOfDeathDetector.scala:203
- ClassTooLong: SubscriberHandlerSuiteBase dicer/common/testing/src/SubscriberHandlerSuiteBase.scala:60
- Duplicated block (26–30 lines × 2) caching/util/src/EtcdClient.scala:414
- Duplicated block (23–24 lines × 2) caching/util/src/EtcdClient.scala:502
- Duplicated block (9 lines × 2) dicer/common/testing/src/SliceTestUtils.scala:290
- Duplicated block (6 lines × 2) dicer/assigner/src/AssignerSlicez.scala:323
- Duplicated block (16 lines × 2) dicer/assigner/testing/src/PreferredAssignerTestUtils.scala:176
- Unstable project //dicer/assigner/algorithm:algorithm
- Unstable project //dicer/assigner/config:config_provider
- Unstable project //dicer/client/javaapi:slicelet_conf_impl
- Unstable project //dicer/external:dicer_client_conf
- Unstable project //wrappers/instrumentation:info-service
- Unstable project //wrappers/util:databricks_main
- Low cohesion: DicerAssignerConf (LCOM4 4) dicer/assigner/src/conf/DicerAssignerConf.scala:375
- Empty method body — does nothing with its inputs wrappers/rpc/src/JetcdTLS.scala:7
- README may be stale
- Swallowed exception (caught, then discarded) caching/util/src/WhereAmIHelper.scala:53
Minor — 15 finding(s)
- Duplicated predicate dicer/external/javaapi/src/ResourceAddress.java:39
- Duplicated predicate dicer/common/src/Assignment.scala:72
- REDACTED
- No network policy
- No ADRs
- No src/ separation
- README/code drift dicer/demo/deploy/helm/README.md:323
- CI build step not evidenced
- No SAST .github/workflows/ci.yml:10
- No changelog
- No app-layer HTTPS enforcement detected
- No security response headers detected
- No inbound request validation detected
- Interpolated log message defeats structured logging wrappers/rust/throttled_logger/src/lib.rs:20
- Scala's null is not held to the type system everywhere
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-500e2814f23f42caadd2d6af94097efd/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.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-500e2814f23f42caadd2d6af94097efd/tree.json --exit-code 0 --source . | 0 | artifacts/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 . | 0 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 2 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 6 | artifacts/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 & Signing | provenance | — | provenance: not applicable — The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release). | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | 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 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — The repository ships application workloads but no cluster-governance resources (CRDs, admission webhooks, or a committed policy engine). Runtime threat-detection (Falco/Tetragon) and admission control (Kyverno/OPA-Gatekeeper/PodSecurity) are cluster-OPERATOR controls owned by the platform, not shipped by an application repo/chart — nothing for this repo to assess. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |