Executive summary
bazelbuild/bazel scores 60 out of 100, but it is rated At risk while a critical security finding is open; the score itself is unchanged.
The weakest lens counts most in the score, and here that is Maturity, which scores 55 and is rated Adequate. Its Architecture documentation dimension scores 0 out of 10, and until that reaches 4, Maturity can't be rated higher than Adequate. The first actions are to resolve the 1 Documentation finding(s) in Documentation Quality and to resolve the 1 Orphaned knowledge finding(s) in Knowledge Freshness, and if Maturity rose to 70, the score would rise from 60 to about 64.
42 findings are critical: 17 in Test Quality, eight in Secrets (history), five in Static Analysis (SAST), three in Dependency Vulnerabilities, three in REDACTED Scanning, three in Test Reliability, one in Change Coupling, one in Knowledge Freshness and one in License Compliance.
Watchdog couldn't measure 14 dimensions in this code, among them Code Coverage, Dependency Hygiene and ADR Quality, so they are left out of the score. The product code is 595,527 lines, which would take an estimated 10.2 person-years, around €1,500,000, to rebuild.
If Maturity rose from 55 to 70, the lowest score rated Strong, the score would rise from 60 to about 64.
New since the last survey: 83 findings
- Cyclomatic Complexity · NodeDependencyHandler.reduce (cyclomatic 21) src/main/java/com/google/devtools/build/lib/skyframe/serialization/analysis/FileDependencySerializer.java
- Cyclomatic Complexity · JavaUtil.javaSegmentIndexImpl (cyclomatic 19) src/main/java/com/google/devtools/build/lib/rules/java/JavaUtil.java
- Cyclomatic Complexity · ActionExecutionFunction.checkCacheAndExecuteIfNeeded (cyclomatic 17) src/main/java/com/google/devtools/build/lib/skyframe/ActionExecutionFunction.java
- Cyclomatic Complexity · ConfigExpander.expandConfigOptions (cyclomatic 17) src/main/java/com/google/devtools/build/lib/runtime/ConfigExpander.java
- Cyclomatic Complexity · CommonPrerequisiteValidator.validateDirectPrerequisiteVisibility (cyclomatic 17) src/main/java/com/google/devtools/build/lib/analysis/CommonPrerequisiteValidator.java
- Cyclomatic Complexity · PathFragment.subFragmentImpl (cyclomatic 16) src/main/java/com/google/devtools/build/lib/vfs/PathFragment.java
- Cyclomatic Complexity · ActionExecutionFunction.addDiscoveredInputs (cyclomatic 16) src/main/java/com/google/devtools/build/lib/skyframe/ActionExecutionFunction.java
- Cyclomatic Complexity · ConfiguredTargetFactory.createConfiguredTarget (cyclomatic 16) src/main/java/com/google/devtools/build/lib/analysis/ConfiguredTargetFactory.java
- Cognitive Complexity · NodeDependencyHandler.reduce (cognitive 29) src/main/java/com/google/devtools/build/lib/skyframe/serialization/analysis/FileDependencySerializer.java
- Cognitive Complexity · ActionExecutionFunction.addDiscoveredInputs (cognitive 27) src/main/java/com/google/devtools/build/lib/skyframe/ActionExecutionFunction.java
- Cognitive Complexity · JavaUtil.javaSegmentIndexImpl (cognitive 27) src/main/java/com/google/devtools/build/lib/rules/java/JavaUtil.java
- Cognitive Complexity · Eval.execFor (cognitive 26) src/main/java/net/starlark/java/eval/Eval.java
- Cognitive Complexity · ConfigExpander.expandConfigOptions (cognitive 23) src/main/java/com/google/devtools/build/lib/runtime/ConfigExpander.java
- Cognitive Complexity · ActionRunner.actuallyCompleteAction (cognitive 18) src/main/java/com/google/devtools/build/lib/skyframe/SkyframeActionExecutor.java
- Cognitive Complexity · JavaCompileAction.createFullOutputDeps (cognitive 18) src/main/java/com/google/devtools/build/lib/rules/java/JavaCompileAction.java
- Cognitive Complexity · DefaultNestedSetBuilder.addTransitiveImpl (cognitive 17) src/main/java/com/google/devtools/build/lib/collect/nestedset/NestedSetBuilder.java
- Cognitive Complexity · ArgumentProcessor.addNamedArg (cognitive 16) src/main/java/net/starlark/java/eval/BuiltinFunction.java
- Cognitive Complexity · DependencyResolutionHelpers.resolveAttributes (cognitive 16) src/main/java/com/google/devtools/build/lib/analysis/DependencyResolutionHelpers.java
- God Classes · TooManyMethods: StarlarkFunction src/main/java/net/starlark/java/eval/StarlarkFunction.java
- God Classes · FileTooLong: runtime/BlazeOptionHandler.java src/main/java/com/google/devtools/build/lib/runtime/BlazeOptionHandler.java
- God Classes · FileTooLong: repository/RepositoryOptions.java src/main/java/com/google/devtools/build/lib/bazel/repository/RepositoryOptions.java
- God Classes · ClassTooLong: NestedSet src/main/java/com/google/devtools/build/lib/collect/nestedset/NestedSet.java
- God Classes · TooManyMethods: CriticalPathComponent src/main/java/com/google/devtools/build/lib/metrics/criticalpath/CriticalPathComponent.java
- God Classes · FileTooLong: analysis/CommonPrerequisiteValidator.java src/main/java/com/google/devtools/build/lib/analysis/CommonPrerequisiteValidator.java
- Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) src/main/java/com/google/devtools/build/lib/rules/cpp/CppCompileAction.java
- Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) src/main/java/com/google/devtools/build/lib/bazel/commands/FetchCommand.java
- Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) src/main/java/com/google/devtools/build/lib/runtime/commands/AqueryCommand.java
- Code Duplication · Duplicated block (14–16 lines × 2) src/main/java/com/google/devtools/build/lib/skyframe/BzlCompileFunction.java
- Code Duplication · Duplicated block (14 lines × 2) src/main/java/com/google/devtools/build/lib/analysis/ConfiguredAspect.java
- Code Duplication · Duplicated block (8 lines × 2) src/main/java/com/google/devtools/common/options/InvocationPolicyEnforcer.java
- Cohesion (LCOM4) · Low cohesion: Builder (LCOM4 5) src/main/java/com/google/devtools/build/lib/analysis/ConfiguredRuleClassProvider.java
- Cohesion (LCOM4) · Low cohesion: TypeTable (LCOM4 4) src/main/java/net/starlark/java/syntax/TypeTable.java
- Test Quality · No assertions: labelFlagDepsFailRefinedEnvironmentCheckWhenIncompatible src/test/java/com/google/devtools/build/lib/analysis/constraints/ConstraintsTest.java
- Test Quality · No assertions: testGetReachableLabelsWithDefaultValues_noDefaultValue src/test/java/com/google/devtools/build/lib/analysis/select/AggregatingAttributeMapperTest.java
- Test Quality · No assertions (empty test): testAttributeTypeChecking src/test/java/com/google/devtools/build/lib/analysis/select/NonconfigurableAttributeMapperTest.java
- Test Quality · No assertions (empty test): testVisitation src/test/java/com/google/devtools/build/lib/analysis/select/NonconfigurableAttributeMapperTest.java
- Test Quality · No assertions (empty test): testOptionConversionCrosstoolTop src/test/java/com/google/devtools/build/lib/analysis/starlark/StarlarkAttrTransitionProviderTest.java
- Test Quality · No assertions (empty test): testOptionConversionDynamicMode src/test/java/com/google/devtools/build/lib/analysis/starlark/StarlarkAttrTransitionProviderTest.java
- Test Quality · No assertions: testAspectSubruleImplicitDep_visibility src/test/java/com/google/devtools/build/lib/analysis/starlark/StarlarkSubruleTest.java
- Test Quality · No assertions: testSubruleImplicitDep_transitiveSubruleVisibility src/test/java/com/google/devtools/build/lib/analysis/starlark/StarlarkSubruleTest.java
- Test Quality · No assertions: testSubruleImplicitDep_visibleOnlyToConsumingRulePackage_fails src/test/java/com/google/devtools/build/lib/analysis/starlark/StarlarkSubruleTest.java
- Test Quality · No assertions: testSubruleImplicitDep_visibleToSubrulePackage_passes src/test/java/com/google/devtools/build/lib/analysis/starlark/StarlarkSubruleTest.java
- Test Quality · No assertions: testInvalidModuleInjection src/test/java/com/google/devtools/build/lib/bazel/repository/RepositoryOptionsTest.java
- Test Quality · No assertions: testInvalidModuleOverride src/test/java/com/google/devtools/build/lib/bazel/repository/RepositoryOptionsTest.java
- Test Quality · No assertions (empty test): testGraphOrderOfWildcards src/test/java/com/google/devtools/build/lib/query2/engine/GraphlessQueryTest.java
- Test Quality · No assertions: actionTemplateExpansionRewound_symlinkToTreeLost src/test/java/com/google/devtools/build/lib/skyframe/rewinding/RewindingTest.java
- Test Quality · No assertions: changedRewoundOutputDetected src/test/java/com/google/devtools/build/lib/skyframe/rewinding/RewindingTest.java
- Test Quality · No assertions: changedRewoundOutputFromPreviousBuildDetected src/test/java/com/google/devtools/build/lib/skyframe/rewinding/RewindingTest.java
- Test Quality · No assertions: deterministicRewoundOutputCheckSucceeds src/test/java/com/google/devtools/build/lib/skyframe/rewinding/RewindingTest.java
- Test Quality · No assertions: omittedRewoundOutputCheckSucceeds src/test/java/com/google/devtools/build/lib/skyframe/rewinding/RewindingTest.java
- Test Quality · No assertions: sharedRewoundOutputCheckIsBestEffort src/test/java/com/google/devtools/build/lib/skyframe/rewinding/RewindingTest.java
- Test Quality · No assertions: sharedRewoundOutputCheckSucceeds src/test/java/com/google/devtools/build/lib/skyframe/rewinding/RewindingTest.java
- Test Quality · No assertions: testDirectoryWithSubdirectoryMovedOutAndRecreated src/test/java/com/google/devtools/build/lib/skyframe/LocalDiffAwarenessTest.java
- Test Quality · No assertions: testAbsoluteSymlinkRelativePathThrowsEvalError src/test/java/com/google/devtools/build/lib/rules/cpp/StarlarkCcCommonTest.java
- Test Quality · No assertions: testForLoopIterationLock src/test/java/net/starlark/java/eval/EvaluationTest.java
- Test Quality · No assertions: testForLoopOverSequences src/test/java/net/starlark/java/eval/EvaluationTest.java
- Test Quality · No assertions: testJavaFunctionMutatingEmptyKwargs src/test/java/net/starlark/java/eval/StarlarkEvaluationTest.java
- Test Quality · No assertions: testFlagGuardedMethods src/test/java/net/starlark/java/eval/StarlarkFlagGuardingTest.java
- Test Quality · No assertions: testNonExperimentalOrIncompatibleGuardedParam src/test/java/net/starlark/java/eval/StarlarkFlagGuardingTest.java
- REDACTED Scanning · REDACTED
- REDACTED Scanning · REDACTED
- Churn × Complexity Hotspots · Hotspot: src/main/java/com/google/devtools/build/lib/collect/nestedset/NestedSet.java src/main/java/com/google/devtools/build/lib/collect/nestedset/NestedSet.java
- Churn × Complexity Hotspots · Hotspot: src/main/java/com/google/devtools/build/lib/skyframe/SkyframeActionExecutor.java src/main/java/com/google/devtools/build/lib/skyframe/SkyframeActionExecutor.java
- Churn × Complexity Hotspots · Hotspot: src/main/java/com/google/devtools/build/lib/skyframe/ActionExecutionFunction.java src/main/java/com/google/devtools/build/lib/skyframe/ActionExecutionFunction.java
- Churn × Complexity Hotspots · Hotspot: src/main/java/com/google/devtools/build/skyframe/AbstractParallelEvaluator.java src/main/java/com/google/devtools/build/skyframe/AbstractParallelEvaluator.java
- Churn × Complexity Hotspots · Hotspot: src/main/java/com/google/devtools/build/lib/vfs/WindowsOsPathPolicy.java src/main/java/com/google/devtools/build/lib/vfs/WindowsOsPathPolicy.java
- Churn × Complexity Hotspots · Hotspot: src/main/java/com/google/devtools/build/lib/rules/java/JavaHeaderCompileAction.java src/main/java/com/google/devtools/build/lib/rules/java/JavaHeaderCompileAction.java
- Churn × Complexity Hotspots · Hotspot: src/main/java/com/google/devtools/build/lib/buildtool/SymlinkForest.java src/main/java/com/google/devtools/build/lib/buildtool/SymlinkForest.java
- Churn × Complexity Hotspots · Hotspot: src/main/java/com/google/devtools/build/lib/rules/java/JavaUtil.java src/main/java/com/google/devtools/build/lib/rules/java/JavaUtil.java
- Explicit Debt · TodoComment src/main/java/com/google/devtools/build/lib/analysis/RuleDefinitionEnvironment.java
- Explicit Debt · TodoComment src/main/java/com/google/devtools/build/lib/bazel/rules/java/BazelJavaSemantics.java
- Explicit Debt · TodoComment src/main/java/com/google/devtools/build/lib/rules/java/JavaSemantics.java
- Explicit Debt · TodoComment src/main/java/com/google/devtools/build/lib/rules/java/JavaHeaderCompileAction.java
- Explicit Debt · TodoComment src/main/java/com/google/devtools/build/lib/rules/java/JavaHeaderCompileAction.java
- Explicit Debt · TodoComment src/main/java/com/google/devtools/build/lib/skyframe/TreeArtifactValue.java
- Explicit Debt · TodoComment src/main/java/com/google/devtools/build/lib/skyframe/serialization/analysis/FrontierSerializer.java
- Explicit Debt · TodoComment src/main/java/com/google/devtools/build/lib/skyframe/serialization/analysis/FileDependencySerializer.java
- Explicit Debt · TodoComment src/main/java/net/starlark/java/syntax/Types.java
- Dependency Vulnerabilities · REDACTED
- Knowledge Freshness · Orphaned knowledge src/main/java/com/google/devtools/build/skyframe/InvalidatingNodeVisitor.java
- Change Coupling · Change-coupling hub: BuildTool.java → Project.java, ProjectValue.java, FlagSetValue.java, RemoteAnalysisCacheDeps.java, RemoteAnalysisCachingEventListener.java, RemoteAnalysisCachingOptions.java src/main/java/com/google/devtools/build/lib/buildtool/BuildTool.java
- Change Coupling · Change coupling: RunfilesSupport.java ↔ PyBuiltins.java src/main/java/com/google/devtools/build/lib/analysis/RunfilesSupport.java
- Supply-chain Provenance & Signing · REDACTED
Fixed since the last survey: 1449 findings
- Cyclomatic Complexity · NodeDependencyHandler.getValue (cyclomatic 32) src/main/java/com/google/devtools/build/lib/skyframe/serialization/analysis/FileDependencySerializer.java
- Cyclomatic Complexity · SkyfocusExecutor.prepareActiveDirectories (cyclomatic 24) src/main/java/com/google/devtools/build/lib/skyframe/SkyfocusExecutor.java
- Cyclomatic Complexity · JavaUtil.javaSegmentIndex (cyclomatic 20) src/main/java/com/google/devtools/build/lib/rules/java/JavaUtil.java
- Cyclomatic Complexity · BzlCompileFunction.isFileAllowlisted (cyclomatic 19) src/main/java/com/google/devtools/build/lib/skyframe/BzlCompileFunction.java
- Cyclomatic Complexity · AnalysisPhaseRunner.evaluateProjectFile (cyclomatic 19) src/main/java/com/google/devtools/build/lib/buildtool/AnalysisPhaseRunner.java
- Cyclomatic Complexity · InfoCommand.exec (cyclomatic 18) src/main/java/com/google/devtools/build/lib/runtime/commands/InfoCommand.java
- Cyclomatic Complexity · Eval.newFunction (cyclomatic 16) src/main/java/net/starlark/java/eval/Eval.java
- Cyclomatic Complexity · BzlCompileFunction.registerAllowlistDepIfOversized (cyclomatic 16) src/main/java/com/google/devtools/build/lib/skyframe/BzlCompileFunction.java
- Cyclomatic Complexity · BuildTool.buildTargets (cyclomatic 16) src/main/java/com/google/devtools/build/lib/buildtool/BuildTool.java
- Cognitive Complexity · SkyfocusExecutor.prepareActiveDirectories (cognitive 47) src/main/java/com/google/devtools/build/lib/skyframe/SkyfocusExecutor.java
- Cognitive Complexity · NodeDependencyHandler.getValue (cognitive 33) src/main/java/com/google/devtools/build/lib/skyframe/serialization/analysis/FileDependencySerializer.java
- Cognitive Complexity · InfoCommand.exec (cognitive 32) src/main/java/com/google/devtools/build/lib/runtime/commands/InfoCommand.java
- Cognitive Complexity · JavaUtil.javaSegmentIndex (cognitive 28) src/main/java/com/google/devtools/build/lib/rules/java/JavaUtil.java
- Cognitive Complexity · ShellQuotedReader.readArg (cognitive 27) src/main/java/com/google/devtools/common/options/ShellQuotedParamsFilePreProcessor.java
- Cognitive Complexity · AnalysisPhaseRunner.evaluateProjectFile (cognitive 23) src/main/java/com/google/devtools/build/lib/buildtool/AnalysisPhaseRunner.java
- Cognitive Complexity · SkyfocusNodeVisitor.run (cognitive 21) src/main/java/com/google/devtools/build/lib/skyframe/SkyframeFocuser.java
- Cognitive Complexity · Eval.execStatements (cognitive 20) src/main/java/net/starlark/java/eval/Eval.java
- Cognitive Complexity · SkyframeFocuser.run (cognitive 20) src/main/java/com/google/devtools/build/lib/skyframe/SkyframeFocuser.java
- Cognitive Complexity · BzlCompileFunction.isFileAllowlisted (cognitive 20) src/main/java/com/google/devtools/build/lib/skyframe/BzlCompileFunction.java
- Cognitive Complexity · TarFileWriter.add_file (cognitive 18) tools/build_defs/pkg/archive.py
- Cognitive Complexity · CommandEnvironment.beforeCommand (cognitive 16) src/main/java/com/google/devtools/build/lib/runtime/CommandEnvironment.java
- Cognitive Complexity · IndexRegistry.createLocalPathRepoSpec (cognitive 16) src/main/java/com/google/devtools/build/lib/bazel/bzlmod/IndexRegistry.java
- God Classes · MethodTooLong: SkyfocusExecutor.prepareActiveDirectories src/main/java/com/google/devtools/build/lib/skyframe/SkyfocusExecutor.java
- God Classes · MethodTooLong: FrontierSerializer.serializeAndUploadFrontier src/main/java/com/google/devtools/build/lib/skyframe/serialization/analysis/FrontierSerializer.java
- God Classes · FileTooLong: skyframe/BzlCompileFunction.java src/main/java/com/google/devtools/build/lib/skyframe/BzlCompileFunction.java
- Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) src/main/java/com/google/devtools/build/lib/rules/cpp/CppCompileAction.java
- Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) src/main/java/com/google/devtools/build/lib/bazel/commands/FetchCommand.java
- Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) src/main/java/com/google/devtools/build/lib/runtime/commands/AqueryCommand.java
- Code Duplication · Duplicated block (19–20 lines × 3) src/main/java/com/google/devtools/build/lib/skyframe/serialization/analysis/FileDependencySerializer.java
- Code Duplication · Duplicated block (14–16 lines × 2) src/main/java/com/google/devtools/build/lib/skyframe/BzlCompileFunction.java
- Code Duplication · Duplicated block (11 lines × 3) src/main/java/com/google/devtools/build/lib/skyframe/BzlCompileFunction.java
- Code Duplication · Duplicated block (10 lines × 2) src/main/java/com/google/devtools/build/lib/analysis/ConfiguredAspect.java
- Code Duplication · Duplicated block (10 lines × 2) src/main/java/com/google/devtools/build/lib/skyframe/serialization/analysis/FrontierSerializer.java
- Code Duplication · Duplicated block (5 lines × 2) src/main/java/com/google/devtools/build/lib/analysis/config/BuildConfigurationValue.java
- Cohesion (LCOM4) · Low cohesion: Builder (LCOM4 6) src/main/java/com/google/devtools/build/lib/analysis/ConfiguredRuleClassProvider.java
- Test Quality · No assertions: testRule src/test/java/com/google/devtools/build/docgen/RuleLinkExpanderTest.java
- Test Quality · No assertions: testRuleAndAttribute src/test/java/com/google/devtools/build/docgen/RuleLinkExpanderTest.java
- Test Quality · No assertions: testRuleArgs src/test/java/com/google/devtools/build/docgen/RuleLinkExpanderTest.java
- Test Quality · No assertions: testRuleExamples src/test/java/com/google/devtools/build/docgen/RuleLinkExpanderTest.java
- Test Quality · No assertions: testRuleHeadingLink src/test/java/com/google/devtools/build/docgen/RuleLinkExpanderTest.java
- Test Quality · No assertions: testRuleImplicitOutputsj src/test/java/com/google/devtools/build/docgen/RuleLinkExpanderTest.java
- Test Quality · No assertions: testStaticPageHeadingLink_pageReplacedBySinglePageBE src/test/java/com/google/devtools/build/docgen/RuleLinkExpanderTest.java
- Test Quality · No assertions: testStaticPageHeadingLink_separatePage src/test/java/com/google/devtools/build/docgen/RuleLinkExpanderTest.java
- Test Quality · No assertions: testStaticPageRef_pageReplacedBySinglePageBE src/test/java/com/google/devtools/build/docgen/RuleLinkExpanderTest.java
- Test Quality · No assertions: testStaticPageRef_separatePage src/test/java/com/google/devtools/build/docgen/RuleLinkExpanderTest.java
- Test Quality · No assertions: testUpperCaseRule src/test/java/com/google/devtools/build/docgen/RuleLinkExpanderTest.java
- Test Quality · No assertions: testStarlarkRuleClassBuiltInItemsAreDocumented src/test/java/com/google/devtools/build/docgen/StarlarkDocumentationTest.java
- Test Quality · No assertions: testSaveDiscoverInputs src/test/java/com/google/devtools/build/lib/actions/cache/CompactPersistentActionCacheTest.java
- Test Quality · No assertions: testSaveNoDiscoverInputs src/test/java/com/google/devtools/build/lib/actions/cache/CompactPersistentActionCacheTest.java
- Test Quality · No assertions: testCategories src/test/java/com/google/devtools/build/lib/actions/ActionExecutionStatusReporterTest.java
- Test Quality · No assertions: testDynamicUpdate src/test/java/com/google/devtools/build/lib/actions/ActionExecutionStatusReporterTest.java
- Test Quality · No assertions: testGroups src/test/java/com/google/devtools/build/lib/actions/ActionExecutionStatusReporterTest.java
- Test Quality · No assertions: testNoProgressMessage src/test/java/com/google/devtools/build/lib/actions/ActionExecutionStatusReporterTest.java
- Test Quality · No assertions: testOrdering src/test/java/com/google/devtools/build/lib/actions/ActionExecutionStatusReporterTest.java
- Test Quality · No assertions: testSingleAction src/test/java/com/google/devtools/build/lib/actions/ActionExecutionStatusReporterTest.java
- Test Quality · No assertions: testTruncation src/test/java/com/google/devtools/build/lib/actions/ActionExecutionStatusReporterTest.java
- Test Quality · No assertions: getMetadata_missingFileWithinTree_returnsNull src/test/java/com/google/devtools/build/lib/actions/ActionInputMapTest.java
- Test Quality · No assertions: getters_missingTree_returnNull src/test/java/com/google/devtools/build/lib/actions/ActionInputMapTest.java
- Test Quality · No assertions: putTreeArtifact_mixedTreeAndFiles_addsTreeAndChildren src/test/java/com/google/devtools/build/lib/actions/ActionInputMapTest.java
- Test Quality · No assertions: putTreeArtifact_multipleTreesUnderSameDirectory_addsAllTrees src/test/java/com/google/devtools/build/lib/actions/ActionInputMapTest.java
- Test Quality · No assertions: putTreeArtifact_multipleTrees_addsAllTreesAndChildren src/test/java/com/google/devtools/build/lib/actions/ActionInputMapTest.java
- Test Quality · No assertions: put_treeFileArtifact_addsEntry src/test/java/com/google/devtools/build/lib/actions/ActionInputMapTest.java
- Test Quality · No assertions: testCanWriteExecutableFile src/test/java/com/google/devtools/build/lib/analysis/actions/BinaryFileWriteActionTest.java
- Test Quality · No assertions: testCanWriteNonExecutableFile src/test/java/com/google/devtools/build/lib/analysis/actions/BinaryFileWriteActionTest.java
- Test Quality · No assertions: testDestinationArtifactIsOutput src/test/java/com/google/devtools/build/lib/analysis/actions/BinaryFileWriteActionTest.java
- Test Quality · No assertions: testNoInputs src/test/java/com/google/devtools/build/lib/analysis/actions/BinaryFileWriteActionTest.java
- Test Quality · No assertions: testCanWriteExecutableFile src/test/java/com/google/devtools/build/lib/analysis/actions/FileWriteActionTest.java
- Test Quality · No assertions: testCanWriteNonExecutableFile src/test/java/com/google/devtools/build/lib/analysis/actions/FileWriteActionTest.java
- Test Quality · No assertions: testDestinationArtifactIsOutput src/test/java/com/google/devtools/build/lib/analysis/actions/FileWriteActionTest.java
- Test Quality · No assertions: testNoInputs src/test/java/com/google/devtools/build/lib/analysis/actions/FileWriteActionTest.java
- Test Quality · No assertions: testArtifactTemplateExpansion src/test/java/com/google/devtools/build/lib/analysis/actions/TemplateExpansionActionTest.java
- Test Quality · No assertions: testWithSpecialCharacters src/test/java/com/google/devtools/build/lib/analysis/actions/TemplateExpansionActionTest.java
- Test Quality · No assertions: executionInfoModifier_multipleExpressions src/test/java/com/google/devtools/build/lib/analysis/config/ExecutionInfoModifierTest.java
- Test Quality · No assertions: executionInfoModifier_multipleOptions src/test/java/com/google/devtools/build/lib/analysis/config/ExecutionInfoModifierTest.java
- Test Quality · No assertions: testParsing src/test/java/com/google/devtools/build/lib/analysis/config/PerLabelOptionsTest.java
- Test Quality · No assertions: testConverter src/test/java/com/google/devtools/build/lib/analysis/config/RunUnderConverterTest.java
- Test Quality · No assertions: testAttributeTypeChecking src/test/java/com/google/devtools/build/lib/analysis/select/NonconfigurableAttributeMapperTest.java
- Test Quality · No assertions: testVisitation src/test/java/com/google/devtools/build/lib/analysis/select/NonconfigurableAttributeMapperTest.java
- Test Quality · No assertions: add_all_name src/test/java/com/google/devtools/build/lib/analysis/starlark/FlagPerLineTest.java
- Test Quality · No assertions: add_all_noname src/test/java/com/google/devtools/build/lib/analysis/starlark/FlagPerLineTest.java
- Test Quality · No assertions: add_joined_name src/test/java/com/google/devtools/build/lib/analysis/starlark/FlagPerLineTest.java
- Test Quality · No assertions: add_joined_noname src/test/java/com/google/devtools/build/lib/analysis/starlark/FlagPerLineTest.java
- Test Quality · No assertions: add_name src/test/java/com/google/devtools/build/lib/analysis/starlark/FlagPerLineTest.java
- Test Quality · No assertions: add_noname src/test/java/com/google/devtools/build/lib/analysis/starlark/FlagPerLineTest.java
- Test Quality · No assertions: args_combinedOmittedAddAllAndAdd src/test/java/com/google/devtools/build/lib/analysis/starlark/FlagPerLineTest.java
- Test Quality · No assertions: testFunctionSplitTransitionCheckAttrDep src/test/java/com/google/devtools/build/lib/analysis/starlark/StarlarkAttrTransitionProviderTest.java
- Test Quality · No assertions: testFunctionSplitTransitionCheckAttrDeps src/test/java/com/google/devtools/build/lib/analysis/starlark/StarlarkAttrTransitionProviderTest.java
- Test Quality · No assertions: testNoOpTransitionLeavesSameConfig_native_directRead src/test/java/com/google/devtools/build/lib/analysis/starlark/StarlarkAttrTransitionProviderTest.java
- Test Quality · No assertions: testNoOpTransitionLeavesSameConfig_native_setToSame src/test/java/com/google/devtools/build/lib/analysis/starlark/StarlarkAttrTransitionProviderTest.java
- Test Quality · No assertions: testNoOpTransitionLeavesSameConfig_starlark_directRead src/test/java/com/google/devtools/build/lib/analysis/starlark/StarlarkAttrTransitionProviderTest.java
- Test Quality · No assertions: testNoOpTransitionLeavesSameConfig_starlark_setToDefault src/test/java/com/google/devtools/build/lib/analysis/starlark/StarlarkAttrTransitionProviderTest.java
- Test Quality · No assertions: testNoOpTransitionLeavesSameConfig_starlark_setToSame src/test/java/com/google/devtools/build/lib/analysis/starlark/StarlarkAttrTransitionProviderTest.java
- Test Quality · No assertions: testOptionConversionCrosstoolTop src/test/java/com/google/devtools/build/lib/analysis/starlark/StarlarkAttrTransitionProviderTest.java
- Test Quality · No assertions: testOptionConversionDynamicMode src/test/java/com/google/devtools/build/lib/analysis/starlark/StarlarkAttrTransitionProviderTest.java
- Test Quality · No assertions: testSubruleFunctionSymbol_notVisibleInBUILD src/test/java/com/google/devtools/build/lib/analysis/starlark/StarlarkSubruleTest.java
- Test Quality · No assertions: testSharding src/test/java/com/google/devtools/build/lib/analysis/test/TestActionBuilderTest.java
- Test Quality · No assertions: testShardingDisabled src/test/java/com/google/devtools/build/lib/analysis/test/TestActionBuilderTest.java
- Test Quality · No assertions: testShardingForced src/test/java/com/google/devtools/build/lib/analysis/test/TestActionBuilderTest.java
- Test Quality · No assertions: testDefaultTimeout src/test/java/com/google/devtools/build/lib/analysis/test/TestTimeoutConverterTest.java
- Test Quality · No assertions: testIncorrectStrings src/test/java/com/google/devtools/build/lib/analysis/test/TestTimeoutConverterTest.java
Rebuild cost: about €1,500,000 · Estimate
| Cost to rebuild | €490,000 to €2,500,000, for 8,197 to 26,005 hours of work, about 10.2 person-years for 6 to 20 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 60. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Very large: 595,527 lines of product code |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 net.starlark.java.syntax | 2 com.google.devtools.build.lib.events | 3 com.google.devtools.common.options | 4 net.starlark.java.eval | 5 proguard.classfile.visitor | 6 com.google.devtools.build.skyframe | 7 proguard.classfile.constant.visitor | 8 com.google.devtools.build.lib.vfs | 9 proguard.classfile.editor | 10 com.google.devtools.build.lib.skyframe.config | 11 com.google.devtools.build.lib.util | 12 proguard.classfile.util | 13 com.google.devtools.build.lib.bazel.bzlmod | 14 com.google.devtools.build.lib.buildeventstream | 15 com.google.devtools.build.lib.exec | 16 com.google.devtools.build.lib.query2.common | 17 proguard.classfile.attribute.visitor | 18 com.google.devtools.build.lib.pkgcache | 19 com.google.devtools.build.lib.skyframe.serialization.analysis | 20 proguard.classfile.attribute | 21 com.google.devtools.build.lib.query2 | 22 proguard.classfile | 23 com.google.devtools.build.lib.buildtool | 24 com.google.devtools.build.lib.skyframe | 25 com.google.devtools.build.lib.packages | 26 com.google.devtools.build.lib.analysis.starlark | 27 com.google.devtools.build.lib.analysis.test | 28 com.google.devtools.build.lib.runtime | 29 com.google.devtools.build.lib.skyframe.serialization | 30 com.google.devtools.build.lib.collect.nestedset | 31 com.google.devtools.build.lib.cmdline | 32 com.google.devtools.build.lib.analysis.platform | 33 com.google.devtools.build.lib.analysis.config | 34 com.google.devtools.build.lib.analysis.actions | 35 com.google.devtools.build.lib.analysis | 36 com.google.devtools.build.lib.remote | 37 com.google.devtools.build.lib.actions | 38 com.google.devtools.build.lib.rules.cpp | 39 com.google.devtools.build.lib.runtime.commands | 40 com.google.devtools.build.lib.bazel |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 net.starlark.java.syntax | ||||||||||||||||||||||||||||||||||||||||
| 2 com.google.devtools.build.lib.events | 3 | |||||||||||||||||||||||||||||||||||||||
| 3 com.google.devtools.common.options | 1 | |||||||||||||||||||||||||||||||||||||||
| 4 net.starlark.java.eval | 97 | |||||||||||||||||||||||||||||||||||||||
| 5 proguard.classfile.visitor | 11 | 22 | 31 | 70 | 259 | |||||||||||||||||||||||||||||||||||
| 6 com.google.devtools.build.skyframe | 26 | 5 | 1 | 9 | 2 | |||||||||||||||||||||||||||||||||||
| 7 proguard.classfile.constant.visitor | 2 | 5 | 3 | 4 | 13 | |||||||||||||||||||||||||||||||||||
| 8 com.google.devtools.build.lib.vfs | 3 | 1 | 2 | 5 | 1 | 5 | 1 | 15 | ||||||||||||||||||||||||||||||||
| 9 proguard.classfile.editor | 35 | 16 | 45 | 70 | 212 | 201 | ||||||||||||||||||||||||||||||||||
| 10 com.google.devtools.build.lib.skyframe.config | 2 | 8 | 34 | 1 | 2 | 3 | 2 | 8 | 9 | 16 | 2 | 2 | ||||||||||||||||||||||||||||
| 11 com.google.devtools.build.lib.util | 11 | 17 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 12 proguard.classfile.util | 15 | 11 | 6 | 10 | 44 | 81 | ||||||||||||||||||||||||||||||||||
| 13 com.google.devtools.build.lib.bazel.bzlmod | 18 | 11 | 56 | 84 | 22 | 1 | 4 | 8 | 8 | 40 | 3 | |||||||||||||||||||||||||||||
| 14 com.google.devtools.build.lib.buildeventstream | 2 | 3 | 7 | 1 | 3 | 1 | 2 | 3 | ||||||||||||||||||||||||||||||||
| 15 com.google.devtools.build.lib.exec | 10 | 6 | 51 | 6 | 3 | 6 | 1 | 1 | 2 | 3 | 3 | 2 | 120 | |||||||||||||||||||||||||||
| 16 com.google.devtools.build.lib.query2.common | 4 | 2 | 2 | 6 | 3 | 1 | 1 | 7 | 7 | 1 | 1 | |||||||||||||||||||||||||||||
| 17 proguard.classfile.attribute.visitor | 3 | 9 | 159 | 54 | ||||||||||||||||||||||||||||||||||||
| 18 com.google.devtools.build.lib.pkgcache | 12 | 6 | 8 | 3 | 2 | 1 | 33 | 26 | 1 | |||||||||||||||||||||||||||||||
| 19 com.google.devtools.build.lib.skyframe.serialization.analysis | 5 | 6 | 42 | 10 | 2 | 2 | 18 | 1 | 2 | 83 | 8 | 3 | 1 | 6 | ||||||||||||||||||||||||||
| 20 proguard.classfile.attribute | 5 | 5 | 26 | 49 | ||||||||||||||||||||||||||||||||||||
| 21 com.google.devtools.build.lib.query2 | 3 | 1 | 26 | 5 | 6 | 6 | 4 | 19 | 22 | 2 | 2 | 1 | ||||||||||||||||||||||||||||
| 22 proguard.classfile | 20 | 3 | 6 | 4 | ||||||||||||||||||||||||||||||||||||
| 23 com.google.devtools.build.lib.buildtool | 8 | 11 | 14 | 22 | 1 | 10 | 2 | 5 | 2 | 3 | 8 | 2 | 17 | 2 | 2 | 18 | 1 | 1 | 10 | 20 | 24 | 17 | ||||||||||||||||||
| 24 com.google.devtools.build.lib.skyframe | 23 | 64 | 11 | 17 | 543 | 226 | 21 | 40 | 3 | 2 | 5 | 37 | 12 | 1 | 196 | 3 | 6 | 22 | 41 | 224 | 1 | 29 | 127 | 310 | ||||||||||||||||
| 25 com.google.devtools.build.lib.packages | 56 | 29 | 2 | 140 | 3 | 32 | 20 | 6 | 16 | 4 | 145 | 10 | 5 | 2 | ||||||||||||||||||||||||||
| 26 com.google.devtools.build.lib.analysis.starlark | 9 | 9 | 115 | 3 | 4 | 11 | 2 | 57 | 1 | 8 | 33 | 2 | 22 | 4 | 29 | 76 | ||||||||||||||||||||||||
| 27 com.google.devtools.build.lib.analysis.test | 3 | 7 | 13 | 10 | 13 | 4 | 1 | 1 | 19 | 1 | 1 | 12 | 10 | 1 | 18 | 3 | 21 | 58 | ||||||||||||||||||||||
| 28 com.google.devtools.build.lib.runtime | 1 | 27 | 74 | 6 | 56 | 25 | 37 | 10 | 2 | 11 | 3 | 2 | 5 | 23 | 13 | 4 | 4 | 4 | 11 | 8 | 36 | 71 | ||||||||||||||||||
| 29 com.google.devtools.build.lib.skyframe.serialization | 10 | 3 | 7 | 1 | 3 | 1 | 1 | 3 | ||||||||||||||||||||||||||||||||
| 30 com.google.devtools.build.lib.collect.nestedset | 8 | 3 | 1 | 5 | 21 | 4 | ||||||||||||||||||||||||||||||||||
| 31 com.google.devtools.build.lib.cmdline | 2 | 7 | 7 | 13 | 2 | 1 | 15 | 1 | 1 | |||||||||||||||||||||||||||||||
| 32 com.google.devtools.build.lib.analysis.platform | 12 | 8 | 1 | 4 | 1 | 13 | 10 | 3 | 3 | 1 | ||||||||||||||||||||||||||||||
| 33 com.google.devtools.build.lib.analysis.config | 5 | 8 | 25 | 16 | 1 | 3 | 1 | 9 | 1 | 1 | 5 | 7 | 4 | 11 | 35 | 1 | 7 | 12 | ||||||||||||||||||||||
| 34 com.google.devtools.build.lib.analysis.actions | 3 | 6 | 7 | 33 | 1 | 18 | 1 | 2 | 6 | 3 | 190 | |||||||||||||||||||||||||||||
| 35 com.google.devtools.build.lib.analysis | 8 | 11 | 6 | 38 | 5 | 29 | 3 | 30 | 22 | 2 | 2 | 1 | 35 | 154 | 4 | 5 | 1 | 11 | 54 | 81 | 12 | 46 | 11 | 140 | ||||||||||||||||
| 36 com.google.devtools.build.lib.remote | 17 | 3 | 9 | 100 | 9 | 5 | 14 | 1 | 4 | 22 | 3 | 1 | 1 | 12 | 78 | |||||||||||||||||||||||||
| 37 com.google.devtools.build.lib.actions | 5 | 11 | 3 | 17 | 11 | 132 | 1 | 36 | 6 | 20 | 4 | 24 | 21 | 17 | 10 | 7 | 2 | 2 | ||||||||||||||||||||||
| 38 com.google.devtools.build.lib.rules.cpp | 1 | 3 | 5 | 31 | 1 | 25 | 30 | 1 | 28 | 6 | 3 | 16 | 9 | 6 | 16 | 6 | 11 | 141 | ||||||||||||||||||||||
| 39 com.google.devtools.build.lib.runtime.commands | 3 | 44 | 3 | 9 | 2 | 13 | 1 | 2 | 4 | 1 | 5 | 2 | 5 | 69 | 1 | 2 | 8 | 7 | 5 | |||||||||||||||||||||
| 40 com.google.devtools.build.lib.bazel | 1 | 7 | 8 | 6 | 7 | 4 | 2 | 2 | 24 | 1 | 9 | 4 | 1 |
2→1 com.google.devtools.build.lib.events uses net.starlark.java.syntax✕
- Connections
- 3 pairs of types, where a type in com.google.devtools.build.lib.events uses a type in net.starlark.java.syntax.
- The types involved
com.google.devtools.build.lib.events.Event→net.starlark.java.syntax.Locationcom.google.devtools.build.lib.events.Event→net.starlark.java.syntax.SyntaxErrorcom.google.devtools.build.lib.events.Reporter→net.starlark.java.syntax.Location
- Direction
- com.google.devtools.build.lib.events uses net.starlark.java.syntax, so a change to net.starlark.java.syntax can break com.google.devtools.build.lib.events, while a change to com.google.devtools.build.lib.events can't break net.starlark.java.syntax.
- Position
- Below the diagonal: com.google.devtools.build.lib.events uses a module listed above it, which is the healthy direction.
3→11 com.google.devtools.common.options uses com.google.devtools.build.lib.util part of a loop✕
- Connections
- 1 pair of types, where a type in com.google.devtools.common.options uses a type in com.google.devtools.build.lib.util.
- The types involved
com.google.devtools.common.options.OptionsParser→com.google.devtools.build.lib.util.Pair
- Direction
- com.google.devtools.common.options uses com.google.devtools.build.lib.util, so a change to com.google.devtools.build.lib.util can break com.google.devtools.common.options, while a change to com.google.devtools.common.options can't break com.google.devtools.build.lib.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.
4→1 net.starlark.java.eval uses net.starlark.java.syntax✕
- Connections
- 97 pairs of types, where a type in net.starlark.java.eval uses a type in net.starlark.java.syntax. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
net.starlark.java.eval.BuiltinFunction→net.starlark.java.syntax.StarlarkTypenet.starlark.java.eval.BuiltinManager→net.starlark.java.syntax.StarlarkTypenet.starlark.java.eval.BuiltinManager→net.starlark.java.syntax.TypeConstructornet.starlark.java.eval.BuiltinManager→net.starlark.java.syntax.TypeContextnet.starlark.java.eval.BuiltinTypeFunction→net.starlark.java.syntax.StarlarkTypenet.starlark.java.eval.BuiltinTypeFunction→net.starlark.java.syntax.Termnet.starlark.java.eval.BuiltinTypeFunction→net.starlark.java.syntax.TypeConstructornet.starlark.java.eval.BuiltinTypeFunctionType→net.starlark.java.syntax.StarlarkTypenet.starlark.java.eval.BuiltinTypeFunctionType→net.starlark.java.syntax.TypeContextnet.starlark.java.eval.CallStackEntry→net.starlark.java.syntax.Locationnet.starlark.java.eval.CallUtils→net.starlark.java.syntax.StarlarkTypenet.starlark.java.eval.CallUtils→net.starlark.java.syntax.TypeConstructornet.starlark.java.eval.ClassDescriptor→net.starlark.java.syntax.StarlarkTypenet.starlark.java.eval.ClassDescriptor→net.starlark.java.syntax.TypeConstructornet.starlark.java.eval.Debugger→net.starlark.java.syntax.Locationnet.starlark.java.eval.Dict→net.starlark.java.syntax.StarlarkTypenet.starlark.java.eval.Dict→net.starlark.java.syntax.TypeConstructornet.starlark.java.eval.Eval→net.starlark.java.syntax.Argumentnet.starlark.java.eval.Eval→net.starlark.java.syntax.AssignmentStatementnet.starlark.java.eval.Eval→net.starlark.java.syntax.BinaryOperatorExpressionnet.starlark.java.eval.Eval→net.starlark.java.syntax.CallExpressionnet.starlark.java.eval.Eval→net.starlark.java.syntax.Comprehensionnet.starlark.java.eval.Eval→net.starlark.java.syntax.ConditionalExpressionnet.starlark.java.eval.Eval→net.starlark.java.syntax.DictExpressionnet.starlark.java.eval.Eval→net.starlark.java.syntax.DotExpression
- Direction
- net.starlark.java.eval uses net.starlark.java.syntax, so a change to net.starlark.java.syntax can break net.starlark.java.eval, while a change to net.starlark.java.eval can't break net.starlark.java.syntax.
- Position
- Below the diagonal: net.starlark.java.eval uses a module listed above it, which is the healthy direction.
5→7 proguard.classfile.visitor uses proguard.classfile.constant.visitor part of a loop✕
- Connections
- 11 pairs of types, where a type in proguard.classfile.visitor uses a type in proguard.classfile.constant.visitor.
- The types involved
proguard.classfile.visitor.ClassCleaner→proguard.classfile.constant.visitor.ConstantVisitorproguard.classfile.visitor.ClassPrinter→proguard.classfile.constant.visitor.ConstantVisitorproguard.classfile.visitor.DotClassClassVisitor→proguard.classfile.constant.visitor.ConstantVisitorproguard.classfile.visitor.DynamicReturnedClassVisitor→proguard.classfile.constant.visitor.ConstantVisitorproguard.classfile.visitor.ExceptionHandlerConstantVisitor→proguard.classfile.constant.visitor.ConstantVisitorproguard.classfile.visitor.ImplementedClassConstantFilter→proguard.classfile.constant.visitor.ConstantVisitorproguard.classfile.visitor.ImplementingClassConstantFilter→proguard.classfile.constant.visitor.ConstantVisitorproguard.classfile.visitor.MultiConstantVisitor→proguard.classfile.constant.visitor.ConstantVisitorproguard.classfile.visitor.ReferencedClassVisitor→proguard.classfile.constant.visitor.ConstantVisitorproguard.classfile.visitor.ReferencedMemberVisitor→proguard.classfile.constant.visitor.ConstantVisitorproguard.classfile.visitor.VisitorInfoSetter→proguard.classfile.constant.visitor.ConstantVisitor
- Direction
- proguard.classfile.visitor uses proguard.classfile.constant.visitor, so a change to proguard.classfile.constant.visitor can break proguard.classfile.visitor, while a change to proguard.classfile.visitor can't break proguard.classfile.constant.visitor.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
5→12 proguard.classfile.visitor uses proguard.classfile.util part of a loop✕
- Connections
- 22 pairs of types, where a type in proguard.classfile.visitor uses a type in proguard.classfile.util.
- The types involved
proguard.classfile.visitor.ClassCleaner→proguard.classfile.util.SimplifiedVisitorproguard.classfile.visitor.ClassCollector→proguard.classfile.util.SimplifiedVisitorproguard.classfile.visitor.ClassPoolFiller→proguard.classfile.util.SimplifiedVisitorproguard.classfile.visitor.ClassPoolRemover→proguard.classfile.util.SimplifiedVisitorproguard.classfile.visitor.ClassPrinter→proguard.classfile.util.SimplifiedVisitorproguard.classfile.visitor.ConstructorMethodFilter→proguard.classfile.util.InstructionSequenceMatcherproguard.classfile.visitor.ConstructorMethodFilter→proguard.classfile.util.SimplifiedVisitorproguard.classfile.visitor.DotClassClassVisitor→proguard.classfile.util.SimplifiedVisitorproguard.classfile.visitor.DynamicReturnedClassVisitor→proguard.classfile.util.SimplifiedVisitorproguard.classfile.visitor.ImplementedClassConstantFilter→proguard.classfile.util.SimplifiedVisitorproguard.classfile.visitor.ImplementingClassConstantFilter→proguard.classfile.util.SimplifiedVisitorproguard.classfile.visitor.MemberClassAccessFilter→proguard.classfile.util.NestHostFinderproguard.classfile.visitor.MemberCollector→proguard.classfile.util.SimplifiedVisitorproguard.classfile.visitor.MemberDescriptorReferencedClassVisitor→proguard.classfile.util.SimplifiedVisitorproguard.classfile.visitor.MethodCollector→proguard.classfile.util.SimplifiedVisitorproguard.classfile.visitor.MethodImplementationFilter→proguard.classfile.util.SimplifiedVisitorproguard.classfile.visitor.MethodImplementationTraveler→proguard.classfile.util.SimplifiedVisitorproguard.classfile.visitor.MultiConstantVisitor→proguard.classfile.util.SimplifiedVisitorproguard.classfile.visitor.ReferencedClassVisitor→proguard.classfile.util.SimplifiedVisitorproguard.classfile.visitor.ReferencedMemberVisitor→proguard.classfile.util.SimplifiedVisitorproguard.classfile.visitor.SignatureAttributeReferencedClassVisitor→proguard.classfile.util.SimplifiedVisitorproguard.classfile.visitor.VisitorInfoSetter→proguard.classfile.util.SimplifiedVisitor
- Direction
- proguard.classfile.visitor uses proguard.classfile.util, so a change to proguard.classfile.util can break proguard.classfile.visitor, while a change to proguard.classfile.visitor can't break proguard.classfile.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.
5→17 proguard.classfile.visitor uses proguard.classfile.attribute.visitor part of a loop✕
- Connections
- 31 pairs of types, where a type in proguard.classfile.visitor uses a type in proguard.classfile.attribute.visitor. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
proguard.classfile.visitor.ClassCleaner→proguard.classfile.attribute.visitor.AttributeVisitorproguard.classfile.visitor.ClassCleaner→proguard.classfile.attribute.visitor.BootstrapMethodInfoVisitorproguard.classfile.visitor.ClassCleaner→proguard.classfile.attribute.visitor.ExceptionInfoVisitorproguard.classfile.visitor.ClassCleaner→proguard.classfile.attribute.visitor.InnerClassesInfoVisitorproguard.classfile.visitor.ClassCleaner→proguard.classfile.attribute.visitor.LocalVariableInfoVisitorproguard.classfile.visitor.ClassCleaner→proguard.classfile.attribute.visitor.LocalVariableTypeInfoVisitorproguard.classfile.visitor.ClassCleaner→proguard.classfile.attribute.visitor.ParameterInfoVisitorproguard.classfile.visitor.ClassPrinter→proguard.classfile.attribute.visitor.AttributeVisitorproguard.classfile.visitor.ClassPrinter→proguard.classfile.attribute.visitor.BootstrapMethodInfoVisitorproguard.classfile.visitor.ClassPrinter→proguard.classfile.attribute.visitor.ExceptionInfoVisitorproguard.classfile.visitor.ClassPrinter→proguard.classfile.attribute.visitor.InnerClassesInfoVisitorproguard.classfile.visitor.ClassPrinter→proguard.classfile.attribute.visitor.LineNumberInfoVisitorproguard.classfile.visitor.ClassPrinter→proguard.classfile.attribute.visitor.LocalVariableInfoVisitorproguard.classfile.visitor.ClassPrinter→proguard.classfile.attribute.visitor.LocalVariableTypeInfoVisitorproguard.classfile.visitor.ClassPrinter→proguard.classfile.attribute.visitor.ParameterInfoVisitorproguard.classfile.visitor.ConstructorMethodFilter→proguard.classfile.attribute.visitor.AttributeVisitorproguard.classfile.visitor.ExceptionCounter→proguard.classfile.attribute.visitor.ExceptionInfoVisitorproguard.classfile.visitor.ExceptionExcludedOffsetFilter→proguard.classfile.attribute.visitor.ExceptionInfoVisitorproguard.classfile.visitor.ExceptionHandlerConstantVisitor→proguard.classfile.attribute.visitor.ExceptionInfoVisitorproguard.classfile.visitor.ExceptionHandlerFilter→proguard.classfile.attribute.visitor.ExceptionInfoVisitorproguard.classfile.visitor.ExceptionOffsetFilter→proguard.classfile.attribute.visitor.ExceptionInfoVisitorproguard.classfile.visitor.ExceptionRangeFilter→proguard.classfile.attribute.visitor.ExceptionInfoVisitorproguard.classfile.visitor.ReferencedClassVisitor→proguard.classfile.attribute.visitor.AttributeVisitorproguard.classfile.visitor.ReferencedClassVisitor→proguard.classfile.attribute.visitor.LocalVariableInfoVisitorproguard.classfile.visitor.ReferencedClassVisitor→proguard.classfile.attribute.visitor.LocalVariableTypeInfoVisitor
- Direction
- proguard.classfile.visitor uses proguard.classfile.attribute.visitor, so a change to proguard.classfile.attribute.visitor can break proguard.classfile.visitor, while a change to proguard.classfile.visitor can't break proguard.classfile.attribute.visitor.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
5→20 proguard.classfile.visitor uses proguard.classfile.attribute part of a loop✕
- Connections
- 70 pairs of types, where a type in proguard.classfile.visitor uses a type in proguard.classfile.attribute. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
proguard.classfile.visitor.ClassCleaner→proguard.classfile.attribute.Attributeproguard.classfile.visitor.ClassCleaner→proguard.classfile.attribute.BootstrapMethodInfoproguard.classfile.visitor.ClassCleaner→proguard.classfile.attribute.BootstrapMethodsAttributeproguard.classfile.visitor.ClassCleaner→proguard.classfile.attribute.CodeAttributeproguard.classfile.visitor.ClassCleaner→proguard.classfile.attribute.ExceptionInfoproguard.classfile.visitor.ClassCleaner→proguard.classfile.attribute.ExceptionsAttributeproguard.classfile.visitor.ClassCleaner→proguard.classfile.attribute.InnerClassesAttributeproguard.classfile.visitor.ClassCleaner→proguard.classfile.attribute.InnerClassesInfoproguard.classfile.visitor.ClassCleaner→proguard.classfile.attribute.LocalVariableInfoproguard.classfile.visitor.ClassCleaner→proguard.classfile.attribute.LocalVariableTableAttributeproguard.classfile.visitor.ClassCleaner→proguard.classfile.attribute.LocalVariableTypeInfoproguard.classfile.visitor.ClassCleaner→proguard.classfile.attribute.LocalVariableTypeTableAttributeproguard.classfile.visitor.ClassCleaner→proguard.classfile.attribute.MethodParametersAttributeproguard.classfile.visitor.ClassCleaner→proguard.classfile.attribute.ParameterInfoproguard.classfile.visitor.ClassPrinter→proguard.classfile.attribute.BootstrapMethodInfoproguard.classfile.visitor.ClassPrinter→proguard.classfile.attribute.BootstrapMethodsAttributeproguard.classfile.visitor.ClassPrinter→proguard.classfile.attribute.CodeAttributeproguard.classfile.visitor.ClassPrinter→proguard.classfile.attribute.ConstantValueAttributeproguard.classfile.visitor.ClassPrinter→proguard.classfile.attribute.DeprecatedAttributeproguard.classfile.visitor.ClassPrinter→proguard.classfile.attribute.EnclosingMethodAttributeproguard.classfile.visitor.ClassPrinter→proguard.classfile.attribute.ExceptionInfoproguard.classfile.visitor.ClassPrinter→proguard.classfile.attribute.ExceptionsAttributeproguard.classfile.visitor.ClassPrinter→proguard.classfile.attribute.InnerClassesAttributeproguard.classfile.visitor.ClassPrinter→proguard.classfile.attribute.InnerClassesInfoproguard.classfile.visitor.ClassPrinter→proguard.classfile.attribute.LineNumberInfo
- Direction
- proguard.classfile.visitor uses proguard.classfile.attribute, so a change to proguard.classfile.attribute can break proguard.classfile.visitor, while a change to proguard.classfile.visitor can't break proguard.classfile.attribute.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
5→22 proguard.classfile.visitor uses proguard.classfile part of a loop✕
- Connections
- 259 pairs of types, where a type in proguard.classfile.visitor uses a type in proguard.classfile. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
proguard.classfile.visitor.AllClassVisitor→proguard.classfile.ClassPoolproguard.classfile.visitor.AllFieldVisitor→proguard.classfile.LibraryClassproguard.classfile.visitor.AllFieldVisitor→proguard.classfile.ProgramClassproguard.classfile.visitor.AllMemberVisitor→proguard.classfile.LibraryClassproguard.classfile.visitor.AllMemberVisitor→proguard.classfile.ProgramClassproguard.classfile.visitor.AllMethodVisitor→proguard.classfile.LibraryClassproguard.classfile.visitor.AllMethodVisitor→proguard.classfile.ProgramClassproguard.classfile.visitor.BottomClassFilter→proguard.classfile.LibraryClassproguard.classfile.visitor.BottomClassFilter→proguard.classfile.ProgramClassproguard.classfile.visitor.ClassAccessFilter→proguard.classfile.LibraryClassproguard.classfile.visitor.ClassAccessFilter→proguard.classfile.ProgramClassproguard.classfile.visitor.ClassCleaner→proguard.classfile.Clazzproguard.classfile.visitor.ClassCleaner→proguard.classfile.LibraryClassproguard.classfile.visitor.ClassCleaner→proguard.classfile.LibraryMemberproguard.classfile.visitor.ClassCleaner→proguard.classfile.Methodproguard.classfile.visitor.ClassCleaner→proguard.classfile.ProgramClassproguard.classfile.visitor.ClassCleaner→proguard.classfile.ProgramMemberproguard.classfile.visitor.ClassCleaner→proguard.classfile.VisitorAccepterproguard.classfile.visitor.ClassCollector→proguard.classfile.Clazzproguard.classfile.visitor.ClassCounter→proguard.classfile.LibraryClassproguard.classfile.visitor.ClassCounter→proguard.classfile.ProgramClassproguard.classfile.visitor.ClassHierarchyTraveler→proguard.classfile.LibraryClassproguard.classfile.visitor.ClassHierarchyTraveler→proguard.classfile.ProgramClassproguard.classfile.visitor.ClassNameFilter→proguard.classfile.LibraryClassproguard.classfile.visitor.ClassNameFilter→proguard.classfile.ProgramClass
- Direction
- proguard.classfile.visitor uses proguard.classfile, so a change to proguard.classfile can break proguard.classfile.visitor, while a change to proguard.classfile.visitor can't break proguard.classfile.
- 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→2 com.google.devtools.build.skyframe uses com.google.devtools.build.lib.events✕
- Connections
- 26 pairs of types, where a type in com.google.devtools.build.skyframe uses a type in com.google.devtools.build.lib.events. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.google.devtools.build.skyframe.AbstractInMemoryMemoizingEvaluator→com.google.devtools.build.lib.events.ExtendedEventHandlercom.google.devtools.build.skyframe.AbstractParallelEvaluator→com.google.devtools.build.lib.events.ExtendedEventHandlercom.google.devtools.build.skyframe.AbstractParallelEvaluator→com.google.devtools.build.lib.events.Reportablecom.google.devtools.build.skyframe.CyclesReporter→com.google.devtools.build.lib.events.ExtendedEventHandlercom.google.devtools.build.skyframe.EmittedEventState→com.google.devtools.build.lib.events.Eventcom.google.devtools.build.skyframe.EmittedEventState→com.google.devtools.build.lib.events.Reportablecom.google.devtools.build.skyframe.Environment→com.google.devtools.build.lib.events.ExtendedEventHandlercom.google.devtools.build.skyframe.ErrorInfoValue→com.google.devtools.build.lib.events.Reportablecom.google.devtools.build.skyframe.EvaluationContext→com.google.devtools.build.lib.events.ExtendedEventHandlercom.google.devtools.build.skyframe.MemoizingEvaluator→com.google.devtools.build.lib.events.ExtendedEventHandlercom.google.devtools.build.skyframe.NestedSetEventReceiver→com.google.devtools.build.lib.events.ExtendedEventHandlercom.google.devtools.build.skyframe.NestedSetEventReceiver→com.google.devtools.build.lib.events.Reportablecom.google.devtools.build.skyframe.NotComparableValueWithEvents→com.google.devtools.build.lib.events.Reportablecom.google.devtools.build.skyframe.ParallelEvaluator→com.google.devtools.build.lib.events.ExtendedEventHandlercom.google.devtools.build.skyframe.ParallelEvaluatorContext→com.google.devtools.build.lib.events.ExtendedEventHandlercom.google.devtools.build.skyframe.ParallelEvaluatorContext→com.google.devtools.build.lib.events.Reportablecom.google.devtools.build.skyframe.RecordingSkyFunctionEnvironment→com.google.devtools.build.lib.events.ExtendedEventHandlercom.google.devtools.build.skyframe.SingleCycleReporter→com.google.devtools.build.lib.events.ExtendedEventHandlercom.google.devtools.build.skyframe.SkyFunctionEnvironment→com.google.devtools.build.lib.events.Eventcom.google.devtools.build.skyframe.SkyFunctionEnvironment→com.google.devtools.build.lib.events.ExtendedEventHandlercom.google.devtools.build.skyframe.SkyFunctionEnvironment→com.google.devtools.build.lib.events.Reportablecom.google.devtools.build.skyframe.SkyframeGraphStatsEvent→com.google.devtools.build.lib.events.Postablecom.google.devtools.build.skyframe.ValueWithEvents→com.google.devtools.build.lib.events.Reportablecom.google.devtools.build.skyframe.ValueWithMetadata→com.google.devtools.build.lib.events.Reportablecom.google.devtools.build.skyframe.WorkerSkyFunctionEnvironment→com.google.devtools.build.lib.events.Event
- Direction
- com.google.devtools.build.skyframe uses com.google.devtools.build.lib.events, so a change to com.google.devtools.build.lib.events can break com.google.devtools.build.skyframe, while a change to com.google.devtools.build.skyframe can't break com.google.devtools.build.lib.events.
- Position
- Below the diagonal: com.google.devtools.build.skyframe uses a module listed above it, which is the healthy direction.
6→11 com.google.devtools.build.skyframe uses com.google.devtools.build.lib.util part of a loop✕
- Connections
- 5 pairs of types, where a type in com.google.devtools.build.skyframe uses a type in com.google.devtools.build.lib.util.
- The types involved
com.google.devtools.build.skyframe.DelegatingWalkableGraph→com.google.devtools.build.lib.util.Paircom.google.devtools.build.skyframe.DeletingNodeVisitor→com.google.devtools.build.lib.util.Paircom.google.devtools.build.skyframe.InvalidatingNodeVisitor→com.google.devtools.build.lib.util.Paircom.google.devtools.build.skyframe.InvalidationState→com.google.devtools.build.lib.util.Paircom.google.devtools.build.skyframe.WalkableGraph→com.google.devtools.build.lib.util.Pair
- Direction
- com.google.devtools.build.skyframe uses com.google.devtools.build.lib.util, so a change to com.google.devtools.build.lib.util can break com.google.devtools.build.skyframe, while a change to com.google.devtools.build.skyframe can't break com.google.devtools.build.lib.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→24 com.google.devtools.build.skyframe uses com.google.devtools.build.lib.skyframe part of a loop✕
- Connections
- 1 pair of types, where a type in com.google.devtools.build.skyframe uses a type in com.google.devtools.build.lib.skyframe.
- The types involved
com.google.devtools.build.skyframe.InMemoryGraphImpl→com.google.devtools.build.lib.skyframe.PackageoidValue
- Direction
- com.google.devtools.build.skyframe uses com.google.devtools.build.lib.skyframe, so a change to com.google.devtools.build.lib.skyframe can break com.google.devtools.build.skyframe, while a change to com.google.devtools.build.skyframe can't break com.google.devtools.build.lib.skyframe.
- 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→30 com.google.devtools.build.skyframe uses com.google.devtools.build.lib.collect.nestedset part of a loop✕
- Connections
- 9 pairs of types, where a type in com.google.devtools.build.skyframe uses a type in com.google.devtools.build.lib.collect.nestedset.
- The types involved
com.google.devtools.build.skyframe.AbstractParallelEvaluator→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.skyframe.ErrorInfoValue→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.skyframe.NestedSetEventReceiver→com.google.devtools.build.lib.collect.nestedset.Receivercom.google.devtools.build.skyframe.NotComparableValueWithEvents→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.skyframe.ParallelEvaluatorContext→com.google.devtools.build.lib.collect.nestedset.NestedSetVisitorcom.google.devtools.build.skyframe.SkyFunctionEnvironment→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.skyframe.SkyFunctionEnvironment→com.google.devtools.build.lib.collect.nestedset.NestedSetBuildercom.google.devtools.build.skyframe.ValueWithEvents→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.skyframe.ValueWithMetadata→com.google.devtools.build.lib.collect.nestedset.NestedSet
- Direction
- com.google.devtools.build.skyframe uses com.google.devtools.build.lib.collect.nestedset, so a change to com.google.devtools.build.lib.collect.nestedset can break com.google.devtools.build.skyframe, while a change to com.google.devtools.build.skyframe can't break com.google.devtools.build.lib.collect.nestedset.
- 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→31 com.google.devtools.build.skyframe uses com.google.devtools.build.lib.cmdline part of a loop✕
- Connections
- 2 pairs of types, where a type in com.google.devtools.build.skyframe uses a type in com.google.devtools.build.lib.cmdline.
- The types involved
com.google.devtools.build.skyframe.InMemoryGraphImpl→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.skyframe.LabelPool→com.google.devtools.build.lib.cmdline.Label
- Direction
- com.google.devtools.build.skyframe uses com.google.devtools.build.lib.cmdline, so a change to com.google.devtools.build.lib.cmdline can break com.google.devtools.build.skyframe, while a change to com.google.devtools.build.skyframe can't break com.google.devtools.build.lib.cmdline.
- 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→5 proguard.classfile.constant.visitor uses proguard.classfile.visitor✕
- Connections
- 2 pairs of types, where a type in proguard.classfile.constant.visitor uses a type in proguard.classfile.visitor.
- The types involved
proguard.classfile.constant.visitor.AllConstantVisitor→proguard.classfile.visitor.ClassVisitorproguard.classfile.constant.visitor.SuperClassConstantVisitor→proguard.classfile.visitor.ClassVisitor
- Direction
- proguard.classfile.constant.visitor uses proguard.classfile.visitor, so a change to proguard.classfile.visitor can break proguard.classfile.constant.visitor, while a change to proguard.classfile.constant.visitor can't break proguard.classfile.visitor.
- Position
- Below the diagonal: proguard.classfile.constant.visitor uses a module listed above it, which is the healthy direction.
7→12 proguard.classfile.constant.visitor uses proguard.classfile.util part of a loop✕
- Connections
- 5 pairs of types, where a type in proguard.classfile.constant.visitor uses a type in proguard.classfile.util.
- The types involved
proguard.classfile.constant.visitor.BootstrapMethodHandleTraveler→proguard.classfile.util.SimplifiedVisitorproguard.classfile.constant.visitor.ConstantCounter→proguard.classfile.util.SimplifiedVisitorproguard.classfile.constant.visitor.ConstantTagFilter→proguard.classfile.util.SimplifiedVisitorproguard.classfile.constant.visitor.ExceptClassConstantFilter→proguard.classfile.util.SimplifiedVisitorproguard.classfile.constant.visitor.MethodrefTraveler→proguard.classfile.util.SimplifiedVisitor
- Direction
- proguard.classfile.constant.visitor uses proguard.classfile.util, so a change to proguard.classfile.util can break proguard.classfile.constant.visitor, while a change to proguard.classfile.constant.visitor can't break proguard.classfile.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.
7→17 proguard.classfile.constant.visitor uses proguard.classfile.attribute.visitor part of a loop✕
- Connections
- 3 pairs of types, where a type in proguard.classfile.constant.visitor uses a type in proguard.classfile.attribute.visitor.
- The types involved
proguard.classfile.constant.visitor.AllBootstrapMethodArgumentVisitor→proguard.classfile.attribute.visitor.BootstrapMethodInfoVisitorproguard.classfile.constant.visitor.BootstrapMethodHandleTraveler→proguard.classfile.attribute.visitor.AttributeVisitorproguard.classfile.constant.visitor.BootstrapMethodHandleTraveler→proguard.classfile.attribute.visitor.BootstrapMethodInfoVisitor
- Direction
- proguard.classfile.constant.visitor uses proguard.classfile.attribute.visitor, so a change to proguard.classfile.attribute.visitor can break proguard.classfile.constant.visitor, while a change to proguard.classfile.constant.visitor can't break proguard.classfile.attribute.visitor.
- 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→20 proguard.classfile.constant.visitor uses proguard.classfile.attribute part of a loop✕
- Connections
- 4 pairs of types, where a type in proguard.classfile.constant.visitor uses a type in proguard.classfile.attribute.
- The types involved
proguard.classfile.constant.visitor.AllBootstrapMethodArgumentVisitor→proguard.classfile.attribute.BootstrapMethodInfoproguard.classfile.constant.visitor.BootstrapMethodHandleTraveler→proguard.classfile.attribute.Attributeproguard.classfile.constant.visitor.BootstrapMethodHandleTraveler→proguard.classfile.attribute.BootstrapMethodInfoproguard.classfile.constant.visitor.BootstrapMethodHandleTraveler→proguard.classfile.attribute.BootstrapMethodsAttribute
- Direction
- proguard.classfile.constant.visitor uses proguard.classfile.attribute, so a change to proguard.classfile.attribute can break proguard.classfile.constant.visitor, while a change to proguard.classfile.constant.visitor can't break proguard.classfile.attribute.
- 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→22 proguard.classfile.constant.visitor uses proguard.classfile part of a loop✕
- Connections
- 13 pairs of types, where a type in proguard.classfile.constant.visitor uses a type in proguard.classfile.
- The types involved
proguard.classfile.constant.visitor.AllBootstrapMethodArgumentVisitor→proguard.classfile.Clazzproguard.classfile.constant.visitor.AllConstantVisitor→proguard.classfile.LibraryClassproguard.classfile.constant.visitor.AllConstantVisitor→proguard.classfile.ProgramClassproguard.classfile.constant.visitor.BootstrapMethodHandleTraveler→proguard.classfile.Clazzproguard.classfile.constant.visitor.ConstantCounter→proguard.classfile.Clazzproguard.classfile.constant.visitor.ConstantTagFilter→proguard.classfile.Clazzproguard.classfile.constant.visitor.ConstantVisitor→proguard.classfile.Clazzproguard.classfile.constant.visitor.ExceptClassConstantFilter→proguard.classfile.Clazzproguard.classfile.constant.visitor.MethodrefTraveler→proguard.classfile.Clazzproguard.classfile.constant.visitor.PrimitiveArrayConstantElementVisitor→proguard.classfile.Clazzproguard.classfile.constant.visitor.PrimitiveArrayConstantVisitor→proguard.classfile.Clazzproguard.classfile.constant.visitor.SuperClassConstantVisitor→proguard.classfile.LibraryClassproguard.classfile.constant.visitor.SuperClassConstantVisitor→proguard.classfile.ProgramClass
- Direction
- proguard.classfile.constant.visitor uses proguard.classfile, so a change to proguard.classfile can break proguard.classfile.constant.visitor, while a change to proguard.classfile.constant.visitor can't break proguard.classfile.
- 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→2 com.google.devtools.build.lib.vfs uses com.google.devtools.build.lib.events✕
- Connections
- 3 pairs of types, where a type in com.google.devtools.build.lib.vfs uses a type in com.google.devtools.build.lib.events.
- The types involved
com.google.devtools.build.lib.vfs.LocalOutputService→com.google.devtools.build.lib.events.EventHandlercom.google.devtools.build.lib.vfs.ModifiedFileSet→com.google.devtools.build.lib.events.Eventcom.google.devtools.build.lib.vfs.OutputService→com.google.devtools.build.lib.events.EventHandler
- Direction
- com.google.devtools.build.lib.vfs uses com.google.devtools.build.lib.events, so a change to com.google.devtools.build.lib.events can break com.google.devtools.build.lib.vfs, while a change to com.google.devtools.build.lib.vfs can't break com.google.devtools.build.lib.events.
- Position
- Below the diagonal: com.google.devtools.build.lib.vfs uses a module listed above it, which is the healthy direction.
8→3 com.google.devtools.build.lib.vfs uses com.google.devtools.common.options✕
- Connections
- 1 pair of types, where a type in com.google.devtools.build.lib.vfs uses a type in com.google.devtools.common.options.
- The types involved
com.google.devtools.build.lib.vfs.DigestFunctionConverter→com.google.devtools.common.options.Contextless
- Direction
- com.google.devtools.build.lib.vfs uses com.google.devtools.common.options, so a change to com.google.devtools.common.options can break com.google.devtools.build.lib.vfs, while a change to com.google.devtools.build.lib.vfs can't break com.google.devtools.common.options.
- Position
- Below the diagonal: com.google.devtools.build.lib.vfs uses a module listed above it, which is the healthy direction.
8→6 com.google.devtools.build.lib.vfs uses com.google.devtools.build.skyframe✕
- Connections
- 2 pairs of types, where a type in com.google.devtools.build.lib.vfs uses a type in com.google.devtools.build.skyframe.
- The types involved
com.google.devtools.build.lib.vfs.FileStateKey→com.google.devtools.build.skyframe.SkyFunctionNamecom.google.devtools.build.lib.vfs.FileStateKey→com.google.devtools.build.skyframe.SkyKey
- Direction
- com.google.devtools.build.lib.vfs uses com.google.devtools.build.skyframe, so a change to com.google.devtools.build.skyframe can break com.google.devtools.build.lib.vfs, while a change to com.google.devtools.build.lib.vfs can't break com.google.devtools.build.skyframe.
- Position
- Below the diagonal: com.google.devtools.build.lib.vfs uses a module listed above it, which is the healthy direction.
8→11 com.google.devtools.build.lib.vfs uses com.google.devtools.build.lib.util part of a loop✕
- Connections
- 5 pairs of types, where a type in com.google.devtools.build.lib.vfs uses a type in com.google.devtools.build.lib.util.
- The types involved
com.google.devtools.build.lib.vfs.DetailedIOException→com.google.devtools.build.lib.util.DetailedExitCodecom.google.devtools.build.lib.vfs.OsPathPolicy→com.google.devtools.build.lib.util.OScom.google.devtools.build.lib.vfs.Path→com.google.devtools.build.lib.util.HasFileTypecom.google.devtools.build.lib.vfs.PathFragment→com.google.devtools.build.lib.util.HasFileTypecom.google.devtools.build.lib.vfs.PathFragment→com.google.devtools.build.lib.util.OS
- Direction
- com.google.devtools.build.lib.vfs uses com.google.devtools.build.lib.util, so a change to com.google.devtools.build.lib.util can break com.google.devtools.build.lib.vfs, while a change to com.google.devtools.build.lib.vfs can't break com.google.devtools.build.lib.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.
8→24 com.google.devtools.build.lib.vfs uses com.google.devtools.build.lib.skyframe part of a loop✕
- Connections
- 1 pair of types, where a type in com.google.devtools.build.lib.vfs uses a type in com.google.devtools.build.lib.skyframe.
- The types involved
com.google.devtools.build.lib.vfs.DetailedIOException→com.google.devtools.build.lib.skyframe.DetailedException
- Direction
- com.google.devtools.build.lib.vfs uses com.google.devtools.build.lib.skyframe, so a change to com.google.devtools.build.lib.skyframe can break com.google.devtools.build.lib.vfs, while a change to com.google.devtools.build.lib.vfs can't break com.google.devtools.build.lib.skyframe.
- 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→29 com.google.devtools.build.lib.vfs uses com.google.devtools.build.lib.skyframe.serialization part of a loop✕
- Connections
- 5 pairs of types, where a type in com.google.devtools.build.lib.vfs uses a type in com.google.devtools.build.lib.skyframe.serialization.
- The types involved
com.google.devtools.build.lib.vfs.Codec→com.google.devtools.build.lib.skyframe.serialization.EnumCodeccom.google.devtools.build.lib.vfs.RootCodec→com.google.devtools.build.lib.skyframe.serialization.AsyncDeserializationContextcom.google.devtools.build.lib.vfs.RootCodec→com.google.devtools.build.lib.skyframe.serialization.AsyncObjectCodeccom.google.devtools.build.lib.vfs.RootCodec→com.google.devtools.build.lib.skyframe.serialization.DynamicCodeccom.google.devtools.build.lib.vfs.RootCodec→com.google.devtools.build.lib.skyframe.serialization.SerializationContext
- Direction
- com.google.devtools.build.lib.vfs uses com.google.devtools.build.lib.skyframe.serialization, so a change to com.google.devtools.build.lib.skyframe.serialization can break com.google.devtools.build.lib.vfs, while a change to com.google.devtools.build.lib.vfs can't break com.google.devtools.build.lib.skyframe.serialization.
- 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→35 com.google.devtools.build.lib.vfs uses com.google.devtools.build.lib.analysis part of a loop✕
- Connections
- 1 pair of types, where a type in com.google.devtools.build.lib.vfs uses a type in com.google.devtools.build.lib.analysis.
- The types involved
com.google.devtools.build.lib.vfs.LocalOutputService→com.google.devtools.build.lib.analysis.BlazeDirectories
- Direction
- com.google.devtools.build.lib.vfs uses com.google.devtools.build.lib.analysis, so a change to com.google.devtools.build.lib.analysis can break com.google.devtools.build.lib.vfs, while a change to com.google.devtools.build.lib.vfs can't break com.google.devtools.build.lib.analysis.
- 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→37 com.google.devtools.build.lib.vfs uses com.google.devtools.build.lib.actions part of a loop✕
- Connections
- 15 pairs of types, where a type in com.google.devtools.build.lib.vfs uses a type in com.google.devtools.build.lib.actions.
- The types involved
com.google.devtools.build.lib.vfs.LocalOutputService→com.google.devtools.build.lib.actions.Actioncom.google.devtools.build.lib.vfs.LocalOutputService→com.google.devtools.build.lib.actions.OutputCheckercom.google.devtools.build.lib.vfs.LocalOutputService→com.google.devtools.build.lib.actions.OutputMetadataStorecom.google.devtools.build.lib.vfs.OutputService→com.google.devtools.build.lib.actions.Actioncom.google.devtools.build.lib.vfs.OutputService→com.google.devtools.build.lib.actions.ActionExecutionMetadatacom.google.devtools.build.lib.vfs.OutputService→com.google.devtools.build.lib.actions.ActionInputMapcom.google.devtools.build.lib.vfs.OutputService→com.google.devtools.build.lib.actions.Artifactcom.google.devtools.build.lib.vfs.OutputService→com.google.devtools.build.lib.actions.ArtifactPathResolvercom.google.devtools.build.lib.vfs.OutputService→com.google.devtools.build.lib.actions.InputMetadataProvidercom.google.devtools.build.lib.vfs.OutputService→com.google.devtools.build.lib.actions.OutputCheckercom.google.devtools.build.lib.vfs.OutputService→com.google.devtools.build.lib.actions.OutputMetadataStorecom.google.devtools.build.lib.vfs.OutputService→com.google.devtools.build.lib.actions.ProxyMetadataFactorycom.google.devtools.build.lib.vfs.PathStrippable→com.google.devtools.build.lib.actions.CommandLineItemcom.google.devtools.build.lib.vfs.RewoundActionSynchronizer→com.google.devtools.build.lib.actions.Actioncom.google.devtools.build.lib.vfs.RewoundActionSynchronizer→com.google.devtools.build.lib.actions.InputMetadataProvider
- Direction
- com.google.devtools.build.lib.vfs uses com.google.devtools.build.lib.actions, so a change to com.google.devtools.build.lib.actions can break com.google.devtools.build.lib.vfs, while a change to com.google.devtools.build.lib.vfs can't break com.google.devtools.build.lib.actions.
- 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 proguard.classfile.editor uses proguard.classfile.visitor✕
- Connections
- 35 pairs of types, where a type in proguard.classfile.editor uses a type in proguard.classfile.visitor. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
proguard.classfile.editor.AccessFixer→proguard.classfile.visitor.ClassVisitorproguard.classfile.editor.AttributeSorter→proguard.classfile.visitor.ClassVisitorproguard.classfile.editor.AttributeSorter→proguard.classfile.visitor.MemberVisitorproguard.classfile.editor.BootstrapMethodsAttributeShrinker→proguard.classfile.visitor.ClassVisitorproguard.classfile.editor.BootstrapMethodsAttributeShrinker→proguard.classfile.visitor.MemberVisitorproguard.classfile.editor.BridgeMethodFixer→proguard.classfile.visitor.MemberVisitorproguard.classfile.editor.ClassElementSorter→proguard.classfile.visitor.ClassVisitorproguard.classfile.editor.ClassMemberSorter→proguard.classfile.visitor.ClassVisitorproguard.classfile.editor.ClassReferenceFixer→proguard.classfile.visitor.ClassVisitorproguard.classfile.editor.ClassReferenceFixer→proguard.classfile.visitor.MemberVisitorproguard.classfile.editor.ConstantPoolRemapper→proguard.classfile.visitor.ClassVisitorproguard.classfile.editor.ConstantPoolRemapper→proguard.classfile.visitor.MemberVisitorproguard.classfile.editor.ConstantPoolShrinker→proguard.classfile.visitor.ClassVisitorproguard.classfile.editor.ConstantPoolShrinker→proguard.classfile.visitor.MemberVisitorproguard.classfile.editor.ConstantPoolSorter→proguard.classfile.visitor.ClassVisitorproguard.classfile.editor.InnerClassesAccessFixer→proguard.classfile.visitor.ClassVisitorproguard.classfile.editor.InterfaceDeleter→proguard.classfile.visitor.ClassVisitorproguard.classfile.editor.InterfaceSorter→proguard.classfile.visitor.ClassVisitorproguard.classfile.editor.MemberAdder→proguard.classfile.visitor.MemberVisitorproguard.classfile.editor.MemberReferenceFixer→proguard.classfile.visitor.ClassVisitorproguard.classfile.editor.MemberReferenceFixer→proguard.classfile.visitor.MemberVisitorproguard.classfile.editor.MemberRemover→proguard.classfile.visitor.ClassVisitorproguard.classfile.editor.MemberRemover→proguard.classfile.visitor.MemberVisitorproguard.classfile.editor.MyReferencedClassAccessFixer→proguard.classfile.visitor.ClassVisitorproguard.classfile.editor.MyReferencedMemberAccessFixer→proguard.classfile.visitor.MemberVisitor
- Direction
- proguard.classfile.editor uses proguard.classfile.visitor, so a change to proguard.classfile.visitor can break proguard.classfile.editor, while a change to proguard.classfile.editor can't break proguard.classfile.visitor.
- Position
- Below the diagonal: proguard.classfile.editor uses a module listed above it, which is the healthy direction.
9→7 proguard.classfile.editor uses proguard.classfile.constant.visitor✕
- Connections
- 16 pairs of types, where a type in proguard.classfile.editor uses a type in proguard.classfile.constant.visitor.
- The types involved
proguard.classfile.editor.BootstrapMethodRemapper→proguard.classfile.constant.visitor.ConstantVisitorproguard.classfile.editor.BridgeMethodFixer→proguard.classfile.constant.visitor.ConstantVisitorproguard.classfile.editor.ClassReferenceFixer→proguard.classfile.constant.visitor.ConstantVisitorproguard.classfile.editor.ComparableConstant→proguard.classfile.constant.visitor.ConstantVisitorproguard.classfile.editor.ConstantAdder→proguard.classfile.constant.visitor.ConstantVisitorproguard.classfile.editor.ConstantPoolEditor→proguard.classfile.constant.visitor.ConstantVisitorproguard.classfile.editor.ConstantPoolRemapper→proguard.classfile.constant.visitor.ConstantVisitorproguard.classfile.editor.ConstantPoolShrinker→proguard.classfile.constant.visitor.ConstantVisitorproguard.classfile.editor.ExceptionAdder→proguard.classfile.constant.visitor.ConstantVisitorproguard.classfile.editor.InnerClassesAccessFixer→proguard.classfile.constant.visitor.ConstantVisitorproguard.classfile.editor.InterfaceAdder→proguard.classfile.constant.visitor.ConstantVisitorproguard.classfile.editor.MemberReferenceFixer→proguard.classfile.constant.visitor.ConstantVisitorproguard.classfile.editor.MethodInvocationFixer→proguard.classfile.constant.visitor.ConstantVisitorproguard.classfile.editor.NameAndTypeShrinker→proguard.classfile.constant.visitor.ConstantVisitorproguard.classfile.editor.NestMemberAdder→proguard.classfile.constant.visitor.ConstantVisitorproguard.classfile.editor.Utf8Shrinker→proguard.classfile.constant.visitor.ConstantVisitor
- Direction
- proguard.classfile.editor uses proguard.classfile.constant.visitor, so a change to proguard.classfile.constant.visitor can break proguard.classfile.editor, while a change to proguard.classfile.editor can't break proguard.classfile.constant.visitor.
- Position
- Below the diagonal: proguard.classfile.editor uses a module listed above it, which is the healthy direction.
9→12 proguard.classfile.editor uses proguard.classfile.util part of a loop✕
- Connections
- 45 pairs of types, where a type in proguard.classfile.editor uses a type in proguard.classfile.util. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
proguard.classfile.editor.AnnotationAdder→proguard.classfile.util.SimplifiedVisitorproguard.classfile.editor.AttributeAdder→proguard.classfile.util.SimplifiedVisitorproguard.classfile.editor.AttributeSorter→proguard.classfile.util.SimplifiedVisitorproguard.classfile.editor.BootstrapMethodRemapper→proguard.classfile.util.SimplifiedVisitorproguard.classfile.editor.BootstrapMethodsAttributeShrinker→proguard.classfile.util.SimplifiedVisitorproguard.classfile.editor.BridgeMethodFixer→proguard.classfile.util.SimplifiedVisitorproguard.classfile.editor.ClassElementSorter→proguard.classfile.util.SimplifiedVisitorproguard.classfile.editor.ClassReferenceFixer→proguard.classfile.util.SimplifiedVisitorproguard.classfile.editor.CodeAttributeComposer→proguard.classfile.util.SimplifiedVisitorproguard.classfile.editor.CodeAttributeEditor→proguard.classfile.util.SimplifiedVisitorproguard.classfile.editor.CodeAttributeEditorResetter→proguard.classfile.util.SimplifiedVisitorproguard.classfile.editor.CompactCodeAttributeComposer→proguard.classfile.util.SimplifiedVisitorproguard.classfile.editor.ComparableConstant→proguard.classfile.util.SimplifiedVisitorproguard.classfile.editor.ConstantPoolRemapper→proguard.classfile.util.SimplifiedVisitorproguard.classfile.editor.ConstantPoolShrinker→proguard.classfile.util.SimplifiedVisitorproguard.classfile.editor.ConstantPoolSorter→proguard.classfile.util.SimplifiedVisitorproguard.classfile.editor.ExceptionAdder→proguard.classfile.util.SimplifiedVisitorproguard.classfile.editor.InnerClassesAccessFixer→proguard.classfile.util.SimplifiedVisitorproguard.classfile.editor.InstructionAdder→proguard.classfile.util.SimplifiedVisitorproguard.classfile.editor.InstructionWriter→proguard.classfile.util.SimplifiedVisitorproguard.classfile.editor.InterfaceAdder→proguard.classfile.util.SimplifiedVisitorproguard.classfile.editor.InterfaceDeleter→proguard.classfile.util.SimplifiedVisitorproguard.classfile.editor.InterfaceSorter→proguard.classfile.util.SimplifiedVisitorproguard.classfile.editor.LineNumberInfoAdder→proguard.classfile.util.SimplifiedVisitorproguard.classfile.editor.LineNumberTableAttributeTrimmer→proguard.classfile.util.SimplifiedVisitor
- Direction
- proguard.classfile.editor uses proguard.classfile.util, so a change to proguard.classfile.util can break proguard.classfile.editor, while a change to proguard.classfile.editor can't break proguard.classfile.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.
9→17 proguard.classfile.editor uses proguard.classfile.attribute.visitor part of a loop✕
- Connections
- 70 pairs of types, where a type in proguard.classfile.editor uses a type in proguard.classfile.attribute.visitor. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
proguard.classfile.editor.AttributeAdder→proguard.classfile.attribute.visitor.AttributeVisitorproguard.classfile.editor.AttributeSorter→proguard.classfile.attribute.visitor.AttributeVisitorproguard.classfile.editor.BootstrapMethodInfoAdder→proguard.classfile.attribute.visitor.BootstrapMethodInfoVisitorproguard.classfile.editor.BootstrapMethodsAttributeAdder→proguard.classfile.attribute.visitor.BootstrapMethodInfoVisitorproguard.classfile.editor.BootstrapMethodsAttributeShrinker→proguard.classfile.attribute.visitor.AttributeVisitorproguard.classfile.editor.BootstrapMethodsAttributeShrinker→proguard.classfile.attribute.visitor.BootstrapMethodInfoVisitorproguard.classfile.editor.BridgeMethodFixer→proguard.classfile.attribute.visitor.AttributeVisitorproguard.classfile.editor.ClassReferenceFixer→proguard.classfile.attribute.visitor.AttributeVisitorproguard.classfile.editor.ClassReferenceFixer→proguard.classfile.attribute.visitor.InnerClassesInfoVisitorproguard.classfile.editor.ClassReferenceFixer→proguard.classfile.attribute.visitor.LocalVariableInfoVisitorproguard.classfile.editor.ClassReferenceFixer→proguard.classfile.attribute.visitor.LocalVariableTypeInfoVisitorproguard.classfile.editor.CodeAttributeComposer→proguard.classfile.attribute.visitor.AttributeVisitorproguard.classfile.editor.CodeAttributeComposer→proguard.classfile.attribute.visitor.ExceptionInfoVisitorproguard.classfile.editor.CodeAttributeComposer→proguard.classfile.attribute.visitor.LineNumberInfoVisitorproguard.classfile.editor.CodeAttributeComposer→proguard.classfile.attribute.visitor.LocalVariableInfoVisitorproguard.classfile.editor.CodeAttributeComposer→proguard.classfile.attribute.visitor.LocalVariableTypeInfoVisitorproguard.classfile.editor.CodeAttributeEditor→proguard.classfile.attribute.visitor.AttributeVisitorproguard.classfile.editor.CodeAttributeEditor→proguard.classfile.attribute.visitor.ExceptionInfoVisitorproguard.classfile.editor.CodeAttributeEditor→proguard.classfile.attribute.visitor.LineNumberInfoVisitorproguard.classfile.editor.CodeAttributeEditor→proguard.classfile.attribute.visitor.LocalVariableInfoVisitorproguard.classfile.editor.CodeAttributeEditor→proguard.classfile.attribute.visitor.LocalVariableTypeInfoVisitorproguard.classfile.editor.CodeAttributeEditorResetter→proguard.classfile.attribute.visitor.AttributeVisitorproguard.classfile.editor.CompactCodeAttributeComposer→proguard.classfile.attribute.visitor.AttributeVisitorproguard.classfile.editor.ConstantPoolRemapper→proguard.classfile.attribute.visitor.AttributeVisitorproguard.classfile.editor.ConstantPoolRemapper→proguard.classfile.attribute.visitor.BootstrapMethodInfoVisitor
- Direction
- proguard.classfile.editor uses proguard.classfile.attribute.visitor, so a change to proguard.classfile.attribute.visitor can break proguard.classfile.editor, while a change to proguard.classfile.editor can't break proguard.classfile.attribute.visitor.
- 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→20 proguard.classfile.editor uses proguard.classfile.attribute part of a loop✕
- Connections
- 212 pairs of types, where a type in proguard.classfile.editor uses a type in proguard.classfile.attribute. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
proguard.classfile.editor.AttributeAdder→proguard.classfile.attribute.Attributeproguard.classfile.editor.AttributeAdder→proguard.classfile.attribute.CodeAttributeproguard.classfile.editor.AttributeAdder→proguard.classfile.attribute.ConstantValueAttributeproguard.classfile.editor.AttributeAdder→proguard.classfile.attribute.DeprecatedAttributeproguard.classfile.editor.AttributeAdder→proguard.classfile.attribute.EnclosingMethodAttributeproguard.classfile.editor.AttributeAdder→proguard.classfile.attribute.ExceptionInfoproguard.classfile.editor.AttributeAdder→proguard.classfile.attribute.ExceptionsAttributeproguard.classfile.editor.AttributeAdder→proguard.classfile.attribute.InnerClassesAttributeproguard.classfile.editor.AttributeAdder→proguard.classfile.attribute.LineNumberTableAttributeproguard.classfile.editor.AttributeAdder→proguard.classfile.attribute.LocalVariableTableAttributeproguard.classfile.editor.AttributeAdder→proguard.classfile.attribute.LocalVariableTypeTableAttributeproguard.classfile.editor.AttributeAdder→proguard.classfile.attribute.MethodParametersAttributeproguard.classfile.editor.AttributeAdder→proguard.classfile.attribute.NestHostAttributeproguard.classfile.editor.AttributeAdder→proguard.classfile.attribute.NestMembersAttributeproguard.classfile.editor.AttributeAdder→proguard.classfile.attribute.SignatureAttributeproguard.classfile.editor.AttributeAdder→proguard.classfile.attribute.SourceDirAttributeproguard.classfile.editor.AttributeAdder→proguard.classfile.attribute.SourceFileAttributeproguard.classfile.editor.AttributeAdder→proguard.classfile.attribute.SyntheticAttributeproguard.classfile.editor.AttributeAdder→proguard.classfile.attribute.UnknownAttributeproguard.classfile.editor.AttributeSorter→proguard.classfile.attribute.Attributeproguard.classfile.editor.AttributeSorter→proguard.classfile.attribute.CodeAttributeproguard.classfile.editor.AttributesEditor→proguard.classfile.attribute.Attributeproguard.classfile.editor.AttributesEditor→proguard.classfile.attribute.CodeAttributeproguard.classfile.editor.BootstrapMethodInfoAdder→proguard.classfile.attribute.BootstrapMethodInfoproguard.classfile.editor.BootstrapMethodInfoAdder→proguard.classfile.attribute.BootstrapMethodsAttribute
- Direction
- proguard.classfile.editor uses proguard.classfile.attribute, so a change to proguard.classfile.attribute can break proguard.classfile.editor, while a change to proguard.classfile.editor can't break proguard.classfile.attribute.
- 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→22 proguard.classfile.editor uses proguard.classfile part of a loop✕
- Connections
- 201 pairs of types, where a type in proguard.classfile.editor uses a type in proguard.classfile. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
proguard.classfile.editor.AccessFixer→proguard.classfile.Clazzproguard.classfile.editor.AccessFixer→proguard.classfile.LibraryClassproguard.classfile.editor.AccessFixer→proguard.classfile.ProgramClassproguard.classfile.editor.AnnotationAdder→proguard.classfile.Clazzproguard.classfile.editor.AnnotationAdder→proguard.classfile.Methodproguard.classfile.editor.AnnotationAdder→proguard.classfile.ProgramClassproguard.classfile.editor.AttributeAdder→proguard.classfile.Clazzproguard.classfile.editor.AttributeAdder→proguard.classfile.Fieldproguard.classfile.editor.AttributeAdder→proguard.classfile.Methodproguard.classfile.editor.AttributeAdder→proguard.classfile.ProgramClassproguard.classfile.editor.AttributeAdder→proguard.classfile.ProgramMemberproguard.classfile.editor.AttributeSorter→proguard.classfile.Clazzproguard.classfile.editor.AttributeSorter→proguard.classfile.Methodproguard.classfile.editor.AttributeSorter→proguard.classfile.ProgramClassproguard.classfile.editor.AttributeSorter→proguard.classfile.ProgramMemberproguard.classfile.editor.AttributesEditor→proguard.classfile.ProgramClassproguard.classfile.editor.AttributesEditor→proguard.classfile.ProgramMemberproguard.classfile.editor.BootstrapMethodInfoAdder→proguard.classfile.Clazzproguard.classfile.editor.BootstrapMethodInfoAdder→proguard.classfile.ProgramClassproguard.classfile.editor.BootstrapMethodRemapper→proguard.classfile.Clazzproguard.classfile.editor.BootstrapMethodsAttributeAdder→proguard.classfile.Clazzproguard.classfile.editor.BootstrapMethodsAttributeAdder→proguard.classfile.ProgramClassproguard.classfile.editor.BootstrapMethodsAttributeShrinker→proguard.classfile.Clazzproguard.classfile.editor.BootstrapMethodsAttributeShrinker→proguard.classfile.LibraryClassproguard.classfile.editor.BootstrapMethodsAttributeShrinker→proguard.classfile.Method
- Direction
- proguard.classfile.editor uses proguard.classfile, so a change to proguard.classfile can break proguard.classfile.editor, while a change to proguard.classfile.editor can't break proguard.classfile.
- 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→2 com.google.devtools.build.lib.skyframe.config uses com.google.devtools.build.lib.events✕
- Connections
- 2 pairs of types, where a type in com.google.devtools.build.lib.skyframe.config uses a type in com.google.devtools.build.lib.events.
- The types involved
com.google.devtools.build.lib.skyframe.config.FlagSetFunction→com.google.devtools.build.lib.events.Eventcom.google.devtools.build.lib.skyframe.config.FlagSetValue→com.google.devtools.build.lib.events.Event
- Direction
- com.google.devtools.build.lib.skyframe.config uses com.google.devtools.build.lib.events, so a change to com.google.devtools.build.lib.events can break com.google.devtools.build.lib.skyframe.config, while a change to com.google.devtools.build.lib.skyframe.config can't break com.google.devtools.build.lib.events.
- Position
- Below the diagonal: com.google.devtools.build.lib.skyframe.config uses a module listed above it, which is the healthy direction.
10→3 com.google.devtools.build.lib.skyframe.config uses com.google.devtools.common.options✕
- Connections
- 8 pairs of types, where a type in com.google.devtools.build.lib.skyframe.config uses a type in com.google.devtools.common.options.
- The types involved
com.google.devtools.build.lib.skyframe.config.BuildConfigurationKeyFunctionException→com.google.devtools.common.options.OptionsParsingExceptioncom.google.devtools.build.lib.skyframe.config.NativeAndStarlarkFlags→com.google.devtools.common.options.OptionsParsingResultcom.google.devtools.build.lib.skyframe.config.ParsedFlagsFunctionException→com.google.devtools.common.options.OptionsParsingExceptioncom.google.devtools.build.lib.skyframe.config.ParsedFlagsValue→com.google.devtools.common.options.OptionDefinitioncom.google.devtools.build.lib.skyframe.config.ParsedFlagsValue→com.google.devtools.common.options.OptionValueDescriptioncom.google.devtools.build.lib.skyframe.config.ParsedFlagsValue→com.google.devtools.common.options.OptionsParsingResultcom.google.devtools.build.lib.skyframe.config.PlatformMappingParsingException→com.google.devtools.common.options.OptionsParsingExceptioncom.google.devtools.build.lib.skyframe.config.Sink→com.google.devtools.common.options.OptionsParsingException
- Direction
- com.google.devtools.build.lib.skyframe.config uses com.google.devtools.common.options, so a change to com.google.devtools.common.options can break com.google.devtools.build.lib.skyframe.config, while a change to com.google.devtools.build.lib.skyframe.config can't break com.google.devtools.common.options.
- Position
- Below the diagonal: com.google.devtools.build.lib.skyframe.config uses a module listed above it, which is the healthy direction.
10→6 com.google.devtools.build.lib.skyframe.config uses com.google.devtools.build.skyframe✕
- Connections
- 34 pairs of types, where a type in com.google.devtools.build.lib.skyframe.config uses a type in com.google.devtools.build.skyframe. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.google.devtools.build.lib.skyframe.config.BaselineOptionsFunction→com.google.devtools.build.skyframe.SkyFunctioncom.google.devtools.build.lib.skyframe.config.BaselineOptionsFunction→com.google.devtools.build.skyframe.SkyKeycom.google.devtools.build.lib.skyframe.config.BaselineOptionsFunction→com.google.devtools.build.skyframe.SkyValuecom.google.devtools.build.lib.skyframe.config.BaselineOptionsFunction→com.google.devtools.build.skyframe.Versioncom.google.devtools.build.lib.skyframe.config.BaselineOptionsFunctionException→com.google.devtools.build.skyframe.SkyFunctionExceptioncom.google.devtools.build.lib.skyframe.config.BuildConfigurationFunction→com.google.devtools.build.skyframe.SkyFunctioncom.google.devtools.build.lib.skyframe.config.BuildConfigurationFunction→com.google.devtools.build.skyframe.SkyKeycom.google.devtools.build.lib.skyframe.config.BuildConfigurationFunction→com.google.devtools.build.skyframe.SkyValuecom.google.devtools.build.lib.skyframe.config.BuildConfigurationFunctionException→com.google.devtools.build.skyframe.SkyFunctionExceptioncom.google.devtools.build.lib.skyframe.config.BuildConfigurationKey→com.google.devtools.build.skyframe.SkyFunctionNamecom.google.devtools.build.lib.skyframe.config.BuildConfigurationKey→com.google.devtools.build.skyframe.SkyKeycom.google.devtools.build.lib.skyframe.config.BuildConfigurationKeyFunction→com.google.devtools.build.skyframe.SkyFunctioncom.google.devtools.build.lib.skyframe.config.BuildConfigurationKeyFunction→com.google.devtools.build.skyframe.SkyKeycom.google.devtools.build.lib.skyframe.config.BuildConfigurationKeyFunction→com.google.devtools.build.skyframe.SkyValuecom.google.devtools.build.lib.skyframe.config.BuildConfigurationKeyFunctionException→com.google.devtools.build.skyframe.SkyFunctionExceptioncom.google.devtools.build.lib.skyframe.config.BuildConfigurationKeyValue→com.google.devtools.build.skyframe.SkyValuecom.google.devtools.build.lib.skyframe.config.FlagSetFunction→com.google.devtools.build.skyframe.SkyFunctioncom.google.devtools.build.lib.skyframe.config.FlagSetFunction→com.google.devtools.build.skyframe.SkyKeycom.google.devtools.build.lib.skyframe.config.FlagSetFunction→com.google.devtools.build.skyframe.SkyValuecom.google.devtools.build.lib.skyframe.config.FlagSetFunctionException→com.google.devtools.build.skyframe.SkyFunctionExceptioncom.google.devtools.build.lib.skyframe.config.FlagSetValue→com.google.devtools.build.skyframe.SkyValuecom.google.devtools.build.lib.skyframe.config.Key→com.google.devtools.build.skyframe.SkyFunctionNamecom.google.devtools.build.lib.skyframe.config.Key→com.google.devtools.build.skyframe.SkyKeycom.google.devtools.build.lib.skyframe.config.ParsedFlagsFunction→com.google.devtools.build.skyframe.SkyFunctioncom.google.devtools.build.lib.skyframe.config.ParsedFlagsFunction→com.google.devtools.build.skyframe.SkyKey
- Direction
- com.google.devtools.build.lib.skyframe.config uses com.google.devtools.build.skyframe, so a change to com.google.devtools.build.skyframe can break com.google.devtools.build.lib.skyframe.config, while a change to com.google.devtools.build.lib.skyframe.config can't break com.google.devtools.build.skyframe.
- Position
- Below the diagonal: com.google.devtools.build.lib.skyframe.config uses a module listed above it, which is the healthy direction.
10→8 com.google.devtools.build.lib.skyframe.config uses com.google.devtools.build.lib.vfs✕
- Connections
- 1 pair of types, where a type in com.google.devtools.build.lib.skyframe.config uses a type in com.google.devtools.build.lib.vfs.
- The types involved
com.google.devtools.build.lib.skyframe.config.PlatformMappingKey→com.google.devtools.build.lib.vfs.PathFragment
- Direction
- com.google.devtools.build.lib.skyframe.config uses com.google.devtools.build.lib.vfs, so a change to com.google.devtools.build.lib.vfs can break com.google.devtools.build.lib.skyframe.config, while a change to com.google.devtools.build.lib.skyframe.config can't break com.google.devtools.build.lib.vfs.
- Position
- Below the diagonal: com.google.devtools.build.lib.skyframe.config uses a module listed above it, which is the healthy direction.
10→24 com.google.devtools.build.lib.skyframe.config uses com.google.devtools.build.lib.skyframe part of a loop✕
- Connections
- 2 pairs of types, where a type in com.google.devtools.build.lib.skyframe.config uses a type in com.google.devtools.build.lib.skyframe.
- The types involved
com.google.devtools.build.lib.skyframe.config.FlagSetFunction→com.google.devtools.build.lib.skyframe.BuildableUnitcom.google.devtools.build.lib.skyframe.config.FlagSetFunction→com.google.devtools.build.lib.skyframe.ProjectValue
- Direction
- com.google.devtools.build.lib.skyframe.config uses com.google.devtools.build.lib.skyframe, so a change to com.google.devtools.build.lib.skyframe can break com.google.devtools.build.lib.skyframe.config, while a change to com.google.devtools.build.lib.skyframe.config can't break com.google.devtools.build.lib.skyframe.
- 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→25 com.google.devtools.build.lib.skyframe.config uses com.google.devtools.build.lib.packages part of a loop✕
- Connections
- 3 pairs of types, where a type in com.google.devtools.build.lib.skyframe.config uses a type in com.google.devtools.build.lib.packages.
- The types involved
com.google.devtools.build.lib.skyframe.config.BuildConfigurationFunction→com.google.devtools.build.lib.packages.RuleClassProvidercom.google.devtools.build.lib.skyframe.config.ParsedFlagsFunction→com.google.devtools.build.lib.packages.Targetcom.google.devtools.build.lib.skyframe.config.SkyframeTargetLoader→com.google.devtools.build.lib.packages.Target
- Direction
- com.google.devtools.build.lib.skyframe.config uses com.google.devtools.build.lib.packages, so a change to com.google.devtools.build.lib.packages can break com.google.devtools.build.lib.skyframe.config, while a change to com.google.devtools.build.lib.skyframe.config can't break com.google.devtools.build.lib.packages.
- 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→28 com.google.devtools.build.lib.skyframe.config uses com.google.devtools.build.lib.runtime part of a loop✕
- Connections
- 2 pairs of types, where a type in com.google.devtools.build.lib.skyframe.config uses a type in com.google.devtools.build.lib.runtime.
- The types involved
com.google.devtools.build.lib.skyframe.config.FlagSetFunction→com.google.devtools.build.lib.runtime.ConfigFlagDefinitionscom.google.devtools.build.lib.skyframe.config.SkyframeTargetLoader→com.google.devtools.build.lib.runtime.BuildSettingLoader
- Direction
- com.google.devtools.build.lib.skyframe.config uses com.google.devtools.build.lib.runtime, so a change to com.google.devtools.build.lib.runtime can break com.google.devtools.build.lib.skyframe.config, while a change to com.google.devtools.build.lib.skyframe.config can't break com.google.devtools.build.lib.runtime.
- 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→29 com.google.devtools.build.lib.skyframe.config uses com.google.devtools.build.lib.skyframe.serialization part of a loop✕
- Connections
- 8 pairs of types, where a type in com.google.devtools.build.lib.skyframe.config uses a type in com.google.devtools.build.lib.skyframe.serialization.
- The types involved
com.google.devtools.build.lib.skyframe.config.BuildConfigurationKey→com.google.devtools.build.lib.skyframe.serialization.DeferredObjectCodeccom.google.devtools.build.lib.skyframe.config.BuildConfigurationKeyBaselineDiffCodec→com.google.devtools.build.lib.skyframe.serialization.AsyncDeserializationContextcom.google.devtools.build.lib.skyframe.config.BuildConfigurationKeyBaselineDiffCodec→com.google.devtools.build.lib.skyframe.serialization.DeferredObjectCodeccom.google.devtools.build.lib.skyframe.config.BuildConfigurationKeyBaselineDiffCodec→com.google.devtools.build.lib.skyframe.serialization.DeferredValuecom.google.devtools.build.lib.skyframe.config.BuildConfigurationKeyBaselineDiffCodec→com.google.devtools.build.lib.skyframe.serialization.SerializationContextcom.google.devtools.build.lib.skyframe.config.CodecHolder→com.google.devtools.build.lib.skyframe.serialization.DeferredObjectCodeccom.google.devtools.build.lib.skyframe.config.PlatformDiffBuilder→com.google.devtools.build.lib.skyframe.serialization.DeferredValuecom.google.devtools.build.lib.skyframe.config.PlatformDiffBuilder→com.google.devtools.build.lib.skyframe.serialization.PlatformConfigurationProvider
- Direction
- com.google.devtools.build.lib.skyframe.config uses com.google.devtools.build.lib.skyframe.serialization, so a change to com.google.devtools.build.lib.skyframe.serialization can break com.google.devtools.build.lib.skyframe.config, while a change to com.google.devtools.build.lib.skyframe.config can't break com.google.devtools.build.lib.skyframe.serialization.
- 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→31 com.google.devtools.build.lib.skyframe.config uses com.google.devtools.build.lib.cmdline part of a loop✕
- Connections
- 9 pairs of types, where a type in com.google.devtools.build.lib.skyframe.config uses a type in com.google.devtools.build.lib.cmdline.
- The types involved
com.google.devtools.build.lib.skyframe.config.Builder→com.google.devtools.build.lib.cmdline.RepositoryMappingcom.google.devtools.build.lib.skyframe.config.FlagSetFunction→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.skyframe.config.Key→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.skyframe.config.Mappings→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.skyframe.config.NativeAndStarlarkFlags→com.google.devtools.build.lib.cmdline.RepositoryMappingcom.google.devtools.build.lib.skyframe.config.ParsedFlagsFunction→com.google.devtools.build.lib.cmdline.PackageIdentifiercom.google.devtools.build.lib.skyframe.config.PlatformDiffBuilder→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.skyframe.config.PlatformMappingFunction→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.skyframe.config.PlatformMappingValue→com.google.devtools.build.lib.cmdline.Label
- Direction
- com.google.devtools.build.lib.skyframe.config uses com.google.devtools.build.lib.cmdline, so a change to com.google.devtools.build.lib.cmdline can break com.google.devtools.build.lib.skyframe.config, while a change to com.google.devtools.build.lib.skyframe.config can't break com.google.devtools.build.lib.cmdline.
- 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→33 com.google.devtools.build.lib.skyframe.config uses com.google.devtools.build.lib.analysis.config part of a loop✕
- Connections
- 16 pairs of types, where a type in com.google.devtools.build.lib.skyframe.config uses a type in com.google.devtools.build.lib.analysis.config.
- The types involved
com.google.devtools.build.lib.skyframe.config.BaselineOptionsFunction→com.google.devtools.build.lib.analysis.config.BuildOptionscom.google.devtools.build.lib.skyframe.config.BuildConfigurationFunction→com.google.devtools.build.lib.analysis.config.BuildOptionscom.google.devtools.build.lib.skyframe.config.BuildConfigurationFunction→com.google.devtools.build.lib.analysis.config.FragmentFactorycom.google.devtools.build.lib.skyframe.config.BuildConfigurationKey→com.google.devtools.build.lib.analysis.config.BuildOptionscom.google.devtools.build.lib.skyframe.config.Builder→com.google.devtools.build.lib.analysis.config.FragmentOptionscom.google.devtools.build.lib.skyframe.config.FlagSetFunction→com.google.devtools.build.lib.analysis.config.BuildOptionscom.google.devtools.build.lib.skyframe.config.Mappings→com.google.devtools.build.lib.analysis.config.FragmentOptionscom.google.devtools.build.lib.skyframe.config.NativeAndStarlarkFlags→com.google.devtools.build.lib.analysis.config.FragmentOptionscom.google.devtools.build.lib.skyframe.config.ParsedFlagsFunction→com.google.devtools.build.lib.analysis.config.FragmentOptionscom.google.devtools.build.lib.skyframe.config.ParsedFlagsValue→com.google.devtools.build.lib.analysis.config.BuildOptionscom.google.devtools.build.lib.skyframe.config.ParsedFlagsValue→com.google.devtools.build.lib.analysis.config.Buildercom.google.devtools.build.lib.skyframe.config.ParsedFlagsValue→com.google.devtools.build.lib.analysis.config.FragmentOptionscom.google.devtools.build.lib.skyframe.config.PlatformDiffBuilder→com.google.devtools.build.lib.analysis.config.OptionsDiffcom.google.devtools.build.lib.skyframe.config.PlatformMappingFunction→com.google.devtools.build.lib.analysis.config.FragmentOptionscom.google.devtools.build.lib.skyframe.config.PlatformMappingValue→com.google.devtools.build.lib.analysis.config.BuildOptionscom.google.devtools.build.lib.skyframe.config.PlatformMappingValue→com.google.devtools.build.lib.analysis.config.FragmentOptions
- Direction
- com.google.devtools.build.lib.skyframe.config uses com.google.devtools.build.lib.analysis.config, so a change to com.google.devtools.build.lib.analysis.config can break com.google.devtools.build.lib.skyframe.config, while a change to com.google.devtools.build.lib.skyframe.config can't break com.google.devtools.build.lib.analysis.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.
10→35 com.google.devtools.build.lib.skyframe.config uses com.google.devtools.build.lib.analysis part of a loop✕
- Connections
- 2 pairs of types, where a type in com.google.devtools.build.lib.skyframe.config uses a type in com.google.devtools.build.lib.analysis.
- The types involved
com.google.devtools.build.lib.skyframe.config.BuildConfigurationFunction→com.google.devtools.build.lib.analysis.BlazeDirectoriescom.google.devtools.build.lib.skyframe.config.BuildConfigurationFunction→com.google.devtools.build.lib.analysis.ConfiguredRuleClassProvider
- Direction
- com.google.devtools.build.lib.skyframe.config uses com.google.devtools.build.lib.analysis, so a change to com.google.devtools.build.lib.analysis can break com.google.devtools.build.lib.skyframe.config, while a change to com.google.devtools.build.lib.skyframe.config can't break com.google.devtools.build.lib.analysis.
- 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→37 com.google.devtools.build.lib.skyframe.config uses com.google.devtools.build.lib.actions part of a loop✕
- Connections
- 2 pairs of types, where a type in com.google.devtools.build.lib.skyframe.config uses a type in com.google.devtools.build.lib.actions.
- The types involved
com.google.devtools.build.lib.skyframe.config.PlatformMappingException→com.google.devtools.build.lib.actions.MissingInputFileExceptioncom.google.devtools.build.lib.skyframe.config.PlatformMappingFunctionException→com.google.devtools.build.lib.actions.MissingInputFileException
- Direction
- com.google.devtools.build.lib.skyframe.config uses com.google.devtools.build.lib.actions, so a change to com.google.devtools.build.lib.actions can break com.google.devtools.build.lib.skyframe.config, while a change to com.google.devtools.build.lib.skyframe.config can't break com.google.devtools.build.lib.actions.
- 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→3 com.google.devtools.build.lib.util uses com.google.devtools.common.options✕
- Connections
- 11 pairs of types, where a type in com.google.devtools.build.lib.util uses a type in com.google.devtools.common.options.
- The types involved
com.google.devtools.build.lib.util.AbsolutePathFragmentConverter→com.google.devtools.common.options.Contextlesscom.google.devtools.build.lib.util.AssignmentConverter→com.google.devtools.common.options.Contextlesscom.google.devtools.build.lib.util.EmptyToNullPathFragmentConverter→com.google.devtools.common.options.Contextlesscom.google.devtools.build.lib.util.OptionsUtils→com.google.devtools.common.options.OptionsParsingResultcom.google.devtools.build.lib.util.OptionsUtils→com.google.devtools.common.options.ParsedOptionDescriptioncom.google.devtools.build.lib.util.PathFragmentConverter→com.google.devtools.common.options.Contextlesscom.google.devtools.build.lib.util.PathFragmentFilterConverter→com.google.devtools.common.options.Contextlesscom.google.devtools.build.lib.util.PathFragmentListConverter→com.google.devtools.common.options.Contextlesscom.google.devtools.build.lib.util.RegexFilterConverter→com.google.devtools.common.options.Contextlesscom.google.devtools.build.lib.util.ResourceConverter→com.google.devtools.common.options.Contextlesscom.google.devtools.build.lib.util.WorkspacePathFragmentConverter→com.google.devtools.common.options.Contextless
- Direction
- com.google.devtools.build.lib.util uses com.google.devtools.common.options, so a change to com.google.devtools.common.options can break com.google.devtools.build.lib.util, while a change to com.google.devtools.build.lib.util can't break com.google.devtools.common.options.
- Position
- Below the diagonal: com.google.devtools.build.lib.util uses a module listed above it, which is the healthy direction.
11→8 com.google.devtools.build.lib.util uses com.google.devtools.build.lib.vfs✕
- Connections
- 17 pairs of types, where a type in com.google.devtools.build.lib.util uses a type in com.google.devtools.build.lib.vfs.
- The types involved
com.google.devtools.build.lib.util.AbsolutePathFragmentConverter→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.util.CommandBuilder→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.util.DependencySet→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.util.EmptyToNullPathFragmentConverter→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.util.FileSystemLock→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.util.Fingerprint→com.google.devtools.build.lib.vfs.DigestHashFunctioncom.google.devtools.build.lib.util.Fingerprint→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.util.Fingerprint→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.util.LockAlreadyHeldException→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.util.MapCodec→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.util.OptionsUtils→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.util.PathFragmentConverter→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.util.PathFragmentFilter→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.util.PathFragmentListConverter→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.util.PersistentMap→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.util.TempPathGenerator→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.util.WorkspacePathFragmentConverter→com.google.devtools.build.lib.vfs.PathFragment
- Direction
- com.google.devtools.build.lib.util uses com.google.devtools.build.lib.vfs, so a change to com.google.devtools.build.lib.vfs can break com.google.devtools.build.lib.util, while a change to com.google.devtools.build.lib.util can't break com.google.devtools.build.lib.vfs.
- Position
- Below the diagonal: com.google.devtools.build.lib.util uses a module listed above it, which is the healthy direction.
11→28 com.google.devtools.build.lib.util uses com.google.devtools.build.lib.runtime part of a loop✕
- Connections
- 1 pair of types, where a type in com.google.devtools.build.lib.util uses a type in com.google.devtools.build.lib.runtime.
- The types involved
com.google.devtools.build.lib.util.ServerLogPathService→com.google.devtools.build.lib.runtime.BlazeService
- Direction
- com.google.devtools.build.lib.util uses com.google.devtools.build.lib.runtime, so a change to com.google.devtools.build.lib.runtime can break com.google.devtools.build.lib.util, while a change to com.google.devtools.build.lib.util can't break com.google.devtools.build.lib.runtime.
- 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→31 com.google.devtools.build.lib.util uses com.google.devtools.build.lib.cmdline part of a loop✕
- Connections
- 2 pairs of types, where a type in com.google.devtools.build.lib.util uses a type in com.google.devtools.build.lib.cmdline.
- The types involved
com.google.devtools.build.lib.util.CommandFailureUtils→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.util.DescribableExecutionUnit→com.google.devtools.build.lib.cmdline.Label
- Direction
- com.google.devtools.build.lib.util uses com.google.devtools.build.lib.cmdline, so a change to com.google.devtools.build.lib.cmdline can break com.google.devtools.build.lib.util, while a change to com.google.devtools.build.lib.util can't break com.google.devtools.build.lib.cmdline.
- 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→5 proguard.classfile.util uses proguard.classfile.visitor✕
- Connections
- 15 pairs of types, where a type in proguard.classfile.util uses a type in proguard.classfile.visitor.
- The types involved
proguard.classfile.util.AllParameterVisitor→proguard.classfile.visitor.MemberVisitorproguard.classfile.util.AllParameterVisitor→proguard.classfile.visitor.ParameterVisitorproguard.classfile.util.ArrayInitializationReplacer→proguard.classfile.visitor.ClassVisitorproguard.classfile.util.ClassReferenceInitializer→proguard.classfile.visitor.ClassVisitorproguard.classfile.util.ClassReferenceInitializer→proguard.classfile.visitor.MemberVisitorproguard.classfile.util.ClassSubHierarchyInitializer→proguard.classfile.visitor.ClassVisitorproguard.classfile.util.ClassSuperHierarchyInitializer→proguard.classfile.visitor.ClassVisitorproguard.classfile.util.DynamicMemberReferenceInitializer→proguard.classfile.visitor.MemberVisitorproguard.classfile.util.EnumFieldReferenceInitializer→proguard.classfile.visitor.MemberVisitorproguard.classfile.util.MemberFinder→proguard.classfile.visitor.MemberVisitorproguard.classfile.util.MethodLinker→proguard.classfile.visitor.ClassVisitorproguard.classfile.util.MethodLinker→proguard.classfile.visitor.MemberVisitorproguard.classfile.util.NestHostFinder→proguard.classfile.visitor.ClassVisitorproguard.classfile.util.PrimitiveArrayConstantReplacer→proguard.classfile.visitor.ClassVisitorproguard.classfile.util.StringSharer→proguard.classfile.visitor.ClassVisitor
- Direction
- proguard.classfile.util uses proguard.classfile.visitor, so a change to proguard.classfile.visitor can break proguard.classfile.util, while a change to proguard.classfile.util can't break proguard.classfile.visitor.
- Position
- Below the diagonal: proguard.classfile.util uses a module listed above it, which is the healthy direction.
12→7 proguard.classfile.util uses proguard.classfile.constant.visitor✕
- Connections
- 11 pairs of types, where a type in proguard.classfile.util uses a type in proguard.classfile.constant.visitor.
- The types involved
proguard.classfile.util.ClassReferenceInitializer→proguard.classfile.constant.visitor.ConstantVisitorproguard.classfile.util.ClassSuperHierarchyInitializer→proguard.classfile.constant.visitor.ConstantVisitorproguard.classfile.util.DynamicClassReferenceInitializer→proguard.classfile.constant.visitor.ConstantVisitorproguard.classfile.util.DynamicMemberReferenceInitializer→proguard.classfile.constant.visitor.ConstantVisitorproguard.classfile.util.EnumFieldReferenceInitializer→proguard.classfile.constant.visitor.ConstantVisitorproguard.classfile.util.InstructionSequenceMatcher→proguard.classfile.constant.visitor.ConstantVisitorproguard.classfile.util.MyDynamicMemberFinder→proguard.classfile.constant.visitor.ConstantVisitorproguard.classfile.util.PrimitiveArrayConstantReplacer→proguard.classfile.constant.visitor.ConstantVisitorproguard.classfile.util.PrimitiveArrayConstantReplacer→proguard.classfile.constant.visitor.PrimitiveArrayConstantElementVisitorproguard.classfile.util.StringReferenceInitializer→proguard.classfile.constant.visitor.ConstantVisitorproguard.classfile.util.StringSharer→proguard.classfile.constant.visitor.ConstantVisitor
- Direction
- proguard.classfile.util uses proguard.classfile.constant.visitor, so a change to proguard.classfile.constant.visitor can break proguard.classfile.util, while a change to proguard.classfile.util can't break proguard.classfile.constant.visitor.
- Position
- Below the diagonal: proguard.classfile.util uses a module listed above it, which is the healthy direction.
12→9 proguard.classfile.util uses proguard.classfile.editor✕
- Connections
- 6 pairs of types, where a type in proguard.classfile.util uses a type in proguard.classfile.editor.
- The types involved
proguard.classfile.util.ArrayInitializationReplacer→proguard.classfile.editor.CodeAttributeEditorproguard.classfile.util.ArrayInitializationReplacer→proguard.classfile.editor.ConstantPoolEditorproguard.classfile.util.DynamicMemberReferenceInitializer→proguard.classfile.editor.CodeAttributeEditorproguard.classfile.util.PrimitiveArrayConstantReplacer→proguard.classfile.editor.CodeAttributeEditorproguard.classfile.util.PrimitiveArrayConstantReplacer→proguard.classfile.editor.ConstantPoolShrinkerproguard.classfile.util.PrimitiveArrayConstantReplacer→proguard.classfile.editor.InstructionSequenceBuilder
- Direction
- proguard.classfile.util uses proguard.classfile.editor, so a change to proguard.classfile.editor can break proguard.classfile.util, while a change to proguard.classfile.util can't break proguard.classfile.editor.
- Position
- Below the diagonal: proguard.classfile.util uses a module listed above it, which is the healthy direction.
12→17 proguard.classfile.util uses proguard.classfile.attribute.visitor part of a loop✕
- Connections
- 10 pairs of types, where a type in proguard.classfile.util uses a type in proguard.classfile.attribute.visitor.
- The types involved
proguard.classfile.util.ArrayInitializationFilter→proguard.classfile.attribute.visitor.AttributeVisitorproguard.classfile.util.ArrayInitializationReplacer→proguard.classfile.attribute.visitor.AttributeVisitorproguard.classfile.util.ClassReferenceInitializer→proguard.classfile.attribute.visitor.AttributeVisitorproguard.classfile.util.ClassReferenceInitializer→proguard.classfile.attribute.visitor.LocalVariableInfoVisitorproguard.classfile.util.ClassReferenceInitializer→proguard.classfile.attribute.visitor.LocalVariableTypeInfoVisitorproguard.classfile.util.DynamicClassReferenceInitializer→proguard.classfile.attribute.visitor.AttributeVisitorproguard.classfile.util.DynamicMemberReferenceInitializer→proguard.classfile.attribute.visitor.AttributeVisitorproguard.classfile.util.NestHostFinder→proguard.classfile.attribute.visitor.AttributeVisitorproguard.classfile.util.PrimitiveArrayConstantReplacer→proguard.classfile.attribute.visitor.AttributeVisitorproguard.classfile.util.StringSharer→proguard.classfile.attribute.visitor.AttributeVisitor
- Direction
- proguard.classfile.util uses proguard.classfile.attribute.visitor, so a change to proguard.classfile.attribute.visitor can break proguard.classfile.util, while a change to proguard.classfile.util can't break proguard.classfile.attribute.visitor.
- 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→20 proguard.classfile.util uses proguard.classfile.attribute part of a loop✕
- Connections
- 44 pairs of types, where a type in proguard.classfile.util uses a type in proguard.classfile.attribute. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
proguard.classfile.util.ArrayInitializationFilter→proguard.classfile.attribute.Attributeproguard.classfile.util.ArrayInitializationFilter→proguard.classfile.attribute.CodeAttributeproguard.classfile.util.ArrayInitializationMatcher→proguard.classfile.attribute.CodeAttributeproguard.classfile.util.ArrayInitializationReplacer→proguard.classfile.attribute.Attributeproguard.classfile.util.ArrayInitializationReplacer→proguard.classfile.attribute.CodeAttributeproguard.classfile.util.ClassReferenceInitializer→proguard.classfile.attribute.Attributeproguard.classfile.util.ClassReferenceInitializer→proguard.classfile.attribute.CodeAttributeproguard.classfile.util.ClassReferenceInitializer→proguard.classfile.attribute.EnclosingMethodAttributeproguard.classfile.util.ClassReferenceInitializer→proguard.classfile.attribute.LocalVariableInfoproguard.classfile.util.ClassReferenceInitializer→proguard.classfile.attribute.LocalVariableTableAttributeproguard.classfile.util.ClassReferenceInitializer→proguard.classfile.attribute.LocalVariableTypeInfoproguard.classfile.util.ClassReferenceInitializer→proguard.classfile.attribute.LocalVariableTypeTableAttributeproguard.classfile.util.ClassReferenceInitializer→proguard.classfile.attribute.SignatureAttributeproguard.classfile.util.DynamicClassReferenceInitializer→proguard.classfile.attribute.Attributeproguard.classfile.util.DynamicClassReferenceInitializer→proguard.classfile.attribute.CodeAttributeproguard.classfile.util.DynamicMemberReferenceInitializer→proguard.classfile.attribute.Attributeproguard.classfile.util.DynamicMemberReferenceInitializer→proguard.classfile.attribute.CodeAttributeproguard.classfile.util.EnumFieldReferenceInitializer→proguard.classfile.attribute.CodeAttributeproguard.classfile.util.InstructionSequenceMatcher→proguard.classfile.attribute.CodeAttributeproguard.classfile.util.MyDynamicMemberFinder→proguard.classfile.attribute.CodeAttributeproguard.classfile.util.NestHostFinder→proguard.classfile.attribute.Attributeproguard.classfile.util.NestHostFinder→proguard.classfile.attribute.NestHostAttributeproguard.classfile.util.PrimitiveArrayConstantReplacer→proguard.classfile.attribute.Attributeproguard.classfile.util.PrimitiveArrayConstantReplacer→proguard.classfile.attribute.CodeAttributeproguard.classfile.util.SimplifiedVisitor→proguard.classfile.attribute.Attribute
- Direction
- proguard.classfile.util uses proguard.classfile.attribute, so a change to proguard.classfile.attribute can break proguard.classfile.util, while a change to proguard.classfile.util can't break proguard.classfile.attribute.
- 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→22 proguard.classfile.util uses proguard.classfile part of a loop✕
- Connections
- 81 pairs of types, where a type in proguard.classfile.util uses a type in proguard.classfile. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
proguard.classfile.util.AllParameterVisitor→proguard.classfile.Clazzproguard.classfile.util.AllParameterVisitor→proguard.classfile.Fieldproguard.classfile.util.AllParameterVisitor→proguard.classfile.LibraryClassproguard.classfile.util.AllParameterVisitor→proguard.classfile.LibraryFieldproguard.classfile.util.AllParameterVisitor→proguard.classfile.LibraryMethodproguard.classfile.util.AllParameterVisitor→proguard.classfile.Methodproguard.classfile.util.AllParameterVisitor→proguard.classfile.ProgramClassproguard.classfile.util.AllParameterVisitor→proguard.classfile.ProgramFieldproguard.classfile.util.AllParameterVisitor→proguard.classfile.ProgramMethodproguard.classfile.util.ArrayInitializationFilter→proguard.classfile.Clazzproguard.classfile.util.ArrayInitializationFilter→proguard.classfile.Methodproguard.classfile.util.ArrayInitializationMatcher→proguard.classfile.Clazzproguard.classfile.util.ArrayInitializationMatcher→proguard.classfile.Methodproguard.classfile.util.ArrayInitializationReplacer→proguard.classfile.Clazzproguard.classfile.util.ArrayInitializationReplacer→proguard.classfile.Methodproguard.classfile.util.ArrayInitializationReplacer→proguard.classfile.ProgramClassproguard.classfile.util.ClassReferenceInitializer→proguard.classfile.ClassPoolproguard.classfile.util.ClassReferenceInitializer→proguard.classfile.Clazzproguard.classfile.util.ClassReferenceInitializer→proguard.classfile.LibraryClassproguard.classfile.util.ClassReferenceInitializer→proguard.classfile.LibraryFieldproguard.classfile.util.ClassReferenceInitializer→proguard.classfile.LibraryMethodproguard.classfile.util.ClassReferenceInitializer→proguard.classfile.Methodproguard.classfile.util.ClassReferenceInitializer→proguard.classfile.ProgramClassproguard.classfile.util.ClassReferenceInitializer→proguard.classfile.ProgramFieldproguard.classfile.util.ClassReferenceInitializer→proguard.classfile.ProgramMethod
- Direction
- proguard.classfile.util uses proguard.classfile, so a change to proguard.classfile can break proguard.classfile.util, while a change to proguard.classfile.util can't break proguard.classfile.
- 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→1 com.google.devtools.build.lib.bazel.bzlmod uses net.starlark.java.syntax✕
- Connections
- 18 pairs of types, where a type in com.google.devtools.build.lib.bazel.bzlmod uses a type in net.starlark.java.syntax.
- The types involved
com.google.devtools.build.lib.bazel.bzlmod.Builder→net.starlark.java.syntax.Locationcom.google.devtools.build.lib.bazel.bzlmod.CompiledModuleFile→net.starlark.java.syntax.Programcom.google.devtools.build.lib.bazel.bzlmod.CompiledModuleFile→net.starlark.java.syntax.StarlarkFilecom.google.devtools.build.lib.bazel.bzlmod.Facts→net.starlark.java.syntax.StarlarkTypecom.google.devtools.build.lib.bazel.bzlmod.IncludeStatement→net.starlark.java.syntax.Locationcom.google.devtools.build.lib.bazel.bzlmod.ModuleExtension→net.starlark.java.syntax.Locationcom.google.devtools.build.lib.bazel.bzlmod.ModuleExtensionProxy→net.starlark.java.syntax.Locationcom.google.devtools.build.lib.bazel.bzlmod.Proxy→net.starlark.java.syntax.Locationcom.google.devtools.build.lib.bazel.bzlmod.RegularRunnableExtension→net.starlark.java.syntax.Locationcom.google.devtools.build.lib.bazel.bzlmod.RepoNameUsage→net.starlark.java.syntax.Locationcom.google.devtools.build.lib.bazel.bzlmod.RepoOverride→net.starlark.java.syntax.Locationcom.google.devtools.build.lib.bazel.bzlmod.RepoRuleCall→net.starlark.java.syntax.Locationcom.google.devtools.build.lib.bazel.bzlmod.SyntaxChecker→net.starlark.java.syntax.AssignmentStatementcom.google.devtools.build.lib.bazel.bzlmod.SyntaxChecker→net.starlark.java.syntax.ExpressionStatementcom.google.devtools.build.lib.bazel.bzlmod.SyntaxChecker→net.starlark.java.syntax.Identifiercom.google.devtools.build.lib.bazel.bzlmod.Tag→net.starlark.java.syntax.Locationcom.google.devtools.build.lib.bazel.bzlmod.TypeCheckedTag→net.starlark.java.syntax.Locationcom.google.devtools.build.lib.bazel.bzlmod.VendorFileFunction→net.starlark.java.syntax.StarlarkFile
- Direction
- com.google.devtools.build.lib.bazel.bzlmod uses net.starlark.java.syntax, so a change to net.starlark.java.syntax can break com.google.devtools.build.lib.bazel.bzlmod, while a change to com.google.devtools.build.lib.bazel.bzlmod can't break net.starlark.java.syntax.
- Position
- Below the diagonal: com.google.devtools.build.lib.bazel.bzlmod uses a module listed above it, which is the healthy direction.
13→2 com.google.devtools.build.lib.bazel.bzlmod uses com.google.devtools.build.lib.events✕
- Connections
- 11 pairs of types, where a type in com.google.devtools.build.lib.bazel.bzlmod uses a type in com.google.devtools.build.lib.events.
- The types involved
com.google.devtools.build.lib.bazel.bzlmod.BazelModuleResolutionFunction→com.google.devtools.build.lib.events.EventHandlercom.google.devtools.build.lib.bazel.bzlmod.CompiledModuleFile→com.google.devtools.build.lib.events.ExtendedEventHandlercom.google.devtools.build.lib.bazel.bzlmod.GetModuleFileResult→com.google.devtools.build.lib.events.StoredEventHandlercom.google.devtools.build.lib.bazel.bzlmod.IndexRegistry→com.google.devtools.build.lib.events.ExtendedEventHandlercom.google.devtools.build.lib.bazel.bzlmod.IndexRegistry→com.google.devtools.build.lib.events.StoredEventHandlercom.google.devtools.build.lib.bazel.bzlmod.ModuleExtensionEvalStarlarkThreadContext→com.google.devtools.build.lib.events.ExtendedEventHandlercom.google.devtools.build.lib.bazel.bzlmod.ModuleExtensionProxy→com.google.devtools.build.lib.events.EventHandlercom.google.devtools.build.lib.bazel.bzlmod.ModuleFileFunction→com.google.devtools.build.lib.events.ExtendedEventHandlercom.google.devtools.build.lib.bazel.bzlmod.ModuleThreadContext→com.google.devtools.build.lib.events.Eventcom.google.devtools.build.lib.bazel.bzlmod.Registry→com.google.devtools.build.lib.events.ExtendedEventHandlercom.google.devtools.build.lib.bazel.bzlmod.RootModuleFileFixup→com.google.devtools.build.lib.events.Event
- Direction
- com.google.devtools.build.lib.bazel.bzlmod uses com.google.devtools.build.lib.events, so a change to com.google.devtools.build.lib.events can break com.google.devtools.build.lib.bazel.bzlmod, while a change to com.google.devtools.build.lib.bazel.bzlmod can't break com.google.devtools.build.lib.events.
- Position
- Below the diagonal: com.google.devtools.build.lib.bazel.bzlmod uses a module listed above it, which is the healthy direction.
13→4 com.google.devtools.build.lib.bazel.bzlmod uses net.starlark.java.eval✕
- Connections
- 56 pairs of types, where a type in com.google.devtools.build.lib.bazel.bzlmod uses a type in net.starlark.java.eval. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.google.devtools.build.lib.bazel.bzlmod.ArchiveRepoSpecBuilder→net.starlark.java.eval.Buildercom.google.devtools.build.lib.bazel.bzlmod.AttributeValues→net.starlark.java.eval.Dictcom.google.devtools.build.lib.bazel.bzlmod.CompiledModuleFile→net.starlark.java.eval.StarlarkSemanticscom.google.devtools.build.lib.bazel.bzlmod.CompiledModuleFile→net.starlark.java.eval.StarlarkThreadcom.google.devtools.build.lib.bazel.bzlmod.Facts→net.starlark.java.eval.Dictcom.google.devtools.build.lib.bazel.bzlmod.Facts→net.starlark.java.eval.Printercom.google.devtools.build.lib.bazel.bzlmod.Facts→net.starlark.java.eval.StarlarkIndexablecom.google.devtools.build.lib.bazel.bzlmod.Facts→net.starlark.java.eval.StarlarkSemanticscom.google.devtools.build.lib.bazel.bzlmod.Facts→net.starlark.java.eval.StarlarkThreadcom.google.devtools.build.lib.bazel.bzlmod.FactsAdapter→net.starlark.java.eval.StarlarkSemanticscom.google.devtools.build.lib.bazel.bzlmod.GitRepoSpecBuilder→net.starlark.java.eval.Buildercom.google.devtools.build.lib.bazel.bzlmod.InnateRunnableExtension→net.starlark.java.eval.StarlarkSemanticscom.google.devtools.build.lib.bazel.bzlmod.ModuleExtension→net.starlark.java.eval.StarlarkCallablecom.google.devtools.build.lib.bazel.bzlmod.ModuleExtension→net.starlark.java.eval.StarlarkValuecom.google.devtools.build.lib.bazel.bzlmod.ModuleExtensionContext→net.starlark.java.eval.StarlarkListcom.google.devtools.build.lib.bazel.bzlmod.ModuleExtensionContext→net.starlark.java.eval.StarlarkSemanticscom.google.devtools.build.lib.bazel.bzlmod.ModuleExtensionEvalStarlarkThreadContext→net.starlark.java.eval.Dictcom.google.devtools.build.lib.bazel.bzlmod.ModuleExtensionEvalStarlarkThreadContext→net.starlark.java.eval.StarlarkThreadcom.google.devtools.build.lib.bazel.bzlmod.ModuleExtensionMetadata→net.starlark.java.eval.Dictcom.google.devtools.build.lib.bazel.bzlmod.ModuleExtensionMetadata→net.starlark.java.eval.StarlarkValuecom.google.devtools.build.lib.bazel.bzlmod.ModuleExtensionProxy→net.starlark.java.eval.CallStackEntrycom.google.devtools.build.lib.bazel.bzlmod.ModuleExtensionProxy→net.starlark.java.eval.Structurecom.google.devtools.build.lib.bazel.bzlmod.ModuleExtensionUsageBuilder→net.starlark.java.eval.CallStackEntrycom.google.devtools.build.lib.bazel.bzlmod.ModuleFileFunction→net.starlark.java.eval.StarlarkSemanticscom.google.devtools.build.lib.bazel.bzlmod.ModuleFileFunction→net.starlark.java.eval.StarlarkThread
- Direction
- com.google.devtools.build.lib.bazel.bzlmod uses net.starlark.java.eval, so a change to net.starlark.java.eval can break com.google.devtools.build.lib.bazel.bzlmod, while a change to com.google.devtools.build.lib.bazel.bzlmod can't break net.starlark.java.eval.
- Position
- Below the diagonal: com.google.devtools.build.lib.bazel.bzlmod uses a module listed above it, which is the healthy direction.
13→6 com.google.devtools.build.lib.bazel.bzlmod uses com.google.devtools.build.skyframe✕
- Connections
- 84 pairs of types, where a type in com.google.devtools.build.lib.bazel.bzlmod uses a type in com.google.devtools.build.skyframe. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.google.devtools.build.lib.bazel.bzlmod.2→com.google.devtools.build.skyframe.SkyFunctionNamecom.google.devtools.build.lib.bazel.bzlmod.2→com.google.devtools.build.skyframe.SkyKeycom.google.devtools.build.lib.bazel.bzlmod.BazelDepGraphFunction→com.google.devtools.build.skyframe.SkyFunctioncom.google.devtools.build.lib.bazel.bzlmod.BazelDepGraphFunction→com.google.devtools.build.skyframe.SkyKeycom.google.devtools.build.lib.bazel.bzlmod.BazelDepGraphFunction→com.google.devtools.build.skyframe.SkyValuecom.google.devtools.build.lib.bazel.bzlmod.BazelDepGraphFunctionException→com.google.devtools.build.skyframe.SkyFunctionExceptioncom.google.devtools.build.lib.bazel.bzlmod.BazelDepGraphValue→com.google.devtools.build.skyframe.SkyKeycom.google.devtools.build.lib.bazel.bzlmod.BazelDepGraphValue→com.google.devtools.build.skyframe.SkyValuecom.google.devtools.build.lib.bazel.bzlmod.BazelFetchAllFunction→com.google.devtools.build.skyframe.SkyFunctioncom.google.devtools.build.lib.bazel.bzlmod.BazelFetchAllFunction→com.google.devtools.build.skyframe.SkyKeycom.google.devtools.build.lib.bazel.bzlmod.BazelFetchAllFunction→com.google.devtools.build.skyframe.SkyValuecom.google.devtools.build.lib.bazel.bzlmod.BazelFetchAllValue→com.google.devtools.build.skyframe.SkyValuecom.google.devtools.build.lib.bazel.bzlmod.BazelLockFileFunction→com.google.devtools.build.skyframe.SkyFunctioncom.google.devtools.build.lib.bazel.bzlmod.BazelLockFileFunction→com.google.devtools.build.skyframe.SkyKeycom.google.devtools.build.lib.bazel.bzlmod.BazelLockFileFunction→com.google.devtools.build.skyframe.SkyValuecom.google.devtools.build.lib.bazel.bzlmod.BazelLockFileValue→com.google.devtools.build.skyframe.SkyKeycom.google.devtools.build.lib.bazel.bzlmod.BazelLockFileValue→com.google.devtools.build.skyframe.SkyValuecom.google.devtools.build.lib.bazel.bzlmod.BazelLockfileFunctionException→com.google.devtools.build.skyframe.SkyFunctionExceptioncom.google.devtools.build.lib.bazel.bzlmod.BazelModTidyFunction→com.google.devtools.build.skyframe.SkyFunctioncom.google.devtools.build.lib.bazel.bzlmod.BazelModTidyFunction→com.google.devtools.build.skyframe.SkyKeycom.google.devtools.build.lib.bazel.bzlmod.BazelModTidyFunction→com.google.devtools.build.skyframe.SkyValuecom.google.devtools.build.lib.bazel.bzlmod.BazelModTidyValue→com.google.devtools.build.skyframe.SkyKeycom.google.devtools.build.lib.bazel.bzlmod.BazelModTidyValue→com.google.devtools.build.skyframe.SkyValuecom.google.devtools.build.lib.bazel.bzlmod.BazelModuleInspectorFunction→com.google.devtools.build.skyframe.SkyFunctioncom.google.devtools.build.lib.bazel.bzlmod.BazelModuleInspectorFunction→com.google.devtools.build.skyframe.SkyKey
- Direction
- com.google.devtools.build.lib.bazel.bzlmod uses com.google.devtools.build.skyframe, so a change to com.google.devtools.build.skyframe can break com.google.devtools.build.lib.bazel.bzlmod, while a change to com.google.devtools.build.lib.bazel.bzlmod can't break com.google.devtools.build.skyframe.
- Position
- Below the diagonal: com.google.devtools.build.lib.bazel.bzlmod uses a module listed above it, which is the healthy direction.
13→8 com.google.devtools.build.lib.bazel.bzlmod uses com.google.devtools.build.lib.vfs✕
- Connections
- 22 pairs of types, where a type in com.google.devtools.build.lib.bazel.bzlmod uses a type in com.google.devtools.build.lib.vfs.
- The types involved
com.google.devtools.build.lib.bazel.bzlmod.BazelLockFileFunction→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.bazel.bzlmod.BazelLockFileFunction→com.google.devtools.build.lib.vfs.RootedPathcom.google.devtools.build.lib.bazel.bzlmod.BazelLockFileModule→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.bazel.bzlmod.BazelModTidyValue→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.bazel.bzlmod.BazelModTidyValue→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.bazel.bzlmod.IndexRegistry→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.bazel.bzlmod.IndexRegistry→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.bazel.bzlmod.ModuleExtensionContext→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.bazel.bzlmod.ModuleFileFunction→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.bazel.bzlmod.ModuleFileFunction→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.bazel.bzlmod.ModuleFileFunction→com.google.devtools.build.lib.vfs.RootedPathcom.google.devtools.build.lib.bazel.bzlmod.ModuleThreadContext→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.bazel.bzlmod.Proxy→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.bazel.bzlmod.RegistryFactory→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.bazel.bzlmod.RegistryFactoryImpl→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.bazel.bzlmod.RegistryFunction→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.bazel.bzlmod.RegistryFunction→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.bazel.bzlmod.RootModuleFileFixup→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.bazel.bzlmod.RootModuleFileValue→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.bazel.bzlmod.VendorFileFunction→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.bazel.bzlmod.VendorManager→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.bazel.bzlmod.VendorManager→com.google.devtools.build.lib.vfs.PathFragment
- Direction
- com.google.devtools.build.lib.bazel.bzlmod uses com.google.devtools.build.lib.vfs, so a change to com.google.devtools.build.lib.vfs can break com.google.devtools.build.lib.bazel.bzlmod, while a change to com.google.devtools.build.lib.bazel.bzlmod can't break com.google.devtools.build.lib.vfs.
- Position
- Below the diagonal: com.google.devtools.build.lib.bazel.bzlmod uses a module listed above it, which is the healthy direction.
13→11 com.google.devtools.build.lib.bazel.bzlmod uses com.google.devtools.build.lib.util✕
- Connections
- 1 pair of types, where a type in com.google.devtools.build.lib.bazel.bzlmod uses a type in com.google.devtools.build.lib.util.
- The types involved
com.google.devtools.build.lib.bazel.bzlmod.ExternalDepsException→com.google.devtools.build.lib.util.DetailedExitCode
- Direction
- com.google.devtools.build.lib.bazel.bzlmod uses com.google.devtools.build.lib.util, so a change to com.google.devtools.build.lib.util can break com.google.devtools.build.lib.bazel.bzlmod, while a change to com.google.devtools.build.lib.bazel.bzlmod can't break com.google.devtools.build.lib.util.
- Position
- Below the diagonal: com.google.devtools.build.lib.bazel.bzlmod uses a module listed above it, which is the healthy direction.
13→24 com.google.devtools.build.lib.bazel.bzlmod uses com.google.devtools.build.lib.skyframe part of a loop✕
- Connections
- 4 pairs of types, where a type in com.google.devtools.build.lib.bazel.bzlmod uses a type in com.google.devtools.build.lib.skyframe.
- The types involved
com.google.devtools.build.lib.bazel.bzlmod.ExternalDepsException→com.google.devtools.build.lib.skyframe.DetailedExceptioncom.google.devtools.build.lib.bazel.bzlmod.InnateRunnableExtension→com.google.devtools.build.lib.skyframe.BzlLoadValuecom.google.devtools.build.lib.bazel.bzlmod.RegularRunnableExtension→com.google.devtools.build.lib.skyframe.BzlLoadValuecom.google.devtools.build.lib.bazel.bzlmod.YankedVersionsUtil→com.google.devtools.build.lib.skyframe.Precomputed
- Direction
- com.google.devtools.build.lib.bazel.bzlmod uses com.google.devtools.build.lib.skyframe, so a change to com.google.devtools.build.lib.skyframe can break com.google.devtools.build.lib.bazel.bzlmod, while a change to com.google.devtools.build.lib.bazel.bzlmod can't break com.google.devtools.build.lib.skyframe.
- 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→25 com.google.devtools.build.lib.bazel.bzlmod uses com.google.devtools.build.lib.packages part of a loop✕
- Connections
- 8 pairs of types, where a type in com.google.devtools.build.lib.bazel.bzlmod uses a type in com.google.devtools.build.lib.packages.
- The types involved
com.google.devtools.build.lib.bazel.bzlmod.CompiledModuleFile→com.google.devtools.build.lib.packages.BazelStarlarkEnvironmentcom.google.devtools.build.lib.bazel.bzlmod.ModuleExtensionProxy→com.google.devtools.build.lib.packages.StarlarkExportablecom.google.devtools.build.lib.bazel.bzlmod.ModuleFileFunction→com.google.devtools.build.lib.packages.BazelStarlarkEnvironmentcom.google.devtools.build.lib.bazel.bzlmod.SyntaxChecker→com.google.devtools.build.lib.packages.DotBazelFileSyntaxCheckercom.google.devtools.build.lib.bazel.bzlmod.TagClass→com.google.devtools.build.lib.packages.Attributecom.google.devtools.build.lib.bazel.bzlmod.TypeCheckedTag→com.google.devtools.build.lib.packages.LabelConvertercom.google.devtools.build.lib.bazel.bzlmod.VendorFileFunction→com.google.devtools.build.lib.packages.BazelStarlarkEnvironmentcom.google.devtools.build.lib.bazel.bzlmod.VendorFileFunction→com.google.devtools.build.lib.packages.VendorThreadContext
- Direction
- com.google.devtools.build.lib.bazel.bzlmod uses com.google.devtools.build.lib.packages, so a change to com.google.devtools.build.lib.packages can break com.google.devtools.build.lib.bazel.bzlmod, while a change to com.google.devtools.build.lib.bazel.bzlmod can't break com.google.devtools.build.lib.packages.
- 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→28 com.google.devtools.build.lib.bazel.bzlmod uses com.google.devtools.build.lib.runtime part of a loop✕
- Connections
- 8 pairs of types, where a type in com.google.devtools.build.lib.bazel.bzlmod uses a type in com.google.devtools.build.lib.runtime.
- The types involved
com.google.devtools.build.lib.bazel.bzlmod.BazelLockFileModule→com.google.devtools.build.lib.runtime.BlazeModulecom.google.devtools.build.lib.bazel.bzlmod.BazelLockFileModule→com.google.devtools.build.lib.runtime.CommandEnvironmentcom.google.devtools.build.lib.bazel.bzlmod.ModuleExtensionContext→com.google.devtools.build.lib.runtime.ProcessWrappercom.google.devtools.build.lib.bazel.bzlmod.ModuleExtensionContext→com.google.devtools.build.lib.runtime.RepositoryRemoteExecutorcom.google.devtools.build.lib.bazel.bzlmod.RegularRunnableExtension→com.google.devtools.build.lib.runtime.ProcessWrappercom.google.devtools.build.lib.bazel.bzlmod.RegularRunnableExtension→com.google.devtools.build.lib.runtime.RepositoryRemoteExecutorcom.google.devtools.build.lib.bazel.bzlmod.SingleExtensionEvalFunction→com.google.devtools.build.lib.runtime.ProcessWrappercom.google.devtools.build.lib.bazel.bzlmod.SingleExtensionEvalFunction→com.google.devtools.build.lib.runtime.RepositoryRemoteExecutor
- Direction
- com.google.devtools.build.lib.bazel.bzlmod uses com.google.devtools.build.lib.runtime, so a change to com.google.devtools.build.lib.runtime can break com.google.devtools.build.lib.bazel.bzlmod, while a change to com.google.devtools.build.lib.bazel.bzlmod can't break com.google.devtools.build.lib.runtime.
- 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→31 com.google.devtools.build.lib.bazel.bzlmod uses com.google.devtools.build.lib.cmdline part of a loop✕
- Connections
- 40 pairs of types, where a type in com.google.devtools.build.lib.bazel.bzlmod uses a type in com.google.devtools.build.lib.cmdline. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.google.devtools.build.lib.bazel.bzlmod.5089→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.bazel.bzlmod.6615→com.google.devtools.build.lib.cmdline.RepositoryNamecom.google.devtools.build.lib.bazel.bzlmod.ArchiveRepoSpecBuilder→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.bazel.bzlmod.BazelDepGraphFunction→com.google.devtools.build.lib.cmdline.RepositoryNamecom.google.devtools.build.lib.bazel.bzlmod.BazelDepGraphValue→com.google.devtools.build.lib.cmdline.RepositoryMappingcom.google.devtools.build.lib.bazel.bzlmod.BazelDepGraphValue→com.google.devtools.build.lib.cmdline.RepositoryNamecom.google.devtools.build.lib.bazel.bzlmod.BazelFetchAllValue→com.google.devtools.build.lib.cmdline.RepositoryNamecom.google.devtools.build.lib.bazel.bzlmod.BazelModuleInspectorValue→com.google.devtools.build.lib.cmdline.RepositoryNamecom.google.devtools.build.lib.bazel.bzlmod.GsonTypeAdapterUtil→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.bazel.bzlmod.GsonTypeAdapterUtil→com.google.devtools.build.lib.cmdline.RepositoryNamecom.google.devtools.build.lib.bazel.bzlmod.InnateRunnableExtension→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.bazel.bzlmod.InnateRunnableExtension→com.google.devtools.build.lib.cmdline.RepositoryMappingcom.google.devtools.build.lib.bazel.bzlmod.Module→com.google.devtools.build.lib.cmdline.RepositoryMappingcom.google.devtools.build.lib.bazel.bzlmod.Module→com.google.devtools.build.lib.cmdline.RepositoryNamecom.google.devtools.build.lib.bazel.bzlmod.ModuleExtension→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.bazel.bzlmod.ModuleExtensionContext→com.google.devtools.build.lib.cmdline.RepositoryNamecom.google.devtools.build.lib.bazel.bzlmod.ModuleExtensionEvalStarlarkThreadContext→com.google.devtools.build.lib.cmdline.PackageIdentifiercom.google.devtools.build.lib.bazel.bzlmod.ModuleExtensionEvalStarlarkThreadContext→com.google.devtools.build.lib.cmdline.RepositoryMappingcom.google.devtools.build.lib.bazel.bzlmod.ModuleExtensionEvalStarlarkThreadContext→com.google.devtools.build.lib.cmdline.RepositoryNamecom.google.devtools.build.lib.bazel.bzlmod.ModuleExtensionEvalStarlarkThreadContext→com.google.devtools.build.lib.cmdline.StarlarkThreadContextcom.google.devtools.build.lib.bazel.bzlmod.ModuleExtensionId→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.bazel.bzlmod.ModuleExtensionProxy→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.bazel.bzlmod.ModuleExtensionRepoMappingEntriesFunction→com.google.devtools.build.lib.cmdline.RepositoryMappingcom.google.devtools.build.lib.bazel.bzlmod.ModuleExtensionRepoMappingEntriesValue→com.google.devtools.build.lib.cmdline.RepositoryNamecom.google.devtools.build.lib.bazel.bzlmod.ModuleFileGlobals→com.google.devtools.build.lib.cmdline.Label
- Direction
- com.google.devtools.build.lib.bazel.bzlmod uses com.google.devtools.build.lib.cmdline, so a change to com.google.devtools.build.lib.cmdline can break com.google.devtools.build.lib.bazel.bzlmod, while a change to com.google.devtools.build.lib.bazel.bzlmod can't break com.google.devtools.build.lib.cmdline.
- 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→35 com.google.devtools.build.lib.bazel.bzlmod uses com.google.devtools.build.lib.analysis part of a loop✕
- Connections
- 3 pairs of types, where a type in com.google.devtools.build.lib.bazel.bzlmod uses a type in com.google.devtools.build.lib.analysis.
- The types involved
com.google.devtools.build.lib.bazel.bzlmod.ModuleExtensionContext→com.google.devtools.build.lib.analysis.BlazeDirectoriescom.google.devtools.build.lib.bazel.bzlmod.RegularRunnableExtension→com.google.devtools.build.lib.analysis.BlazeDirectoriescom.google.devtools.build.lib.bazel.bzlmod.SingleExtensionEvalFunction→com.google.devtools.build.lib.analysis.BlazeDirectories
- Direction
- com.google.devtools.build.lib.bazel.bzlmod uses com.google.devtools.build.lib.analysis, so a change to com.google.devtools.build.lib.analysis can break com.google.devtools.build.lib.bazel.bzlmod, while a change to com.google.devtools.build.lib.bazel.bzlmod can't break com.google.devtools.build.lib.analysis.
- 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→2 com.google.devtools.build.lib.buildeventstream uses com.google.devtools.build.lib.events✕
- Connections
- 2 pairs of types, where a type in com.google.devtools.build.lib.buildeventstream uses a type in com.google.devtools.build.lib.events.
- The types involved
com.google.devtools.build.lib.buildeventstream.BuildEvent→com.google.devtools.build.lib.events.Postablecom.google.devtools.build.lib.buildeventstream.FetchEvent→com.google.devtools.build.lib.events.Postable
- Direction
- com.google.devtools.build.lib.buildeventstream uses com.google.devtools.build.lib.events, so a change to com.google.devtools.build.lib.events can break com.google.devtools.build.lib.buildeventstream, while a change to com.google.devtools.build.lib.buildeventstream can't break com.google.devtools.build.lib.events.
- Position
- Below the diagonal: com.google.devtools.build.lib.buildeventstream uses a module listed above it, which is the healthy direction.
14→3 com.google.devtools.build.lib.buildeventstream uses com.google.devtools.common.options✕
- Connections
- 3 pairs of types, where a type in com.google.devtools.build.lib.buildeventstream uses a type in com.google.devtools.common.options.
- The types involved
com.google.devtools.build.lib.buildeventstream.BuildEventOutputGroupModeConverter→com.google.devtools.common.options.Contextlesscom.google.devtools.build.lib.buildeventstream.BuildEventProtocolOptions→com.google.devtools.common.options.OptionsBasecom.google.devtools.build.lib.buildeventstream.OutputGroupFileModeConverter→com.google.devtools.common.options.EnumConverter
- Direction
- com.google.devtools.build.lib.buildeventstream uses com.google.devtools.common.options, so a change to com.google.devtools.common.options can break com.google.devtools.build.lib.buildeventstream, while a change to com.google.devtools.build.lib.buildeventstream can't break com.google.devtools.common.options.
- Position
- Below the diagonal: com.google.devtools.build.lib.buildeventstream uses a module listed above it, which is the healthy direction.
14→8 com.google.devtools.build.lib.buildeventstream uses com.google.devtools.build.lib.vfs✕
- Connections
- 7 pairs of types, where a type in com.google.devtools.build.lib.buildeventstream uses a type in com.google.devtools.build.lib.vfs.
- The types involved
com.google.devtools.build.lib.buildeventstream.BuildEventArtifactUploader→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.buildeventstream.BuildEventIdUtil→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.buildeventstream.FileUriPathConverter→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.buildeventstream.LocalFile→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.buildeventstream.LocalFilesArtifactUploader→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.buildeventstream.PathConverter→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.buildeventstream.PathConverterImpl→com.google.devtools.build.lib.vfs.Path
- Direction
- com.google.devtools.build.lib.buildeventstream uses com.google.devtools.build.lib.vfs, so a change to com.google.devtools.build.lib.vfs can break com.google.devtools.build.lib.buildeventstream, while a change to com.google.devtools.build.lib.buildeventstream can't break com.google.devtools.build.lib.vfs.
- Position
- Below the diagonal: com.google.devtools.build.lib.buildeventstream uses a module listed above it, which is the healthy direction.
14→10 com.google.devtools.build.lib.buildeventstream uses com.google.devtools.build.lib.skyframe.config✕
- Connections
- 1 pair of types, where a type in com.google.devtools.build.lib.buildeventstream uses a type in com.google.devtools.build.lib.skyframe.config.
- The types involved
com.google.devtools.build.lib.buildeventstream.BuildEventIdUtil→com.google.devtools.build.lib.skyframe.config.BuildConfigurationKey
- Direction
- com.google.devtools.build.lib.buildeventstream uses com.google.devtools.build.lib.skyframe.config, so a change to com.google.devtools.build.lib.skyframe.config can break com.google.devtools.build.lib.buildeventstream, while a change to com.google.devtools.build.lib.buildeventstream can't break com.google.devtools.build.lib.skyframe.config.
- Position
- Below the diagonal: com.google.devtools.build.lib.buildeventstream uses a module listed above it, which is the healthy direction.
14→11 com.google.devtools.build.lib.buildeventstream uses com.google.devtools.build.lib.util✕
- Connections
- 3 pairs of types, where a type in com.google.devtools.build.lib.buildeventstream uses a type in com.google.devtools.build.lib.util.
- The types involved
com.google.devtools.build.lib.buildeventstream.BuildCompletingEvent→com.google.devtools.build.lib.util.DetailedExitCodecom.google.devtools.build.lib.buildeventstream.BuildCompletingEvent→com.google.devtools.build.lib.util.ExitCodecom.google.devtools.build.lib.buildeventstream.BuildToolLogs→com.google.devtools.build.lib.util.Pair
- Direction
- com.google.devtools.build.lib.buildeventstream uses com.google.devtools.build.lib.util, so a change to com.google.devtools.build.lib.util can break com.google.devtools.build.lib.buildeventstream, while a change to com.google.devtools.build.lib.buildeventstream can't break com.google.devtools.build.lib.util.
- Position
- Below the diagonal: com.google.devtools.build.lib.buildeventstream uses a module listed above it, which is the healthy direction.
14→30 com.google.devtools.build.lib.buildeventstream uses com.google.devtools.build.lib.collect.nestedset part of a loop✕
- Connections
- 1 pair of types, where a type in com.google.devtools.build.lib.buildeventstream uses a type in com.google.devtools.build.lib.collect.nestedset.
- The types involved
com.google.devtools.build.lib.buildeventstream.ArtifactGroupNamer→com.google.devtools.build.lib.collect.nestedset.Node
- Direction
- com.google.devtools.build.lib.buildeventstream uses com.google.devtools.build.lib.collect.nestedset, so a change to com.google.devtools.build.lib.collect.nestedset can break com.google.devtools.build.lib.buildeventstream, while a change to com.google.devtools.build.lib.buildeventstream can't break com.google.devtools.build.lib.collect.nestedset.
- 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→31 com.google.devtools.build.lib.buildeventstream uses com.google.devtools.build.lib.cmdline part of a loop✕
- Connections
- 2 pairs of types, where a type in com.google.devtools.build.lib.buildeventstream uses a type in com.google.devtools.build.lib.cmdline.
- The types involved
com.google.devtools.build.lib.buildeventstream.AbortedEvent→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.buildeventstream.BuildEventIdUtil→com.google.devtools.build.lib.cmdline.Label
- Direction
- com.google.devtools.build.lib.buildeventstream uses com.google.devtools.build.lib.cmdline, so a change to com.google.devtools.build.lib.cmdline can break com.google.devtools.build.lib.buildeventstream, while a change to com.google.devtools.build.lib.buildeventstream can't break com.google.devtools.build.lib.cmdline.
- 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→37 com.google.devtools.build.lib.buildeventstream uses com.google.devtools.build.lib.actions part of a loop✕
- Connections
- 3 pairs of types, where a type in com.google.devtools.build.lib.buildeventstream uses a type in com.google.devtools.build.lib.actions.
- The types involved
com.google.devtools.build.lib.buildeventstream.LocalFile→com.google.devtools.build.lib.actions.FileArtifactValuecom.google.devtools.build.lib.buildeventstream.LocalFileType→com.google.devtools.build.lib.actions.Artifactcom.google.devtools.build.lib.buildeventstream.LocalFileType→com.google.devtools.build.lib.actions.FileArtifactValue
- Direction
- com.google.devtools.build.lib.buildeventstream uses com.google.devtools.build.lib.actions, so a change to com.google.devtools.build.lib.actions can break com.google.devtools.build.lib.buildeventstream, while a change to com.google.devtools.build.lib.buildeventstream can't break com.google.devtools.build.lib.actions.
- 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.
15→2 com.google.devtools.build.lib.exec uses com.google.devtools.build.lib.events✕
- Connections
- 10 pairs of types, where a type in com.google.devtools.build.lib.exec uses a type in com.google.devtools.build.lib.events.
- The types involved
com.google.devtools.build.lib.exec.BlazeExecutor→com.google.devtools.build.lib.events.Reportercom.google.devtools.build.lib.exec.CompactSpawnLogContext→com.google.devtools.build.lib.events.ExtendedEventHandlercom.google.devtools.build.lib.exec.ProgressStatus→com.google.devtools.build.lib.events.ExtendedEventHandlercom.google.devtools.build.lib.exec.SpawnCheckingCacheEvent→com.google.devtools.build.lib.events.ExtendedEventHandlercom.google.devtools.build.lib.exec.SpawnExecutingEvent→com.google.devtools.build.lib.events.ExtendedEventHandlercom.google.devtools.build.lib.exec.SpawnProgressEvent→com.google.devtools.build.lib.events.ExtendedEventHandlercom.google.devtools.build.lib.exec.SpawnSchedulingEvent→com.google.devtools.build.lib.events.ExtendedEventHandlercom.google.devtools.build.lib.exec.SpawnStrategyRegistry→com.google.devtools.build.lib.events.EventHandlercom.google.devtools.build.lib.exec.SpawnUploadingEvent→com.google.devtools.build.lib.events.ExtendedEventHandlercom.google.devtools.build.lib.exec.StrategyRegexFilter→com.google.devtools.build.lib.events.EventHandler
- Direction
- com.google.devtools.build.lib.exec uses com.google.devtools.build.lib.events, so a change to com.google.devtools.build.lib.events can break com.google.devtools.build.lib.exec, while a change to com.google.devtools.build.lib.exec can't break com.google.devtools.build.lib.events.
- Position
- Below the diagonal: com.google.devtools.build.lib.exec uses a module listed above it, which is the healthy direction.
15→3 com.google.devtools.build.lib.exec uses com.google.devtools.common.options✕
- Connections
- 6 pairs of types, where a type in com.google.devtools.build.lib.exec uses a type in com.google.devtools.common.options.
- The types involved
com.google.devtools.build.lib.exec.BlazeExecutor→com.google.devtools.common.options.OptionsProvidercom.google.devtools.build.lib.exec.Converter→com.google.devtools.common.options.EnumConvertercom.google.devtools.build.lib.exec.ExecutionLogFileConverter→com.google.devtools.common.options.BooleanStyleOptioncom.google.devtools.build.lib.exec.ExecutionLogFileConverter→com.google.devtools.common.options.Contextlesscom.google.devtools.build.lib.exec.ExecutionOptions→com.google.devtools.common.options.OptionsBasecom.google.devtools.build.lib.exec.ShowSubcommandsConverter→com.google.devtools.common.options.BoolOrEnumConverter
- Direction
- com.google.devtools.build.lib.exec uses com.google.devtools.common.options, so a change to com.google.devtools.common.options can break com.google.devtools.build.lib.exec, while a change to com.google.devtools.build.lib.exec can't break com.google.devtools.common.options.
- Position
- Below the diagonal: com.google.devtools.build.lib.exec uses a module listed above it, which is the healthy direction.
15→8 com.google.devtools.build.lib.exec uses com.google.devtools.build.lib.vfs✕
- Connections
- 51 pairs of types, where a type in com.google.devtools.build.lib.exec uses a type in com.google.devtools.build.lib.vfs. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.google.devtools.build.lib.exec.AbstractSpawnExecutionContext→com.google.devtools.build.lib.vfs.FileSystemcom.google.devtools.build.lib.exec.BinTools→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.exec.BlazeExecutor→com.google.devtools.build.lib.vfs.FileSystemcom.google.devtools.build.lib.exec.BlazeExecutor→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.exec.CompactSpawnLogContext→com.google.devtools.build.lib.vfs.DigestHashFunctioncom.google.devtools.build.lib.exec.CompactSpawnLogContext→com.google.devtools.build.lib.vfs.FileSystemcom.google.devtools.build.lib.exec.CompactSpawnLogContext→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.exec.CompactSpawnLogContext→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.exec.CompactSpawnLogContext→com.google.devtools.build.lib.vfs.XattrProvidercom.google.devtools.build.lib.exec.Directory→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.exec.Directory→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.exec.DirectoryChildVisitor→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.exec.DirectoryVisitor→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.exec.ExecutionLogFileConverter→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.exec.ExecutionOptions→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.exec.ExpandedSpawnLogContext→com.google.devtools.build.lib.vfs.DigestHashFunctioncom.google.devtools.build.lib.exec.ExpandedSpawnLogContext→com.google.devtools.build.lib.vfs.FileSystemcom.google.devtools.build.lib.exec.ExpandedSpawnLogContext→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.exec.ExpandedSpawnLogContext→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.exec.ExpandedSpawnLogContext→com.google.devtools.build.lib.vfs.XattrProvidercom.google.devtools.build.lib.exec.PathActionInput→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.exec.PathActionInput→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.exec.RunfilesTreeUpdater→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.exec.RunfilesTreeUpdater→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.exec.RunfilesTreeUpdater→com.google.devtools.build.lib.vfs.XattrProvider
- Direction
- com.google.devtools.build.lib.exec uses com.google.devtools.build.lib.vfs, so a change to com.google.devtools.build.lib.vfs can break com.google.devtools.build.lib.exec, while a change to com.google.devtools.build.lib.exec can't break com.google.devtools.build.lib.vfs.
- Position
- Below the diagonal: com.google.devtools.build.lib.exec uses a module listed above it, which is the healthy direction.
15→11 com.google.devtools.build.lib.exec uses com.google.devtools.build.lib.util✕
- Connections
- 6 pairs of types, where a type in com.google.devtools.build.lib.exec uses a type in com.google.devtools.build.lib.util.
- The types involved
com.google.devtools.build.lib.exec.ExecutionOptions→com.google.devtools.build.lib.util.RegexFiltercom.google.devtools.build.lib.exec.FileWriteStrategy→com.google.devtools.build.lib.util.DeterministicWritercom.google.devtools.build.lib.exec.FilterAndIdentifiers→com.google.devtools.build.lib.util.RegexFiltercom.google.devtools.build.lib.exec.LocalTestJobsConverter→com.google.devtools.build.lib.util.IntegerConvertercom.google.devtools.build.lib.exec.SpawnStrategyRegistry→com.google.devtools.build.lib.util.AbruptExitExceptioncom.google.devtools.build.lib.exec.StrategyRegexFilter→com.google.devtools.build.lib.util.RegexFilter
- Direction
- com.google.devtools.build.lib.exec uses com.google.devtools.build.lib.util, so a change to com.google.devtools.build.lib.util can break com.google.devtools.build.lib.exec, while a change to com.google.devtools.build.lib.exec can't break com.google.devtools.build.lib.util.
- Position
- Below the diagonal: com.google.devtools.build.lib.exec uses a module listed above it, which is the healthy direction.
15→24 com.google.devtools.build.lib.exec uses com.google.devtools.build.lib.skyframe part of a loop✕
- Connections
- 3 pairs of types, where a type in com.google.devtools.build.lib.exec uses a type in com.google.devtools.build.lib.skyframe.
- The types involved
com.google.devtools.build.lib.exec.CompactSpawnLogContext→com.google.devtools.build.lib.skyframe.TreeArtifactValuecom.google.devtools.build.lib.exec.ExecutorLifecycleListener→com.google.devtools.build.lib.skyframe.EphemeralCheckIfOutputConsumedcom.google.devtools.build.lib.exec.SingleBuildFileCache→com.google.devtools.build.lib.skyframe.TreeArtifactValue
- Direction
- com.google.devtools.build.lib.exec uses com.google.devtools.build.lib.skyframe, so a change to com.google.devtools.build.lib.skyframe can break com.google.devtools.build.lib.exec, while a change to com.google.devtools.build.lib.exec can't break com.google.devtools.build.lib.skyframe.
- 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.
15→27 com.google.devtools.build.lib.exec uses com.google.devtools.build.lib.analysis.test part of a loop✕
- Connections
- 6 pairs of types, where a type in com.google.devtools.build.lib.exec uses a type in com.google.devtools.build.lib.analysis.test.
- The types involved
com.google.devtools.build.lib.exec.StandaloneTestResult→com.google.devtools.build.lib.analysis.test.TestAttemptResultcom.google.devtools.build.lib.exec.StandaloneTestRunnerSpawn→com.google.devtools.build.lib.analysis.test.TestRunnerActioncom.google.devtools.build.lib.exec.StandaloneTestStrategy→com.google.devtools.build.lib.analysis.test.TestResultcom.google.devtools.build.lib.exec.StandaloneTestStrategy→com.google.devtools.build.lib.analysis.test.TestRunnerActioncom.google.devtools.build.lib.exec.StandaloneTestStrategy→com.google.devtools.build.lib.analysis.test.TestStrategycom.google.devtools.build.lib.exec.TestPolicy→com.google.devtools.build.lib.analysis.test.TestRunnerAction
- Direction
- com.google.devtools.build.lib.exec uses com.google.devtools.build.lib.analysis.test, so a change to com.google.devtools.build.lib.analysis.test can break com.google.devtools.build.lib.exec, while a change to com.google.devtools.build.lib.exec can't break com.google.devtools.build.lib.analysis.test.
- 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.
15→28 com.google.devtools.build.lib.exec uses com.google.devtools.build.lib.runtime part of a loop✕
- Connections
- 1 pair of types, where a type in com.google.devtools.build.lib.exec uses a type in com.google.devtools.build.lib.runtime.
- The types involved
com.google.devtools.build.lib.exec.StandaloneTestStrategy→com.google.devtools.build.lib.runtime.TestSummaryOptions
- Direction
- com.google.devtools.build.lib.exec uses com.google.devtools.build.lib.runtime, so a change to com.google.devtools.build.lib.runtime can break com.google.devtools.build.lib.exec, while a change to com.google.devtools.build.lib.exec can't break com.google.devtools.build.lib.runtime.
- 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.
15→30 com.google.devtools.build.lib.exec uses com.google.devtools.build.lib.collect.nestedset part of a loop✕
- Connections
- 1 pair of types, where a type in com.google.devtools.build.lib.exec uses a type in com.google.devtools.build.lib.collect.nestedset.
- The types involved
com.google.devtools.build.lib.exec.CompactSpawnLogContext→com.google.devtools.build.lib.collect.nestedset.NestedSet
- Direction
- com.google.devtools.build.lib.exec uses com.google.devtools.build.lib.collect.nestedset, so a change to com.google.devtools.build.lib.collect.nestedset can break com.google.devtools.build.lib.exec, while a change to com.google.devtools.build.lib.exec can't break com.google.devtools.build.lib.collect.nestedset.
- 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.
15→31 com.google.devtools.build.lib.exec uses com.google.devtools.build.lib.cmdline part of a loop✕
- Connections
- 2 pairs of types, where a type in com.google.devtools.build.lib.exec uses a type in com.google.devtools.build.lib.cmdline.
- The types involved
com.google.devtools.build.lib.exec.ExecutionOptions→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.exec.StrategyPlatformFilter→com.google.devtools.build.lib.cmdline.Label
- Direction
- com.google.devtools.build.lib.exec uses com.google.devtools.build.lib.cmdline, so a change to com.google.devtools.build.lib.cmdline can break com.google.devtools.build.lib.exec, while a change to com.google.devtools.build.lib.exec can't break com.google.devtools.build.lib.cmdline.
- 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.
15→33 com.google.devtools.build.lib.exec uses com.google.devtools.build.lib.analysis.config part of a loop✕
- Connections
- 3 pairs of types, where a type in com.google.devtools.build.lib.exec uses a type in com.google.devtools.build.lib.analysis.config.
- The types involved
com.google.devtools.build.lib.exec.ExecutionOptions→com.google.devtools.build.lib.analysis.config.PerLabelOptionscom.google.devtools.build.lib.exec.TestAttemptsConverter→com.google.devtools.build.lib.analysis.config.PerLabelOptionscom.google.devtools.build.lib.exec.TestAttemptsConverter→com.google.devtools.build.lib.analysis.config.PerLabelOptionsConverter
- Direction
- com.google.devtools.build.lib.exec uses com.google.devtools.build.lib.analysis.config, so a change to com.google.devtools.build.lib.analysis.config can break com.google.devtools.build.lib.exec, while a change to com.google.devtools.build.lib.exec can't break com.google.devtools.build.lib.analysis.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.
15→34 com.google.devtools.build.lib.exec uses com.google.devtools.build.lib.analysis.actions part of a loop✕
- Connections
- 3 pairs of types, where a type in com.google.devtools.build.lib.exec uses a type in com.google.devtools.build.lib.analysis.actions.
- The types involved
com.google.devtools.build.lib.exec.FileWriteStrategy→com.google.devtools.build.lib.analysis.actions.FileWriteActionContextcom.google.devtools.build.lib.exec.SymlinkTreeStrategy→com.google.devtools.build.lib.analysis.actions.SymlinkTreeActioncom.google.devtools.build.lib.exec.SymlinkTreeStrategy→com.google.devtools.build.lib.analysis.actions.SymlinkTreeActionContext
- Direction
- com.google.devtools.build.lib.exec uses com.google.devtools.build.lib.analysis.actions, so a change to com.google.devtools.build.lib.analysis.actions can break com.google.devtools.build.lib.exec, while a change to com.google.devtools.build.lib.exec can't break com.google.devtools.build.lib.analysis.actions.
- 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.
15→35 com.google.devtools.build.lib.exec uses com.google.devtools.build.lib.analysis part of a loop✕
- Connections
- 2 pairs of types, where a type in com.google.devtools.build.lib.exec uses a type in com.google.devtools.build.lib.analysis.
- The types involved
com.google.devtools.build.lib.exec.BinTools→com.google.devtools.build.lib.analysis.BlazeDirectoriescom.google.devtools.build.lib.exec.CompactSpawnLogContext→com.google.devtools.build.lib.analysis.SymlinkEntry
- Direction
- com.google.devtools.build.lib.exec uses com.google.devtools.build.lib.analysis, so a change to com.google.devtools.build.lib.analysis can break com.google.devtools.build.lib.exec, while a change to com.google.devtools.build.lib.exec can't break com.google.devtools.build.lib.analysis.
- 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.
15→37 com.google.devtools.build.lib.exec uses com.google.devtools.build.lib.actions part of a loop✕
- Connections
- 120 pairs of types, where a type in com.google.devtools.build.lib.exec uses a type in com.google.devtools.build.lib.actions. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.google.devtools.build.lib.exec.1→com.google.devtools.build.lib.actions.SpawnResultcom.google.devtools.build.lib.exec.2→com.google.devtools.build.lib.actions.SpawnResultcom.google.devtools.build.lib.exec.AbstractSpawnExecutionContext→com.google.devtools.build.lib.actions.ActionExecutionContextcom.google.devtools.build.lib.exec.AbstractSpawnExecutionContext→com.google.devtools.build.lib.actions.ArtifactPathResolvercom.google.devtools.build.lib.exec.AbstractSpawnExecutionContext→com.google.devtools.build.lib.actions.Spawncom.google.devtools.build.lib.exec.AbstractSpawnStrategy→com.google.devtools.build.lib.actions.ActionContextRegistrycom.google.devtools.build.lib.exec.AbstractSpawnStrategy→com.google.devtools.build.lib.actions.ActionExecutionContextcom.google.devtools.build.lib.exec.AbstractSpawnStrategy→com.google.devtools.build.lib.actions.SandboxedSpawnStrategycom.google.devtools.build.lib.exec.AbstractSpawnStrategy→com.google.devtools.build.lib.actions.Spawncom.google.devtools.build.lib.exec.AbstractSpawnStrategy→com.google.devtools.build.lib.actions.SpawnResultcom.google.devtools.build.lib.exec.AbstractSpawnStrategy→com.google.devtools.build.lib.actions.StopConcurrentSpawnscom.google.devtools.build.lib.exec.ActionContextInformation→com.google.devtools.build.lib.actions.ActionContextcom.google.devtools.build.lib.exec.ActionInputMetadata→com.google.devtools.build.lib.actions.ActionInputcom.google.devtools.build.lib.exec.ActionInputMetadata→com.google.devtools.build.lib.actions.FileArtifactValuecom.google.devtools.build.lib.exec.BinTools→com.google.devtools.build.lib.actions.ActionInputcom.google.devtools.build.lib.exec.BlazeExecutor→com.google.devtools.build.lib.actions.Executorcom.google.devtools.build.lib.exec.Builder→com.google.devtools.build.lib.actions.SpawnResultcom.google.devtools.build.lib.exec.CacheHandle→com.google.devtools.build.lib.actions.SpawnResultcom.google.devtools.build.lib.exec.CheckUpToDateFilter→com.google.devtools.build.lib.actions.Actioncom.google.devtools.build.lib.exec.CompactSpawnLogContext→com.google.devtools.build.lib.actions.AbstractActioncom.google.devtools.build.lib.exec.CompactSpawnLogContext→com.google.devtools.build.lib.actions.ActionInputcom.google.devtools.build.lib.exec.CompactSpawnLogContext→com.google.devtools.build.lib.actions.InputMetadataProvidercom.google.devtools.build.lib.exec.CompactSpawnLogContext→com.google.devtools.build.lib.actions.RunfilesTreecom.google.devtools.build.lib.exec.CompactSpawnLogContext→com.google.devtools.build.lib.actions.Spawncom.google.devtools.build.lib.exec.CompactSpawnLogContext→com.google.devtools.build.lib.actions.SpawnResult
- Direction
- com.google.devtools.build.lib.exec uses com.google.devtools.build.lib.actions, so a change to com.google.devtools.build.lib.actions can break com.google.devtools.build.lib.exec, while a change to com.google.devtools.build.lib.exec can't break com.google.devtools.build.lib.actions.
- 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→2 com.google.devtools.build.lib.query2.common uses com.google.devtools.build.lib.events✕
- Connections
- 4 pairs of types, where a type in com.google.devtools.build.lib.query2.common uses a type in com.google.devtools.build.lib.events.
- The types involved
com.google.devtools.build.lib.query2.common.AbstractBlazeQueryEnvironment→com.google.devtools.build.lib.events.ErrorSensingEventHandlercom.google.devtools.build.lib.query2.common.AbstractBlazeQueryEnvironment→com.google.devtools.build.lib.events.Eventcom.google.devtools.build.lib.query2.common.AbstractBlazeQueryEnvironment→com.google.devtools.build.lib.events.ExtendedEventHandlercom.google.devtools.build.lib.query2.common.QueryTransitivePackagePreloader→com.google.devtools.build.lib.events.ExtendedEventHandler
- Direction
- com.google.devtools.build.lib.query2.common uses com.google.devtools.build.lib.events, so a change to com.google.devtools.build.lib.events can break com.google.devtools.build.lib.query2.common, while a change to com.google.devtools.build.lib.query2.common can't break com.google.devtools.build.lib.events.
- Position
- Below the diagonal: com.google.devtools.build.lib.query2.common uses a module listed above it, which is the healthy direction.
16→3 com.google.devtools.build.lib.query2.common uses com.google.devtools.common.options✕
- Connections
- 2 pairs of types, where a type in com.google.devtools.build.lib.query2.common uses a type in com.google.devtools.common.options.
- The types involved
com.google.devtools.build.lib.query2.common.AspectResolutionModeConverter→com.google.devtools.common.options.EnumConvertercom.google.devtools.build.lib.query2.common.CommonQueryOptions→com.google.devtools.common.options.OptionsBase
- Direction
- com.google.devtools.build.lib.query2.common uses com.google.devtools.common.options, so a change to com.google.devtools.common.options can break com.google.devtools.build.lib.query2.common, while a change to com.google.devtools.build.lib.query2.common can't break com.google.devtools.common.options.
- Position
- Below the diagonal: com.google.devtools.build.lib.query2.common uses a module listed above it, which is the healthy direction.
16→4 com.google.devtools.build.lib.query2.common uses net.starlark.java.eval✕
- Connections
- 2 pairs of types, where a type in com.google.devtools.build.lib.query2.common uses a type in net.starlark.java.eval.
- The types involved
com.google.devtools.build.lib.query2.common.CommonQueryOptions→net.starlark.java.eval.StarlarkSemanticscom.google.devtools.build.lib.query2.common.CqueryNode→net.starlark.java.eval.Dict
- Direction
- com.google.devtools.build.lib.query2.common uses net.starlark.java.eval, so a change to net.starlark.java.eval can break com.google.devtools.build.lib.query2.common, while a change to com.google.devtools.build.lib.query2.common can't break net.starlark.java.eval.
- Position
- Below the diagonal: com.google.devtools.build.lib.query2.common uses a module listed above it, which is the healthy direction.
16→6 com.google.devtools.build.lib.query2.common uses com.google.devtools.build.skyframe✕
- Connections
- 6 pairs of types, where a type in com.google.devtools.build.lib.query2.common uses a type in com.google.devtools.build.skyframe.
- The types involved
com.google.devtools.build.lib.query2.common.QueryTransitivePackagePreloader→com.google.devtools.build.skyframe.Buildercom.google.devtools.build.lib.query2.common.QueryTransitivePackagePreloader→com.google.devtools.build.skyframe.EvaluationResultcom.google.devtools.build.lib.query2.common.QueryTransitivePackagePreloader→com.google.devtools.build.skyframe.MemoizingEvaluatorcom.google.devtools.build.lib.query2.common.QueryTransitivePackagePreloader→com.google.devtools.build.skyframe.SkyKeycom.google.devtools.build.lib.query2.common.QueryTransitivePackagePreloader→com.google.devtools.build.skyframe.SkyValuecom.google.devtools.build.lib.query2.common.UniverseSkyKey→com.google.devtools.build.skyframe.SkyKey
- Direction
- com.google.devtools.build.lib.query2.common uses com.google.devtools.build.skyframe, so a change to com.google.devtools.build.skyframe can break com.google.devtools.build.lib.query2.common, while a change to com.google.devtools.build.lib.query2.common can't break com.google.devtools.build.skyframe.
- Position
- Below the diagonal: com.google.devtools.build.lib.query2.common uses a module listed above it, which is the healthy direction.
16→8 com.google.devtools.build.lib.query2.common uses com.google.devtools.build.lib.vfs✕
- Connections
- 3 pairs of types, where a type in com.google.devtools.build.lib.query2.common uses a type in com.google.devtools.build.lib.vfs.
- The types involved
com.google.devtools.build.lib.query2.common.ConstantUniverseScope→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.query2.common.InferredUniverseScope→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.query2.common.UniverseScope→com.google.devtools.build.lib.vfs.PathFragment
- Direction
- com.google.devtools.build.lib.query2.common uses com.google.devtools.build.lib.vfs, so a change to com.google.devtools.build.lib.vfs can break com.google.devtools.build.lib.query2.common, while a change to com.google.devtools.build.lib.query2.common can't break com.google.devtools.build.lib.vfs.
- Position
- Below the diagonal: com.google.devtools.build.lib.query2.common uses a module listed above it, which is the healthy direction.
16→10 com.google.devtools.build.lib.query2.common uses com.google.devtools.build.lib.skyframe.config✕
- Connections
- 1 pair of types, where a type in com.google.devtools.build.lib.query2.common uses a type in com.google.devtools.build.lib.skyframe.config.
- The types involved
com.google.devtools.build.lib.query2.common.CqueryNode→com.google.devtools.build.lib.skyframe.config.BuildConfigurationKey
- Direction
- com.google.devtools.build.lib.query2.common uses com.google.devtools.build.lib.skyframe.config, so a change to com.google.devtools.build.lib.skyframe.config can break com.google.devtools.build.lib.query2.common, while a change to com.google.devtools.build.lib.query2.common can't break com.google.devtools.build.lib.skyframe.config.
- Position
- Below the diagonal: com.google.devtools.build.lib.query2.common uses a module listed above it, which is the healthy direction.
16→11 com.google.devtools.build.lib.query2.common uses com.google.devtools.build.lib.util✕
- Connections
- 1 pair of types, where a type in com.google.devtools.build.lib.query2.common uses a type in com.google.devtools.build.lib.util.
- The types involved
com.google.devtools.build.lib.query2.common.AbstractBlazeQueryEnvironment→com.google.devtools.build.lib.util.DetailedExitCode
- Direction
- com.google.devtools.build.lib.query2.common uses com.google.devtools.build.lib.util, so a change to com.google.devtools.build.lib.util can break com.google.devtools.build.lib.query2.common, while a change to com.google.devtools.build.lib.query2.common can't break com.google.devtools.build.lib.util.
- Position
- Below the diagonal: com.google.devtools.build.lib.query2.common uses a module listed above it, which is the healthy direction.
16→25 com.google.devtools.build.lib.query2.common uses com.google.devtools.build.lib.packages part of a loop✕
- Connections
- 7 pairs of types, where a type in com.google.devtools.build.lib.query2.common uses a type in com.google.devtools.build.lib.packages.
- The types involved
com.google.devtools.build.lib.query2.common.AbstractBlazeQueryEnvironment→com.google.devtools.build.lib.packages.DependencyFiltercom.google.devtools.build.lib.query2.common.AbstractBlazeQueryEnvironment→com.google.devtools.build.lib.packages.LabelPrintercom.google.devtools.build.lib.query2.common.AbstractBlazeQueryEnvironment→com.google.devtools.build.lib.packages.Targetcom.google.devtools.build.lib.query2.common.CommonQueryOptions→com.google.devtools.build.lib.packages.LabelPrintercom.google.devtools.build.lib.query2.common.CqueryNode→com.google.devtools.build.lib.packages.LabelPrintercom.google.devtools.build.lib.query2.common.TargetKeyExtractor→com.google.devtools.build.lib.packages.Targetcom.google.devtools.build.lib.query2.common.TransitiveLoadFilesHelperForTargets→com.google.devtools.build.lib.packages.Target
- Direction
- com.google.devtools.build.lib.query2.common uses com.google.devtools.build.lib.packages, so a change to com.google.devtools.build.lib.packages can break com.google.devtools.build.lib.query2.common, while a change to com.google.devtools.build.lib.query2.common can't break com.google.devtools.build.lib.packages.
- 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 com.google.devtools.build.lib.query2.common uses com.google.devtools.build.lib.cmdline part of a loop✕
- Connections
- 7 pairs of types, where a type in com.google.devtools.build.lib.query2.common uses a type in com.google.devtools.build.lib.cmdline.
- The types involved
com.google.devtools.build.lib.query2.common.AbstractBlazeQueryEnvironment→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.query2.common.AbstractBlazeQueryEnvironment→com.google.devtools.build.lib.cmdline.PackageIdentifiercom.google.devtools.build.lib.query2.common.CommonQueryOptions→com.google.devtools.build.lib.cmdline.RepositoryMappingcom.google.devtools.build.lib.query2.common.CqueryNode→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.query2.common.QueryTransitivePackagePreloader→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.query2.common.TargetKeyExtractor→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.query2.common.TransitiveLoadFilesHelperForTargets→com.google.devtools.build.lib.cmdline.PackageIdentifier
- Direction
- com.google.devtools.build.lib.query2.common uses com.google.devtools.build.lib.cmdline, so a change to com.google.devtools.build.lib.cmdline can break com.google.devtools.build.lib.query2.common, while a change to com.google.devtools.build.lib.query2.common can't break com.google.devtools.build.lib.cmdline.
- 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→33 com.google.devtools.build.lib.query2.common uses com.google.devtools.build.lib.analysis.config part of a loop✕
- Connections
- 1 pair of types, where a type in com.google.devtools.build.lib.query2.common uses a type in com.google.devtools.build.lib.analysis.config.
- The types involved
com.google.devtools.build.lib.query2.common.CqueryNode→com.google.devtools.build.lib.analysis.config.ConfigMatchingProvider
- Direction
- com.google.devtools.build.lib.query2.common uses com.google.devtools.build.lib.analysis.config, so a change to com.google.devtools.build.lib.analysis.config can break com.google.devtools.build.lib.query2.common, while a change to com.google.devtools.build.lib.query2.common can't break com.google.devtools.build.lib.analysis.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.
16→37 com.google.devtools.build.lib.query2.common uses com.google.devtools.build.lib.actions part of a loop✕
- Connections
- 1 pair of types, where a type in com.google.devtools.build.lib.query2.common uses a type in com.google.devtools.build.lib.actions.
- The types involved
com.google.devtools.build.lib.query2.common.CqueryNode→com.google.devtools.build.lib.actions.ActionLookupKey
- Direction
- com.google.devtools.build.lib.query2.common uses com.google.devtools.build.lib.actions, so a change to com.google.devtools.build.lib.actions can break com.google.devtools.build.lib.query2.common, while a change to com.google.devtools.build.lib.query2.common can't break com.google.devtools.build.lib.actions.
- 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→5 proguard.classfile.attribute.visitor uses proguard.classfile.visitor✕
- Connections
- 3 pairs of types, where a type in proguard.classfile.attribute.visitor uses a type in proguard.classfile.visitor.
- The types involved
proguard.classfile.attribute.visitor.AllAttributeVisitor→proguard.classfile.visitor.ClassVisitorproguard.classfile.attribute.visitor.AllAttributeVisitor→proguard.classfile.visitor.MemberVisitorproguard.classfile.attribute.visitor.AttributeToClassVisitor→proguard.classfile.visitor.ClassVisitor
- Direction
- proguard.classfile.attribute.visitor uses proguard.classfile.visitor, so a change to proguard.classfile.visitor can break proguard.classfile.attribute.visitor, while a change to proguard.classfile.attribute.visitor can't break proguard.classfile.visitor.
- Position
- Below the diagonal: proguard.classfile.attribute.visitor uses a module listed above it, which is the healthy direction.
17→12 proguard.classfile.attribute.visitor uses proguard.classfile.util✕
- Connections
- 9 pairs of types, where a type in proguard.classfile.attribute.visitor uses a type in proguard.classfile.util.
- The types involved
proguard.classfile.attribute.visitor.AllAttributeVisitor→proguard.classfile.util.SimplifiedVisitorproguard.classfile.attribute.visitor.AllBootstrapMethodInfoVisitor→proguard.classfile.util.SimplifiedVisitorproguard.classfile.attribute.visitor.AllExceptionInfoVisitor→proguard.classfile.util.SimplifiedVisitorproguard.classfile.attribute.visitor.AllInnerClassesInfoVisitor→proguard.classfile.util.SimplifiedVisitorproguard.classfile.attribute.visitor.AllLineNumberInfoVisitor→proguard.classfile.util.SimplifiedVisitorproguard.classfile.attribute.visitor.AttributeCounter→proguard.classfile.util.SimplifiedVisitorproguard.classfile.attribute.visitor.AttributeToClassVisitor→proguard.classfile.util.SimplifiedVisitorproguard.classfile.attribute.visitor.InstructionToAttributeVisitor→proguard.classfile.util.SimplifiedVisitorproguard.classfile.attribute.visitor.StackSizeComputer→proguard.classfile.util.SimplifiedVisitor
- Direction
- proguard.classfile.attribute.visitor uses proguard.classfile.util, so a change to proguard.classfile.util can break proguard.classfile.attribute.visitor, while a change to proguard.classfile.attribute.visitor can't break proguard.classfile.util.
- Position
- Below the diagonal: proguard.classfile.attribute.visitor uses a module listed above it, which is the healthy direction.
17→20 proguard.classfile.attribute.visitor uses proguard.classfile.attribute part of a loop✕
- Connections
- 159 pairs of types, where a type in proguard.classfile.attribute.visitor uses a type in proguard.classfile.attribute. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
proguard.classfile.attribute.visitor.AllAttributeVisitor→proguard.classfile.attribute.Attributeproguard.classfile.attribute.visitor.AllAttributeVisitor→proguard.classfile.attribute.CodeAttributeproguard.classfile.attribute.visitor.AllBootstrapMethodInfoVisitor→proguard.classfile.attribute.Attributeproguard.classfile.attribute.visitor.AllBootstrapMethodInfoVisitor→proguard.classfile.attribute.BootstrapMethodsAttributeproguard.classfile.attribute.visitor.AllExceptionInfoVisitor→proguard.classfile.attribute.Attributeproguard.classfile.attribute.visitor.AllExceptionInfoVisitor→proguard.classfile.attribute.CodeAttributeproguard.classfile.attribute.visitor.AllInnerClassesInfoVisitor→proguard.classfile.attribute.Attributeproguard.classfile.attribute.visitor.AllInnerClassesInfoVisitor→proguard.classfile.attribute.InnerClassesAttributeproguard.classfile.attribute.visitor.AllLineNumberInfoVisitor→proguard.classfile.attribute.Attributeproguard.classfile.attribute.visitor.AllLineNumberInfoVisitor→proguard.classfile.attribute.CodeAttributeproguard.classfile.attribute.visitor.AllLineNumberInfoVisitor→proguard.classfile.attribute.LineNumberTableAttributeproguard.classfile.attribute.visitor.AttributeCounter→proguard.classfile.attribute.Attributeproguard.classfile.attribute.visitor.AttributeNameFilter→proguard.classfile.attribute.Attributeproguard.classfile.attribute.visitor.AttributeNameFilter→proguard.classfile.attribute.BootstrapMethodsAttributeproguard.classfile.attribute.visitor.AttributeNameFilter→proguard.classfile.attribute.CodeAttributeproguard.classfile.attribute.visitor.AttributeNameFilter→proguard.classfile.attribute.ConstantValueAttributeproguard.classfile.attribute.visitor.AttributeNameFilter→proguard.classfile.attribute.DeprecatedAttributeproguard.classfile.attribute.visitor.AttributeNameFilter→proguard.classfile.attribute.EnclosingMethodAttributeproguard.classfile.attribute.visitor.AttributeNameFilter→proguard.classfile.attribute.ExceptionsAttributeproguard.classfile.attribute.visitor.AttributeNameFilter→proguard.classfile.attribute.InnerClassesAttributeproguard.classfile.attribute.visitor.AttributeNameFilter→proguard.classfile.attribute.LineNumberTableAttributeproguard.classfile.attribute.visitor.AttributeNameFilter→proguard.classfile.attribute.LocalVariableTableAttributeproguard.classfile.attribute.visitor.AttributeNameFilter→proguard.classfile.attribute.LocalVariableTypeTableAttributeproguard.classfile.attribute.visitor.AttributeNameFilter→proguard.classfile.attribute.MethodParametersAttributeproguard.classfile.attribute.visitor.AttributeNameFilter→proguard.classfile.attribute.NestHostAttribute
- Direction
- proguard.classfile.attribute.visitor uses proguard.classfile.attribute, so a change to proguard.classfile.attribute can break proguard.classfile.attribute.visitor, while a change to proguard.classfile.attribute.visitor can't break proguard.classfile.attribute.
- 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→22 proguard.classfile.attribute.visitor uses proguard.classfile part of a loop✕
- Connections
- 54 pairs of types, where a type in proguard.classfile.attribute.visitor uses a type in proguard.classfile. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
proguard.classfile.attribute.visitor.AllAttributeVisitor→proguard.classfile.Clazzproguard.classfile.attribute.visitor.AllAttributeVisitor→proguard.classfile.LibraryClassproguard.classfile.attribute.visitor.AllAttributeVisitor→proguard.classfile.LibraryMemberproguard.classfile.attribute.visitor.AllAttributeVisitor→proguard.classfile.Methodproguard.classfile.attribute.visitor.AllAttributeVisitor→proguard.classfile.ProgramClassproguard.classfile.attribute.visitor.AllAttributeVisitor→proguard.classfile.ProgramMemberproguard.classfile.attribute.visitor.AllBootstrapMethodInfoVisitor→proguard.classfile.Clazzproguard.classfile.attribute.visitor.AllExceptionInfoVisitor→proguard.classfile.Clazzproguard.classfile.attribute.visitor.AllExceptionInfoVisitor→proguard.classfile.Methodproguard.classfile.attribute.visitor.AllInnerClassesInfoVisitor→proguard.classfile.Clazzproguard.classfile.attribute.visitor.AllLineNumberInfoVisitor→proguard.classfile.Clazzproguard.classfile.attribute.visitor.AllLineNumberInfoVisitor→proguard.classfile.Methodproguard.classfile.attribute.visitor.AttributeCounter→proguard.classfile.Clazzproguard.classfile.attribute.visitor.AttributeNameFilter→proguard.classfile.Clazzproguard.classfile.attribute.visitor.AttributeNameFilter→proguard.classfile.Fieldproguard.classfile.attribute.visitor.AttributeNameFilter→proguard.classfile.Methodproguard.classfile.attribute.visitor.AttributeToClassVisitor→proguard.classfile.Clazzproguard.classfile.attribute.visitor.AttributeVisitor→proguard.classfile.Clazzproguard.classfile.attribute.visitor.AttributeVisitor→proguard.classfile.Fieldproguard.classfile.attribute.visitor.AttributeVisitor→proguard.classfile.Methodproguard.classfile.attribute.visitor.BootstrapMethodInfoVisitor→proguard.classfile.Clazzproguard.classfile.attribute.visitor.DebugAttributeVisitor→proguard.classfile.Clazzproguard.classfile.attribute.visitor.DebugAttributeVisitor→proguard.classfile.Fieldproguard.classfile.attribute.visitor.DebugAttributeVisitor→proguard.classfile.LibraryClassproguard.classfile.attribute.visitor.DebugAttributeVisitor→proguard.classfile.Method
- Direction
- proguard.classfile.attribute.visitor uses proguard.classfile, so a change to proguard.classfile can break proguard.classfile.attribute.visitor, while a change to proguard.classfile.attribute.visitor can't break proguard.classfile.
- 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.
18→2 com.google.devtools.build.lib.pkgcache uses com.google.devtools.build.lib.events✕
- Connections
- 12 pairs of types, where a type in com.google.devtools.build.lib.pkgcache uses a type in com.google.devtools.build.lib.events.
- The types involved
com.google.devtools.build.lib.pkgcache.AbstractRecursivePackageProvider→com.google.devtools.build.lib.events.ExtendedEventHandlercom.google.devtools.build.lib.pkgcache.CompileOneDependencyTransformer→com.google.devtools.build.lib.events.ExtendedEventHandlercom.google.devtools.build.lib.pkgcache.LoadedPackage→com.google.devtools.build.lib.events.Eventcom.google.devtools.build.lib.pkgcache.LoadedPackageProvider→com.google.devtools.build.lib.events.ExtendedEventHandlercom.google.devtools.build.lib.pkgcache.LoadingPhaseCompleteEvent→com.google.devtools.build.lib.events.Postablecom.google.devtools.build.lib.pkgcache.PackageBackedRecursivePackageProvider→com.google.devtools.build.lib.events.ExtendedEventHandlercom.google.devtools.build.lib.pkgcache.PackageProvider→com.google.devtools.build.lib.events.ExtendedEventHandlercom.google.devtools.build.lib.pkgcache.ParsingFailedEvent→com.google.devtools.build.lib.events.Postablecom.google.devtools.build.lib.pkgcache.PathPackageLocator→com.google.devtools.build.lib.events.EventHandlercom.google.devtools.build.lib.pkgcache.RecursivePackageProvider→com.google.devtools.build.lib.events.ExtendedEventHandlercom.google.devtools.build.lib.pkgcache.TargetPatternPreloader→com.google.devtools.build.lib.events.ExtendedEventHandlercom.google.devtools.build.lib.pkgcache.TargetProvider→com.google.devtools.build.lib.events.ExtendedEventHandler
- Direction
- com.google.devtools.build.lib.pkgcache uses com.google.devtools.build.lib.events, so a change to com.google.devtools.build.lib.events can break com.google.devtools.build.lib.pkgcache, while a change to com.google.devtools.build.lib.pkgcache can't break com.google.devtools.build.lib.events.
- Position
- Below the diagonal: com.google.devtools.build.lib.pkgcache uses a module listed above it, which is the healthy direction.
18→3 com.google.devtools.build.lib.pkgcache uses com.google.devtools.common.options✕
- Connections
- 6 pairs of types, where a type in com.google.devtools.build.lib.pkgcache uses a type in com.google.devtools.common.options.
- The types involved
com.google.devtools.build.lib.pkgcache.CommaSeparatedPackageNameListConverter→com.google.devtools.common.options.Contextlesscom.google.devtools.build.lib.pkgcache.DefaultVisibilityConverter→com.google.devtools.common.options.Contextlesscom.google.devtools.build.lib.pkgcache.LoadingOptions→com.google.devtools.common.options.OptionsBasecom.google.devtools.build.lib.pkgcache.OptionConverter→com.google.devtools.common.options.Contextlesscom.google.devtools.build.lib.pkgcache.PackageOptions→com.google.devtools.common.options.OptionsBasecom.google.devtools.build.lib.pkgcache.PathPackageLocator→com.google.devtools.common.options.OptionsProvider
- Direction
- com.google.devtools.build.lib.pkgcache uses com.google.devtools.common.options, so a change to com.google.devtools.common.options can break com.google.devtools.build.lib.pkgcache, while a change to com.google.devtools.build.lib.pkgcache can't break com.google.devtools.common.options.
- Position
- Below the diagonal: com.google.devtools.build.lib.pkgcache uses a module listed above it, which is the healthy direction.
18→8 com.google.devtools.build.lib.pkgcache uses com.google.devtools.build.lib.vfs✕
- Connections
- 8 pairs of types, where a type in com.google.devtools.build.lib.pkgcache uses a type in com.google.devtools.build.lib.vfs.
- The types involved
com.google.devtools.build.lib.pkgcache.PackageBackedRecursivePackageProvider→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.pkgcache.PackagePathCodecDependencies→com.google.devtools.build.lib.vfs.Rootcom.google.devtools.build.lib.pkgcache.PathPackageLocator→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.pkgcache.PathPackageLocator→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.pkgcache.PathPackageLocator→com.google.devtools.build.lib.vfs.Rootcom.google.devtools.build.lib.pkgcache.PathPackageLocator→com.google.devtools.build.lib.vfs.SyscallCachecom.google.devtools.build.lib.pkgcache.RecursivePackageProvider→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.pkgcache.TargetPatternResolverUtil→com.google.devtools.build.lib.vfs.PathFragment
- Direction
- com.google.devtools.build.lib.pkgcache uses com.google.devtools.build.lib.vfs, so a change to com.google.devtools.build.lib.vfs can break com.google.devtools.build.lib.pkgcache, while a change to com.google.devtools.build.lib.pkgcache can't break com.google.devtools.build.lib.vfs.
- Position
- Below the diagonal: com.google.devtools.build.lib.pkgcache uses a module listed above it, which is the healthy direction.
18→11 com.google.devtools.build.lib.pkgcache uses com.google.devtools.build.lib.util✕
- Connections
- 3 pairs of types, where a type in com.google.devtools.build.lib.pkgcache uses a type in com.google.devtools.build.lib.util.
- The types involved
com.google.devtools.build.lib.pkgcache.CompileOneDependencyTransformer→com.google.devtools.build.lib.util.FileTypecom.google.devtools.build.lib.pkgcache.LoadingFailedException→com.google.devtools.build.lib.util.DetailedExitCodecom.google.devtools.build.lib.pkgcache.ParallelismConverter→com.google.devtools.build.lib.util.IntegerConverter
- Direction
- com.google.devtools.build.lib.pkgcache uses com.google.devtools.build.lib.util, so a change to com.google.devtools.build.lib.util can break com.google.devtools.build.lib.pkgcache, while a change to com.google.devtools.build.lib.pkgcache can't break com.google.devtools.build.lib.util.
- Position
- Below the diagonal: com.google.devtools.build.lib.pkgcache uses a module listed above it, which is the healthy direction.
18→14 com.google.devtools.build.lib.pkgcache uses com.google.devtools.build.lib.buildeventstream✕
- Connections
- 2 pairs of types, where a type in com.google.devtools.build.lib.pkgcache uses a type in com.google.devtools.build.lib.buildeventstream.
- The types involved
com.google.devtools.build.lib.pkgcache.TargetParsingCompleteEvent→com.google.devtools.build.lib.buildeventstream.BuildEventContextcom.google.devtools.build.lib.pkgcache.TargetParsingCompleteEvent→com.google.devtools.build.lib.buildeventstream.BuildEventWithOrderConstraint
- Direction
- com.google.devtools.build.lib.pkgcache uses com.google.devtools.build.lib.buildeventstream, so a change to com.google.devtools.build.lib.buildeventstream can break com.google.devtools.build.lib.pkgcache, while a change to com.google.devtools.build.lib.pkgcache can't break com.google.devtools.build.lib.buildeventstream.
- Position
- Below the diagonal: com.google.devtools.build.lib.pkgcache uses a module listed above it, which is the healthy direction.
18→24 com.google.devtools.build.lib.pkgcache uses com.google.devtools.build.lib.skyframe part of a loop✕
- Connections
- 1 pair of types, where a type in com.google.devtools.build.lib.pkgcache uses a type in com.google.devtools.build.lib.skyframe.
- The types involved
com.google.devtools.build.lib.pkgcache.LoadingFailedException→com.google.devtools.build.lib.skyframe.DetailedException
- Direction
- com.google.devtools.build.lib.pkgcache uses com.google.devtools.build.lib.skyframe, so a change to com.google.devtools.build.lib.skyframe can break com.google.devtools.build.lib.pkgcache, while a change to com.google.devtools.build.lib.pkgcache can't break com.google.devtools.build.lib.skyframe.
- 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.
18→25 com.google.devtools.build.lib.pkgcache uses com.google.devtools.build.lib.packages part of a loop✕
- Connections
- 33 pairs of types, where a type in com.google.devtools.build.lib.pkgcache uses a type in com.google.devtools.build.lib.packages. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.google.devtools.build.lib.pkgcache.AbstractRecursivePackageProvider→com.google.devtools.build.lib.packages.Targetcom.google.devtools.build.lib.pkgcache.AndFilteringPolicy→com.google.devtools.build.lib.packages.Targetcom.google.devtools.build.lib.pkgcache.CompileOneDependencyTransformer→com.google.devtools.build.lib.packages.Rulecom.google.devtools.build.lib.pkgcache.CompileOneDependencyTransformer→com.google.devtools.build.lib.packages.Targetcom.google.devtools.build.lib.pkgcache.DefaultVisibilityConverter→com.google.devtools.build.lib.packages.RuleVisibilitycom.google.devtools.build.lib.pkgcache.FilterManual→com.google.devtools.build.lib.packages.Targetcom.google.devtools.build.lib.pkgcache.FilterTests→com.google.devtools.build.lib.packages.Targetcom.google.devtools.build.lib.pkgcache.FilteringPolicy→com.google.devtools.build.lib.packages.Targetcom.google.devtools.build.lib.pkgcache.LoadedPackageProvider→com.google.devtools.build.lib.packages.Targetcom.google.devtools.build.lib.pkgcache.LoadingOptions→com.google.devtools.build.lib.packages.TestSizecom.google.devtools.build.lib.pkgcache.LoadingOptions→com.google.devtools.build.lib.packages.TestTimeoutcom.google.devtools.build.lib.pkgcache.NoFilter→com.google.devtools.build.lib.packages.Targetcom.google.devtools.build.lib.pkgcache.PackageBackedRecursivePackageProvider→com.google.devtools.build.lib.packages.InputFilecom.google.devtools.build.lib.pkgcache.PackageBackedRecursivePackageProvider→com.google.devtools.build.lib.packages.Targetcom.google.devtools.build.lib.pkgcache.PackageManager→com.google.devtools.build.lib.packages.CachingPackageLocatorcom.google.devtools.build.lib.pkgcache.PackageOptions→com.google.devtools.build.lib.packages.RuleVisibilitycom.google.devtools.build.lib.pkgcache.PackageProvider→com.google.devtools.build.lib.packages.InputFilecom.google.devtools.build.lib.pkgcache.PackageProvider→com.google.devtools.build.lib.packages.Targetcom.google.devtools.build.lib.pkgcache.PathPackageLocator→com.google.devtools.build.lib.packages.BuildFileNamecom.google.devtools.build.lib.pkgcache.RuleTypeFilter→com.google.devtools.build.lib.packages.Targetcom.google.devtools.build.lib.pkgcache.RulesOnly→com.google.devtools.build.lib.packages.Targetcom.google.devtools.build.lib.pkgcache.TargetEdgeObserver→com.google.devtools.build.lib.packages.Attributecom.google.devtools.build.lib.pkgcache.TargetEdgeObserver→com.google.devtools.build.lib.packages.NoSuchThingExceptioncom.google.devtools.build.lib.pkgcache.TargetEdgeObserver→com.google.devtools.build.lib.packages.Targetcom.google.devtools.build.lib.pkgcache.TargetParsingCompleteEvent→com.google.devtools.build.lib.packages.Target
- Direction
- com.google.devtools.build.lib.pkgcache uses com.google.devtools.build.lib.packages, so a change to com.google.devtools.build.lib.packages can break com.google.devtools.build.lib.pkgcache, while a change to com.google.devtools.build.lib.pkgcache can't break com.google.devtools.build.lib.packages.
- 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.
18→31 com.google.devtools.build.lib.pkgcache uses com.google.devtools.build.lib.cmdline part of a loop✕
- Connections
- 26 pairs of types, where a type in com.google.devtools.build.lib.pkgcache uses a type in com.google.devtools.build.lib.cmdline. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.google.devtools.build.lib.pkgcache.1→com.google.devtools.build.lib.cmdline.PackageIdentifiercom.google.devtools.build.lib.pkgcache.AbstractRecursivePackageProvider→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.pkgcache.CommaSeparatedPackageNameListConverter→com.google.devtools.build.lib.cmdline.PackageIdentifiercom.google.devtools.build.lib.pkgcache.CompileOneDependencyTransformer→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.pkgcache.CompileOneDependencyTransformer→com.google.devtools.build.lib.cmdline.ResolvedTargetscom.google.devtools.build.lib.pkgcache.LazyMacroExpansionPackages→com.google.devtools.build.lib.cmdline.PackageIdentifiercom.google.devtools.build.lib.pkgcache.LazyMacroExpansionPackagesSet→com.google.devtools.build.lib.cmdline.PackageIdentifiercom.google.devtools.build.lib.pkgcache.LoadedPackageProvider→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.pkgcache.LoadingFailureEvent→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.pkgcache.LoadingPhaseCompleteEvent→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.pkgcache.LoadingPhaseCompleteEvent→com.google.devtools.build.lib.cmdline.RepositoryMappingcom.google.devtools.build.lib.pkgcache.PackageBackedRecursivePackageProvider→com.google.devtools.build.lib.cmdline.IgnoredSubdirectoriescom.google.devtools.build.lib.pkgcache.PackageBackedRecursivePackageProvider→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.pkgcache.PackageBackedRecursivePackageProvider→com.google.devtools.build.lib.cmdline.PackageIdentifiercom.google.devtools.build.lib.pkgcache.PackageBackedRecursivePackageProvider→com.google.devtools.build.lib.cmdline.RepositoryNamecom.google.devtools.build.lib.pkgcache.PackageOptions→com.google.devtools.build.lib.cmdline.PackageIdentifiercom.google.devtools.build.lib.pkgcache.PackageProvider→com.google.devtools.build.lib.cmdline.PackageIdentifiercom.google.devtools.build.lib.pkgcache.PathPackageLocator→com.google.devtools.build.lib.cmdline.PackageIdentifiercom.google.devtools.build.lib.pkgcache.RecursivePackageProvider→com.google.devtools.build.lib.cmdline.IgnoredSubdirectoriescom.google.devtools.build.lib.pkgcache.RecursivePackageProvider→com.google.devtools.build.lib.cmdline.PackageIdentifiercom.google.devtools.build.lib.pkgcache.RecursivePackageProvider→com.google.devtools.build.lib.cmdline.RepositoryNamecom.google.devtools.build.lib.pkgcache.TargetEdgeObserver→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.pkgcache.TargetParsingCompleteEvent→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.pkgcache.TargetPatternPreloader→com.google.devtools.build.lib.cmdline.Parsercom.google.devtools.build.lib.pkgcache.TargetProvider→com.google.devtools.build.lib.cmdline.Label
- Direction
- com.google.devtools.build.lib.pkgcache uses com.google.devtools.build.lib.cmdline, so a change to com.google.devtools.build.lib.cmdline can break com.google.devtools.build.lib.pkgcache, while a change to com.google.devtools.build.lib.pkgcache can't break com.google.devtools.build.lib.cmdline.
- 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.
18→35 com.google.devtools.build.lib.pkgcache uses com.google.devtools.build.lib.analysis part of a loop✕
- Connections
- 1 pair of types, where a type in com.google.devtools.build.lib.pkgcache uses a type in com.google.devtools.build.lib.analysis.
- The types involved
com.google.devtools.build.lib.pkgcache.PathPackageLocator→com.google.devtools.build.lib.analysis.BlazeDirectories
- Direction
- com.google.devtools.build.lib.pkgcache uses com.google.devtools.build.lib.analysis, so a change to com.google.devtools.build.lib.analysis can break com.google.devtools.build.lib.pkgcache, while a change to com.google.devtools.build.lib.pkgcache can't break com.google.devtools.build.lib.analysis.
- 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.
19→2 com.google.devtools.build.lib.skyframe.serialization.analysis uses com.google.devtools.build.lib.events✕
- Connections
- 5 pairs of types, where a type in com.google.devtools.build.lib.skyframe.serialization.analysis uses a type in com.google.devtools.build.lib.events.
- The types involved
com.google.devtools.build.lib.skyframe.serialization.analysis.AnalysisCacheInvalidator→com.google.devtools.build.lib.events.ExtendedEventHandlercom.google.devtools.build.lib.skyframe.serialization.analysis.FrontierSerializer→com.google.devtools.build.lib.events.Reportercom.google.devtools.build.lib.skyframe.serialization.analysis.RemoteAnalysisCacheDeps→com.google.devtools.build.lib.events.ExtendedEventHandlercom.google.devtools.build.lib.skyframe.serialization.analysis.RemoteAnalysisCacheFactory→com.google.devtools.build.lib.events.ExtendedEventHandlercom.google.devtools.build.lib.skyframe.serialization.analysis.RemoteAnalysisCacheManager→com.google.devtools.build.lib.events.ExtendedEventHandler
- Direction
- com.google.devtools.build.lib.skyframe.serialization.analysis uses com.google.devtools.build.lib.events, so a change to com.google.devtools.build.lib.events can break com.google.devtools.build.lib.skyframe.serialization.analysis, while a change to com.google.devtools.build.lib.skyframe.serialization.analysis can't break com.google.devtools.build.lib.events.
- Position
- Below the diagonal: com.google.devtools.build.lib.skyframe.serialization.analysis uses a module listed above it, which is the healthy direction.
19→3 com.google.devtools.build.lib.skyframe.serialization.analysis uses com.google.devtools.common.options✕
- Connections
- 6 pairs of types, where a type in com.google.devtools.build.lib.skyframe.serialization.analysis uses a type in com.google.devtools.common.options.
- The types involved
com.google.devtools.build.lib.skyframe.serialization.analysis.Md5Converter→com.google.devtools.common.options.Convertercom.google.devtools.build.lib.skyframe.serialization.analysis.RemoteAnalysisCacheModeConverter→com.google.devtools.common.options.Contextlesscom.google.devtools.build.lib.skyframe.serialization.analysis.RemoteAnalysisCacheStorageTypeConverter→com.google.devtools.common.options.EnumConvertercom.google.devtools.build.lib.skyframe.serialization.analysis.RemoteAnalysisCachingOptions→com.google.devtools.common.options.OptionsBasecom.google.devtools.build.lib.skyframe.serialization.analysis.RemoteAnalysisCachingServicesOptions→com.google.devtools.common.options.OptionsBasecom.google.devtools.build.lib.skyframe.serialization.analysis.RemoteAnalysisCachingServicesSupplier→com.google.devtools.common.options.OptionsProvider
- Direction
- com.google.devtools.build.lib.skyframe.serialization.analysis uses com.google.devtools.common.options, so a change to com.google.devtools.common.options can break com.google.devtools.build.lib.skyframe.serialization.analysis, while a change to com.google.devtools.build.lib.skyframe.serialization.analysis can't break com.google.devtools.common.options.
- Position
- Below the diagonal: com.google.devtools.build.lib.skyframe.serialization.analysis uses a module listed above it, which is the healthy direction.
19→6 com.google.devtools.build.lib.skyframe.serialization.analysis uses com.google.devtools.build.skyframe✕
- Connections
- 42 pairs of types, where a type in com.google.devtools.build.lib.skyframe.serialization.analysis uses a type in com.google.devtools.build.skyframe. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.google.devtools.build.lib.skyframe.serialization.analysis.AnalysisCacheInvalidator→com.google.devtools.build.skyframe.SkyKeycom.google.devtools.build.lib.skyframe.serialization.analysis.AnalysisValueWithMtsv→com.google.devtools.build.skyframe.SkyValuecom.google.devtools.build.lib.skyframe.serialization.analysis.AnalysisValueWithMtsv→com.google.devtools.build.skyframe.Versioncom.google.devtools.build.lib.skyframe.serialization.analysis.DenseLeafIdsAndUploadOrder→com.google.devtools.build.skyframe.SkyKeycom.google.devtools.build.lib.skyframe.serialization.analysis.FileDependencySerializer→com.google.devtools.build.skyframe.InMemoryGraphcom.google.devtools.build.lib.skyframe.serialization.analysis.FileOpNodeCollector→com.google.devtools.build.skyframe.SkyKeycom.google.devtools.build.lib.skyframe.serialization.analysis.FileOpNodeMap→com.google.devtools.build.skyframe.SkyKeycom.google.devtools.build.lib.skyframe.serialization.analysis.FileOpNodeMap→com.google.devtools.build.skyframe.SkyValuecom.google.devtools.build.lib.skyframe.serialization.analysis.FileOpNodeMemoizingLookup→com.google.devtools.build.skyframe.InMemoryGraphcom.google.devtools.build.lib.skyframe.serialization.analysis.FileOpNodeMemoizingLookup→com.google.devtools.build.skyframe.SkyKeycom.google.devtools.build.lib.skyframe.serialization.analysis.FileOpNodeMemoizingLookup→com.google.devtools.build.skyframe.SkyValuecom.google.devtools.build.lib.skyframe.serialization.analysis.FrontierSerializer→com.google.devtools.build.skyframe.InMemoryGraphcom.google.devtools.build.lib.skyframe.serialization.analysis.FrontierSerializer→com.google.devtools.build.skyframe.InMemoryNodeEntrycom.google.devtools.build.lib.skyframe.serialization.analysis.FrontierSerializer→com.google.devtools.build.skyframe.MemoizingEvaluatorcom.google.devtools.build.lib.skyframe.serialization.analysis.FrontierSerializer→com.google.devtools.build.skyframe.SkyKeycom.google.devtools.build.lib.skyframe.serialization.analysis.FunctionAndPhase→com.google.devtools.build.skyframe.SkyFunctionNamecom.google.devtools.build.lib.skyframe.serialization.analysis.GraphDumper→com.google.devtools.build.skyframe.InMemoryGraphcom.google.devtools.build.lib.skyframe.serialization.analysis.LookupQuiescence→com.google.devtools.build.skyframe.SkyKeycom.google.devtools.build.lib.skyframe.serialization.analysis.MissingSkyframeEntryException→com.google.devtools.build.skyframe.SkyKeycom.google.devtools.build.lib.skyframe.serialization.analysis.RemoteAnalysisCacheDeps→com.google.devtools.build.skyframe.InMemoryGraphcom.google.devtools.build.lib.skyframe.serialization.analysis.RemoteAnalysisCacheDeps→com.google.devtools.build.skyframe.SkyKeycom.google.devtools.build.lib.skyframe.serialization.analysis.RemoteAnalysisCacheManager→com.google.devtools.build.skyframe.InMemoryGraphcom.google.devtools.build.lib.skyframe.serialization.analysis.RemoteAnalysisCacheManager→com.google.devtools.build.skyframe.SkyKeycom.google.devtools.build.lib.skyframe.serialization.analysis.RemoteAnalysisCacheReaderDepsProvider→com.google.devtools.build.skyframe.SkyKeycom.google.devtools.build.lib.skyframe.serialization.analysis.RemoteAnalysisCachingDependenciesProvider→com.google.devtools.build.skyframe.InMemoryGraph
- Direction
- com.google.devtools.build.lib.skyframe.serialization.analysis uses com.google.devtools.build.skyframe, so a change to com.google.devtools.build.skyframe can break com.google.devtools.build.lib.skyframe.serialization.analysis, while a change to com.google.devtools.build.lib.skyframe.serialization.analysis can't break com.google.devtools.build.skyframe.
- Position
- Below the diagonal: com.google.devtools.build.lib.skyframe.serialization.analysis uses a module listed above it, which is the healthy direction.
19→8 com.google.devtools.build.lib.skyframe.serialization.analysis uses com.google.devtools.build.lib.vfs✕
- Connections
- 10 pairs of types, where a type in com.google.devtools.build.lib.skyframe.serialization.analysis uses a type in com.google.devtools.build.lib.vfs.
- The types involved
com.google.devtools.build.lib.skyframe.serialization.analysis.FileDependencyDeserializer→com.google.devtools.build.lib.vfs.OsPathPolicycom.google.devtools.build.lib.skyframe.serialization.analysis.FileDependencySerializer→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.skyframe.serialization.analysis.FileDependencySerializer→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.skyframe.serialization.analysis.FileDependencySerializer→com.google.devtools.build.lib.vfs.RootedPathcom.google.devtools.build.lib.skyframe.serialization.analysis.FileInvalidationDataInfo→com.google.devtools.build.lib.vfs.RootedPathcom.google.devtools.build.lib.skyframe.serialization.analysis.FileInvalidationDataUploader→com.google.devtools.build.lib.vfs.RootedPathcom.google.devtools.build.lib.skyframe.serialization.analysis.ListingFileHandler→com.google.devtools.build.lib.vfs.RootedPathcom.google.devtools.build.lib.skyframe.serialization.analysis.PathResolver→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.skyframe.serialization.analysis.SymlinkParentProcessor→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.skyframe.serialization.analysis.SymlinkParentProcessor→com.google.devtools.build.lib.vfs.RootedPath
- Direction
- com.google.devtools.build.lib.skyframe.serialization.analysis uses com.google.devtools.build.lib.vfs, so a change to com.google.devtools.build.lib.vfs can break com.google.devtools.build.lib.skyframe.serialization.analysis, while a change to com.google.devtools.build.lib.skyframe.serialization.analysis can't break com.google.devtools.build.lib.vfs.
- Position
- Below the diagonal: com.google.devtools.build.lib.skyframe.serialization.analysis uses a module listed above it, which is the healthy direction.
19→11 com.google.devtools.build.lib.skyframe.serialization.analysis uses com.google.devtools.build.lib.util✕
- Connections
- 2 pairs of types, where a type in com.google.devtools.build.lib.skyframe.serialization.analysis uses a type in com.google.devtools.build.lib.util.
- The types involved
com.google.devtools.build.lib.skyframe.serialization.analysis.RemoteAnalysisCachingEventListener→com.google.devtools.build.lib.util.DecimalBucketercom.google.devtools.build.lib.skyframe.serialization.analysis.Stats→com.google.devtools.build.lib.util.Bucket
- Direction
- com.google.devtools.build.lib.skyframe.serialization.analysis uses com.google.devtools.build.lib.util, so a change to com.google.devtools.build.lib.util can break com.google.devtools.build.lib.skyframe.serialization.analysis, while a change to com.google.devtools.build.lib.skyframe.serialization.analysis can't break com.google.devtools.build.lib.util.
- Position
- Below the diagonal: com.google.devtools.build.lib.skyframe.serialization.analysis uses a module listed above it, which is the healthy direction.
19→14 com.google.devtools.build.lib.skyframe.serialization.analysis uses com.google.devtools.build.lib.buildeventstream✕
- Connections
- 2 pairs of types, where a type in com.google.devtools.build.lib.skyframe.serialization.analysis uses a type in com.google.devtools.build.lib.buildeventstream.
- The types involved
com.google.devtools.build.lib.skyframe.serialization.analysis.SkyValueUploadedEvent→com.google.devtools.build.lib.buildeventstream.BuildEventcom.google.devtools.build.lib.skyframe.serialization.analysis.SkyValueUploadedEvent→com.google.devtools.build.lib.buildeventstream.BuildEventContext
- Direction
- com.google.devtools.build.lib.skyframe.serialization.analysis uses com.google.devtools.build.lib.buildeventstream, so a change to com.google.devtools.build.lib.buildeventstream can break com.google.devtools.build.lib.skyframe.serialization.analysis, while a change to com.google.devtools.build.lib.skyframe.serialization.analysis can't break com.google.devtools.build.lib.buildeventstream.
- Position
- Below the diagonal: com.google.devtools.build.lib.skyframe.serialization.analysis uses a module listed above it, which is the healthy direction.
19→24 com.google.devtools.build.lib.skyframe.serialization.analysis uses com.google.devtools.build.lib.skyframe part of a loop✕
- Connections
- 18 pairs of types, where a type in com.google.devtools.build.lib.skyframe.serialization.analysis uses a type in com.google.devtools.build.lib.skyframe.
- The types involved
com.google.devtools.build.lib.skyframe.serialization.analysis.FileDependencySerializer→com.google.devtools.build.lib.skyframe.AbstractNestedFileOpNodescom.google.devtools.build.lib.skyframe.serialization.analysis.FileDependencySerializer→com.google.devtools.build.lib.skyframe.DirectoryListingKeycom.google.devtools.build.lib.skyframe.serialization.analysis.FileDependencySerializer→com.google.devtools.build.lib.skyframe.FileKeycom.google.devtools.build.lib.skyframe.serialization.analysis.FileOpNodeCollector→com.google.devtools.build.lib.skyframe.FileKeycom.google.devtools.build.lib.skyframe.serialization.analysis.FileOpNodeMap→com.google.devtools.build.lib.skyframe.FileOpNodeOrFuturecom.google.devtools.build.lib.skyframe.serialization.analysis.FileOpNodeMemoizingLookup→com.google.devtools.build.lib.skyframe.FileOpNodeOrFuturecom.google.devtools.build.lib.skyframe.serialization.analysis.FutureFileDataInfo→com.google.devtools.build.lib.skyframe.FileKeycom.google.devtools.build.lib.skyframe.serialization.analysis.FutureListingDataInfo→com.google.devtools.build.lib.skyframe.DirectoryListingKeycom.google.devtools.build.lib.skyframe.serialization.analysis.FutureNodeDataInfo→com.google.devtools.build.lib.skyframe.AbstractNestedFileOpNodescom.google.devtools.build.lib.skyframe.serialization.analysis.LeafIdAssignment→com.google.devtools.build.lib.skyframe.DirectoryListingKeycom.google.devtools.build.lib.skyframe.serialization.analysis.LeafIdAssignment→com.google.devtools.build.lib.skyframe.FileKeycom.google.devtools.build.lib.skyframe.serialization.analysis.NodeDependencyHandler→com.google.devtools.build.lib.skyframe.AbstractNestedFileOpNodescom.google.devtools.build.lib.skyframe.serialization.analysis.NodeDependencyHandler→com.google.devtools.build.lib.skyframe.DirectoryListingKeycom.google.devtools.build.lib.skyframe.serialization.analysis.NodeDependencyHandler→com.google.devtools.build.lib.skyframe.FileKeycom.google.devtools.build.lib.skyframe.serialization.analysis.NodeGraphLayout→com.google.devtools.build.lib.skyframe.AbstractNestedFileOpNodescom.google.devtools.build.lib.skyframe.serialization.analysis.NodeGraphLayout→com.google.devtools.build.lib.skyframe.FileKeycom.google.devtools.build.lib.skyframe.serialization.analysis.RemoteAnalysisCacheFactory→com.google.devtools.build.lib.skyframe.SkyframeExecutorcom.google.devtools.build.lib.skyframe.serialization.analysis.UploadLayout→com.google.devtools.build.lib.skyframe.AbstractNestedFileOpNodes
- Direction
- com.google.devtools.build.lib.skyframe.serialization.analysis uses com.google.devtools.build.lib.skyframe, so a change to com.google.devtools.build.lib.skyframe can break com.google.devtools.build.lib.skyframe.serialization.analysis, while a change to com.google.devtools.build.lib.skyframe.serialization.analysis can't break com.google.devtools.build.lib.skyframe.
- 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.
19→25 com.google.devtools.build.lib.skyframe.serialization.analysis uses com.google.devtools.build.lib.packages part of a loop✕
- Connections
- 1 pair of types, where a type in com.google.devtools.build.lib.skyframe.serialization.analysis uses a type in com.google.devtools.build.lib.packages.
- The types involved
com.google.devtools.build.lib.skyframe.serialization.analysis.RemoteAnalysisCacheFactory→com.google.devtools.build.lib.packages.RuleClassProvider
- Direction
- com.google.devtools.build.lib.skyframe.serialization.analysis uses com.google.devtools.build.lib.packages, so a change to com.google.devtools.build.lib.packages can break com.google.devtools.build.lib.skyframe.serialization.analysis, while a change to com.google.devtools.build.lib.skyframe.serialization.analysis can't break com.google.devtools.build.lib.packages.
- 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.
19→28 com.google.devtools.build.lib.skyframe.serialization.analysis uses com.google.devtools.build.lib.runtime part of a loop✕
- Connections
- 2 pairs of types, where a type in com.google.devtools.build.lib.skyframe.serialization.analysis uses a type in com.google.devtools.build.lib.runtime.
- The types involved
com.google.devtools.build.lib.skyframe.serialization.analysis.RemoteAnalysisCacheFactory→com.google.devtools.build.lib.runtime.CommandEnvironmentcom.google.devtools.build.lib.skyframe.serialization.analysis.RemoteAnalysisCachingServicesSupplier→com.google.devtools.build.lib.runtime.BlazeService
- Direction
- com.google.devtools.build.lib.skyframe.serialization.analysis uses com.google.devtools.build.lib.runtime, so a change to com.google.devtools.build.lib.runtime can break com.google.devtools.build.lib.skyframe.serialization.analysis, while a change to com.google.devtools.build.lib.skyframe.serialization.analysis can't break com.google.devtools.build.lib.runtime.
- 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.
19→29 com.google.devtools.build.lib.skyframe.serialization.analysis uses com.google.devtools.build.lib.skyframe.serialization part of a loop✕
- Connections
- 83 pairs of types, where a type in com.google.devtools.build.lib.skyframe.serialization.analysis uses a type in com.google.devtools.build.lib.skyframe.serialization. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.google.devtools.build.lib.skyframe.serialization.analysis.AnalysisCacheInvalidator→com.google.devtools.build.lib.skyframe.serialization.FingerprintValueServicecom.google.devtools.build.lib.skyframe.serialization.analysis.AnalysisCacheInvalidator→com.google.devtools.build.lib.skyframe.serialization.FrontierNodeVersioncom.google.devtools.build.lib.skyframe.serialization.analysis.AnalysisCacheInvalidator→com.google.devtools.build.lib.skyframe.serialization.ObjectCodecscom.google.devtools.build.lib.skyframe.serialization.analysis.AvailableNestedDependencies→com.google.devtools.build.lib.skyframe.serialization.PackedFingerprintcom.google.devtools.build.lib.skyframe.serialization.analysis.BaseInvalidationDataInfo→com.google.devtools.build.lib.skyframe.serialization.WriteStatuscom.google.devtools.build.lib.skyframe.serialization.analysis.DefaultPlatformConfigurationProvider→com.google.devtools.build.lib.skyframe.serialization.PlatformConfigurationProvidercom.google.devtools.build.lib.skyframe.serialization.analysis.DependencyMap→com.google.devtools.build.lib.skyframe.serialization.FingerprintValueStorecom.google.devtools.build.lib.skyframe.serialization.analysis.Edge→com.google.devtools.build.lib.skyframe.serialization.PackedFingerprintcom.google.devtools.build.lib.skyframe.serialization.analysis.FileDependencyDeserializer→com.google.devtools.build.lib.skyframe.serialization.FingerprintValueStorecom.google.devtools.build.lib.skyframe.serialization.analysis.FileDependencyDeserializer→com.google.devtools.build.lib.skyframe.serialization.Fingerprintercom.google.devtools.build.lib.skyframe.serialization.analysis.FileDependencyDeserializer→com.google.devtools.build.lib.skyframe.serialization.KeyBytesProvidercom.google.devtools.build.lib.skyframe.serialization.analysis.FileDependencyDeserializer→com.google.devtools.build.lib.skyframe.serialization.PackedFingerprintcom.google.devtools.build.lib.skyframe.serialization.analysis.FileDependencySerializer→com.google.devtools.build.lib.skyframe.serialization.KeyBytesProvidercom.google.devtools.build.lib.skyframe.serialization.analysis.FileDependencySerializer→com.google.devtools.build.lib.skyframe.serialization.KeyValueWritercom.google.devtools.build.lib.skyframe.serialization.analysis.FileDependencySerializer→com.google.devtools.build.lib.skyframe.serialization.PackedFingerprintcom.google.devtools.build.lib.skyframe.serialization.analysis.FileDependencySerializer→com.google.devtools.build.lib.skyframe.serialization.ProfileCollectorcom.google.devtools.build.lib.skyframe.serialization.analysis.FileDependencySerializer→com.google.devtools.build.lib.skyframe.serialization.ProfileRecordercom.google.devtools.build.lib.skyframe.serialization.analysis.FileDependencySerializer→com.google.devtools.build.lib.skyframe.serialization.WriteStatuscom.google.devtools.build.lib.skyframe.serialization.analysis.FileInvalidationDataInfo→com.google.devtools.build.lib.skyframe.serialization.WriteStatuscom.google.devtools.build.lib.skyframe.serialization.analysis.FileInvalidationDataUploader→com.google.devtools.build.lib.skyframe.serialization.WriteStatuscom.google.devtools.build.lib.skyframe.serialization.analysis.FutureNestedDependencies→com.google.devtools.build.lib.skyframe.serialization.PackedFingerprintcom.google.devtools.build.lib.skyframe.serialization.analysis.GraphDumper→com.google.devtools.build.lib.skyframe.serialization.FingerprintValueStorecom.google.devtools.build.lib.skyframe.serialization.analysis.GraphDumper→com.google.devtools.build.lib.skyframe.serialization.Fingerprintercom.google.devtools.build.lib.skyframe.serialization.analysis.GraphDumper→com.google.devtools.build.lib.skyframe.serialization.ObjectCodecscom.google.devtools.build.lib.skyframe.serialization.analysis.GraphDumper→com.google.devtools.build.lib.skyframe.serialization.PackedFingerprint
- Direction
- com.google.devtools.build.lib.skyframe.serialization.analysis uses com.google.devtools.build.lib.skyframe.serialization, so a change to com.google.devtools.build.lib.skyframe.serialization can break com.google.devtools.build.lib.skyframe.serialization.analysis, while a change to com.google.devtools.build.lib.skyframe.serialization.analysis can't break com.google.devtools.build.lib.skyframe.serialization.
- 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.
19→31 com.google.devtools.build.lib.skyframe.serialization.analysis uses com.google.devtools.build.lib.cmdline part of a loop✕
- Connections
- 8 pairs of types, where a type in com.google.devtools.build.lib.skyframe.serialization.analysis uses a type in com.google.devtools.build.lib.cmdline.
- The types involved
com.google.devtools.build.lib.skyframe.serialization.analysis.DefaultPlatformConfigurationProvider→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.skyframe.serialization.analysis.FileOpNodeMemoizingLookup→com.google.devtools.build.lib.cmdline.PackageIdentifiercom.google.devtools.build.lib.skyframe.serialization.analysis.FrontierSerializer→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.skyframe.serialization.analysis.RemoteAnalysisCacheFactory→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.skyframe.serialization.analysis.RemoteAnalysisCacheManager→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.skyframe.serialization.analysis.SelectedEntrySerializer→com.google.devtools.build.lib.cmdline.PackageIdentifiercom.google.devtools.build.lib.skyframe.serialization.analysis.SettablePlatformConfigurationProvider→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.skyframe.serialization.analysis.SkycacheUploadClient→com.google.devtools.build.lib.cmdline.Label
- Direction
- com.google.devtools.build.lib.skyframe.serialization.analysis uses com.google.devtools.build.lib.cmdline, so a change to com.google.devtools.build.lib.cmdline can break com.google.devtools.build.lib.skyframe.serialization.analysis, while a change to com.google.devtools.build.lib.skyframe.serialization.analysis can't break com.google.devtools.build.lib.cmdline.
- 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.
19→33 com.google.devtools.build.lib.skyframe.serialization.analysis uses com.google.devtools.build.lib.analysis.config part of a loop✕
- Connections
- 3 pairs of types, where a type in com.google.devtools.build.lib.skyframe.serialization.analysis uses a type in com.google.devtools.build.lib.analysis.config.
- The types involved
com.google.devtools.build.lib.skyframe.serialization.analysis.DefaultPlatformConfigurationProvider→com.google.devtools.build.lib.analysis.config.BuildOptionscom.google.devtools.build.lib.skyframe.serialization.analysis.RemoteAnalysisCacheFactory→com.google.devtools.build.lib.analysis.config.BuildOptionscom.google.devtools.build.lib.skyframe.serialization.analysis.SettablePlatformConfigurationProvider→com.google.devtools.build.lib.analysis.config.BuildOptions
- Direction
- com.google.devtools.build.lib.skyframe.serialization.analysis uses com.google.devtools.build.lib.analysis.config, so a change to com.google.devtools.build.lib.analysis.config can break com.google.devtools.build.lib.skyframe.serialization.analysis, while a change to com.google.devtools.build.lib.skyframe.serialization.analysis can't break com.google.devtools.build.lib.analysis.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.
19→35 com.google.devtools.build.lib.skyframe.serialization.analysis uses com.google.devtools.build.lib.analysis part of a loop✕
- Connections
- 1 pair of types, where a type in com.google.devtools.build.lib.skyframe.serialization.analysis uses a type in com.google.devtools.build.lib.analysis.
- The types involved
com.google.devtools.build.lib.skyframe.serialization.analysis.RemoteAnalysisCacheFactory→com.google.devtools.build.lib.analysis.BlazeDirectories
- Direction
- com.google.devtools.build.lib.skyframe.serialization.analysis uses com.google.devtools.build.lib.analysis, so a change to com.google.devtools.build.lib.analysis can break com.google.devtools.build.lib.skyframe.serialization.analysis, while a change to com.google.devtools.build.lib.skyframe.serialization.analysis can't break com.google.devtools.build.lib.analysis.
- 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.
19→37 com.google.devtools.build.lib.skyframe.serialization.analysis uses com.google.devtools.build.lib.actions part of a loop✕
- Connections
- 6 pairs of types, where a type in com.google.devtools.build.lib.skyframe.serialization.analysis uses a type in com.google.devtools.build.lib.actions.
- The types involved
com.google.devtools.build.lib.skyframe.serialization.analysis.FileOpNodeMemoizingLookup→com.google.devtools.build.lib.actions.ActionLookupKeycom.google.devtools.build.lib.skyframe.serialization.analysis.FrontierSerializer→com.google.devtools.build.lib.actions.ActionLookupDatacom.google.devtools.build.lib.skyframe.serialization.analysis.FrontierSerializer→com.google.devtools.build.lib.actions.Artifactcom.google.devtools.build.lib.skyframe.serialization.analysis.SelectedEntrySerializer→com.google.devtools.build.lib.actions.ActionLookupKeycom.google.devtools.build.lib.skyframe.serialization.analysis.UploadLayout→com.google.devtools.build.lib.actions.ActionLookupKeycom.google.devtools.build.lib.skyframe.serialization.analysis.UploadTask→com.google.devtools.build.lib.actions.ActionLookupKey
- Direction
- com.google.devtools.build.lib.skyframe.serialization.analysis uses com.google.devtools.build.lib.actions, so a change to com.google.devtools.build.lib.actions can break com.google.devtools.build.lib.skyframe.serialization.analysis, while a change to com.google.devtools.build.lib.skyframe.serialization.analysis can't break com.google.devtools.build.lib.actions.
- 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→5 proguard.classfile.attribute uses proguard.classfile.visitor✕
- Connections
- 5 pairs of types, where a type in proguard.classfile.attribute uses a type in proguard.classfile.visitor.
- The types involved
proguard.classfile.attribute.EnclosingMethodAttribute→proguard.classfile.visitor.ClassVisitorproguard.classfile.attribute.EnclosingMethodAttribute→proguard.classfile.visitor.MemberVisitorproguard.classfile.attribute.LocalVariableInfo→proguard.classfile.visitor.ClassVisitorproguard.classfile.attribute.LocalVariableTypeInfo→proguard.classfile.visitor.ClassVisitorproguard.classfile.attribute.SignatureAttribute→proguard.classfile.visitor.ClassVisitor
- Direction
- proguard.classfile.attribute uses proguard.classfile.visitor, so a change to proguard.classfile.visitor can break proguard.classfile.attribute, while a change to proguard.classfile.attribute can't break proguard.classfile.visitor.
- Position
- Below the diagonal: proguard.classfile.attribute uses a module listed above it, which is the healthy direction.
20→7 proguard.classfile.attribute uses proguard.classfile.constant.visitor✕
- Connections
- 5 pairs of types, where a type in proguard.classfile.attribute uses a type in proguard.classfile.constant.visitor.
- The types involved
proguard.classfile.attribute.BootstrapMethodInfo→proguard.classfile.constant.visitor.ConstantVisitorproguard.classfile.attribute.ExceptionsAttribute→proguard.classfile.constant.visitor.ConstantVisitorproguard.classfile.attribute.InnerClassesInfo→proguard.classfile.constant.visitor.ConstantVisitorproguard.classfile.attribute.NestMembersAttribute→proguard.classfile.constant.visitor.ConstantVisitorproguard.classfile.attribute.ParameterInfo→proguard.classfile.constant.visitor.ConstantVisitor
- Direction
- proguard.classfile.attribute uses proguard.classfile.constant.visitor, so a change to proguard.classfile.constant.visitor can break proguard.classfile.attribute, while a change to proguard.classfile.attribute can't break proguard.classfile.constant.visitor.
- Position
- Below the diagonal: proguard.classfile.attribute uses a module listed above it, which is the healthy direction.
20→17 proguard.classfile.attribute uses proguard.classfile.attribute.visitor✕
- Connections
- 26 pairs of types, where a type in proguard.classfile.attribute uses a type in proguard.classfile.attribute.visitor. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
proguard.classfile.attribute.Attribute→proguard.classfile.attribute.visitor.AttributeVisitorproguard.classfile.attribute.BootstrapMethodsAttribute→proguard.classfile.attribute.visitor.AttributeVisitorproguard.classfile.attribute.BootstrapMethodsAttribute→proguard.classfile.attribute.visitor.BootstrapMethodInfoVisitorproguard.classfile.attribute.CodeAttribute→proguard.classfile.attribute.visitor.AttributeVisitorproguard.classfile.attribute.CodeAttribute→proguard.classfile.attribute.visitor.ExceptionInfoVisitorproguard.classfile.attribute.ConstantValueAttribute→proguard.classfile.attribute.visitor.AttributeVisitorproguard.classfile.attribute.DeprecatedAttribute→proguard.classfile.attribute.visitor.AttributeVisitorproguard.classfile.attribute.EnclosingMethodAttribute→proguard.classfile.attribute.visitor.AttributeVisitorproguard.classfile.attribute.ExceptionsAttribute→proguard.classfile.attribute.visitor.AttributeVisitorproguard.classfile.attribute.InnerClassesAttribute→proguard.classfile.attribute.visitor.AttributeVisitorproguard.classfile.attribute.InnerClassesAttribute→proguard.classfile.attribute.visitor.InnerClassesInfoVisitorproguard.classfile.attribute.LineNumberTableAttribute→proguard.classfile.attribute.visitor.AttributeVisitorproguard.classfile.attribute.LineNumberTableAttribute→proguard.classfile.attribute.visitor.LineNumberInfoVisitorproguard.classfile.attribute.LocalVariableTableAttribute→proguard.classfile.attribute.visitor.AttributeVisitorproguard.classfile.attribute.LocalVariableTableAttribute→proguard.classfile.attribute.visitor.LocalVariableInfoVisitorproguard.classfile.attribute.LocalVariableTypeTableAttribute→proguard.classfile.attribute.visitor.AttributeVisitorproguard.classfile.attribute.LocalVariableTypeTableAttribute→proguard.classfile.attribute.visitor.LocalVariableTypeInfoVisitorproguard.classfile.attribute.MethodParametersAttribute→proguard.classfile.attribute.visitor.AttributeVisitorproguard.classfile.attribute.MethodParametersAttribute→proguard.classfile.attribute.visitor.ParameterInfoVisitorproguard.classfile.attribute.NestHostAttribute→proguard.classfile.attribute.visitor.AttributeVisitorproguard.classfile.attribute.NestMembersAttribute→proguard.classfile.attribute.visitor.AttributeVisitorproguard.classfile.attribute.SignatureAttribute→proguard.classfile.attribute.visitor.AttributeVisitorproguard.classfile.attribute.SourceDirAttribute→proguard.classfile.attribute.visitor.AttributeVisitorproguard.classfile.attribute.SourceFileAttribute→proguard.classfile.attribute.visitor.AttributeVisitorproguard.classfile.attribute.SyntheticAttribute→proguard.classfile.attribute.visitor.AttributeVisitor
- Direction
- proguard.classfile.attribute uses proguard.classfile.attribute.visitor, so a change to proguard.classfile.attribute.visitor can break proguard.classfile.attribute, while a change to proguard.classfile.attribute can't break proguard.classfile.attribute.visitor.
- Position
- Below the diagonal: proguard.classfile.attribute uses a module listed above it, which is the healthy direction.
20→22 proguard.classfile.attribute uses proguard.classfile part of a loop✕
- Connections
- 49 pairs of types, where a type in proguard.classfile.attribute uses a type in proguard.classfile. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
proguard.classfile.attribute.Attribute→proguard.classfile.Clazzproguard.classfile.attribute.Attribute→proguard.classfile.Fieldproguard.classfile.attribute.Attribute→proguard.classfile.Methodproguard.classfile.attribute.Attribute→proguard.classfile.VisitorAccepterproguard.classfile.attribute.BootstrapMethodInfo→proguard.classfile.Clazzproguard.classfile.attribute.BootstrapMethodInfo→proguard.classfile.VisitorAccepterproguard.classfile.attribute.BootstrapMethodsAttribute→proguard.classfile.Clazzproguard.classfile.attribute.CodeAttribute→proguard.classfile.Clazzproguard.classfile.attribute.CodeAttribute→proguard.classfile.Methodproguard.classfile.attribute.ConstantValueAttribute→proguard.classfile.Clazzproguard.classfile.attribute.ConstantValueAttribute→proguard.classfile.Fieldproguard.classfile.attribute.DeprecatedAttribute→proguard.classfile.Clazzproguard.classfile.attribute.DeprecatedAttribute→proguard.classfile.Fieldproguard.classfile.attribute.DeprecatedAttribute→proguard.classfile.Methodproguard.classfile.attribute.EnclosingMethodAttribute→proguard.classfile.Clazzproguard.classfile.attribute.EnclosingMethodAttribute→proguard.classfile.Methodproguard.classfile.attribute.ExceptionInfo→proguard.classfile.VisitorAccepterproguard.classfile.attribute.ExceptionsAttribute→proguard.classfile.Clazzproguard.classfile.attribute.ExceptionsAttribute→proguard.classfile.Methodproguard.classfile.attribute.InnerClassesAttribute→proguard.classfile.Clazzproguard.classfile.attribute.InnerClassesInfo→proguard.classfile.Clazzproguard.classfile.attribute.InnerClassesInfo→proguard.classfile.VisitorAccepterproguard.classfile.attribute.LineNumberTableAttribute→proguard.classfile.Clazzproguard.classfile.attribute.LineNumberTableAttribute→proguard.classfile.Methodproguard.classfile.attribute.LocalVariableInfo→proguard.classfile.Clazz
- Direction
- proguard.classfile.attribute uses proguard.classfile, so a change to proguard.classfile can break proguard.classfile.attribute, while a change to proguard.classfile.attribute can't break proguard.classfile.
- 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→2 com.google.devtools.build.lib.query2 uses com.google.devtools.build.lib.events✕
- Connections
- 3 pairs of types, where a type in com.google.devtools.build.lib.query2 uses a type in com.google.devtools.build.lib.events.
- The types involved
com.google.devtools.build.lib.query2.PostAnalysisQueryEnvironment→com.google.devtools.build.lib.events.ExtendedEventHandlercom.google.devtools.build.lib.query2.QueryEnvironmentFactory→com.google.devtools.build.lib.events.ExtendedEventHandlercom.google.devtools.build.lib.query2.SkyQueryEnvironment→com.google.devtools.build.lib.events.ExtendedEventHandler
- Direction
- com.google.devtools.build.lib.query2 uses com.google.devtools.build.lib.events, so a change to com.google.devtools.build.lib.events can break com.google.devtools.build.lib.query2, while a change to com.google.devtools.build.lib.query2 can't break com.google.devtools.build.lib.events.
- Position
- Below the diagonal: com.google.devtools.build.lib.query2 uses a module listed above it, which is the healthy direction.
21→4 com.google.devtools.build.lib.query2 uses net.starlark.java.eval✕
- Connections
- 1 pair of types, where a type in com.google.devtools.build.lib.query2 uses a type in net.starlark.java.eval.
- The types involved
com.google.devtools.build.lib.query2.PostAnalysisQueryEnvironment→net.starlark.java.eval.StarlarkSemantics
- Direction
- com.google.devtools.build.lib.query2 uses net.starlark.java.eval, so a change to net.starlark.java.eval can break com.google.devtools.build.lib.query2, while a change to com.google.devtools.build.lib.query2 can't break net.starlark.java.eval.
- Position
- Below the diagonal: com.google.devtools.build.lib.query2 uses a module listed above it, which is the healthy direction.
21→6 com.google.devtools.build.lib.query2 uses com.google.devtools.build.skyframe✕
- Connections
- 26 pairs of types, where a type in com.google.devtools.build.lib.query2 uses a type in com.google.devtools.build.skyframe. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.google.devtools.build.lib.query2.AbstractSkyKeyParallelVisitor→com.google.devtools.build.skyframe.SkyKeycom.google.devtools.build.lib.query2.AbstractTargetOuputtingVisitor→com.google.devtools.build.skyframe.SkyKeycom.google.devtools.build.lib.query2.AbstractUnfilteredLabelDTCVisitor→com.google.devtools.build.skyframe.SkyKeycom.google.devtools.build.lib.query2.DepAndRdep→com.google.devtools.build.skyframe.SkyKeycom.google.devtools.build.lib.query2.DepsUnboundedVisitor→com.google.devtools.build.skyframe.SkyKeycom.google.devtools.build.lib.query2.Factory→com.google.devtools.build.skyframe.SkyKeycom.google.devtools.build.lib.query2.ParallelSkyQueryUtils→com.google.devtools.build.skyframe.SkyKeycom.google.devtools.build.lib.query2.ParallelTargetVisitorCallback→com.google.devtools.build.skyframe.SkyKeycom.google.devtools.build.lib.query2.ParallelVisitorUtils→com.google.devtools.build.skyframe.SkyKeycom.google.devtools.build.lib.query2.PostAnalysisQueryEnvironment→com.google.devtools.build.skyframe.SkyKeycom.google.devtools.build.lib.query2.PostAnalysisQueryEnvironment→com.google.devtools.build.skyframe.SkyValuecom.google.devtools.build.lib.query2.PostAnalysisQueryEnvironment→com.google.devtools.build.skyframe.WalkableGraphcom.google.devtools.build.lib.query2.RBuildFilesVisitor→com.google.devtools.build.skyframe.SkyFunctionNamecom.google.devtools.build.lib.query2.RBuildFilesVisitor→com.google.devtools.build.skyframe.SkyKeycom.google.devtools.build.lib.query2.RBuildFilesVisitor→com.google.devtools.build.skyframe.WalkableGraphcom.google.devtools.build.lib.query2.RdepsBoundedVisitor→com.google.devtools.build.skyframe.SkyKeycom.google.devtools.build.lib.query2.RdepsUnboundedVisitor→com.google.devtools.build.skyframe.SkyKeycom.google.devtools.build.lib.query2.RdepsVisitorUtils→com.google.devtools.build.skyframe.SkyKeycom.google.devtools.build.lib.query2.SkyKeyKeyExtractor→com.google.devtools.build.skyframe.SkyKeycom.google.devtools.build.lib.query2.SkyQueryEnvironment→com.google.devtools.build.skyframe.EvaluationContextcom.google.devtools.build.lib.query2.SkyQueryEnvironment→com.google.devtools.build.skyframe.EvaluationResultcom.google.devtools.build.lib.query2.SkyQueryEnvironment→com.google.devtools.build.skyframe.SkyKeycom.google.devtools.build.lib.query2.SkyQueryEnvironment→com.google.devtools.build.skyframe.SkyValuecom.google.devtools.build.lib.query2.SkyQueryEnvironment→com.google.devtools.build.skyframe.WalkableGraphcom.google.devtools.build.lib.query2.ThreadSafeAggregateAllSkyKeysCallback→com.google.devtools.build.skyframe.SkyKey
- Direction
- com.google.devtools.build.lib.query2 uses com.google.devtools.build.skyframe, so a change to com.google.devtools.build.skyframe can break com.google.devtools.build.lib.query2, while a change to com.google.devtools.build.lib.query2 can't break com.google.devtools.build.skyframe.
- Position
- Below the diagonal: com.google.devtools.build.lib.query2 uses a module listed above it, which is the healthy direction.
21→8 com.google.devtools.build.lib.query2 uses com.google.devtools.build.lib.vfs✕
- Connections
- 5 pairs of types, where a type in com.google.devtools.build.lib.query2 uses a type in com.google.devtools.build.lib.vfs.
- The types involved
com.google.devtools.build.lib.query2.ParallelSkyQueryUtils→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.query2.QueryEnvironmentFactory→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.query2.RBuildFilesVisitor→com.google.devtools.build.lib.vfs.FileStateKeycom.google.devtools.build.lib.query2.RBuildFilesVisitor→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.query2.SkyQueryEnvironment→com.google.devtools.build.lib.vfs.PathFragment
- Direction
- com.google.devtools.build.lib.query2 uses com.google.devtools.build.lib.vfs, so a change to com.google.devtools.build.lib.vfs can break com.google.devtools.build.lib.query2, while a change to com.google.devtools.build.lib.query2 can't break com.google.devtools.build.lib.vfs.
- Position
- Below the diagonal: com.google.devtools.build.lib.query2 uses a module listed above it, which is the healthy direction.
21→16 com.google.devtools.build.lib.query2 uses com.google.devtools.build.lib.query2.common✕
- Connections
- 6 pairs of types, where a type in com.google.devtools.build.lib.query2 uses a type in com.google.devtools.build.lib.query2.common.
- The types involved
com.google.devtools.build.lib.query2.PostAnalysisQueryEnvironment→com.google.devtools.build.lib.query2.common.AbstractBlazeQueryEnvironmentcom.google.devtools.build.lib.query2.QueryEnvironmentFactory→com.google.devtools.build.lib.query2.common.AbstractBlazeQueryEnvironmentcom.google.devtools.build.lib.query2.QueryEnvironmentFactory→com.google.devtools.build.lib.query2.common.QueryTransitivePackagePreloadercom.google.devtools.build.lib.query2.QueryEnvironmentFactory→com.google.devtools.build.lib.query2.common.UniverseScopecom.google.devtools.build.lib.query2.SkyQueryEnvironment→com.google.devtools.build.lib.query2.common.AbstractBlazeQueryEnvironmentcom.google.devtools.build.lib.query2.SkyQueryEnvironment→com.google.devtools.build.lib.query2.common.UniverseScope
- Direction
- com.google.devtools.build.lib.query2 uses com.google.devtools.build.lib.query2.common, so a change to com.google.devtools.build.lib.query2.common can break com.google.devtools.build.lib.query2, while a change to com.google.devtools.build.lib.query2 can't break com.google.devtools.build.lib.query2.common.
- Position
- Below the diagonal: com.google.devtools.build.lib.query2 uses a module listed above it, which is the healthy direction.
21→18 com.google.devtools.build.lib.query2 uses com.google.devtools.build.lib.pkgcache✕
- Connections
- 6 pairs of types, where a type in com.google.devtools.build.lib.query2 uses a type in com.google.devtools.build.lib.pkgcache.
- The types involved
com.google.devtools.build.lib.query2.PostAnalysisQueryEnvironment→com.google.devtools.build.lib.pkgcache.PackageManagercom.google.devtools.build.lib.query2.PostAnalysisQueryEnvironment→com.google.devtools.build.lib.pkgcache.PathPackageLocatorcom.google.devtools.build.lib.query2.QueryEnvironmentFactory→com.google.devtools.build.lib.pkgcache.PathPackageLocatorcom.google.devtools.build.lib.query2.QueryEnvironmentFactory→com.google.devtools.build.lib.pkgcache.TargetPatternPreloadercom.google.devtools.build.lib.query2.QueryEnvironmentFactory→com.google.devtools.build.lib.pkgcache.TargetProvidercom.google.devtools.build.lib.query2.SkyQueryEnvironment→com.google.devtools.build.lib.pkgcache.PathPackageLocator
- Direction
- com.google.devtools.build.lib.query2 uses com.google.devtools.build.lib.pkgcache, so a change to com.google.devtools.build.lib.pkgcache can break com.google.devtools.build.lib.query2, while a change to com.google.devtools.build.lib.query2 can't break com.google.devtools.build.lib.pkgcache.
- Position
- Below the diagonal: com.google.devtools.build.lib.query2 uses a module listed above it, which is the healthy direction.
21→24 com.google.devtools.build.lib.query2 uses com.google.devtools.build.lib.skyframe part of a loop✕
- Connections
- 4 pairs of types, where a type in com.google.devtools.build.lib.query2 uses a type in com.google.devtools.build.lib.skyframe.
- The types involved
com.google.devtools.build.lib.query2.PostAnalysisQueryEnvironment→com.google.devtools.build.lib.skyframe.ConfiguredTargetKeycom.google.devtools.build.lib.query2.PostAnalysisQueryEnvironment→com.google.devtools.build.lib.skyframe.RecursivePackageProviderBackedTargetPatternResolvercom.google.devtools.build.lib.query2.PostAnalysisQueryEnvironment→com.google.devtools.build.lib.skyframe.SkyframeExecutorcom.google.devtools.build.lib.query2.SkyQueryEnvironment→com.google.devtools.build.lib.skyframe.GraphBackedRecursivePackageProvider
- Direction
- com.google.devtools.build.lib.query2 uses com.google.devtools.build.lib.skyframe, so a change to com.google.devtools.build.lib.skyframe can break com.google.devtools.build.lib.query2, while a change to com.google.devtools.build.lib.query2 can't break com.google.devtools.build.lib.skyframe.
- 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→25 com.google.devtools.build.lib.query2 uses com.google.devtools.build.lib.packages part of a loop✕
- Connections
- 19 pairs of types, where a type in com.google.devtools.build.lib.query2 uses a type in com.google.devtools.build.lib.packages.
- The types involved
com.google.devtools.build.lib.query2.2→com.google.devtools.build.lib.packages.Targetcom.google.devtools.build.lib.query2.AbstractTargetOuputtingVisitor→com.google.devtools.build.lib.packages.Targetcom.google.devtools.build.lib.query2.BatchStreamedCallback→com.google.devtools.build.lib.packages.Targetcom.google.devtools.build.lib.query2.DepsUnboundedVisitor→com.google.devtools.build.lib.packages.Targetcom.google.devtools.build.lib.query2.ParallelSkyQueryUtils→com.google.devtools.build.lib.packages.Targetcom.google.devtools.build.lib.query2.PostAnalysisQueryEnvironment→com.google.devtools.build.lib.packages.AspectClasscom.google.devtools.build.lib.query2.PostAnalysisQueryEnvironment→com.google.devtools.build.lib.packages.LabelPrintercom.google.devtools.build.lib.query2.PostAnalysisQueryEnvironment→com.google.devtools.build.lib.packages.RuleClassProvidercom.google.devtools.build.lib.query2.PostAnalysisQueryEnvironment→com.google.devtools.build.lib.packages.Targetcom.google.devtools.build.lib.query2.QueryEnvironmentFactory→com.google.devtools.build.lib.packages.CachingPackageLocatorcom.google.devtools.build.lib.query2.QueryEnvironmentFactory→com.google.devtools.build.lib.packages.LabelPrintercom.google.devtools.build.lib.query2.QueryEnvironmentFactory→com.google.devtools.build.lib.packages.Targetcom.google.devtools.build.lib.query2.RBuildFilesVisitor→com.google.devtools.build.lib.packages.Targetcom.google.devtools.build.lib.query2.RdepsBoundedVisitor→com.google.devtools.build.lib.packages.Targetcom.google.devtools.build.lib.query2.RdepsUnboundedVisitor→com.google.devtools.build.lib.packages.Targetcom.google.devtools.build.lib.query2.SkyQueryEnvironment→com.google.devtools.build.lib.packages.LabelPrintercom.google.devtools.build.lib.query2.SkyQueryEnvironment→com.google.devtools.build.lib.packages.Rulecom.google.devtools.build.lib.query2.SkyQueryEnvironment→com.google.devtools.build.lib.packages.Targetcom.google.devtools.build.lib.query2.SkyQueryEvaluateExpressionImpl→com.google.devtools.build.lib.packages.Target
- Direction
- com.google.devtools.build.lib.query2 uses com.google.devtools.build.lib.packages, so a change to com.google.devtools.build.lib.packages can break com.google.devtools.build.lib.query2, while a change to com.google.devtools.build.lib.query2 can't break com.google.devtools.build.lib.packages.
- 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→31 com.google.devtools.build.lib.query2 uses com.google.devtools.build.lib.cmdline part of a loop✕
- Connections
- 22 pairs of types, where a type in com.google.devtools.build.lib.query2 uses a type in com.google.devtools.build.lib.cmdline.
- The types involved
com.google.devtools.build.lib.query2.2→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.query2.AbstractTargetOuputtingVisitor→com.google.devtools.build.lib.cmdline.PackageIdentifiercom.google.devtools.build.lib.query2.FilteredDirectRdepsInUniverseExpressionMapper→com.google.devtools.build.lib.cmdline.Parsercom.google.devtools.build.lib.query2.FilteredDirectRdepsInUniverseExpressionMapper→com.google.devtools.build.lib.cmdline.TargetPatterncom.google.devtools.build.lib.query2.ParallelQueryVisitor→com.google.devtools.build.lib.cmdline.ParallelVisitorcom.google.devtools.build.lib.query2.ParallelTargetVisitorCallback→com.google.devtools.build.lib.cmdline.Factorycom.google.devtools.build.lib.query2.PostAnalysisQueryEnvironment→com.google.devtools.build.lib.cmdline.IgnoredSubdirectoriescom.google.devtools.build.lib.query2.PostAnalysisQueryEnvironment→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.query2.PostAnalysisQueryEnvironment→com.google.devtools.build.lib.cmdline.Parsercom.google.devtools.build.lib.query2.PostAnalysisQueryEnvironment→com.google.devtools.build.lib.cmdline.RepositoryNamecom.google.devtools.build.lib.query2.PostAnalysisQueryEnvironment→com.google.devtools.build.lib.cmdline.TargetPatterncom.google.devtools.build.lib.query2.QueryEnvironmentFactory→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.query2.QueryEnvironmentFactory→com.google.devtools.build.lib.cmdline.Parsercom.google.devtools.build.lib.query2.RBuildFilesVisitor→com.google.devtools.build.lib.cmdline.PackageIdentifiercom.google.devtools.build.lib.query2.RdepsToAllRdepsQueryExpressionMapper→com.google.devtools.build.lib.cmdline.Parsercom.google.devtools.build.lib.query2.RdepsToAllRdepsQueryExpressionMapper→com.google.devtools.build.lib.cmdline.TargetPatterncom.google.devtools.build.lib.query2.SkyQueryEnvironment→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.query2.SkyQueryEnvironment→com.google.devtools.build.lib.cmdline.PackageIdentifiercom.google.devtools.build.lib.query2.SkyQueryEnvironment→com.google.devtools.build.lib.cmdline.Parsercom.google.devtools.build.lib.query2.SkyQueryEnvironment→com.google.devtools.build.lib.cmdline.TargetPatterncom.google.devtools.build.lib.query2.SkyQueryEnvironment→com.google.devtools.build.lib.cmdline.TargetPatternResolvercom.google.devtools.build.lib.query2.TopLevelConfigurations→com.google.devtools.build.lib.cmdline.Label
- Direction
- com.google.devtools.build.lib.query2 uses com.google.devtools.build.lib.cmdline, so a change to com.google.devtools.build.lib.cmdline can break com.google.devtools.build.lib.query2, while a change to com.google.devtools.build.lib.query2 can't break com.google.devtools.build.lib.cmdline.
- 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→33 com.google.devtools.build.lib.query2 uses com.google.devtools.build.lib.analysis.config part of a loop✕
- Connections
- 2 pairs of types, where a type in com.google.devtools.build.lib.query2 uses a type in com.google.devtools.build.lib.analysis.config.
- The types involved
com.google.devtools.build.lib.query2.PostAnalysisQueryEnvironment→com.google.devtools.build.lib.analysis.config.BuildConfigurationValuecom.google.devtools.build.lib.query2.TopLevelConfigurations→com.google.devtools.build.lib.analysis.config.BuildConfigurationValue
- Direction
- com.google.devtools.build.lib.query2 uses com.google.devtools.build.lib.analysis.config, so a change to com.google.devtools.build.lib.analysis.config can break com.google.devtools.build.lib.query2, while a change to com.google.devtools.build.lib.query2 can't break com.google.devtools.build.lib.analysis.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→35 com.google.devtools.build.lib.query2 uses com.google.devtools.build.lib.analysis part of a loop✕
- Connections
- 2 pairs of types, where a type in com.google.devtools.build.lib.query2 uses a type in com.google.devtools.build.lib.analysis.
- The types involved
com.google.devtools.build.lib.query2.PostAnalysisQueryEnvironment→com.google.devtools.build.lib.analysis.AspectValuecom.google.devtools.build.lib.query2.TopLevelConfigurations→com.google.devtools.build.lib.analysis.TargetAndConfiguration
- Direction
- com.google.devtools.build.lib.query2 uses com.google.devtools.build.lib.analysis, so a change to com.google.devtools.build.lib.analysis can break com.google.devtools.build.lib.query2, while a change to com.google.devtools.build.lib.query2 can't break com.google.devtools.build.lib.analysis.
- 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 com.google.devtools.build.lib.query2 uses com.google.devtools.build.lib.actions part of a loop✕
- Connections
- 1 pair of types, where a type in com.google.devtools.build.lib.query2 uses a type in com.google.devtools.build.lib.actions.
- The types involved
com.google.devtools.build.lib.query2.PostAnalysisQueryEnvironment→com.google.devtools.build.lib.actions.ActionLookupKey
- Direction
- com.google.devtools.build.lib.query2 uses com.google.devtools.build.lib.actions, so a change to com.google.devtools.build.lib.actions can break com.google.devtools.build.lib.query2, while a change to com.google.devtools.build.lib.query2 can't break com.google.devtools.build.lib.actions.
- 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→5 proguard.classfile uses proguard.classfile.visitor✕
- Connections
- 20 pairs of types, where a type in proguard.classfile uses a type in proguard.classfile.visitor.
- The types involved
proguard.classfile.ClassPool→proguard.classfile.visitor.ClassPoolVisitorproguard.classfile.ClassPool→proguard.classfile.visitor.ClassVisitorproguard.classfile.Clazz→proguard.classfile.visitor.ClassVisitorproguard.classfile.Clazz→proguard.classfile.visitor.MemberVisitorproguard.classfile.LibraryClass→proguard.classfile.visitor.ClassVisitorproguard.classfile.LibraryClass→proguard.classfile.visitor.MemberVisitorproguard.classfile.LibraryField→proguard.classfile.visitor.ClassVisitorproguard.classfile.LibraryField→proguard.classfile.visitor.MemberVisitorproguard.classfile.LibraryMember→proguard.classfile.visitor.MemberVisitorproguard.classfile.LibraryMethod→proguard.classfile.visitor.ClassVisitorproguard.classfile.LibraryMethod→proguard.classfile.visitor.MemberVisitorproguard.classfile.Member→proguard.classfile.visitor.ClassVisitorproguard.classfile.Member→proguard.classfile.visitor.MemberVisitorproguard.classfile.ProgramClass→proguard.classfile.visitor.ClassVisitorproguard.classfile.ProgramClass→proguard.classfile.visitor.MemberVisitorproguard.classfile.ProgramField→proguard.classfile.visitor.ClassVisitorproguard.classfile.ProgramField→proguard.classfile.visitor.MemberVisitorproguard.classfile.ProgramMember→proguard.classfile.visitor.MemberVisitorproguard.classfile.ProgramMethod→proguard.classfile.visitor.ClassVisitorproguard.classfile.ProgramMethod→proguard.classfile.visitor.MemberVisitor
- Direction
- proguard.classfile uses proguard.classfile.visitor, so a change to proguard.classfile.visitor can break proguard.classfile, while a change to proguard.classfile can't break proguard.classfile.visitor.
- Position
- Below the diagonal: proguard.classfile uses a module listed above it, which is the healthy direction.
22→7 proguard.classfile uses proguard.classfile.constant.visitor✕
- Connections
- 3 pairs of types, where a type in proguard.classfile uses a type in proguard.classfile.constant.visitor.
- The types involved
proguard.classfile.Clazz→proguard.classfile.constant.visitor.ConstantVisitorproguard.classfile.LibraryClass→proguard.classfile.constant.visitor.ConstantVisitorproguard.classfile.ProgramClass→proguard.classfile.constant.visitor.ConstantVisitor
- Direction
- proguard.classfile uses proguard.classfile.constant.visitor, so a change to proguard.classfile.constant.visitor can break proguard.classfile, while a change to proguard.classfile can't break proguard.classfile.constant.visitor.
- Position
- Below the diagonal: proguard.classfile uses a module listed above it, which is the healthy direction.
22→17 proguard.classfile uses proguard.classfile.attribute.visitor✕
- Connections
- 6 pairs of types, where a type in proguard.classfile uses a type in proguard.classfile.attribute.visitor.
- The types involved
proguard.classfile.Clazz→proguard.classfile.attribute.visitor.AttributeVisitorproguard.classfile.LibraryClass→proguard.classfile.attribute.visitor.AttributeVisitorproguard.classfile.ProgramClass→proguard.classfile.attribute.visitor.AttributeVisitorproguard.classfile.ProgramField→proguard.classfile.attribute.visitor.AttributeVisitorproguard.classfile.ProgramMember→proguard.classfile.attribute.visitor.AttributeVisitorproguard.classfile.ProgramMethod→proguard.classfile.attribute.visitor.AttributeVisitor
- Direction
- proguard.classfile uses proguard.classfile.attribute.visitor, so a change to proguard.classfile.attribute.visitor can break proguard.classfile, while a change to proguard.classfile can't break proguard.classfile.attribute.visitor.
- Position
- Below the diagonal: proguard.classfile uses a module listed above it, which is the healthy direction.
22→20 proguard.classfile uses proguard.classfile.attribute✕
- Connections
- 4 pairs of types, where a type in proguard.classfile uses a type in proguard.classfile.attribute.
- The types involved
proguard.classfile.ProgramClass→proguard.classfile.attribute.Attributeproguard.classfile.ProgramField→proguard.classfile.attribute.Attributeproguard.classfile.ProgramMember→proguard.classfile.attribute.Attributeproguard.classfile.ProgramMethod→proguard.classfile.attribute.Attribute
- Direction
- proguard.classfile uses proguard.classfile.attribute, so a change to proguard.classfile.attribute can break proguard.classfile, while a change to proguard.classfile can't break proguard.classfile.attribute.
- Position
- Below the diagonal: proguard.classfile uses a module listed above it, which is the healthy direction.
23→2 com.google.devtools.build.lib.buildtool uses com.google.devtools.build.lib.events✕
- Connections
- 8 pairs of types, where a type in com.google.devtools.build.lib.buildtool uses a type in com.google.devtools.build.lib.events.
- The types involved
com.google.devtools.build.lib.buildtool.BuildTool→com.google.devtools.build.lib.events.ExtendedEventHandlercom.google.devtools.build.lib.buildtool.BuildTool→com.google.devtools.build.lib.events.Reportercom.google.devtools.build.lib.buildtool.ExecutionTool→com.google.devtools.build.lib.events.Reportercom.google.devtools.build.lib.buildtool.ExplanationHandler→com.google.devtools.build.lib.events.Eventcom.google.devtools.build.lib.buildtool.ExplanationHandler→com.google.devtools.build.lib.events.EventHandlercom.google.devtools.build.lib.buildtool.InstrumentationFilterSupport→com.google.devtools.build.lib.events.EventHandlercom.google.devtools.build.lib.buildtool.OutputDirectoryLinksUtils→com.google.devtools.build.lib.events.EventHandlercom.google.devtools.build.lib.buildtool.SkyframeBuilder→com.google.devtools.build.lib.events.Reporter
- Direction
- com.google.devtools.build.lib.buildtool uses com.google.devtools.build.lib.events, so a change to com.google.devtools.build.lib.events can break com.google.devtools.build.lib.buildtool, while a change to com.google.devtools.build.lib.buildtool can't break com.google.devtools.build.lib.events.
- Position
- Below the diagonal: com.google.devtools.build.lib.buildtool uses a module listed above it, which is the healthy direction.
23→3 com.google.devtools.build.lib.buildtool uses com.google.devtools.common.options✕
- Connections
- 11 pairs of types, where a type in com.google.devtools.build.lib.buildtool uses a type in com.google.devtools.common.options.
- The types involved
com.google.devtools.build.lib.buildtool.BuildRequest→com.google.devtools.common.options.OptionsBasecom.google.devtools.build.lib.buildtool.BuildRequest→com.google.devtools.common.options.OptionsParsingResultcom.google.devtools.build.lib.buildtool.BuildRequest→com.google.devtools.common.options.OptionsProvidercom.google.devtools.build.lib.buildtool.BuildRequestOptions→com.google.devtools.common.options.OptionsBasecom.google.devtools.build.lib.buildtool.BuildRequestOptions→com.google.devtools.common.options.RegexPatternOptioncom.google.devtools.build.lib.buildtool.BuildTool→com.google.devtools.common.options.OptionsParsercom.google.devtools.build.lib.buildtool.BuildTool→com.google.devtools.common.options.OptionsParsingResultcom.google.devtools.build.lib.buildtool.BuildTool→com.google.devtools.common.options.OptionsProvidercom.google.devtools.build.lib.buildtool.Builder→com.google.devtools.common.options.OptionsParsingResultcom.google.devtools.build.lib.buildtool.ConvenienceSymlinksConverter→com.google.devtools.common.options.BoolOrEnumConvertercom.google.devtools.build.lib.buildtool.SkyframeBuilder→com.google.devtools.common.options.OptionsProvider
- Direction
- com.google.devtools.build.lib.buildtool uses com.google.devtools.common.options, so a change to com.google.devtools.common.options can break com.google.devtools.build.lib.buildtool, while a change to com.google.devtools.build.lib.buildtool can't break com.google.devtools.common.options.
- Position
- Below the diagonal: com.google.devtools.build.lib.buildtool uses a module listed above it, which is the healthy direction.
23→6 com.google.devtools.build.lib.buildtool uses com.google.devtools.build.skyframe✕
- Connections
- 14 pairs of types, where a type in com.google.devtools.build.lib.buildtool uses a type in com.google.devtools.build.skyframe.
- The types involved
com.google.devtools.build.lib.buildtool.AqueryProcessor→com.google.devtools.build.skyframe.WalkableGraphcom.google.devtools.build.lib.buildtool.CqueryProcessor→com.google.devtools.build.skyframe.WalkableGraphcom.google.devtools.build.lib.buildtool.ExecutionProgressReceiver→com.google.devtools.build.skyframe.DirtyTypecom.google.devtools.build.lib.buildtool.ExecutionProgressReceiver→com.google.devtools.build.skyframe.ErrorInfocom.google.devtools.build.lib.buildtool.ExecutionProgressReceiver→com.google.devtools.build.skyframe.EvaluationProgressReceivercom.google.devtools.build.lib.buildtool.ExecutionProgressReceiver→com.google.devtools.build.skyframe.GroupedDepscom.google.devtools.build.lib.buildtool.ExecutionProgressReceiver→com.google.devtools.build.skyframe.SkyKeycom.google.devtools.build.lib.buildtool.ExecutionProgressReceiver→com.google.devtools.build.skyframe.SkyValuecom.google.devtools.build.lib.buildtool.PostAnalysisQueryProcessor→com.google.devtools.build.skyframe.SkyKeycom.google.devtools.build.lib.buildtool.PostAnalysisQueryProcessor→com.google.devtools.build.skyframe.WalkableGraphcom.google.devtools.build.lib.buildtool.SkyframeMemoryDumper→com.google.devtools.build.skyframe.InMemoryGraphcom.google.devtools.build.lib.buildtool.SkyframeMemoryDumper→com.google.devtools.build.skyframe.NodeEntrycom.google.devtools.build.lib.buildtool.SkyframeMemoryDumper→com.google.devtools.build.skyframe.SkyKeycom.google.devtools.build.lib.buildtool.SkyframeMemoryDumper→com.google.devtools.build.skyframe.SkyValue
- Direction
- com.google.devtools.build.lib.buildtool uses com.google.devtools.build.skyframe, so a change to com.google.devtools.build.skyframe can break com.google.devtools.build.lib.buildtool, while a change to com.google.devtools.build.lib.buildtool can't break com.google.devtools.build.skyframe.
- Position
- Below the diagonal: com.google.devtools.build.lib.buildtool uses a module listed above it, which is the healthy direction.
23→8 com.google.devtools.build.lib.buildtool uses com.google.devtools.build.lib.vfs✕
- Connections
- 22 pairs of types, where a type in com.google.devtools.build.lib.buildtool uses a type in com.google.devtools.build.lib.vfs.
- The types involved
com.google.devtools.build.lib.buildtool.1→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.buildtool.2→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.buildtool.3→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.buildtool.BuildRequestOptions→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.buildtool.BuildResult→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.buildtool.BuildTool→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.buildtool.BuildTool→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.buildtool.BuildToolLogCollection→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.buildtool.ConfigSymlink→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.buildtool.ExecutionTool→com.google.devtools.build.lib.vfs.BulkDeletercom.google.devtools.build.lib.buildtool.ExecutionTool→com.google.devtools.build.lib.vfs.ModifiedFileSetcom.google.devtools.build.lib.buildtool.ExecutionTool→com.google.devtools.build.lib.vfs.OutputServicecom.google.devtools.build.lib.buildtool.ExecutionTool→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.buildtool.ExecutionTool→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.buildtool.OutputDirectoryLinksUtils→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.buildtool.OutputDirectoryLinksUtils→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.buildtool.PathPrettyPrinter→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.buildtool.SkyframeBuilder→com.google.devtools.build.lib.vfs.ModifiedFileSetcom.google.devtools.build.lib.buildtool.SymlinkCreationResult→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.buildtool.SymlinkForest→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.buildtool.SymlinkForest→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.buildtool.SymlinkForest→com.google.devtools.build.lib.vfs.Root
- Direction
- com.google.devtools.build.lib.buildtool uses com.google.devtools.build.lib.vfs, so a change to com.google.devtools.build.lib.vfs can break com.google.devtools.build.lib.buildtool, while a change to com.google.devtools.build.lib.buildtool can't break com.google.devtools.build.lib.vfs.
- Position
- Below the diagonal: com.google.devtools.build.lib.buildtool uses a module listed above it, which is the healthy direction.
23→10 com.google.devtools.build.lib.buildtool uses com.google.devtools.build.lib.skyframe.config✕
- Connections
- 1 pair of types, where a type in com.google.devtools.build.lib.buildtool uses a type in com.google.devtools.build.lib.skyframe.config.
- The types involved
com.google.devtools.build.lib.buildtool.AnalysisPhaseRunner→com.google.devtools.build.lib.skyframe.config.BuildConfigurationKey
- Direction
- com.google.devtools.build.lib.buildtool uses com.google.devtools.build.lib.skyframe.config, so a change to com.google.devtools.build.lib.skyframe.config can break com.google.devtools.build.lib.buildtool, while a change to com.google.devtools.build.lib.buildtool can't break com.google.devtools.build.lib.skyframe.config.
- Position
- Below the diagonal: com.google.devtools.build.lib.buildtool uses a module listed above it, which is the healthy direction.
23→11 com.google.devtools.build.lib.buildtool uses com.google.devtools.build.lib.util✕
- Connections
- 10 pairs of types, where a type in com.google.devtools.build.lib.buildtool uses a type in com.google.devtools.build.lib.util.
- The types involved
com.google.devtools.build.lib.buildtool.BuildResult→com.google.devtools.build.lib.util.DetailedExitCodecom.google.devtools.build.lib.buildtool.BuildTool→com.google.devtools.build.lib.util.DetailedExitCodecom.google.devtools.build.lib.buildtool.BuildToolLogCollection→com.google.devtools.build.lib.util.Paircom.google.devtools.build.lib.buildtool.CollectionObjectTraverser→com.google.devtools.build.lib.util.Measurercom.google.devtools.build.lib.buildtool.ExecutionProgressReceiver→com.google.devtools.build.lib.util.Sleepercom.google.devtools.build.lib.buildtool.ExecutionTool→com.google.devtools.build.lib.util.AbruptExitExceptioncom.google.devtools.build.lib.buildtool.ExitException→com.google.devtools.build.lib.util.DetailedExitCodecom.google.devtools.build.lib.buildtool.JobsConverter→com.google.devtools.build.lib.util.IntegerConvertercom.google.devtools.build.lib.buildtool.SkyframeMemoryDumper→com.google.devtools.build.lib.util.Measurercom.google.devtools.build.lib.buildtool.ThreadConverter→com.google.devtools.build.lib.util.IntegerConverter
- Direction
- com.google.devtools.build.lib.buildtool uses com.google.devtools.build.lib.util, so a change to com.google.devtools.build.lib.util can break com.google.devtools.build.lib.buildtool, while a change to com.google.devtools.build.lib.buildtool can't break com.google.devtools.build.lib.util.
- Position
- Below the diagonal: com.google.devtools.build.lib.buildtool uses a module listed above it, which is the healthy direction.
23→14 com.google.devtools.build.lib.buildtool uses com.google.devtools.build.lib.buildeventstream✕
- Connections
- 2 pairs of types, where a type in com.google.devtools.build.lib.buildtool uses a type in com.google.devtools.build.lib.buildeventstream.
- The types involved
com.google.devtools.build.lib.buildtool.BuildTool→com.google.devtools.build.lib.buildeventstream.BuildEventProtocolOptionscom.google.devtools.build.lib.buildtool.BuildToolLogCollection→com.google.devtools.build.lib.buildeventstream.BuildToolLogs
- Direction
- com.google.devtools.build.lib.buildtool uses com.google.devtools.build.lib.buildeventstream, so a change to com.google.devtools.build.lib.buildeventstream can break com.google.devtools.build.lib.buildtool, while a change to com.google.devtools.build.lib.buildtool can't break com.google.devtools.build.lib.buildeventstream.
- Position
- Below the diagonal: com.google.devtools.build.lib.buildtool uses a module listed above it, which is the healthy direction.
23→15 com.google.devtools.build.lib.buildtool uses com.google.devtools.build.lib.exec✕
- Connections
- 5 pairs of types, where a type in com.google.devtools.build.lib.buildtool uses a type in com.google.devtools.build.lib.exec.
- The types involved
com.google.devtools.build.lib.buildtool.BuildRequest→com.google.devtools.build.lib.exec.ExecutionOptionscom.google.devtools.build.lib.buildtool.ExecutionTool→com.google.devtools.build.lib.exec.BlazeExecutorcom.google.devtools.build.lib.buildtool.ExecutionTool→com.google.devtools.build.lib.exec.ExecutorLifecycleListenercom.google.devtools.build.lib.buildtool.ExecutionTool→com.google.devtools.build.lib.exec.ModuleActionContextRegistrycom.google.devtools.build.lib.buildtool.ExecutionTool→com.google.devtools.build.lib.exec.SpawnStrategyRegistry
- Direction
- com.google.devtools.build.lib.buildtool uses com.google.devtools.build.lib.exec, so a change to com.google.devtools.build.lib.exec can break com.google.devtools.build.lib.buildtool, while a change to com.google.devtools.build.lib.buildtool can't break com.google.devtools.build.lib.exec.
- Position
- Below the diagonal: com.google.devtools.build.lib.buildtool uses a module listed above it, which is the healthy direction.
23→16 com.google.devtools.build.lib.buildtool uses com.google.devtools.build.lib.query2.common✕
- Connections
- 2 pairs of types, where a type in com.google.devtools.build.lib.buildtool uses a type in com.google.devtools.build.lib.query2.common.
- The types involved
com.google.devtools.build.lib.buildtool.CqueryProcessor→com.google.devtools.build.lib.query2.common.CommonQueryOptionscom.google.devtools.build.lib.buildtool.PostAnalysisQueryProcessor→com.google.devtools.build.lib.query2.common.CommonQueryOptions
- Direction
- com.google.devtools.build.lib.buildtool uses com.google.devtools.build.lib.query2.common, so a change to com.google.devtools.build.lib.query2.common can break com.google.devtools.build.lib.buildtool, while a change to com.google.devtools.build.lib.buildtool can't break com.google.devtools.build.lib.query2.common.
- Position
- Below the diagonal: com.google.devtools.build.lib.buildtool uses a module listed above it, which is the healthy direction.
23→18 com.google.devtools.build.lib.buildtool uses com.google.devtools.build.lib.pkgcache✕
- Connections
- 3 pairs of types, where a type in com.google.devtools.build.lib.buildtool uses a type in com.google.devtools.build.lib.pkgcache.
- The types involved
com.google.devtools.build.lib.buildtool.BuildRequest→com.google.devtools.build.lib.pkgcache.LoadingOptionscom.google.devtools.build.lib.buildtool.BuildRequest→com.google.devtools.build.lib.pkgcache.PackageOptionscom.google.devtools.build.lib.buildtool.BuildTool→com.google.devtools.build.lib.pkgcache.LoadingOptions
- Direction
- com.google.devtools.build.lib.buildtool uses com.google.devtools.build.lib.pkgcache, so a change to com.google.devtools.build.lib.pkgcache can break com.google.devtools.build.lib.buildtool, while a change to com.google.devtools.build.lib.buildtool can't break com.google.devtools.build.lib.pkgcache.
- Position
- Below the diagonal: com.google.devtools.build.lib.buildtool uses a module listed above it, which is the healthy direction.
23→19 com.google.devtools.build.lib.buildtool uses com.google.devtools.build.lib.skyframe.serialization.analysis✕
- Connections
- 8 pairs of types, where a type in com.google.devtools.build.lib.buildtool uses a type in com.google.devtools.build.lib.skyframe.serialization.analysis.
- The types involved
com.google.devtools.build.lib.buildtool.AnalysisAndExecutionPhaseRunner→com.google.devtools.build.lib.skyframe.serialization.analysis.RemoteAnalysisCacheReaderDepsProvidercom.google.devtools.build.lib.buildtool.AnalysisAndExecutionPhaseRunner→com.google.devtools.build.lib.skyframe.serialization.analysis.RemoteAnalysisCachingDependenciesProvidercom.google.devtools.build.lib.buildtool.AnalysisPhaseRunner→com.google.devtools.build.lib.skyframe.serialization.analysis.RemoteAnalysisCacheReaderDepsProvidercom.google.devtools.build.lib.buildtool.AnalysisPhaseRunner→com.google.devtools.build.lib.skyframe.serialization.analysis.RemoteAnalysisCachingDependenciesProvidercom.google.devtools.build.lib.buildtool.BuildTool→com.google.devtools.build.lib.skyframe.serialization.analysis.RemoteAnalysisCacheClientcom.google.devtools.build.lib.buildtool.BuildTool→com.google.devtools.build.lib.skyframe.serialization.analysis.RemoteAnalysisCacheReaderDepsProvidercom.google.devtools.build.lib.buildtool.BuildTool→com.google.devtools.build.lib.skyframe.serialization.analysis.RemoteAnalysisCachingDependenciesProvidercom.google.devtools.build.lib.buildtool.BuildTool→com.google.devtools.build.lib.skyframe.serialization.analysis.SerializationDependenciesProvider
- Direction
- com.google.devtools.build.lib.buildtool uses com.google.devtools.build.lib.skyframe.serialization.analysis, so a change to com.google.devtools.build.lib.skyframe.serialization.analysis can break com.google.devtools.build.lib.buildtool, while a change to com.google.devtools.build.lib.buildtool can't break com.google.devtools.build.lib.skyframe.serialization.analysis.
- Position
- Below the diagonal: com.google.devtools.build.lib.buildtool uses a module listed above it, which is the healthy direction.
23→21 com.google.devtools.build.lib.buildtool uses com.google.devtools.build.lib.query2✕
- Connections
- 2 pairs of types, where a type in com.google.devtools.build.lib.buildtool uses a type in com.google.devtools.build.lib.query2.
- The types involved
com.google.devtools.build.lib.buildtool.AqueryProcessor→com.google.devtools.build.lib.query2.PostAnalysisQueryEnvironmentcom.google.devtools.build.lib.buildtool.PostAnalysisQueryProcessor→com.google.devtools.build.lib.query2.PostAnalysisQueryEnvironment
- Direction
- com.google.devtools.build.lib.buildtool uses com.google.devtools.build.lib.query2, so a change to com.google.devtools.build.lib.query2 can break com.google.devtools.build.lib.buildtool, while a change to com.google.devtools.build.lib.buildtool can't break com.google.devtools.build.lib.query2.
- Position
- Below the diagonal: com.google.devtools.build.lib.buildtool uses a module listed above it, which is the healthy direction.
23→24 com.google.devtools.build.lib.buildtool uses com.google.devtools.build.lib.skyframe part of a loop✕
- Connections
- 17 pairs of types, where a type in com.google.devtools.build.lib.buildtool uses a type in com.google.devtools.build.lib.skyframe.
- The types involved
com.google.devtools.build.lib.buildtool.AnalysisAndExecutionPhaseRunner→com.google.devtools.build.lib.skyframe.TargetPatternPhaseValuecom.google.devtools.build.lib.buildtool.AnalysisPhaseRunner→com.google.devtools.build.lib.skyframe.TargetPatternPhaseValuecom.google.devtools.build.lib.buildtool.AqueryProcessor→com.google.devtools.build.lib.skyframe.AspectKeycom.google.devtools.build.lib.buildtool.BuildResultPrinter→com.google.devtools.build.lib.skyframe.ConfiguredTargetKeycom.google.devtools.build.lib.buildtool.BuildTool→com.google.devtools.build.lib.skyframe.SkyframeExecutorcom.google.devtools.build.lib.buildtool.BuildTool→com.google.devtools.build.lib.skyframe.TargetPatternPhaseValuecom.google.devtools.build.lib.buildtool.CqueryProcessor→com.google.devtools.build.lib.skyframe.AspectKeycom.google.devtools.build.lib.buildtool.ExecutionProgressReceiver→com.google.devtools.build.lib.skyframe.ActionCompletedReceivercom.google.devtools.build.lib.buildtool.ExecutionProgressReceiver→com.google.devtools.build.lib.skyframe.ProgressSuppliercom.google.devtools.build.lib.buildtool.ExecutionProgressReceiverSetup→com.google.devtools.build.lib.skyframe.SkyframeExecutorcom.google.devtools.build.lib.buildtool.ExecutionTool→com.google.devtools.build.lib.skyframe.Buildercom.google.devtools.build.lib.buildtool.ExecutionTool→com.google.devtools.build.lib.skyframe.ConfiguredTargetKeycom.google.devtools.build.lib.buildtool.ExecutionTool→com.google.devtools.build.lib.skyframe.IncrementalPackageRootscom.google.devtools.build.lib.buildtool.ExecutionTool→com.google.devtools.build.lib.skyframe.SkyframeExecutorcom.google.devtools.build.lib.buildtool.PostAnalysisQueryProcessor→com.google.devtools.build.lib.skyframe.AspectKeycom.google.devtools.build.lib.buildtool.SkyframeBuilder→com.google.devtools.build.lib.skyframe.Buildercom.google.devtools.build.lib.buildtool.SkyframeBuilder→com.google.devtools.build.lib.skyframe.SkyframeExecutor
- Direction
- com.google.devtools.build.lib.buildtool uses com.google.devtools.build.lib.skyframe, so a change to com.google.devtools.build.lib.skyframe can break com.google.devtools.build.lib.buildtool, while a change to com.google.devtools.build.lib.buildtool can't break com.google.devtools.build.lib.skyframe.
- 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→25 com.google.devtools.build.lib.buildtool uses com.google.devtools.build.lib.packages part of a loop✕
- Connections
- 2 pairs of types, where a type in com.google.devtools.build.lib.buildtool uses a type in com.google.devtools.build.lib.packages.
- The types involved
com.google.devtools.build.lib.buildtool.InstrumentationFilterSupport→com.google.devtools.build.lib.packages.Targetcom.google.devtools.build.lib.buildtool.TargetValidator→com.google.devtools.build.lib.packages.Target
- Direction
- com.google.devtools.build.lib.buildtool uses com.google.devtools.build.lib.packages, so a change to com.google.devtools.build.lib.packages can break com.google.devtools.build.lib.buildtool, while a change to com.google.devtools.build.lib.buildtool can't break com.google.devtools.build.lib.packages.
- 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→27 com.google.devtools.build.lib.buildtool uses com.google.devtools.build.lib.analysis.test part of a loop✕
- Connections
- 2 pairs of types, where a type in com.google.devtools.build.lib.buildtool uses a type in com.google.devtools.build.lib.analysis.test.
- The types involved
com.google.devtools.build.lib.buildtool.ExecutionTool→com.google.devtools.build.lib.analysis.test.TestActionContextcom.google.devtools.build.lib.buildtool.TopLevelTargetAnalysisWatcher→com.google.devtools.build.lib.analysis.test.CoverageArtifactsKnownEvent
- Direction
- com.google.devtools.build.lib.buildtool uses com.google.devtools.build.lib.analysis.test, so a change to com.google.devtools.build.lib.analysis.test can break com.google.devtools.build.lib.buildtool, while a change to com.google.devtools.build.lib.buildtool can't break com.google.devtools.build.lib.analysis.test.
- 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→28 com.google.devtools.build.lib.buildtool uses com.google.devtools.build.lib.runtime part of a loop✕
- Connections
- 18 pairs of types, where a type in com.google.devtools.build.lib.buildtool uses a type in com.google.devtools.build.lib.runtime.
- The types involved
com.google.devtools.build.lib.buildtool.AnalysisAndExecutionPhaseRunner→com.google.devtools.build.lib.runtime.CommandEnvironmentcom.google.devtools.build.lib.buildtool.AnalysisPhaseRunner→com.google.devtools.build.lib.runtime.CommandEnvironmentcom.google.devtools.build.lib.buildtool.AnalysisPostProcessor→com.google.devtools.build.lib.runtime.BlazeRuntimecom.google.devtools.build.lib.buildtool.AnalysisPostProcessor→com.google.devtools.build.lib.runtime.CommandEnvironmentcom.google.devtools.build.lib.buildtool.AqueryProcessor→com.google.devtools.build.lib.runtime.BlazeCommandResultcom.google.devtools.build.lib.buildtool.AqueryProcessor→com.google.devtools.build.lib.runtime.CommandEnvironmentcom.google.devtools.build.lib.buildtool.BuildResultPrinter→com.google.devtools.build.lib.runtime.CommandEnvironmentcom.google.devtools.build.lib.buildtool.BuildTool→com.google.devtools.build.lib.runtime.BlazeRuntimecom.google.devtools.build.lib.buildtool.BuildTool→com.google.devtools.build.lib.runtime.CommandEnvironmentcom.google.devtools.build.lib.buildtool.CqueryProcessor→com.google.devtools.build.lib.runtime.CommandEnvironmentcom.google.devtools.build.lib.buildtool.ExecutionProgressReceiverSetup→com.google.devtools.build.lib.runtime.CommandEnvironmentcom.google.devtools.build.lib.buildtool.ExecutionTool→com.google.devtools.build.lib.runtime.BlazeRuntimecom.google.devtools.build.lib.buildtool.ExecutionTool→com.google.devtools.build.lib.runtime.CommandEnvironmentcom.google.devtools.build.lib.buildtool.PostAnalysisQueryProcessor→com.google.devtools.build.lib.runtime.BlazeRuntimecom.google.devtools.build.lib.buildtool.PostAnalysisQueryProcessor→com.google.devtools.build.lib.runtime.CommandEnvironmentcom.google.devtools.build.lib.buildtool.PostAnalysisQueryProcessor→com.google.devtools.build.lib.runtime.QueryRuntimeHelpercom.google.devtools.build.lib.buildtool.TopLevelTargetAnalysisWatcher→com.google.devtools.build.lib.runtime.BlazeModulecom.google.devtools.build.lib.buildtool.TopLevelTargetAnalysisWatcher→com.google.devtools.build.lib.runtime.CommandEnvironment
- Direction
- com.google.devtools.build.lib.buildtool uses com.google.devtools.build.lib.runtime, so a change to com.google.devtools.build.lib.runtime can break com.google.devtools.build.lib.buildtool, while a change to com.google.devtools.build.lib.buildtool can't break com.google.devtools.build.lib.runtime.
- 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→29 com.google.devtools.build.lib.buildtool uses com.google.devtools.build.lib.skyframe.serialization part of a loop✕
- Connections
- 1 pair of types, where a type in com.google.devtools.build.lib.buildtool uses a type in com.google.devtools.build.lib.skyframe.serialization.
- The types involved
com.google.devtools.build.lib.buildtool.BuildTool→com.google.devtools.build.lib.skyframe.serialization.FingerprintValueService
- Direction
- com.google.devtools.build.lib.buildtool uses com.google.devtools.build.lib.skyframe.serialization, so a change to com.google.devtools.build.lib.skyframe.serialization can break com.google.devtools.build.lib.buildtool, while a change to com.google.devtools.build.lib.buildtool can't break com.google.devtools.build.lib.skyframe.serialization.
- 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→30 com.google.devtools.build.lib.buildtool uses com.google.devtools.build.lib.collect.nestedset part of a loop✕
- Connections
- 1 pair of types, where a type in com.google.devtools.build.lib.buildtool uses a type in com.google.devtools.build.lib.collect.nestedset.
- The types involved
com.google.devtools.build.lib.buildtool.BuildResultPrinter→com.google.devtools.build.lib.collect.nestedset.NestedSet
- Direction
- com.google.devtools.build.lib.buildtool uses com.google.devtools.build.lib.collect.nestedset, so a change to com.google.devtools.build.lib.collect.nestedset can break com.google.devtools.build.lib.buildtool, while a change to com.google.devtools.build.lib.buildtool can't break com.google.devtools.build.lib.collect.nestedset.
- 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→31 com.google.devtools.build.lib.buildtool uses com.google.devtools.build.lib.cmdline part of a loop✕
- Connections
- 10 pairs of types, where a type in com.google.devtools.build.lib.buildtool uses a type in com.google.devtools.build.lib.cmdline.
- The types involved
com.google.devtools.build.lib.buildtool.AnalysisAndExecutionPhaseRunner→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.buildtool.AnalysisPhaseRunner→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.buildtool.AqueryProcessor→com.google.devtools.build.lib.cmdline.Parsercom.google.devtools.build.lib.buildtool.BuildRequestOptions→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.buildtool.CqueryProcessor→com.google.devtools.build.lib.cmdline.Parsercom.google.devtools.build.lib.buildtool.PostAnalysisQueryProcessor→com.google.devtools.build.lib.cmdline.Parsercom.google.devtools.build.lib.buildtool.ProjectEvaluationResult→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.buildtool.SymlinkForest→com.google.devtools.build.lib.cmdline.IgnoredSubdirectoriescom.google.devtools.build.lib.buildtool.SymlinkForest→com.google.devtools.build.lib.cmdline.PackageIdentifiercom.google.devtools.build.lib.buildtool.SymlinkForest→com.google.devtools.build.lib.cmdline.RepositoryName
- Direction
- com.google.devtools.build.lib.buildtool uses com.google.devtools.build.lib.cmdline, so a change to com.google.devtools.build.lib.cmdline can break com.google.devtools.build.lib.buildtool, while a change to com.google.devtools.build.lib.buildtool can't break com.google.devtools.build.lib.cmdline.
- 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→33 com.google.devtools.build.lib.buildtool uses com.google.devtools.build.lib.analysis.config part of a loop✕
- Connections
- 20 pairs of types, where a type in com.google.devtools.build.lib.buildtool uses a type in com.google.devtools.build.lib.analysis.config.
- The types involved
com.google.devtools.build.lib.buildtool.1→com.google.devtools.build.lib.analysis.config.BuildConfigurationValuecom.google.devtools.build.lib.buildtool.2→com.google.devtools.build.lib.analysis.config.BuildConfigurationValuecom.google.devtools.build.lib.buildtool.2→com.google.devtools.build.lib.analysis.config.SymlinkDefinitioncom.google.devtools.build.lib.buildtool.3→com.google.devtools.build.lib.analysis.config.BuildConfigurationValuecom.google.devtools.build.lib.buildtool.3→com.google.devtools.build.lib.analysis.config.SymlinkDefinitioncom.google.devtools.build.lib.buildtool.AnalysisAndExecutionPhaseRunner→com.google.devtools.build.lib.analysis.config.BuildOptionscom.google.devtools.build.lib.buildtool.AnalysisPhaseRunner→com.google.devtools.build.lib.analysis.config.BuildConfigurationValuecom.google.devtools.build.lib.buildtool.AnalysisPhaseRunner→com.google.devtools.build.lib.analysis.config.BuildOptionscom.google.devtools.build.lib.buildtool.AqueryProcessor→com.google.devtools.build.lib.analysis.config.BuildConfigurationValuecom.google.devtools.build.lib.buildtool.BuildResult→com.google.devtools.build.lib.analysis.config.BuildConfigurationValuecom.google.devtools.build.lib.buildtool.BuildTool→com.google.devtools.build.lib.analysis.config.BuildOptionscom.google.devtools.build.lib.buildtool.ConfigPathGetter→com.google.devtools.build.lib.analysis.config.BuildConfigurationValuecom.google.devtools.build.lib.buildtool.ConfigSymlink→com.google.devtools.build.lib.analysis.config.BuildConfigurationValuecom.google.devtools.build.lib.buildtool.ConfigSymlink→com.google.devtools.build.lib.analysis.config.SymlinkDefinitioncom.google.devtools.build.lib.buildtool.CqueryProcessor→com.google.devtools.build.lib.analysis.config.BuildConfigurationValuecom.google.devtools.build.lib.buildtool.ExecutionTool→com.google.devtools.build.lib.analysis.config.BuildConfigurationValuecom.google.devtools.build.lib.buildtool.OutputDirectoryLinksUtils→com.google.devtools.build.lib.analysis.config.BuildConfigurationValuecom.google.devtools.build.lib.buildtool.OutputDirectoryLinksUtils→com.google.devtools.build.lib.analysis.config.SymlinkDefinitioncom.google.devtools.build.lib.buildtool.PostAnalysisQueryProcessor→com.google.devtools.build.lib.analysis.config.BuildConfigurationValuecom.google.devtools.build.lib.buildtool.TopLevelTargetAnalysisWatcher→com.google.devtools.build.lib.analysis.config.BuildOptions
- Direction
- com.google.devtools.build.lib.buildtool uses com.google.devtools.build.lib.analysis.config, so a change to com.google.devtools.build.lib.analysis.config can break com.google.devtools.build.lib.buildtool, while a change to com.google.devtools.build.lib.buildtool can't break com.google.devtools.build.lib.analysis.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→35 com.google.devtools.build.lib.buildtool uses com.google.devtools.build.lib.analysis part of a loop✕
- Connections
- 24 pairs of types, where a type in com.google.devtools.build.lib.buildtool uses a type in com.google.devtools.build.lib.analysis.
- The types involved
com.google.devtools.build.lib.buildtool.AnalysisAndExecutionPhaseRunner→com.google.devtools.build.lib.analysis.AnalysisAndExecutionResultcom.google.devtools.build.lib.buildtool.AnalysisPhaseRunner→com.google.devtools.build.lib.analysis.AnalysisResultcom.google.devtools.build.lib.buildtool.AnalysisPhaseRunner→com.google.devtools.build.lib.analysis.ConfiguredTargetcom.google.devtools.build.lib.buildtool.AnalysisPostProcessor→com.google.devtools.build.lib.analysis.AnalysisResultcom.google.devtools.build.lib.buildtool.AqueryProcessor→com.google.devtools.build.lib.analysis.ConfiguredAspectcom.google.devtools.build.lib.buildtool.AqueryProcessor→com.google.devtools.build.lib.analysis.ConfiguredTargetValuecom.google.devtools.build.lib.buildtool.BuildRequest→com.google.devtools.build.lib.analysis.AnalysisOptionscom.google.devtools.build.lib.buildtool.BuildRequest→com.google.devtools.build.lib.analysis.TopLevelArtifactContextcom.google.devtools.build.lib.buildtool.BuildResult→com.google.devtools.build.lib.analysis.ConfiguredTargetcom.google.devtools.build.lib.buildtool.BuildResultPrinter→com.google.devtools.build.lib.analysis.ConfiguredAspectcom.google.devtools.build.lib.buildtool.BuildResultPrinter→com.google.devtools.build.lib.analysis.ConfiguredTargetcom.google.devtools.build.lib.buildtool.BuildResultPrinter→com.google.devtools.build.lib.analysis.ProviderCollectioncom.google.devtools.build.lib.buildtool.BuildResultPrinter→com.google.devtools.build.lib.analysis.TopLevelArtifactContextcom.google.devtools.build.lib.buildtool.CqueryProcessor→com.google.devtools.build.lib.analysis.ConfiguredAspectcom.google.devtools.build.lib.buildtool.ExecutionTool→com.google.devtools.build.lib.analysis.AnalysisResultcom.google.devtools.build.lib.buildtool.ExecutionTool→com.google.devtools.build.lib.analysis.ConfiguredTargetcom.google.devtools.build.lib.buildtool.ExecutionTool→com.google.devtools.build.lib.analysis.TopLevelArtifactContextcom.google.devtools.build.lib.buildtool.OutputDirectoryLinksUtils→com.google.devtools.build.lib.analysis.BlazeDirectoriescom.google.devtools.build.lib.buildtool.PostAnalysisQueryProcessor→com.google.devtools.build.lib.analysis.AnalysisResultcom.google.devtools.build.lib.buildtool.PostAnalysisQueryProcessor→com.google.devtools.build.lib.analysis.ConfiguredAspectcom.google.devtools.build.lib.buildtool.PostBuildCallback→com.google.devtools.build.lib.analysis.ConfiguredTargetcom.google.devtools.build.lib.buildtool.SkyframeBuilder→com.google.devtools.build.lib.analysis.ConfiguredTargetcom.google.devtools.build.lib.buildtool.SkyframeBuilder→com.google.devtools.build.lib.analysis.TopLevelArtifactContextcom.google.devtools.build.lib.buildtool.SkyframeMemoryDumper→com.google.devtools.build.lib.analysis.ConfiguredRuleClassProvider
- Direction
- com.google.devtools.build.lib.buildtool uses com.google.devtools.build.lib.analysis, so a change to com.google.devtools.build.lib.analysis can break com.google.devtools.build.lib.buildtool, while a change to com.google.devtools.build.lib.buildtool can't break com.google.devtools.build.lib.analysis.
- 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→37 com.google.devtools.build.lib.buildtool uses com.google.devtools.build.lib.actions part of a loop✕
- Connections
- 17 pairs of types, where a type in com.google.devtools.build.lib.buildtool uses a type in com.google.devtools.build.lib.actions.
- The types involved
com.google.devtools.build.lib.buildtool.BuildResultPrinter→com.google.devtools.build.lib.actions.Artifactcom.google.devtools.build.lib.buildtool.ConfigPathGetter→com.google.devtools.build.lib.actions.ArtifactRootcom.google.devtools.build.lib.buildtool.ExecutionProgressReceiver→com.google.devtools.build.lib.actions.ActionExecutionStatusReportercom.google.devtools.build.lib.buildtool.ExecutionProgressReceiver→com.google.devtools.build.lib.actions.ActionLookupDatacom.google.devtools.build.lib.buildtool.ExecutionTool→com.google.devtools.build.lib.actions.ActionCacheCheckercom.google.devtools.build.lib.buildtool.ExecutionTool→com.google.devtools.build.lib.actions.ActionInputPrefetchercom.google.devtools.build.lib.buildtool.ExecutionTool→com.google.devtools.build.lib.actions.Executorcom.google.devtools.build.lib.buildtool.ExecutionTool→com.google.devtools.build.lib.actions.PackageRootscom.google.devtools.build.lib.buildtool.ExecutionTool→com.google.devtools.build.lib.actions.ResourceManagercom.google.devtools.build.lib.buildtool.SkyframeBuilder→com.google.devtools.build.lib.actions.ActionCacheCheckercom.google.devtools.build.lib.buildtool.SkyframeBuilder→com.google.devtools.build.lib.actions.ActionInputPrefetchercom.google.devtools.build.lib.buildtool.SkyframeBuilder→com.google.devtools.build.lib.actions.ActionOutputDirectoryHelpercom.google.devtools.build.lib.buildtool.SkyframeBuilder→com.google.devtools.build.lib.actions.Artifactcom.google.devtools.build.lib.buildtool.SkyframeBuilder→com.google.devtools.build.lib.actions.Executorcom.google.devtools.build.lib.buildtool.SkyframeBuilder→com.google.devtools.build.lib.actions.InputMetadataProvidercom.google.devtools.build.lib.buildtool.SkyframeBuilder→com.google.devtools.build.lib.actions.OutputCheckercom.google.devtools.build.lib.buildtool.SkyframeBuilder→com.google.devtools.build.lib.actions.ResourceManager
- Direction
- com.google.devtools.build.lib.buildtool uses com.google.devtools.build.lib.actions, so a change to com.google.devtools.build.lib.actions can break com.google.devtools.build.lib.buildtool, while a change to com.google.devtools.build.lib.buildtool can't break com.google.devtools.build.lib.actions.
- 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→1 com.google.devtools.build.lib.skyframe uses net.starlark.java.syntax✕
- Connections
- 23 pairs of types, where a type in com.google.devtools.build.lib.skyframe uses a type in net.starlark.java.syntax.
- The types involved
com.google.devtools.build.lib.skyframe.BzlCompileFunction→net.starlark.java.syntax.Buildercom.google.devtools.build.lib.skyframe.BzlCompileFunction→net.starlark.java.syntax.Expressioncom.google.devtools.build.lib.skyframe.BzlCompileFunction→net.starlark.java.syntax.Locationcom.google.devtools.build.lib.skyframe.BzlCompileFunction→net.starlark.java.syntax.StarlarkFilecom.google.devtools.build.lib.skyframe.BzlCompileFunction→net.starlark.java.syntax.Statementcom.google.devtools.build.lib.skyframe.BzlCompileFunction→net.starlark.java.syntax.SyntaxErrorcom.google.devtools.build.lib.skyframe.BzlCompileValue→net.starlark.java.syntax.Programcom.google.devtools.build.lib.skyframe.BzlLoadFunction→net.starlark.java.syntax.Locationcom.google.devtools.build.lib.skyframe.BzlLoadFunction→net.starlark.java.syntax.Programcom.google.devtools.build.lib.skyframe.BzlLoadFunction→net.starlark.java.syntax.StarlarkFilecom.google.devtools.build.lib.skyframe.CompiledBuildFile→net.starlark.java.syntax.Locationcom.google.devtools.build.lib.skyframe.CompiledBuildFile→net.starlark.java.syntax.Programcom.google.devtools.build.lib.skyframe.CompiledBuildFile→net.starlark.java.syntax.SyntaxErrorcom.google.devtools.build.lib.skyframe.ConfiguredTargetAndData→net.starlark.java.syntax.Locationcom.google.devtools.build.lib.skyframe.ConfiguredValueCreationException→net.starlark.java.syntax.Locationcom.google.devtools.build.lib.skyframe.DependencyResolver→net.starlark.java.syntax.Locationcom.google.devtools.build.lib.skyframe.Failure→net.starlark.java.syntax.Programcom.google.devtools.build.lib.skyframe.PackageFunction→net.starlark.java.syntax.Locationcom.google.devtools.build.lib.skyframe.RepoFileFunction→net.starlark.java.syntax.StarlarkFilecom.google.devtools.build.lib.skyframe.StarlarkUtil→net.starlark.java.syntax.ParserInputcom.google.devtools.build.lib.skyframe.State→net.starlark.java.syntax.Locationcom.google.devtools.build.lib.skyframe.Success→net.starlark.java.syntax.Programcom.google.devtools.build.lib.skyframe.TargetCompletor→net.starlark.java.syntax.Location
- Direction
- com.google.devtools.build.lib.skyframe uses net.starlark.java.syntax, so a change to net.starlark.java.syntax can break com.google.devtools.build.lib.skyframe, while a change to com.google.devtools.build.lib.skyframe can't break net.starlark.java.syntax.
- Position
- Below the diagonal: com.google.devtools.build.lib.skyframe uses a module listed above it, which is the healthy direction.
24→2 com.google.devtools.build.lib.skyframe uses com.google.devtools.build.lib.events✕
- Connections
- 64 pairs of types, where a type in com.google.devtools.build.lib.skyframe uses a type in com.google.devtools.build.lib.events. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.google.devtools.build.lib.skyframe.AbstractLabelCycleReporter→com.google.devtools.build.lib.events.ExtendedEventHandlercom.google.devtools.build.lib.skyframe.ActionInputCollectedEvent→com.google.devtools.build.lib.events.Postablecom.google.devtools.build.lib.skyframe.ActionOutputEventData→com.google.devtools.build.lib.events.ProcessOutputcom.google.devtools.build.lib.skyframe.ActionRunner→com.google.devtools.build.lib.events.ExtendedEventHandlercom.google.devtools.build.lib.skyframe.ActionTemplateExpansionFunction→com.google.devtools.build.lib.events.EventHandlercom.google.devtools.build.lib.skyframe.AspectCompletor→com.google.devtools.build.lib.events.Eventcom.google.devtools.build.lib.skyframe.BzlCompileFunction→com.google.devtools.build.lib.events.EventHandlercom.google.devtools.build.lib.skyframe.BzlLoadCycleReporter→com.google.devtools.build.lib.events.ExtendedEventHandlercom.google.devtools.build.lib.skyframe.BzlLoadFunction→com.google.devtools.build.lib.events.EventHandlercom.google.devtools.build.lib.skyframe.BzlLoadFunction→com.google.devtools.build.lib.events.ExtendedEventHandlercom.google.devtools.build.lib.skyframe.BzlmodRepoCycleReporter→com.google.devtools.build.lib.events.ExtendedEventHandlercom.google.devtools.build.lib.skyframe.Completor→com.google.devtools.build.lib.events.Eventcom.google.devtools.build.lib.skyframe.ConfigurationPhaseStartedEvent→com.google.devtools.build.lib.events.Postablecom.google.devtools.build.lib.skyframe.DependencyResolver→com.google.devtools.build.lib.events.ExtendedEventHandlercom.google.devtools.build.lib.skyframe.DiffAwarenessManager→com.google.devtools.build.lib.events.EventHandlercom.google.devtools.build.lib.skyframe.DiffCheckNotificationOptions→com.google.devtools.build.lib.events.EventHandlercom.google.devtools.build.lib.skyframe.EnvironmentBackedRecursivePackageProvider→com.google.devtools.build.lib.events.ExtendedEventHandlercom.google.devtools.build.lib.skyframe.ExternalFilesHelper→com.google.devtools.build.lib.events.ExtendedEventHandlercom.google.devtools.build.lib.skyframe.GraphBackedRecursivePackageProvider→com.google.devtools.build.lib.events.ExtendedEventHandlercom.google.devtools.build.lib.skyframe.LoadingPhaseStartedEvent→com.google.devtools.build.lib.events.Postablecom.google.devtools.build.lib.skyframe.NormalLookup→com.google.devtools.build.lib.events.ExtendedEventHandlercom.google.devtools.build.lib.skyframe.PackageCollectingParallelVisitor→com.google.devtools.build.lib.events.ExtendedEventHandlercom.google.devtools.build.lib.skyframe.PackageFunction→com.google.devtools.build.lib.events.ExtendedEventHandlercom.google.devtools.build.lib.skyframe.PackageLoader→com.google.devtools.build.lib.events.ExtendedEventHandlercom.google.devtools.build.lib.skyframe.PatternLookup→com.google.devtools.build.lib.events.ExtendedEventHandler
- Direction
- com.google.devtools.build.lib.skyframe uses com.google.devtools.build.lib.events, so a change to com.google.devtools.build.lib.events can break com.google.devtools.build.lib.skyframe, while a change to com.google.devtools.build.lib.skyframe can't break com.google.devtools.build.lib.events.
- Position
- Below the diagonal: com.google.devtools.build.lib.skyframe uses a module listed above it, which is the healthy direction.
24→3 com.google.devtools.build.lib.skyframe uses com.google.devtools.common.options✕
- Connections
- 11 pairs of types, where a type in com.google.devtools.build.lib.skyframe uses a type in com.google.devtools.common.options.
- The types involved
com.google.devtools.build.lib.skyframe.4→com.google.devtools.common.options.OptionsProvidercom.google.devtools.build.lib.skyframe.DiffAwareness→com.google.devtools.common.options.OptionsProvidercom.google.devtools.build.lib.skyframe.DiffAwarenessManager→com.google.devtools.common.options.OptionsProvidercom.google.devtools.build.lib.skyframe.DiffCheckNotificationOptions→com.google.devtools.common.options.OptionsProvidercom.google.devtools.build.lib.skyframe.MacOSXFsEventsDiffAwareness→com.google.devtools.common.options.OptionsProvidercom.google.devtools.build.lib.skyframe.Options→com.google.devtools.common.options.OptionsBasecom.google.devtools.build.lib.skyframe.SequencedSkyframeExecutor→com.google.devtools.common.options.OptionsProvidercom.google.devtools.build.lib.skyframe.SkyframeActionExecutor→com.google.devtools.common.options.OptionsProvidercom.google.devtools.build.lib.skyframe.SkyframeBuildView→com.google.devtools.common.options.OptionDefinitioncom.google.devtools.build.lib.skyframe.SkyframeExecutor→com.google.devtools.common.options.OptionsProvidercom.google.devtools.build.lib.skyframe.WatchServiceDiffAwareness→com.google.devtools.common.options.OptionsProvider
- Direction
- com.google.devtools.build.lib.skyframe uses com.google.devtools.common.options, so a change to com.google.devtools.common.options can break com.google.devtools.build.lib.skyframe, while a change to com.google.devtools.build.lib.skyframe can't break com.google.devtools.common.options.
- Position
- Below the diagonal: com.google.devtools.build.lib.skyframe uses a module listed above it, which is the healthy direction.
24→4 com.google.devtools.build.lib.skyframe uses net.starlark.java.eval✕
- Connections
- 17 pairs of types, where a type in com.google.devtools.build.lib.skyframe uses a type in net.starlark.java.eval.
- The types involved
com.google.devtools.build.lib.skyframe.BzlCompileFunction→net.starlark.java.eval.StarlarkSemanticscom.google.devtools.build.lib.skyframe.BzlLoadFunction→net.starlark.java.eval.StarlarkSemanticscom.google.devtools.build.lib.skyframe.BzlLoadFunction→net.starlark.java.eval.StarlarkThreadcom.google.devtools.build.lib.skyframe.BzlLoadThreadOwner→net.starlark.java.eval.SymbolGeneratorcom.google.devtools.build.lib.skyframe.ForBuildFile→net.starlark.java.eval.StarlarkSemanticscom.google.devtools.build.lib.skyframe.NonFinalizerPackagePiecesValue→net.starlark.java.eval.EvalExceptioncom.google.devtools.build.lib.skyframe.NonFinalizerPackagePiecesValue→net.starlark.java.eval.StarlarkSemanticscom.google.devtools.build.lib.skyframe.PackageDeclarationsValue→net.starlark.java.eval.StarlarkSemanticscom.google.devtools.build.lib.skyframe.PackageFunction→net.starlark.java.eval.StarlarkSemanticscom.google.devtools.build.lib.skyframe.PackagePieces→net.starlark.java.eval.CallStackEntrycom.google.devtools.build.lib.skyframe.PackagePieces→net.starlark.java.eval.EvalExceptioncom.google.devtools.build.lib.skyframe.PrecomputedValue→net.starlark.java.eval.StarlarkSemanticscom.google.devtools.build.lib.skyframe.ProjectFunction→net.starlark.java.eval.Dictcom.google.devtools.build.lib.skyframe.RecursiveExpander→net.starlark.java.eval.StarlarkSemanticscom.google.devtools.build.lib.skyframe.RepoFileFunction→net.starlark.java.eval.StarlarkSemanticscom.google.devtools.build.lib.skyframe.SkyframeExecutor→net.starlark.java.eval.StarlarkSemanticscom.google.devtools.build.lib.skyframe.StarlarkBuiltinsValue→net.starlark.java.eval.StarlarkSemantics
- Direction
- com.google.devtools.build.lib.skyframe uses net.starlark.java.eval, so a change to net.starlark.java.eval can break com.google.devtools.build.lib.skyframe, while a change to com.google.devtools.build.lib.skyframe can't break net.starlark.java.eval.
- Position
- Below the diagonal: com.google.devtools.build.lib.skyframe uses a module listed above it, which is the healthy direction.
24→6 com.google.devtools.build.lib.skyframe uses com.google.devtools.build.skyframe✕
- Connections
- 543 pairs of types, where a type in com.google.devtools.build.lib.skyframe uses a type in com.google.devtools.build.skyframe. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.google.devtools.build.lib.skyframe.AbstractLabelCycleReporter→com.google.devtools.build.skyframe.CycleInfocom.google.devtools.build.lib.skyframe.AbstractLabelCycleReporter→com.google.devtools.build.skyframe.SingleCycleReportercom.google.devtools.build.lib.skyframe.AbstractLabelCycleReporter→com.google.devtools.build.skyframe.SkyKeycom.google.devtools.build.lib.skyframe.ActionArtifactCycleReporter→com.google.devtools.build.skyframe.CycleInfocom.google.devtools.build.lib.skyframe.ActionArtifactCycleReporter→com.google.devtools.build.skyframe.SkyFunctionNamecom.google.devtools.build.lib.skyframe.ActionArtifactCycleReporter→com.google.devtools.build.skyframe.SkyKeycom.google.devtools.build.lib.skyframe.ActionConflictFunctionException→com.google.devtools.build.skyframe.SkyFunctionExceptioncom.google.devtools.build.lib.skyframe.ActionEnvironmentFunction→com.google.devtools.build.skyframe.SkyFunctioncom.google.devtools.build.lib.skyframe.ActionEnvironmentFunction→com.google.devtools.build.skyframe.SkyKeycom.google.devtools.build.lib.skyframe.ActionEnvironmentFunction→com.google.devtools.build.skyframe.SkyValuecom.google.devtools.build.lib.skyframe.ActionExecutionFunction→com.google.devtools.build.skyframe.MemoizingEvaluatorcom.google.devtools.build.lib.skyframe.ActionExecutionFunction→com.google.devtools.build.skyframe.SkyFunctioncom.google.devtools.build.lib.skyframe.ActionExecutionFunction→com.google.devtools.build.skyframe.SkyKeycom.google.devtools.build.lib.skyframe.ActionExecutionFunction→com.google.devtools.build.skyframe.SkyValuecom.google.devtools.build.lib.skyframe.ActionExecutionFunction→com.google.devtools.build.skyframe.SkyframeLookupResultcom.google.devtools.build.lib.skyframe.ActionExecutionFunctionException→com.google.devtools.build.skyframe.SkyFunctionExceptioncom.google.devtools.build.lib.skyframe.ActionExecutionFunctionExceptionHandler→com.google.devtools.build.skyframe.SkyKeycom.google.devtools.build.lib.skyframe.ActionExecutionFunctionExceptionHandler→com.google.devtools.build.skyframe.SkyframeLookupResultcom.google.devtools.build.lib.skyframe.ActionExecutionState→com.google.devtools.build.skyframe.Environmentcom.google.devtools.build.lib.skyframe.ActionExecutionState→com.google.devtools.build.skyframe.SkyKeycom.google.devtools.build.lib.skyframe.ActionExecutionValue→com.google.devtools.build.skyframe.SkyValuecom.google.devtools.build.lib.skyframe.ActionInputMapHelper→com.google.devtools.build.skyframe.SkyValuecom.google.devtools.build.lib.skyframe.ActionLookupConflictFindingFunction→com.google.devtools.build.skyframe.SkyFunctioncom.google.devtools.build.lib.skyframe.ActionLookupConflictFindingFunction→com.google.devtools.build.skyframe.SkyKeycom.google.devtools.build.lib.skyframe.ActionLookupConflictFindingFunction→com.google.devtools.build.skyframe.SkyValue
- Direction
- com.google.devtools.build.lib.skyframe uses com.google.devtools.build.skyframe, so a change to com.google.devtools.build.skyframe can break com.google.devtools.build.lib.skyframe, while a change to com.google.devtools.build.lib.skyframe can't break com.google.devtools.build.skyframe.
- Position
- Below the diagonal: com.google.devtools.build.lib.skyframe uses a module listed above it, which is the healthy direction.
24→8 com.google.devtools.build.lib.skyframe uses com.google.devtools.build.lib.vfs✕
- Connections
- 226 pairs of types, where a type in com.google.devtools.build.lib.skyframe uses a type in com.google.devtools.build.lib.vfs. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.google.devtools.build.lib.skyframe.1→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.skyframe.ActionInputMetadataProvider→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.skyframe.ActionOnIOExceptionReadingBuildFile→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.skyframe.ActionOutputMetadataStore→com.google.devtools.build.lib.vfs.BatchStatcom.google.devtools.build.lib.skyframe.ActionOutputMetadataStore→com.google.devtools.build.lib.vfs.FileStatusWithDigestcom.google.devtools.build.lib.skyframe.ActionOutputMetadataStore→com.google.devtools.build.lib.vfs.OutputPermissionscom.google.devtools.build.lib.skyframe.ActionOutputMetadataStore→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.skyframe.ActionOutputMetadataStore→com.google.devtools.build.lib.vfs.XattrProvidercom.google.devtools.build.lib.skyframe.ActionRunner→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.skyframe.ArtifactFunction→com.google.devtools.build.lib.vfs.XattrProvidercom.google.devtools.build.lib.skyframe.BrokenProcessableModifiedFileSet→com.google.devtools.build.lib.vfs.ModifiedFileSetcom.google.devtools.build.lib.skyframe.Builder→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.skyframe.BzlCompileValue→com.google.devtools.build.lib.vfs.Rootcom.google.devtools.build.lib.skyframe.BzlLoadFunction→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.skyframe.BzlLoadFunction→com.google.devtools.build.lib.vfs.Rootcom.google.devtools.build.lib.skyframe.CollectPackagesUnderDirectoryValue→com.google.devtools.build.lib.vfs.RootedPathcom.google.devtools.build.lib.skyframe.CompactSortedDirents→com.google.devtools.build.lib.vfs.Direntcom.google.devtools.build.lib.skyframe.CompactSortedDirents→com.google.devtools.build.lib.vfs.Typecom.google.devtools.build.lib.skyframe.ConfiguredTargetAndData→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.skyframe.ContainingPackage→com.google.devtools.build.lib.vfs.Rootcom.google.devtools.build.lib.skyframe.ContainingPackageLookupValue→com.google.devtools.build.lib.vfs.Rootcom.google.devtools.build.lib.skyframe.DanglingSymlink→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.skyframe.DanglingSymlink→com.google.devtools.build.lib.vfs.RootedPathcom.google.devtools.build.lib.skyframe.DefaultSyscallCache→com.google.devtools.build.lib.vfs.Direntcom.google.devtools.build.lib.skyframe.DefaultSyscallCache→com.google.devtools.build.lib.vfs.FileStatus
- Direction
- com.google.devtools.build.lib.skyframe uses com.google.devtools.build.lib.vfs, so a change to com.google.devtools.build.lib.vfs can break com.google.devtools.build.lib.skyframe, while a change to com.google.devtools.build.lib.skyframe can't break com.google.devtools.build.lib.vfs.
- Position
- Below the diagonal: com.google.devtools.build.lib.skyframe uses a module listed above it, which is the healthy direction.
24→10 com.google.devtools.build.lib.skyframe uses com.google.devtools.build.lib.skyframe.config✕
- Connections
- 21 pairs of types, where a type in com.google.devtools.build.lib.skyframe uses a type in com.google.devtools.build.lib.skyframe.config.
- The types involved
com.google.devtools.build.lib.skyframe.ActionTemplateExpansionKey→com.google.devtools.build.lib.skyframe.config.BuildConfigurationKeycom.google.devtools.build.lib.skyframe.AspectFunction→com.google.devtools.build.lib.skyframe.config.BuildConfigurationKeycom.google.devtools.build.lib.skyframe.AspectKey→com.google.devtools.build.lib.skyframe.config.BuildConfigurationKeycom.google.devtools.build.lib.skyframe.BaseTargetPrerequisitesSupplier→com.google.devtools.build.lib.skyframe.config.BuildConfigurationKeycom.google.devtools.build.lib.skyframe.BaseTargetPrerequisitesSupplierImpl→com.google.devtools.build.lib.skyframe.config.BuildConfigurationKeycom.google.devtools.build.lib.skyframe.BuildDriverFunction→com.google.devtools.build.lib.skyframe.config.BuildConfigurationKeycom.google.devtools.build.lib.skyframe.BuildInfoKey→com.google.devtools.build.lib.skyframe.config.BuildConfigurationKeycom.google.devtools.build.lib.skyframe.ConfiguredTargetAndData→com.google.devtools.build.lib.skyframe.config.BuildConfigurationKeycom.google.devtools.build.lib.skyframe.ConfiguredTargetKey→com.google.devtools.build.lib.skyframe.config.BuildConfigurationKeycom.google.devtools.build.lib.skyframe.ConfiguredTargetKeyValueSharingCodec→com.google.devtools.build.lib.skyframe.config.BuildConfigurationKeycom.google.devtools.build.lib.skyframe.ConfiguredTargetKeyWithFinalConfiguration→com.google.devtools.build.lib.skyframe.config.BuildConfigurationKeycom.google.devtools.build.lib.skyframe.CoverageReportKey→com.google.devtools.build.lib.skyframe.config.BuildConfigurationKeycom.google.devtools.build.lib.skyframe.DependencyResolver→com.google.devtools.build.lib.skyframe.config.BuildConfigurationKeycom.google.devtools.build.lib.skyframe.SequencedSkyframeExecutor→com.google.devtools.build.lib.skyframe.config.BuildConfigurationKeycom.google.devtools.build.lib.skyframe.SkyframeExecutor→com.google.devtools.build.lib.skyframe.config.BuildConfigurationKeycom.google.devtools.build.lib.skyframe.SkyframeExecutor→com.google.devtools.build.lib.skyframe.config.PlatformMappingKeycom.google.devtools.build.lib.skyframe.State→com.google.devtools.build.lib.skyframe.config.BuildConfigurationKeycom.google.devtools.build.lib.skyframe.ToolchainDependencyConfiguredTargetKey→com.google.devtools.build.lib.skyframe.config.BuildConfigurationKeycom.google.devtools.build.lib.skyframe.ToolchainDependencyConfiguredTargetKeyWithFinalConfiguration→com.google.devtools.build.lib.skyframe.config.BuildConfigurationKeycom.google.devtools.build.lib.skyframe.TopLevelAspectsKey→com.google.devtools.build.lib.skyframe.config.BuildConfigurationKeycom.google.devtools.build.lib.skyframe.ToplevelStarlarkAspectFunction→com.google.devtools.build.lib.skyframe.config.BuildConfigurationKey
- Direction
- com.google.devtools.build.lib.skyframe uses com.google.devtools.build.lib.skyframe.config, so a change to com.google.devtools.build.lib.skyframe.config can break com.google.devtools.build.lib.skyframe, while a change to com.google.devtools.build.lib.skyframe can't break com.google.devtools.build.lib.skyframe.config.
- Position
- Below the diagonal: com.google.devtools.build.lib.skyframe uses a module listed above it, which is the healthy direction.
24→11 com.google.devtools.build.lib.skyframe uses com.google.devtools.build.lib.util✕
- Connections
- 40 pairs of types, where a type in com.google.devtools.build.lib.skyframe uses a type in com.google.devtools.build.lib.util. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.google.devtools.build.lib.skyframe.ActionExecutionFunction→com.google.devtools.build.lib.util.DetailedExitCodecom.google.devtools.build.lib.skyframe.ActionExecutionFunction→com.google.devtools.build.lib.util.Paircom.google.devtools.build.lib.skyframe.AggregatingBuilder→com.google.devtools.build.lib.util.DetailedExitCodecom.google.devtools.build.lib.skyframe.ArtifactNestedSetEvalException→com.google.devtools.build.lib.util.Paircom.google.devtools.build.lib.skyframe.AspectCreationException→com.google.devtools.build.lib.util.DetailedExitCodecom.google.devtools.build.lib.skyframe.AspectFunction→com.google.devtools.build.lib.util.OrderedSetMultimapcom.google.devtools.build.lib.skyframe.AspectFunction→com.google.devtools.build.lib.util.Paircom.google.devtools.build.lib.skyframe.BuildDriverFunction→com.google.devtools.build.lib.util.RegexFiltercom.google.devtools.build.lib.skyframe.BzlLoadFailedException→com.google.devtools.build.lib.util.DetailedExitCodecom.google.devtools.build.lib.skyframe.BzlLoadFunction→com.google.devtools.build.lib.util.Fingerprintcom.google.devtools.build.lib.skyframe.BzlLoadFunction→com.google.devtools.build.lib.util.Paircom.google.devtools.build.lib.skyframe.ClassifiedError→com.google.devtools.build.lib.util.DetailedExitCodecom.google.devtools.build.lib.skyframe.CompletionFunction→com.google.devtools.build.lib.util.DetailedExitCodecom.google.devtools.build.lib.skyframe.CompletionFunction→com.google.devtools.build.lib.util.Paircom.google.devtools.build.lib.skyframe.ConfiguredTargetFunction→com.google.devtools.build.lib.util.DetailedExitCodecom.google.devtools.build.lib.skyframe.ConfiguredTargetFunction→com.google.devtools.build.lib.util.OrderedSetMultimapcom.google.devtools.build.lib.skyframe.ConfiguredValueCreationException→com.google.devtools.build.lib.util.DetailedExitCodecom.google.devtools.build.lib.skyframe.CycleUtils→com.google.devtools.build.lib.util.Paircom.google.devtools.build.lib.skyframe.DependencyResolver→com.google.devtools.build.lib.util.DetailedExitCodecom.google.devtools.build.lib.skyframe.DependencyResolver→com.google.devtools.build.lib.util.OrderedSetMultimapcom.google.devtools.build.lib.skyframe.DetailedException→com.google.devtools.build.lib.util.DetailedExitCodecom.google.devtools.build.lib.skyframe.DirectoryTreeDigestFunction→com.google.devtools.build.lib.util.Paircom.google.devtools.build.lib.skyframe.ErrorProcessingResult→com.google.devtools.build.lib.util.DetailedExitCodecom.google.devtools.build.lib.skyframe.MissingArtifactValue→com.google.devtools.build.lib.util.DetailedExitCodecom.google.devtools.build.lib.skyframe.PackageFunction→com.google.devtools.build.lib.util.Pair
- Direction
- com.google.devtools.build.lib.skyframe uses com.google.devtools.build.lib.util, so a change to com.google.devtools.build.lib.util can break com.google.devtools.build.lib.skyframe, while a change to com.google.devtools.build.lib.skyframe can't break com.google.devtools.build.lib.util.
- Position
- Below the diagonal: com.google.devtools.build.lib.skyframe uses a module listed above it, which is the healthy direction.
24→13 com.google.devtools.build.lib.skyframe uses com.google.devtools.build.lib.bazel.bzlmod✕
- Connections
- 3 pairs of types, where a type in com.google.devtools.build.lib.skyframe uses a type in com.google.devtools.build.lib.bazel.bzlmod.
- The types involved
com.google.devtools.build.lib.skyframe.RepositoryMappingFunction→com.google.devtools.build.lib.bazel.bzlmod.BazelDepGraphValuecom.google.devtools.build.lib.skyframe.RepositoryMappingFunction→com.google.devtools.build.lib.bazel.bzlmod.ModuleExtensionIdcom.google.devtools.build.lib.skyframe.RepositoryMappingValue→com.google.devtools.build.lib.bazel.bzlmod.Version
- Direction
- com.google.devtools.build.lib.skyframe uses com.google.devtools.build.lib.bazel.bzlmod, so a change to com.google.devtools.build.lib.bazel.bzlmod can break com.google.devtools.build.lib.skyframe, while a change to com.google.devtools.build.lib.skyframe can't break com.google.devtools.build.lib.bazel.bzlmod.
- Position
- Below the diagonal: com.google.devtools.build.lib.skyframe uses a module listed above it, which is the healthy direction.
24→14 com.google.devtools.build.lib.skyframe uses com.google.devtools.build.lib.buildeventstream✕
- Connections
- 2 pairs of types, where a type in com.google.devtools.build.lib.skyframe uses a type in com.google.devtools.build.lib.buildeventstream.
- The types involved
com.google.devtools.build.lib.skyframe.PatternExpandingError→com.google.devtools.build.lib.buildeventstream.BuildEventcom.google.devtools.build.lib.skyframe.PatternExpandingError→com.google.devtools.build.lib.buildeventstream.BuildEventContext
- Direction
- com.google.devtools.build.lib.skyframe uses com.google.devtools.build.lib.buildeventstream, so a change to com.google.devtools.build.lib.buildeventstream can break com.google.devtools.build.lib.skyframe, while a change to com.google.devtools.build.lib.skyframe can't break com.google.devtools.build.lib.buildeventstream.
- Position
- Below the diagonal: com.google.devtools.build.lib.skyframe uses a module listed above it, which is the healthy direction.
24→16 com.google.devtools.build.lib.skyframe uses com.google.devtools.build.lib.query2.common✕
- Connections
- 5 pairs of types, where a type in com.google.devtools.build.lib.skyframe uses a type in com.google.devtools.build.lib.query2.common.
- The types involved
com.google.devtools.build.lib.skyframe.AspectKey→com.google.devtools.build.lib.query2.common.CqueryNodecom.google.devtools.build.lib.skyframe.ConfiguredTargetKey→com.google.devtools.build.lib.query2.common.CqueryNodecom.google.devtools.build.lib.skyframe.SkyframeExecutor→com.google.devtools.build.lib.query2.common.QueryTransitivePackagePreloadercom.google.devtools.build.lib.skyframe.SkyframeExecutor→com.google.devtools.build.lib.query2.common.UniverseScopecom.google.devtools.build.lib.skyframe.TargetPatternSequence→com.google.devtools.build.lib.query2.common.UniverseSkyKey
- Direction
- com.google.devtools.build.lib.skyframe uses com.google.devtools.build.lib.query2.common, so a change to com.google.devtools.build.lib.query2.common can break com.google.devtools.build.lib.skyframe, while a change to com.google.devtools.build.lib.skyframe can't break com.google.devtools.build.lib.query2.common.
- Position
- Below the diagonal: com.google.devtools.build.lib.skyframe uses a module listed above it, which is the healthy direction.
24→18 com.google.devtools.build.lib.skyframe uses com.google.devtools.build.lib.pkgcache✕
- Connections
- 37 pairs of types, where a type in com.google.devtools.build.lib.skyframe uses a type in com.google.devtools.build.lib.pkgcache. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.google.devtools.build.lib.skyframe.AbstractLabelCycleReporter→com.google.devtools.build.lib.pkgcache.PackageProvidercom.google.devtools.build.lib.skyframe.ActionArtifactCycleReporter→com.google.devtools.build.lib.pkgcache.PackageProvidercom.google.devtools.build.lib.skyframe.CollectTargetsInPackageKey→com.google.devtools.build.lib.pkgcache.FilteringPolicycom.google.devtools.build.lib.skyframe.CollectTargetsInPackageValue→com.google.devtools.build.lib.pkgcache.FilteringPolicycom.google.devtools.build.lib.skyframe.DepsOfPatternPreparer→com.google.devtools.build.lib.pkgcache.FilteringPolicycom.google.devtools.build.lib.skyframe.DepsOfPatternPreparer→com.google.devtools.build.lib.pkgcache.PathPackageLocatorcom.google.devtools.build.lib.skyframe.EnvironmentBackedRecursivePackageProvider→com.google.devtools.build.lib.pkgcache.AbstractRecursivePackageProvidercom.google.devtools.build.lib.skyframe.ExternalFilesHelper→com.google.devtools.build.lib.pkgcache.PathPackageLocatorcom.google.devtools.build.lib.skyframe.FileFunction→com.google.devtools.build.lib.pkgcache.PathPackageLocatorcom.google.devtools.build.lib.skyframe.GetTargetsInPackagesTask→com.google.devtools.build.lib.pkgcache.FilteringPolicycom.google.devtools.build.lib.skyframe.GraphBackedRecursivePackageProvider→com.google.devtools.build.lib.pkgcache.AbstractRecursivePackageProvidercom.google.devtools.build.lib.skyframe.GraphBackedRecursivePackageProvider→com.google.devtools.build.lib.pkgcache.PathPackageLocatorcom.google.devtools.build.lib.skyframe.PackageLookupFunction→com.google.devtools.build.lib.pkgcache.PathPackageLocatorcom.google.devtools.build.lib.skyframe.PrecomputedValue→com.google.devtools.build.lib.pkgcache.PathPackageLocatorcom.google.devtools.build.lib.skyframe.PrepareDepsOfPatternFunction→com.google.devtools.build.lib.pkgcache.PathPackageLocatorcom.google.devtools.build.lib.skyframe.PrepareDepsOfTargetsUnderDirectoryKey→com.google.devtools.build.lib.pkgcache.FilteringPolicycom.google.devtools.build.lib.skyframe.PrepareDepsOfTargetsUnderDirectoryValue→com.google.devtools.build.lib.pkgcache.FilteringPolicycom.google.devtools.build.lib.skyframe.RecursivePackageProviderBackedTargetPatternResolver→com.google.devtools.build.lib.pkgcache.FilteringPolicycom.google.devtools.build.lib.skyframe.RecursivePackageProviderBackedTargetPatternResolver→com.google.devtools.build.lib.pkgcache.RecursivePackageProvidercom.google.devtools.build.lib.skyframe.SequencedSkyframeExecutor→com.google.devtools.build.lib.pkgcache.PathPackageLocatorcom.google.devtools.build.lib.skyframe.SkyframeExecutor→com.google.devtools.build.lib.pkgcache.LoadingOptionscom.google.devtools.build.lib.skyframe.SkyframeExecutor→com.google.devtools.build.lib.pkgcache.PackageManagercom.google.devtools.build.lib.skyframe.SkyframeExecutor→com.google.devtools.build.lib.pkgcache.PackageOptionscom.google.devtools.build.lib.skyframe.SkyframeExecutor→com.google.devtools.build.lib.pkgcache.PathPackageLocatorcom.google.devtools.build.lib.skyframe.SkyframePackageManager→com.google.devtools.build.lib.pkgcache.PackageManager
- Direction
- com.google.devtools.build.lib.skyframe uses com.google.devtools.build.lib.pkgcache, so a change to com.google.devtools.build.lib.pkgcache can break com.google.devtools.build.lib.skyframe, while a change to com.google.devtools.build.lib.skyframe can't break com.google.devtools.build.lib.pkgcache.
- Position
- Below the diagonal: com.google.devtools.build.lib.skyframe uses a module listed above it, which is the healthy direction.
24→19 com.google.devtools.build.lib.skyframe uses com.google.devtools.build.lib.skyframe.serialization.analysis✕
- Connections
- 12 pairs of types, where a type in com.google.devtools.build.lib.skyframe uses a type in com.google.devtools.build.lib.skyframe.serialization.analysis.
- The types involved
com.google.devtools.build.lib.skyframe.ActionExecutionFunction→com.google.devtools.build.lib.skyframe.serialization.analysis.RemoteAnalysisCacheReaderDepsProvidercom.google.devtools.build.lib.skyframe.ActionLookupConflictFindingFunction→com.google.devtools.build.lib.skyframe.serialization.analysis.RemoteAnalysisCacheReaderDepsProvidercom.google.devtools.build.lib.skyframe.ArtifactFunction→com.google.devtools.build.lib.skyframe.serialization.analysis.RemoteAnalysisCacheReaderDepsProvidercom.google.devtools.build.lib.skyframe.AspectFunction→com.google.devtools.build.lib.skyframe.serialization.analysis.RemoteAnalysisCacheReaderDepsProvidercom.google.devtools.build.lib.skyframe.ConfiguredTargetFunction→com.google.devtools.build.lib.skyframe.serialization.analysis.RemoteAnalysisCacheModecom.google.devtools.build.lib.skyframe.ConfiguredTargetFunction→com.google.devtools.build.lib.skyframe.serialization.analysis.RemoteAnalysisCacheReaderDepsProvidercom.google.devtools.build.lib.skyframe.SkyValueRetrieverUtils→com.google.devtools.build.lib.skyframe.serialization.analysis.RemoteAnalysisCacheReaderDepsProvidercom.google.devtools.build.lib.skyframe.SkyframeExecutor→com.google.devtools.build.lib.skyframe.serialization.analysis.ClientIdcom.google.devtools.build.lib.skyframe.SkyframeExecutor→com.google.devtools.build.lib.skyframe.serialization.analysis.RemoteAnalysisCacheReaderDepsProvidercom.google.devtools.build.lib.skyframe.SkyframeExecutor→com.google.devtools.build.lib.skyframe.serialization.analysis.RemoteAnalysisCachingDependenciesProvidercom.google.devtools.build.lib.skyframe.SkyframeExecutor→com.google.devtools.build.lib.skyframe.serialization.analysis.RemoteAnalysisCachingServerStatecom.google.devtools.build.lib.skyframe.WorkspaceInfoFromDiff→com.google.devtools.build.lib.skyframe.serialization.analysis.ClientId
- Direction
- com.google.devtools.build.lib.skyframe uses com.google.devtools.build.lib.skyframe.serialization.analysis, so a change to com.google.devtools.build.lib.skyframe.serialization.analysis can break com.google.devtools.build.lib.skyframe, while a change to com.google.devtools.build.lib.skyframe can't break com.google.devtools.build.lib.skyframe.serialization.analysis.
- Position
- Below the diagonal: com.google.devtools.build.lib.skyframe uses a module listed above it, which is the healthy direction.
24→23 com.google.devtools.build.lib.skyframe uses com.google.devtools.build.lib.buildtool✕
- Connections
- 1 pair of types, where a type in com.google.devtools.build.lib.skyframe uses a type in com.google.devtools.build.lib.buildtool.
- The types involved
com.google.devtools.build.lib.skyframe.SkymeldModule→com.google.devtools.build.lib.buildtool.BuildRequestOptions
- Direction
- com.google.devtools.build.lib.skyframe uses com.google.devtools.build.lib.buildtool, so a change to com.google.devtools.build.lib.buildtool can break com.google.devtools.build.lib.skyframe, while a change to com.google.devtools.build.lib.skyframe can't break com.google.devtools.build.lib.buildtool.
- Position
- Below the diagonal: com.google.devtools.build.lib.skyframe uses a module listed above it, which is the healthy direction.
24→25 com.google.devtools.build.lib.skyframe uses com.google.devtools.build.lib.packages part of a loop✕
- Connections
- 196 pairs of types, where a type in com.google.devtools.build.lib.skyframe uses a type in com.google.devtools.build.lib.packages. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.google.devtools.build.lib.skyframe.5→com.google.devtools.build.lib.packages.NoSuchThingExceptioncom.google.devtools.build.lib.skyframe.AbstractLabelCycleReporter→com.google.devtools.build.lib.packages.Targetcom.google.devtools.build.lib.skyframe.AspectFunction→com.google.devtools.build.lib.packages.Aspectcom.google.devtools.build.lib.skyframe.AspectFunction→com.google.devtools.build.lib.packages.AspectDefinitioncom.google.devtools.build.lib.skyframe.AspectFunction→com.google.devtools.build.lib.packages.RuleClassProvidercom.google.devtools.build.lib.skyframe.AspectFunction→com.google.devtools.build.lib.packages.StarlarkAspectClasscom.google.devtools.build.lib.skyframe.AspectFunction→com.google.devtools.build.lib.packages.StarlarkDefinedAspectcom.google.devtools.build.lib.skyframe.AspectFunction→com.google.devtools.build.lib.packages.Targetcom.google.devtools.build.lib.skyframe.AspectFunctionException→com.google.devtools.build.lib.packages.NoSuchThingExceptioncom.google.devtools.build.lib.skyframe.AspectKey→com.google.devtools.build.lib.packages.AspectClasscom.google.devtools.build.lib.skyframe.AspectKey→com.google.devtools.build.lib.packages.AspectDescriptorcom.google.devtools.build.lib.skyframe.AspectKey→com.google.devtools.build.lib.packages.AspectParameterscom.google.devtools.build.lib.skyframe.AspectKey→com.google.devtools.build.lib.packages.LabelPrintercom.google.devtools.build.lib.skyframe.AspectKeyCreator→com.google.devtools.build.lib.packages.AspectClasscom.google.devtools.build.lib.skyframe.AspectKeyCreator→com.google.devtools.build.lib.packages.AspectDescriptorcom.google.devtools.build.lib.skyframe.AspectKeyWithBaseAspects→com.google.devtools.build.lib.packages.AspectDescriptorcom.google.devtools.build.lib.skyframe.BazelSkyframeExecutorConstants→com.google.devtools.build.lib.packages.BuildFileNamecom.google.devtools.build.lib.skyframe.BuildDriverFunction→com.google.devtools.build.lib.packages.Targetcom.google.devtools.build.lib.skyframe.BuildOptionsScopeFunction→com.google.devtools.build.lib.packages.Targetcom.google.devtools.build.lib.skyframe.BzlCompileFunction→com.google.devtools.build.lib.packages.BazelStarlarkEnvironmentcom.google.devtools.build.lib.skyframe.BzlCompileFunction→com.google.devtools.build.lib.packages.PackageLoadingListenercom.google.devtools.build.lib.skyframe.BzlLoadFunction→com.google.devtools.build.lib.packages.BzlInitThreadContextcom.google.devtools.build.lib.skyframe.BzlLoadFunction→com.google.devtools.build.lib.packages.PackageLoadingListenercom.google.devtools.build.lib.skyframe.BzlLoadFunction→com.google.devtools.build.lib.packages.RuleClassProvidercom.google.devtools.build.lib.skyframe.BzlLoadValue→com.google.devtools.build.lib.packages.BzlVisibility
- Direction
- com.google.devtools.build.lib.skyframe uses com.google.devtools.build.lib.packages, so a change to com.google.devtools.build.lib.packages can break com.google.devtools.build.lib.skyframe, while a change to com.google.devtools.build.lib.skyframe can't break com.google.devtools.build.lib.packages.
- 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→26 com.google.devtools.build.lib.skyframe uses com.google.devtools.build.lib.analysis.starlark part of a loop✕
- Connections
- 3 pairs of types, where a type in com.google.devtools.build.lib.skyframe uses a type in com.google.devtools.build.lib.analysis.starlark.
- The types involved
com.google.devtools.build.lib.skyframe.AspectFunction→com.google.devtools.build.lib.analysis.starlark.StarlarkAttributeTransitionProvidercom.google.devtools.build.lib.skyframe.DependencyResolver→com.google.devtools.build.lib.analysis.starlark.StarlarkAttributeTransitionProvidercom.google.devtools.build.lib.skyframe.SkyframeExecutor→com.google.devtools.build.lib.analysis.starlark.StarlarkAttributeTransitionProvider
- Direction
- com.google.devtools.build.lib.skyframe uses com.google.devtools.build.lib.analysis.starlark, so a change to com.google.devtools.build.lib.analysis.starlark can break com.google.devtools.build.lib.skyframe, while a change to com.google.devtools.build.lib.skyframe can't break com.google.devtools.build.lib.analysis.starlark.
- 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→28 com.google.devtools.build.lib.skyframe uses com.google.devtools.build.lib.runtime part of a loop✕
- Connections
- 6 pairs of types, where a type in com.google.devtools.build.lib.skyframe uses a type in com.google.devtools.build.lib.runtime.
- The types involved
com.google.devtools.build.lib.skyframe.FsEventsNativeDepsService→com.google.devtools.build.lib.runtime.BlazeServicecom.google.devtools.build.lib.skyframe.HighWaterMarkLimiter→com.google.devtools.build.lib.runtime.MemoryPressureEventcom.google.devtools.build.lib.skyframe.HighWaterMarkLimiter→com.google.devtools.build.lib.runtime.MemoryPressureOptionscom.google.devtools.build.lib.skyframe.SkyframeTargetLoader→com.google.devtools.build.lib.runtime.BuildSettingLoadercom.google.devtools.build.lib.skyframe.SkymeldModule→com.google.devtools.build.lib.runtime.BlazeModulecom.google.devtools.build.lib.skyframe.SkymeldModule→com.google.devtools.build.lib.runtime.CommandEnvironment
- Direction
- com.google.devtools.build.lib.skyframe uses com.google.devtools.build.lib.runtime, so a change to com.google.devtools.build.lib.runtime can break com.google.devtools.build.lib.skyframe, while a change to com.google.devtools.build.lib.skyframe can't break com.google.devtools.build.lib.runtime.
- 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→29 com.google.devtools.build.lib.skyframe uses com.google.devtools.build.lib.skyframe.serialization part of a loop✕
- Connections
- 22 pairs of types, where a type in com.google.devtools.build.lib.skyframe uses a type in com.google.devtools.build.lib.skyframe.serialization.
- The types involved
com.google.devtools.build.lib.skyframe.BzlLoadThreadOwner→com.google.devtools.build.lib.skyframe.serialization.DeferredObjectCodeccom.google.devtools.build.lib.skyframe.Codec→com.google.devtools.build.lib.skyframe.serialization.AsyncDeserializationContextcom.google.devtools.build.lib.skyframe.Codec→com.google.devtools.build.lib.skyframe.serialization.DeferredObjectCodeccom.google.devtools.build.lib.skyframe.Codec→com.google.devtools.build.lib.skyframe.serialization.SerializationContextcom.google.devtools.build.lib.skyframe.ConfiguredTargetKey→com.google.devtools.build.lib.skyframe.serialization.DeferredObjectCodeccom.google.devtools.build.lib.skyframe.ConfiguredTargetKeyCodec→com.google.devtools.build.lib.skyframe.serialization.AsyncDeserializationContextcom.google.devtools.build.lib.skyframe.ConfiguredTargetKeyCodec→com.google.devtools.build.lib.skyframe.serialization.DeferredObjectCodeccom.google.devtools.build.lib.skyframe.ConfiguredTargetKeyCodec→com.google.devtools.build.lib.skyframe.serialization.SerializationContextcom.google.devtools.build.lib.skyframe.ConfiguredTargetKeyValueSharingCodec→com.google.devtools.build.lib.skyframe.serialization.AsyncDeserializationContextcom.google.devtools.build.lib.skyframe.ConfiguredTargetKeyValueSharingCodec→com.google.devtools.build.lib.skyframe.serialization.DeferredObjectCodeccom.google.devtools.build.lib.skyframe.ConfiguredTargetKeyValueSharingCodec→com.google.devtools.build.lib.skyframe.serialization.SerializationContextcom.google.devtools.build.lib.skyframe.ConfiguredTargetValueCodec→com.google.devtools.build.lib.skyframe.serialization.AsyncDeserializationContextcom.google.devtools.build.lib.skyframe.ConfiguredTargetValueCodec→com.google.devtools.build.lib.skyframe.serialization.DeferredObjectCodeccom.google.devtools.build.lib.skyframe.ConfiguredTargetValueCodec→com.google.devtools.build.lib.skyframe.serialization.SerializationContextcom.google.devtools.build.lib.skyframe.KeyCodec→com.google.devtools.build.lib.skyframe.serialization.LeafDeserializationContextcom.google.devtools.build.lib.skyframe.KeyCodec→com.google.devtools.build.lib.skyframe.serialization.LeafObjectCodeccom.google.devtools.build.lib.skyframe.KeyCodec→com.google.devtools.build.lib.skyframe.serialization.LeafSerializationContextcom.google.devtools.build.lib.skyframe.RemoteConfiguredTargetValue→com.google.devtools.build.lib.skyframe.serialization.DeserializedSkyValuecom.google.devtools.build.lib.skyframe.SkyframeExecutor→com.google.devtools.build.lib.skyframe.serialization.FrontierNodeVersioncom.google.devtools.build.lib.skyframe.TreeArtifactValueCodec→com.google.devtools.build.lib.skyframe.serialization.AsyncDeserializationContextcom.google.devtools.build.lib.skyframe.TreeArtifactValueCodec→com.google.devtools.build.lib.skyframe.serialization.DeferredObjectCodeccom.google.devtools.build.lib.skyframe.TreeArtifactValueCodec→com.google.devtools.build.lib.skyframe.serialization.SerializationContext
- Direction
- com.google.devtools.build.lib.skyframe uses com.google.devtools.build.lib.skyframe.serialization, so a change to com.google.devtools.build.lib.skyframe.serialization can break com.google.devtools.build.lib.skyframe, while a change to com.google.devtools.build.lib.skyframe can't break com.google.devtools.build.lib.skyframe.serialization.
- 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→30 com.google.devtools.build.lib.skyframe uses com.google.devtools.build.lib.collect.nestedset part of a loop✕
- Connections
- 41 pairs of types, where a type in com.google.devtools.build.lib.skyframe uses a type in com.google.devtools.build.lib.collect.nestedset. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.google.devtools.build.lib.skyframe.AbstractConfiguredTargetValue→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.skyframe.ActionExecutionFunction→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.skyframe.ActionExecutionFunctionExceptionHandler→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.skyframe.ActionExecutionValue→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.skyframe.ActionInputCollectedEvent→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.skyframe.ActionLookupConflictFindingFunction→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.skyframe.AllInputs→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.skyframe.ArtifactNestedSetEvalException→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.skyframe.AspectCompletor→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.skyframe.AspectCreationException→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.skyframe.BuildResultListener→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.skyframe.ClassifiedError→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.skyframe.CompletionFunction→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.skyframe.CompletionFunction→com.google.devtools.build.lib.collect.nestedset.NestedSetBuildercom.google.devtools.build.lib.skyframe.Completor→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.skyframe.ConfiguredTargetFunction→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.skyframe.ConfiguredValueCreationException→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.skyframe.DependencyResolver→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.skyframe.GlobFunctionWithMultipleRecursiveFunctions→com.google.devtools.build.lib.collect.nestedset.NestedSetBuildercom.google.devtools.build.lib.skyframe.GlobValueWithNestedSet→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.skyframe.IncrementalPackageRoots→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.skyframe.IncrementalPackageRoots→com.google.devtools.build.lib.collect.nestedset.Nodecom.google.devtools.build.lib.skyframe.InputDiscoveryState→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.skyframe.ModuleDiscovering→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.skyframe.MyPackageDirectoryConsumer→com.google.devtools.build.lib.collect.nestedset.NestedSet
- Direction
- com.google.devtools.build.lib.skyframe uses com.google.devtools.build.lib.collect.nestedset, so a change to com.google.devtools.build.lib.collect.nestedset can break com.google.devtools.build.lib.skyframe, while a change to com.google.devtools.build.lib.skyframe can't break com.google.devtools.build.lib.collect.nestedset.
- 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→31 com.google.devtools.build.lib.skyframe uses com.google.devtools.build.lib.cmdline part of a loop✕
- Connections
- 224 pairs of types, where a type in com.google.devtools.build.lib.skyframe uses a type in com.google.devtools.build.lib.cmdline. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.google.devtools.build.lib.skyframe.AbstractLabelCycleReporter→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.skyframe.ActionArtifactCycleReporter→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.skyframe.ActionExecutionFunction→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.skyframe.ActionTemplateExpansionKey→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.skyframe.AspectCreationException→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.skyframe.AspectFunction→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.skyframe.AspectKey→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.skyframe.AspectKeyCreator→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.skyframe.BuildDriverFunction→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.skyframe.BuildInfoKey→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.skyframe.BuildOptionsScopeFunction→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.skyframe.BuildOptionsScopeFunction→com.google.devtools.build.lib.cmdline.PackageIdentifiercom.google.devtools.build.lib.skyframe.BuildOptionsScopeFunctionException→com.google.devtools.build.lib.cmdline.TargetParsingExceptioncom.google.devtools.build.lib.skyframe.BuildOptionsScopeValue→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.skyframe.BzlCompileFunction→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.skyframe.BzlCompileValue→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.skyframe.BzlLoadFunction→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.skyframe.BzlLoadFunction→com.google.devtools.build.lib.cmdline.PackageIdentifiercom.google.devtools.build.lib.skyframe.BzlLoadFunction→com.google.devtools.build.lib.cmdline.RepoMappingRecordercom.google.devtools.build.lib.skyframe.BzlLoadFunction→com.google.devtools.build.lib.cmdline.RepositoryMappingcom.google.devtools.build.lib.skyframe.BzlLoadValue→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.skyframe.BzlLoadValue→com.google.devtools.build.lib.cmdline.RepositoryNamecom.google.devtools.build.lib.skyframe.ClassifiedError→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.skyframe.CollectPackagesUnderDirectoryValue→com.google.devtools.build.lib.cmdline.IgnoredSubdirectoriescom.google.devtools.build.lib.skyframe.CollectPackagesUnderDirectoryValue→com.google.devtools.build.lib.cmdline.RepositoryName
- Direction
- com.google.devtools.build.lib.skyframe uses com.google.devtools.build.lib.cmdline, so a change to com.google.devtools.build.lib.cmdline can break com.google.devtools.build.lib.skyframe, while a change to com.google.devtools.build.lib.skyframe can't break com.google.devtools.build.lib.cmdline.
- 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→32 com.google.devtools.build.lib.skyframe uses com.google.devtools.build.lib.analysis.platform part of a loop✕
- Connections
- 1 pair of types, where a type in com.google.devtools.build.lib.skyframe uses a type in com.google.devtools.build.lib.analysis.platform.
- The types involved
com.google.devtools.build.lib.skyframe.DependencyResolver→com.google.devtools.build.lib.analysis.platform.PlatformInfo
- Direction
- com.google.devtools.build.lib.skyframe uses com.google.devtools.build.lib.analysis.platform, so a change to com.google.devtools.build.lib.analysis.platform can break com.google.devtools.build.lib.skyframe, while a change to com.google.devtools.build.lib.skyframe can't break com.google.devtools.build.lib.analysis.platform.
- 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→33 com.google.devtools.build.lib.skyframe uses com.google.devtools.build.lib.analysis.config part of a loop✕
- Connections
- 29 pairs of types, where a type in com.google.devtools.build.lib.skyframe uses a type in com.google.devtools.build.lib.analysis.config. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.google.devtools.build.lib.skyframe.AspectCreationException→com.google.devtools.build.lib.analysis.config.BuildConfigurationValuecom.google.devtools.build.lib.skyframe.AspectFunction→com.google.devtools.build.lib.analysis.config.BuildConfigurationValuecom.google.devtools.build.lib.skyframe.AspectFunction→com.google.devtools.build.lib.analysis.config.ConfigConditionscom.google.devtools.build.lib.skyframe.AspectKeyCreator→com.google.devtools.build.lib.analysis.config.BuildConfigurationValuecom.google.devtools.build.lib.skyframe.BaseTargetPrerequisitesSupplier→com.google.devtools.build.lib.analysis.config.BuildConfigurationValuecom.google.devtools.build.lib.skyframe.BaseTargetPrerequisitesSupplierImpl→com.google.devtools.build.lib.analysis.config.BuildConfigurationValuecom.google.devtools.build.lib.skyframe.BaselineConfigurations→com.google.devtools.build.lib.analysis.config.BuildOptionscom.google.devtools.build.lib.skyframe.BuildDriverFunction→com.google.devtools.build.lib.analysis.config.BuildConfigurationValuecom.google.devtools.build.lib.skyframe.BuildOptionsScopeFunction→com.google.devtools.build.lib.analysis.config.Scopecom.google.devtools.build.lib.skyframe.BuildOptionsScopeValue→com.google.devtools.build.lib.analysis.config.BuildOptionscom.google.devtools.build.lib.skyframe.BuildOptionsScopeValue→com.google.devtools.build.lib.analysis.config.Scopecom.google.devtools.build.lib.skyframe.ConfiguredTargetAndData→com.google.devtools.build.lib.analysis.config.BuildConfigurationValuecom.google.devtools.build.lib.skyframe.ConfiguredTargetFunction→com.google.devtools.build.lib.analysis.config.ConfigConditionscom.google.devtools.build.lib.skyframe.DependencyResolver→com.google.devtools.build.lib.analysis.config.BuildConfigurationValuecom.google.devtools.build.lib.skyframe.DependencyResolver→com.google.devtools.build.lib.analysis.config.ConfigConditionscom.google.devtools.build.lib.skyframe.DependencyResolver→com.google.devtools.build.lib.analysis.config.DependencyEvaluationExceptioncom.google.devtools.build.lib.skyframe.DependencyResolver→com.google.devtools.build.lib.analysis.config.StarlarkTransitionCachecom.google.devtools.build.lib.skyframe.SkyframeBuildView→com.google.devtools.build.lib.analysis.config.AdditionalConfigurationChangeEventcom.google.devtools.build.lib.skyframe.SkyframeBuildView→com.google.devtools.build.lib.analysis.config.BuildConfigurationValuecom.google.devtools.build.lib.skyframe.SkyframeBuildView→com.google.devtools.build.lib.analysis.config.BuildOptionscom.google.devtools.build.lib.skyframe.SkyframeBuildView→com.google.devtools.build.lib.analysis.config.ConfigConditionscom.google.devtools.build.lib.skyframe.SkyframeBuildView→com.google.devtools.build.lib.analysis.config.OptionsDiffcom.google.devtools.build.lib.skyframe.SkyframeBuildView→com.google.devtools.build.lib.analysis.config.StarlarkTransitionCachecom.google.devtools.build.lib.skyframe.SkyframeExecutor→com.google.devtools.build.lib.analysis.config.BuildConfigurationValuecom.google.devtools.build.lib.skyframe.SkyframeExecutor→com.google.devtools.build.lib.analysis.config.BuildOptions
- Direction
- com.google.devtools.build.lib.skyframe uses com.google.devtools.build.lib.analysis.config, so a change to com.google.devtools.build.lib.analysis.config can break com.google.devtools.build.lib.skyframe, while a change to com.google.devtools.build.lib.skyframe can't break com.google.devtools.build.lib.analysis.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.
24→35 com.google.devtools.build.lib.skyframe uses com.google.devtools.build.lib.analysis part of a loop✕
- Connections
- 127 pairs of types, where a type in com.google.devtools.build.lib.skyframe uses a type in com.google.devtools.build.lib.analysis. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.google.devtools.build.lib.skyframe.3→com.google.devtools.build.lib.analysis.Environmentcom.google.devtools.build.lib.skyframe.5→com.google.devtools.build.lib.analysis.InconsistentNullConfigExceptioncom.google.devtools.build.lib.skyframe.AbstractConfiguredTargetValue→com.google.devtools.build.lib.analysis.ConfiguredTargetValuecom.google.devtools.build.lib.skyframe.ActionExecutionFunction→com.google.devtools.build.lib.analysis.BlazeDirectoriescom.google.devtools.build.lib.skyframe.AspectAnalyzedEvent→com.google.devtools.build.lib.analysis.ConfiguredAspectcom.google.devtools.build.lib.skyframe.AspectCompletionKey→com.google.devtools.build.lib.analysis.TopLevelArtifactContextcom.google.devtools.build.lib.skyframe.AspectCompletionValue→com.google.devtools.build.lib.analysis.TopLevelArtifactContextcom.google.devtools.build.lib.skyframe.AspectCompletor→com.google.devtools.build.lib.analysis.AspectCompleteEventcom.google.devtools.build.lib.skyframe.AspectCompletor→com.google.devtools.build.lib.analysis.AspectValuecom.google.devtools.build.lib.skyframe.AspectFunction→com.google.devtools.build.lib.analysis.AspectBaseTargetResolvedToolchainContextcom.google.devtools.build.lib.skyframe.AspectFunction→com.google.devtools.build.lib.analysis.AspectValuecom.google.devtools.build.lib.skyframe.AspectFunction→com.google.devtools.build.lib.analysis.Buildercom.google.devtools.build.lib.skyframe.AspectFunction→com.google.devtools.build.lib.analysis.ConfiguredAspectFactorycom.google.devtools.build.lib.skyframe.AspectFunction→com.google.devtools.build.lib.analysis.ConfiguredTargetcom.google.devtools.build.lib.skyframe.AspectFunction→com.google.devtools.build.lib.analysis.DependencyKindcom.google.devtools.build.lib.skyframe.AspectFunction→com.google.devtools.build.lib.analysis.ResolvedToolchainContextcom.google.devtools.build.lib.skyframe.AspectFunction→com.google.devtools.build.lib.analysis.TargetAndConfigurationcom.google.devtools.build.lib.skyframe.AspectFunction→com.google.devtools.build.lib.analysis.ToolchainCollectioncom.google.devtools.build.lib.skyframe.AspectFunction→com.google.devtools.build.lib.analysis.TransitiveDependencyStatecom.google.devtools.build.lib.skyframe.BaseTargetPrerequisitesSupplier→com.google.devtools.build.lib.analysis.ConfiguredTargetValuecom.google.devtools.build.lib.skyframe.BaseTargetPrerequisitesSupplierImpl→com.google.devtools.build.lib.analysis.ConfiguredTargetValuecom.google.devtools.build.lib.skyframe.BuildDriverFunction→com.google.devtools.build.lib.analysis.ConfiguredTargetcom.google.devtools.build.lib.skyframe.BuildDriverFunction→com.google.devtools.build.lib.analysis.ConfiguredTargetValuecom.google.devtools.build.lib.skyframe.BuildDriverFunction→com.google.devtools.build.lib.analysis.ExtraActionArtifactsProvidercom.google.devtools.build.lib.skyframe.BuildDriverFunction→com.google.devtools.build.lib.analysis.TopLevelArtifactContext
- Direction
- com.google.devtools.build.lib.skyframe uses com.google.devtools.build.lib.analysis, so a change to com.google.devtools.build.lib.analysis can break com.google.devtools.build.lib.skyframe, while a change to com.google.devtools.build.lib.skyframe can't break com.google.devtools.build.lib.analysis.
- 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→37 com.google.devtools.build.lib.skyframe uses com.google.devtools.build.lib.actions part of a loop✕
- Connections
- 310 pairs of types, where a type in com.google.devtools.build.lib.skyframe uses a type in com.google.devtools.build.lib.actions. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.google.devtools.build.lib.skyframe.1→com.google.devtools.build.lib.actions.FileArtifactValuecom.google.devtools.build.lib.skyframe.3→com.google.devtools.build.lib.actions.Artifactcom.google.devtools.build.lib.skyframe.ActionArtifactCycleReporter→com.google.devtools.build.lib.actions.Artifactcom.google.devtools.build.lib.skyframe.ActionCompletedReceiver→com.google.devtools.build.lib.actions.ActionLookupDatacom.google.devtools.build.lib.skyframe.ActionConflictFunctionException→com.google.devtools.build.lib.actions.ActionConflictExceptioncom.google.devtools.build.lib.skyframe.ActionConflictsAndStats→com.google.devtools.build.lib.actions.ActionAnalysisMetadatacom.google.devtools.build.lib.skyframe.ActionConflictsAndStats→com.google.devtools.build.lib.actions.ActionConflictExceptioncom.google.devtools.build.lib.skyframe.ActionExecutionFunction→com.google.devtools.build.lib.actions.Actioncom.google.devtools.build.lib.skyframe.ActionExecutionFunction→com.google.devtools.build.lib.actions.ActionExecutionExceptioncom.google.devtools.build.lib.skyframe.ActionExecutionFunction→com.google.devtools.build.lib.actions.ActionInputMapcom.google.devtools.build.lib.skyframe.ActionExecutionFunction→com.google.devtools.build.lib.actions.ActionLookupDatacom.google.devtools.build.lib.skyframe.ActionExecutionFunction→com.google.devtools.build.lib.actions.Artifactcom.google.devtools.build.lib.skyframe.ActionExecutionFunction→com.google.devtools.build.lib.actions.LostInputsActionExecutionExceptioncom.google.devtools.build.lib.skyframe.ActionExecutionFunctionException→com.google.devtools.build.lib.actions.ActionExecutionExceptioncom.google.devtools.build.lib.skyframe.ActionExecutionFunctionExceptionHandler→com.google.devtools.build.lib.actions.Actioncom.google.devtools.build.lib.skyframe.ActionExecutionFunctionExceptionHandler→com.google.devtools.build.lib.actions.ActionExecutionExceptioncom.google.devtools.build.lib.skyframe.ActionExecutionFunctionExceptionHandler→com.google.devtools.build.lib.actions.Artifactcom.google.devtools.build.lib.skyframe.ActionExecutionState→com.google.devtools.build.lib.actions.Actioncom.google.devtools.build.lib.skyframe.ActionExecutionState→com.google.devtools.build.lib.actions.ActionLookupDatacom.google.devtools.build.lib.skyframe.ActionExecutionValue→com.google.devtools.build.lib.actions.Actioncom.google.devtools.build.lib.skyframe.ActionExecutionValue→com.google.devtools.build.lib.actions.Artifactcom.google.devtools.build.lib.skyframe.ActionExecutionValue→com.google.devtools.build.lib.actions.FileArtifactValuecom.google.devtools.build.lib.skyframe.ActionExecutionValue→com.google.devtools.build.lib.actions.RichArtifactDatacom.google.devtools.build.lib.skyframe.ActionInputCollectedEvent→com.google.devtools.build.lib.actions.Actioncom.google.devtools.build.lib.skyframe.ActionInputCollectedEvent→com.google.devtools.build.lib.actions.Artifact
- Direction
- com.google.devtools.build.lib.skyframe uses com.google.devtools.build.lib.actions, so a change to com.google.devtools.build.lib.actions can break com.google.devtools.build.lib.skyframe, while a change to com.google.devtools.build.lib.skyframe can't break com.google.devtools.build.lib.actions.
- 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→1 com.google.devtools.build.lib.packages uses net.starlark.java.syntax✕
- Connections
- 56 pairs of types, where a type in com.google.devtools.build.lib.packages uses a type in net.starlark.java.syntax. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.google.devtools.build.lib.packages.AbstractBuilder→net.starlark.java.syntax.Locationcom.google.devtools.build.lib.packages.Builder→net.starlark.java.syntax.Locationcom.google.devtools.build.lib.packages.Builder→net.starlark.java.syntax.TypeContextcom.google.devtools.build.lib.packages.BuiltinProvider→net.starlark.java.syntax.Locationcom.google.devtools.build.lib.packages.DotBazelFileSyntaxChecker→net.starlark.java.syntax.CallExpressioncom.google.devtools.build.lib.packages.DotBazelFileSyntaxChecker→net.starlark.java.syntax.DefStatementcom.google.devtools.build.lib.packages.DotBazelFileSyntaxChecker→net.starlark.java.syntax.ForStatementcom.google.devtools.build.lib.packages.DotBazelFileSyntaxChecker→net.starlark.java.syntax.IfStatementcom.google.devtools.build.lib.packages.DotBazelFileSyntaxChecker→net.starlark.java.syntax.LambdaExpressioncom.google.devtools.build.lib.packages.DotBazelFileSyntaxChecker→net.starlark.java.syntax.LoadStatementcom.google.devtools.build.lib.packages.DotBazelFileSyntaxChecker→net.starlark.java.syntax.Locationcom.google.devtools.build.lib.packages.DotBazelFileSyntaxChecker→net.starlark.java.syntax.NodeVisitorcom.google.devtools.build.lib.packages.DotBazelFileSyntaxChecker→net.starlark.java.syntax.StarlarkFilecom.google.devtools.build.lib.packages.DotBazelFileSyntaxChecker→net.starlark.java.syntax.SyntaxErrorcom.google.devtools.build.lib.packages.EnvironmentGroup→net.starlark.java.syntax.Locationcom.google.devtools.build.lib.packages.InputFile→net.starlark.java.syntax.Locationcom.google.devtools.build.lib.packages.MacroInstance→net.starlark.java.syntax.Locationcom.google.devtools.build.lib.packages.Metadata→net.starlark.java.syntax.Locationcom.google.devtools.build.lib.packages.Node→net.starlark.java.syntax.Locationcom.google.devtools.build.lib.packages.OutputFile→net.starlark.java.syntax.Locationcom.google.devtools.build.lib.packages.OutputFileData→net.starlark.java.syntax.Locationcom.google.devtools.build.lib.packages.Package→net.starlark.java.syntax.Locationcom.google.devtools.build.lib.packages.PackageFactory→net.starlark.java.syntax.Locationcom.google.devtools.build.lib.packages.PackageFactory→net.starlark.java.syntax.Programcom.google.devtools.build.lib.packages.PackageFactory→net.starlark.java.syntax.StarlarkFile
- Direction
- com.google.devtools.build.lib.packages uses net.starlark.java.syntax, so a change to net.starlark.java.syntax can break com.google.devtools.build.lib.packages, while a change to com.google.devtools.build.lib.packages can't break net.starlark.java.syntax.
- Position
- Below the diagonal: com.google.devtools.build.lib.packages uses a module listed above it, which is the healthy direction.
25→2 com.google.devtools.build.lib.packages uses com.google.devtools.build.lib.events✕
- Connections
- 29 pairs of types, where a type in com.google.devtools.build.lib.packages uses a type in com.google.devtools.build.lib.events. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.google.devtools.build.lib.packages.AbstractBuilder→com.google.devtools.build.lib.events.EventHandlercom.google.devtools.build.lib.packages.AspectPropagationPredicate→com.google.devtools.build.lib.events.ExtendedEventHandlercom.google.devtools.build.lib.packages.AttrAspectsFunctionSupplier→com.google.devtools.build.lib.events.ExtendedEventHandlercom.google.devtools.build.lib.packages.EnvironmentGroup→com.google.devtools.build.lib.events.Eventcom.google.devtools.build.lib.packages.FunctionCombinationImplicitOutputsFunction→com.google.devtools.build.lib.events.EventHandlercom.google.devtools.build.lib.packages.FunctionSupplier→com.google.devtools.build.lib.events.ExtendedEventHandlercom.google.devtools.build.lib.packages.ImplicitOutputsFunction→com.google.devtools.build.lib.events.EventHandlercom.google.devtools.build.lib.packages.MaterializingDefault→com.google.devtools.build.lib.events.EventHandlercom.google.devtools.build.lib.packages.Package→com.google.devtools.build.lib.events.Eventcom.google.devtools.build.lib.packages.Package→com.google.devtools.build.lib.events.EventHandlercom.google.devtools.build.lib.packages.PackageFactory→com.google.devtools.build.lib.events.ExtendedEventHandlercom.google.devtools.build.lib.packages.PackageGroup→com.google.devtools.build.lib.events.EventHandlercom.google.devtools.build.lib.packages.PackageValidator→com.google.devtools.build.lib.events.ExtendedEventHandlercom.google.devtools.build.lib.packages.Resolver→com.google.devtools.build.lib.events.EventHandlercom.google.devtools.build.lib.packages.Rule→com.google.devtools.build.lib.events.EventHandlercom.google.devtools.build.lib.packages.RuleClass→com.google.devtools.build.lib.events.EventHandlercom.google.devtools.build.lib.packages.SafeImplicitOutputsFunction→com.google.devtools.build.lib.events.EventHandlercom.google.devtools.build.lib.packages.StarlarkCallbackHelper→com.google.devtools.build.lib.events.EventHandlercom.google.devtools.build.lib.packages.StarlarkDefinedAspect→com.google.devtools.build.lib.events.EventHandlercom.google.devtools.build.lib.packages.StarlarkExportable→com.google.devtools.build.lib.events.EventHandlercom.google.devtools.build.lib.packages.StarlarkImplicitOutputsFunction→com.google.devtools.build.lib.events.EventHandlercom.google.devtools.build.lib.packages.StarlarkImplicitOutputsFunctionWithCallback→com.google.devtools.build.lib.events.EventHandlercom.google.devtools.build.lib.packages.StarlarkImplicitOutputsFunctionWithMap→com.google.devtools.build.lib.events.EventHandlercom.google.devtools.build.lib.packages.StarlarkProvider→com.google.devtools.build.lib.events.EventHandlercom.google.devtools.build.lib.packages.TargetDefinitionContext→com.google.devtools.build.lib.events.EventHandler
- Direction
- com.google.devtools.build.lib.packages uses com.google.devtools.build.lib.events, so a change to com.google.devtools.build.lib.events can break com.google.devtools.build.lib.packages, while a change to com.google.devtools.build.lib.packages can't break com.google.devtools.build.lib.events.
- Position
- Below the diagonal: com.google.devtools.build.lib.packages uses a module listed above it, which is the healthy direction.
25→3 com.google.devtools.build.lib.packages uses com.google.devtools.common.options✕
- Connections
- 2 pairs of types, where a type in com.google.devtools.build.lib.packages uses a type in com.google.devtools.common.options.
- The types involved
com.google.devtools.build.lib.packages.EnumFilterConverter→com.google.devtools.common.options.Contextlesscom.google.devtools.build.lib.packages.TestTimeoutConverter→com.google.devtools.common.options.Contextless
- Direction
- com.google.devtools.build.lib.packages uses com.google.devtools.common.options, so a change to com.google.devtools.common.options can break com.google.devtools.build.lib.packages, while a change to com.google.devtools.build.lib.packages can't break com.google.devtools.common.options.
- Position
- Below the diagonal: com.google.devtools.build.lib.packages uses a module listed above it, which is the healthy direction.
25→4 com.google.devtools.build.lib.packages uses net.starlark.java.eval✕
- Connections
- 140 pairs of types, where a type in com.google.devtools.build.lib.packages uses a type in net.starlark.java.eval. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.google.devtools.build.lib.packages.AbstractBuilder→net.starlark.java.eval.StarlarkThreadcom.google.devtools.build.lib.packages.AbstractBuilder→net.starlark.java.eval.SymbolGeneratorcom.google.devtools.build.lib.packages.ArgumentProcessorWithInit→net.starlark.java.eval.ArgumentProcessorcom.google.devtools.build.lib.packages.ArgumentProcessorWithInit→net.starlark.java.eval.StarlarkCallablecom.google.devtools.build.lib.packages.ArgumentProcessorWithInit→net.starlark.java.eval.StarlarkThreadcom.google.devtools.build.lib.packages.AspectPropagationEdgesSupplier→net.starlark.java.eval.StarlarkThreadcom.google.devtools.build.lib.packages.AspectPropagationPredicate→net.starlark.java.eval.StarlarkFunctioncom.google.devtools.build.lib.packages.AspectPropagationPredicate→net.starlark.java.eval.StarlarkSemanticscom.google.devtools.build.lib.packages.AttrAspectsFunctionSupplier→net.starlark.java.eval.StarlarkFunctioncom.google.devtools.build.lib.packages.AttrAspectsFunctionSupplier→net.starlark.java.eval.StarlarkSemanticscom.google.devtools.build.lib.packages.BazelStarlarkEnvironment→net.starlark.java.eval.Structurecom.google.devtools.build.lib.packages.BuildGlobals→net.starlark.java.eval.NoneTypecom.google.devtools.build.lib.packages.BuildGlobals→net.starlark.java.eval.Sequencecom.google.devtools.build.lib.packages.BuildGlobals→net.starlark.java.eval.StarlarkThreadcom.google.devtools.build.lib.packages.BuildSetting→net.starlark.java.eval.Printercom.google.devtools.build.lib.packages.BuildSetting→net.starlark.java.eval.StarlarkSemanticscom.google.devtools.build.lib.packages.Builder→net.starlark.java.eval.StarlarkCallablecom.google.devtools.build.lib.packages.Builder→net.starlark.java.eval.StarlarkSemanticscom.google.devtools.build.lib.packages.Builder→net.starlark.java.eval.Symbolcom.google.devtools.build.lib.packages.BuiltinProvider→net.starlark.java.eval.Printercom.google.devtools.build.lib.packages.BuiltinProvider→net.starlark.java.eval.StarlarkSemanticscom.google.devtools.build.lib.packages.BuiltinRestriction→net.starlark.java.eval.StarlarkThreadcom.google.devtools.build.lib.packages.BuiltinRuleFunction→net.starlark.java.eval.Dictcom.google.devtools.build.lib.packages.BuiltinRuleFunction→net.starlark.java.eval.NoneTypecom.google.devtools.build.lib.packages.BuiltinRuleFunction→net.starlark.java.eval.Printer
- Direction
- com.google.devtools.build.lib.packages uses net.starlark.java.eval, so a change to net.starlark.java.eval can break com.google.devtools.build.lib.packages, while a change to com.google.devtools.build.lib.packages can't break net.starlark.java.eval.
- Position
- Below the diagonal: com.google.devtools.build.lib.packages uses a module listed above it, which is the healthy direction.
25→6 com.google.devtools.build.lib.packages uses com.google.devtools.build.skyframe✕
- Connections
- 3 pairs of types, where a type in com.google.devtools.build.lib.packages uses a type in com.google.devtools.build.skyframe.
- The types involved
com.google.devtools.build.lib.packages.ForBuildFile→com.google.devtools.build.skyframe.SkyFunctionNamecom.google.devtools.build.lib.packages.ForMacro→com.google.devtools.build.skyframe.SkyFunctionNamecom.google.devtools.build.lib.packages.PackagePieceIdentifier→com.google.devtools.build.skyframe.SkyKey
- Direction
- com.google.devtools.build.lib.packages uses com.google.devtools.build.skyframe, so a change to com.google.devtools.build.skyframe can break com.google.devtools.build.lib.packages, while a change to com.google.devtools.build.lib.packages can't break com.google.devtools.build.skyframe.
- Position
- Below the diagonal: com.google.devtools.build.lib.packages uses a module listed above it, which is the healthy direction.
25→8 com.google.devtools.build.lib.packages uses com.google.devtools.build.lib.vfs✕
- Connections
- 32 pairs of types, where a type in com.google.devtools.build.lib.packages uses a type in com.google.devtools.build.lib.vfs. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.google.devtools.build.lib.packages.AllowlistEntry→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.packages.BuildFileName→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.packages.BuilderForTesting→com.google.devtools.build.lib.vfs.FileSystemcom.google.devtools.build.lib.packages.CachingPackageLocator→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.packages.CompositePackageLoadingListener→com.google.devtools.build.lib.vfs.RootedPathcom.google.devtools.build.lib.packages.CountingFilesystemOps→com.google.devtools.build.lib.vfs.Direntcom.google.devtools.build.lib.packages.CountingFilesystemOps→com.google.devtools.build.lib.vfs.FileStatuscom.google.devtools.build.lib.packages.CountingFilesystemOps→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.packages.CountingFilesystemOps→com.google.devtools.build.lib.vfs.SyscallCachecom.google.devtools.build.lib.packages.GlobCache→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.packages.GlobCache→com.google.devtools.build.lib.vfs.SyscallCachecom.google.devtools.build.lib.packages.GlobUnixPathDiscriminator→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.packages.GlobUnixPathDiscriminator→com.google.devtools.build.lib.vfs.UnixGlobPathDiscriminatorcom.google.devtools.build.lib.packages.InputFile→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.packages.InputFile→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.packages.InputFileData→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.packages.Metadata→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.packages.Metadata→com.google.devtools.build.lib.vfs.Rootcom.google.devtools.build.lib.packages.Metadata→com.google.devtools.build.lib.vfs.RootedPathcom.google.devtools.build.lib.packages.Package→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.packages.Package→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.packages.Package→com.google.devtools.build.lib.vfs.Rootcom.google.devtools.build.lib.packages.Package→com.google.devtools.build.lib.vfs.RootedPathcom.google.devtools.build.lib.packages.PackageFactory→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.packages.PackageFactory→com.google.devtools.build.lib.vfs.RootedPath
- Direction
- com.google.devtools.build.lib.packages uses com.google.devtools.build.lib.vfs, so a change to com.google.devtools.build.lib.vfs can break com.google.devtools.build.lib.packages, while a change to com.google.devtools.build.lib.packages can't break com.google.devtools.build.lib.vfs.
- Position
- Below the diagonal: com.google.devtools.build.lib.packages uses a module listed above it, which is the healthy direction.
25→11 com.google.devtools.build.lib.packages uses com.google.devtools.build.lib.util✕
- Connections
- 20 pairs of types, where a type in com.google.devtools.build.lib.packages uses a type in com.google.devtools.build.lib.util.
- The types involved
com.google.devtools.build.lib.packages.AdvertisedProviderSet→com.google.devtools.build.lib.util.Fingerprintcom.google.devtools.build.lib.packages.Attribute→com.google.devtools.build.lib.util.FileTypeSetcom.google.devtools.build.lib.packages.BuildFileContainsErrorsException→com.google.devtools.build.lib.util.DetailedExitCodecom.google.devtools.build.lib.packages.BuildFileNotFoundException→com.google.devtools.build.lib.util.DetailedExitCodecom.google.devtools.build.lib.packages.FileTarget→com.google.devtools.build.lib.util.HasFileTypecom.google.devtools.build.lib.packages.GlobCache→com.google.devtools.build.lib.util.Paircom.google.devtools.build.lib.packages.ImmutableAttributeFactory→com.google.devtools.build.lib.util.FileTypeSetcom.google.devtools.build.lib.packages.InvalidPackageException→com.google.devtools.build.lib.util.DetailedExitCodecom.google.devtools.build.lib.packages.InvalidPackageNameException→com.google.devtools.build.lib.util.DetailedExitCodecom.google.devtools.build.lib.packages.InvalidPackagePieceException→com.google.devtools.build.lib.util.DetailedExitCodecom.google.devtools.build.lib.packages.Key→com.google.devtools.build.lib.util.Fingerprintcom.google.devtools.build.lib.packages.KeyedIdentifier→com.google.devtools.build.lib.util.Fingerprintcom.google.devtools.build.lib.packages.NoSuchPackageException→com.google.devtools.build.lib.util.DetailedExitCodecom.google.devtools.build.lib.packages.NoSuchPackagePieceException→com.google.devtools.build.lib.util.DetailedExitCodecom.google.devtools.build.lib.packages.NoSuchTargetException→com.google.devtools.build.lib.util.DetailedExitCodecom.google.devtools.build.lib.packages.NoSuchThingException→com.google.devtools.build.lib.util.DetailedExitCodecom.google.devtools.build.lib.packages.Package→com.google.devtools.build.lib.util.DetailedExitCodecom.google.devtools.build.lib.packages.StarlarkProviderIdentifier→com.google.devtools.build.lib.util.Fingerprintcom.google.devtools.build.lib.packages.TargetDefinitionContext→com.google.devtools.build.lib.util.DetailedExitCodecom.google.devtools.build.lib.packages.TestTargetUtils→com.google.devtools.build.lib.util.Pair
- Direction
- com.google.devtools.build.lib.packages uses com.google.devtools.build.lib.util, so a change to com.google.devtools.build.lib.util can break com.google.devtools.build.lib.packages, while a change to com.google.devtools.build.lib.packages can't break com.google.devtools.build.lib.util.
- Position
- Below the diagonal: com.google.devtools.build.lib.packages uses a module listed above it, which is the healthy direction.
25→24 com.google.devtools.build.lib.packages uses com.google.devtools.build.lib.skyframe✕
- Connections
- 6 pairs of types, where a type in com.google.devtools.build.lib.packages uses a type in com.google.devtools.build.lib.skyframe.
- The types involved
com.google.devtools.build.lib.packages.Key→com.google.devtools.build.lib.skyframe.Keycom.google.devtools.build.lib.packages.NoSuchThingException→com.google.devtools.build.lib.skyframe.DetailedExceptioncom.google.devtools.build.lib.packages.RuleClassUtils→com.google.devtools.build.lib.skyframe.StarlarkBuiltinsValuecom.google.devtools.build.lib.packages.StarlarkAspectClass→com.google.devtools.build.lib.skyframe.Keycom.google.devtools.build.lib.packages.StarlarkDefinedAspect→com.google.devtools.build.lib.skyframe.BzlLoadThreadOwnercom.google.devtools.build.lib.packages.StarlarkProviderWrapper→com.google.devtools.build.lib.skyframe.Key
- Direction
- com.google.devtools.build.lib.packages uses com.google.devtools.build.lib.skyframe, so a change to com.google.devtools.build.lib.skyframe can break com.google.devtools.build.lib.packages, while a change to com.google.devtools.build.lib.packages can't break com.google.devtools.build.lib.skyframe.
- Position
- Below the diagonal: com.google.devtools.build.lib.packages uses a module listed above it, which is the healthy direction.
25→29 com.google.devtools.build.lib.packages uses com.google.devtools.build.lib.skyframe.serialization part of a loop✕
- Connections
- 16 pairs of types, where a type in com.google.devtools.build.lib.packages uses a type in com.google.devtools.build.lib.skyframe.serialization.
- The types involved
com.google.devtools.build.lib.packages.AspectCodec→com.google.devtools.build.lib.skyframe.serialization.AsyncDeserializationContextcom.google.devtools.build.lib.packages.AspectCodec→com.google.devtools.build.lib.skyframe.serialization.DeferredObjectCodeccom.google.devtools.build.lib.packages.AspectCodec→com.google.devtools.build.lib.skyframe.serialization.SerializationContextcom.google.devtools.build.lib.packages.Codec→com.google.devtools.build.lib.skyframe.serialization.AbstractExportedStarlarkSymbolCodeccom.google.devtools.build.lib.packages.PackageCodec→com.google.devtools.build.lib.skyframe.serialization.DeserializationContextcom.google.devtools.build.lib.packages.PackageCodec→com.google.devtools.build.lib.skyframe.serialization.ObjectCodeccom.google.devtools.build.lib.packages.PackageCodec→com.google.devtools.build.lib.skyframe.serialization.SerializationContextcom.google.devtools.build.lib.packages.PackageSerializerInterface→com.google.devtools.build.lib.skyframe.serialization.DeserializationContextcom.google.devtools.build.lib.packages.PackageSerializerInterface→com.google.devtools.build.lib.skyframe.serialization.SerializationContextcom.google.devtools.build.lib.packages.RuleCodec→com.google.devtools.build.lib.skyframe.serialization.LeafDeserializationContextcom.google.devtools.build.lib.packages.RuleCodec→com.google.devtools.build.lib.skyframe.serialization.LeafObjectCodeccom.google.devtools.build.lib.packages.RuleCodec→com.google.devtools.build.lib.skyframe.serialization.LeafSerializationContextcom.google.devtools.build.lib.packages.RuleDataCodec→com.google.devtools.build.lib.skyframe.serialization.AsyncDeserializationContextcom.google.devtools.build.lib.packages.RuleDataCodec→com.google.devtools.build.lib.skyframe.serialization.DeferredObjectCodeccom.google.devtools.build.lib.packages.RuleDataCodec→com.google.devtools.build.lib.skyframe.serialization.SerializationContextcom.google.devtools.build.lib.packages.StarlarkProviderCodec→com.google.devtools.build.lib.skyframe.serialization.AbstractExportedStarlarkSymbolCodec
- Direction
- com.google.devtools.build.lib.packages uses com.google.devtools.build.lib.skyframe.serialization, so a change to com.google.devtools.build.lib.skyframe.serialization can break com.google.devtools.build.lib.packages, while a change to com.google.devtools.build.lib.packages can't break com.google.devtools.build.lib.skyframe.serialization.
- 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→30 com.google.devtools.build.lib.packages uses com.google.devtools.build.lib.collect.nestedset part of a loop✕
- Connections
- 4 pairs of types, where a type in com.google.devtools.build.lib.packages uses a type in com.google.devtools.build.lib.collect.nestedset.
- The types involved
com.google.devtools.build.lib.packages.Metadata→com.google.devtools.build.lib.collect.nestedset.NestedSetsShouldBeInternedByEqualitycom.google.devtools.build.lib.packages.PackageGroupContents→com.google.devtools.build.lib.collect.nestedset.NestedSetsShouldBeInternedByEqualitycom.google.devtools.build.lib.packages.StarlarkProvider→com.google.devtools.build.lib.collect.nestedset.Depsetcom.google.devtools.build.lib.packages.StarlarkProvider→com.google.devtools.build.lib.collect.nestedset.NestedSet
- Direction
- com.google.devtools.build.lib.packages uses com.google.devtools.build.lib.collect.nestedset, so a change to com.google.devtools.build.lib.collect.nestedset can break com.google.devtools.build.lib.packages, while a change to com.google.devtools.build.lib.packages can't break com.google.devtools.build.lib.collect.nestedset.
- 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→31 com.google.devtools.build.lib.packages uses com.google.devtools.build.lib.cmdline part of a loop✕
- Connections
- 145 pairs of types, where a type in com.google.devtools.build.lib.packages uses a type in com.google.devtools.build.lib.cmdline. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.google.devtools.build.lib.packages.2→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.packages.7020→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.packages.AbstractAttributeMapper→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.packages.AbstractBuilder→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.packages.AbstractBuilder→com.google.devtools.build.lib.cmdline.RepositoryMappingcom.google.devtools.build.lib.packages.AbstractLabelLateBoundDefault→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.packages.AggregatingAttributeMapper→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.packages.AllPackages→com.google.devtools.build.lib.cmdline.PackageIdentifiercom.google.devtools.build.lib.packages.AllPackagesBeneath→com.google.devtools.build.lib.cmdline.PackageIdentifiercom.google.devtools.build.lib.packages.Allowlist→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.packages.AllowlistEntry→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.packages.AllowlistEntry→com.google.devtools.build.lib.cmdline.RepositoryNamecom.google.devtools.build.lib.packages.AspectDefinition→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.packages.AspectPropagationEdgesSupplier→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.packages.AspectPropagationEdgesThreadContext→com.google.devtools.build.lib.cmdline.StarlarkThreadContextcom.google.devtools.build.lib.packages.AspectPropagationThreadContext→com.google.devtools.build.lib.cmdline.StarlarkThreadContextcom.google.devtools.build.lib.packages.AttributeMap→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.packages.AttributeTransitionData→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.packages.BoundKeyAndOffset→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.packages.BuildFileContainsErrorsException→com.google.devtools.build.lib.cmdline.PackageIdentifiercom.google.devtools.build.lib.packages.BuildFileName→com.google.devtools.build.lib.cmdline.PackageIdentifiercom.google.devtools.build.lib.packages.BuildFileNotFoundException→com.google.devtools.build.lib.cmdline.PackageIdentifiercom.google.devtools.build.lib.packages.BuiltinRestriction→com.google.devtools.build.lib.cmdline.BazelModuleContextcom.google.devtools.build.lib.packages.BuiltinRestriction→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.packages.BzlInitThreadContext→com.google.devtools.build.lib.cmdline.Label
- Direction
- com.google.devtools.build.lib.packages uses com.google.devtools.build.lib.cmdline, so a change to com.google.devtools.build.lib.cmdline can break com.google.devtools.build.lib.packages, while a change to com.google.devtools.build.lib.packages can't break com.google.devtools.build.lib.cmdline.
- 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→33 com.google.devtools.build.lib.packages uses com.google.devtools.build.lib.analysis.config part of a loop✕
- Connections
- 10 pairs of types, where a type in com.google.devtools.build.lib.packages uses a type in com.google.devtools.build.lib.analysis.config.
- The types involved
com.google.devtools.build.lib.packages.AspectDefinition→com.google.devtools.build.lib.analysis.config.ToolchainTypeRequirementcom.google.devtools.build.lib.packages.ConfigKeyAndValue→com.google.devtools.build.lib.analysis.config.ConfigMatchingProvidercom.google.devtools.build.lib.packages.ConfigurationFragmentPolicy→com.google.devtools.build.lib.analysis.config.FragmentClassSetcom.google.devtools.build.lib.packages.ConfiguredAttributeMapper→com.google.devtools.build.lib.analysis.config.BuildConfigurationValuecom.google.devtools.build.lib.packages.ConfiguredAttributeMapper→com.google.devtools.build.lib.analysis.config.ConfigMatchingProvidercom.google.devtools.build.lib.packages.DeclaredExecGroup→com.google.devtools.build.lib.analysis.config.ToolchainTypeRequirementcom.google.devtools.build.lib.packages.PackageArgs→com.google.devtools.build.lib.analysis.config.FeatureSetcom.google.devtools.build.lib.packages.RuleClass→com.google.devtools.build.lib.analysis.config.ToolchainTypeRequirementcom.google.devtools.build.lib.packages.RuleTransitionData→com.google.devtools.build.lib.analysis.config.ConfigMatchingProvidercom.google.devtools.build.lib.packages.StarlarkDefinedAspect→com.google.devtools.build.lib.analysis.config.ToolchainTypeRequirement
- Direction
- com.google.devtools.build.lib.packages uses com.google.devtools.build.lib.analysis.config, so a change to com.google.devtools.build.lib.analysis.config can break com.google.devtools.build.lib.packages, while a change to com.google.devtools.build.lib.packages can't break com.google.devtools.build.lib.analysis.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.
25→35 com.google.devtools.build.lib.packages uses com.google.devtools.build.lib.analysis part of a loop✕
- Connections
- 5 pairs of types, where a type in com.google.devtools.build.lib.packages uses a type in com.google.devtools.build.lib.analysis.
- The types involved
com.google.devtools.build.lib.packages.BuilderFactoryForTesting→com.google.devtools.build.lib.analysis.BlazeDirectoriescom.google.devtools.build.lib.packages.BzlInitThreadContext→com.google.devtools.build.lib.analysis.RuleDefinitionEnvironmentcom.google.devtools.build.lib.packages.Constraint→com.google.devtools.build.lib.analysis.TransitiveInfoProvidercom.google.devtools.build.lib.packages.RequiredProviders→com.google.devtools.build.lib.analysis.TransitiveInfoProvidercom.google.devtools.build.lib.packages.RuleClassProvider→com.google.devtools.build.lib.analysis.RuleDefinitionEnvironment
- Direction
- com.google.devtools.build.lib.packages uses com.google.devtools.build.lib.analysis, so a change to com.google.devtools.build.lib.analysis can break com.google.devtools.build.lib.packages, while a change to com.google.devtools.build.lib.packages can't break com.google.devtools.build.lib.analysis.
- 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→37 com.google.devtools.build.lib.packages uses com.google.devtools.build.lib.actions part of a loop✕
- Connections
- 2 pairs of types, where a type in com.google.devtools.build.lib.packages uses a type in com.google.devtools.build.lib.actions.
- The types involved
com.google.devtools.build.lib.packages.GlobCache→com.google.devtools.build.lib.actions.ThreadStateReceivercom.google.devtools.build.lib.packages.PackageFactory→com.google.devtools.build.lib.actions.ThreadStateReceiver
- Direction
- com.google.devtools.build.lib.packages uses com.google.devtools.build.lib.actions, so a change to com.google.devtools.build.lib.actions can break com.google.devtools.build.lib.packages, while a change to com.google.devtools.build.lib.packages can't break com.google.devtools.build.lib.actions.
- 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 com.google.devtools.build.lib.analysis.starlark uses net.starlark.java.syntax✕
- Connections
- 9 pairs of types, where a type in com.google.devtools.build.lib.analysis.starlark uses a type in net.starlark.java.syntax.
- The types involved
com.google.devtools.build.lib.analysis.starlark.Builder→net.starlark.java.syntax.Locationcom.google.devtools.build.lib.analysis.starlark.CommandLineItemMapEachAdaptor→net.starlark.java.syntax.Locationcom.google.devtools.build.lib.analysis.starlark.MacroFunction→net.starlark.java.syntax.Locationcom.google.devtools.build.lib.analysis.starlark.MutableArgs→net.starlark.java.syntax.Locationcom.google.devtools.build.lib.analysis.starlark.StarlarkCustomCommandLine→net.starlark.java.syntax.Locationcom.google.devtools.build.lib.analysis.starlark.StarlarkRuleConfiguredTargetUtil→net.starlark.java.syntax.Locationcom.google.devtools.build.lib.analysis.starlark.StarlarkRuleFunction→net.starlark.java.syntax.Locationcom.google.devtools.build.lib.analysis.starlark.StarlarkSubrule→net.starlark.java.syntax.Locationcom.google.devtools.build.lib.analysis.starlark.VectorArg→net.starlark.java.syntax.Location
- Direction
- com.google.devtools.build.lib.analysis.starlark uses net.starlark.java.syntax, so a change to net.starlark.java.syntax can break com.google.devtools.build.lib.analysis.starlark, while a change to com.google.devtools.build.lib.analysis.starlark can't break net.starlark.java.syntax.
- Position
- Below the diagonal: com.google.devtools.build.lib.analysis.starlark uses a module listed above it, which is the healthy direction.
26→2 com.google.devtools.build.lib.analysis.starlark uses com.google.devtools.build.lib.events✕
- Connections
- 9 pairs of types, where a type in com.google.devtools.build.lib.analysis.starlark uses a type in com.google.devtools.build.lib.events.
- The types involved
com.google.devtools.build.lib.analysis.starlark.FunctionPatchTransition→com.google.devtools.build.lib.events.EventHandlercom.google.devtools.build.lib.analysis.starlark.FunctionSplitTransition→com.google.devtools.build.lib.events.EventHandlercom.google.devtools.build.lib.analysis.starlark.FunctionTransitionUtil→com.google.devtools.build.lib.events.EventHandlercom.google.devtools.build.lib.analysis.starlark.MacroFunction→com.google.devtools.build.lib.events.EventHandlercom.google.devtools.build.lib.analysis.starlark.StarlarkMapActionTemplate→com.google.devtools.build.lib.events.EventHandlercom.google.devtools.build.lib.analysis.starlark.StarlarkMaterializer→com.google.devtools.build.lib.events.EventHandlercom.google.devtools.build.lib.analysis.starlark.StarlarkRuleFunction→com.google.devtools.build.lib.events.EventHandlercom.google.devtools.build.lib.analysis.starlark.StarlarkSubrule→com.google.devtools.build.lib.events.EventHandlercom.google.devtools.build.lib.analysis.starlark.SubruleAttribute→com.google.devtools.build.lib.events.EventHandler
- Direction
- com.google.devtools.build.lib.analysis.starlark uses com.google.devtools.build.lib.events, so a change to com.google.devtools.build.lib.events can break com.google.devtools.build.lib.analysis.starlark, while a change to com.google.devtools.build.lib.analysis.starlark can't break com.google.devtools.build.lib.events.
- Position
- Below the diagonal: com.google.devtools.build.lib.analysis.starlark uses a module listed above it, which is the healthy direction.
26→4 com.google.devtools.build.lib.analysis.starlark uses net.starlark.java.eval✕
- Connections
- 115 pairs of types, where a type in com.google.devtools.build.lib.analysis.starlark uses a type in net.starlark.java.eval. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.google.devtools.build.lib.analysis.starlark.1→net.starlark.java.eval.StarlarkListcom.google.devtools.build.lib.analysis.starlark.1→net.starlark.java.eval.StarlarkSemanticscom.google.devtools.build.lib.analysis.starlark.1→net.starlark.java.eval.StarlarkThreadcom.google.devtools.build.lib.analysis.starlark.Args→net.starlark.java.eval.Mutabilitycom.google.devtools.build.lib.analysis.starlark.Args→net.starlark.java.eval.Printercom.google.devtools.build.lib.analysis.starlark.Args→net.starlark.java.eval.StarlarkSemanticscom.google.devtools.build.lib.analysis.starlark.Args→net.starlark.java.eval.StarlarkThreadcom.google.devtools.build.lib.analysis.starlark.BazelBuildApiGlobals→net.starlark.java.eval.StarlarkThreadcom.google.devtools.build.lib.analysis.starlark.Builder→net.starlark.java.eval.Sequencecom.google.devtools.build.lib.analysis.starlark.Builder→net.starlark.java.eval.StarlarkCallablecom.google.devtools.build.lib.analysis.starlark.CommandLineItemMapEachAdaptor→net.starlark.java.eval.StarlarkCallablecom.google.devtools.build.lib.analysis.starlark.CommandLineItemMapEachAdaptor→net.starlark.java.eval.StarlarkSemanticscom.google.devtools.build.lib.analysis.starlark.Descriptor→net.starlark.java.eval.Printercom.google.devtools.build.lib.analysis.starlark.Descriptor→net.starlark.java.eval.StarlarkSemanticscom.google.devtools.build.lib.analysis.starlark.ExpandedDirectory→net.starlark.java.eval.Printercom.google.devtools.build.lib.analysis.starlark.ExpandedDirectory→net.starlark.java.eval.StarlarkListcom.google.devtools.build.lib.analysis.starlark.ExpandedDirectory→net.starlark.java.eval.StarlarkSemanticscom.google.devtools.build.lib.analysis.starlark.FilesetSymlinkFile→net.starlark.java.eval.Printercom.google.devtools.build.lib.analysis.starlark.FilesetSymlinkFile→net.starlark.java.eval.StarlarkSemanticscom.google.devtools.build.lib.analysis.starlark.FrozenArgs→net.starlark.java.eval.StarlarkThreadcom.google.devtools.build.lib.analysis.starlark.LazySubstitution→net.starlark.java.eval.StarlarkCallablecom.google.devtools.build.lib.analysis.starlark.LazySubstitution→net.starlark.java.eval.StarlarkSemanticscom.google.devtools.build.lib.analysis.starlark.MacroFunction→net.starlark.java.eval.Dictcom.google.devtools.build.lib.analysis.starlark.MacroFunction→net.starlark.java.eval.Printercom.google.devtools.build.lib.analysis.starlark.MacroFunction→net.starlark.java.eval.StarlarkSemantics
- Direction
- com.google.devtools.build.lib.analysis.starlark uses net.starlark.java.eval, so a change to net.starlark.java.eval can break com.google.devtools.build.lib.analysis.starlark, while a change to com.google.devtools.build.lib.analysis.starlark can't break net.starlark.java.eval.
- Position
- Below the diagonal: com.google.devtools.build.lib.analysis.starlark uses a module listed above it, which is the healthy direction.
26→6 com.google.devtools.build.lib.analysis.starlark uses com.google.devtools.build.skyframe✕
- Connections
- 3 pairs of types, where a type in com.google.devtools.build.lib.analysis.starlark uses a type in com.google.devtools.build.skyframe.
- The types involved
com.google.devtools.build.lib.analysis.starlark.Key→com.google.devtools.build.skyframe.SkyFunctionNamecom.google.devtools.build.lib.analysis.starlark.Key→com.google.devtools.build.skyframe.SkyKeycom.google.devtools.build.lib.analysis.starlark.StarlarkBuildSettingsDetailsValue→com.google.devtools.build.skyframe.SkyValue
- Direction
- com.google.devtools.build.lib.analysis.starlark uses com.google.devtools.build.skyframe, so a change to com.google.devtools.build.skyframe can break com.google.devtools.build.lib.analysis.starlark, while a change to com.google.devtools.build.lib.analysis.starlark can't break com.google.devtools.build.skyframe.
- Position
- Below the diagonal: com.google.devtools.build.lib.analysis.starlark uses a module listed above it, which is the healthy direction.
26→8 com.google.devtools.build.lib.analysis.starlark uses com.google.devtools.build.lib.vfs✕
- Connections
- 4 pairs of types, where a type in com.google.devtools.build.lib.analysis.starlark uses a type in com.google.devtools.build.lib.vfs.
- The types involved
com.google.devtools.build.lib.analysis.starlark.FilesetSymlinkFile→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.analysis.starlark.UnresolvedSymlinkAction→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.analysis.starlark.UnresolvedSymlinkAction→com.google.devtools.build.lib.vfs.SymlinkTargetTypecom.google.devtools.build.lib.analysis.starlark.WithProgressMessage→com.google.devtools.build.lib.vfs.SymlinkTargetType
- Direction
- com.google.devtools.build.lib.analysis.starlark uses com.google.devtools.build.lib.vfs, so a change to com.google.devtools.build.lib.vfs can break com.google.devtools.build.lib.analysis.starlark, while a change to com.google.devtools.build.lib.analysis.starlark can't break com.google.devtools.build.lib.vfs.
- Position
- Below the diagonal: com.google.devtools.build.lib.analysis.starlark uses a module listed above it, which is the healthy direction.
26→11 com.google.devtools.build.lib.analysis.starlark uses com.google.devtools.build.lib.util✕
- Connections
- 11 pairs of types, where a type in com.google.devtools.build.lib.analysis.starlark uses a type in com.google.devtools.build.lib.util.
- The types involved
com.google.devtools.build.lib.analysis.starlark.StarlarkActionResourceSet→com.google.devtools.build.lib.util.OScom.google.devtools.build.lib.analysis.starlark.StarlarkActionResourceSetBuilder→com.google.devtools.build.lib.util.OScom.google.devtools.build.lib.analysis.starlark.StarlarkAspectPropagationContext→com.google.devtools.build.lib.util.OrderedSetMultimapcom.google.devtools.build.lib.analysis.starlark.StarlarkCustomCommandLine→com.google.devtools.build.lib.util.Fingerprintcom.google.devtools.build.lib.analysis.starlark.StarlarkMapActionTemplate→com.google.devtools.build.lib.util.DetailedExitCodecom.google.devtools.build.lib.analysis.starlark.StarlarkMapActionTemplate→com.google.devtools.build.lib.util.Fingerprintcom.google.devtools.build.lib.analysis.starlark.StarlarkRuleClassFunctions→com.google.devtools.build.lib.util.Paircom.google.devtools.build.lib.analysis.starlark.StarlarkSubrule→com.google.devtools.build.lib.util.Paircom.google.devtools.build.lib.analysis.starlark.UnresolvedSymlinkAction→com.google.devtools.build.lib.util.DetailedExitCodecom.google.devtools.build.lib.analysis.starlark.UnresolvedSymlinkAction→com.google.devtools.build.lib.util.Fingerprintcom.google.devtools.build.lib.analysis.starlark.VectorArg→com.google.devtools.build.lib.util.Fingerprint
- Direction
- com.google.devtools.build.lib.analysis.starlark uses com.google.devtools.build.lib.util, so a change to com.google.devtools.build.lib.util can break com.google.devtools.build.lib.analysis.starlark, while a change to com.google.devtools.build.lib.analysis.starlark can't break com.google.devtools.build.lib.util.
- Position
- Below the diagonal: com.google.devtools.build.lib.analysis.starlark uses a module listed above it, which is the healthy direction.
26→24 com.google.devtools.build.lib.analysis.starlark uses com.google.devtools.build.lib.skyframe✕
- Connections
- 2 pairs of types, where a type in com.google.devtools.build.lib.analysis.starlark uses a type in com.google.devtools.build.lib.skyframe.
- The types involved
com.google.devtools.build.lib.analysis.starlark.MacroFunction→com.google.devtools.build.lib.skyframe.BzlLoadThreadOwnercom.google.devtools.build.lib.analysis.starlark.StarlarkRuleClassFunctions→com.google.devtools.build.lib.skyframe.BzlLoadThreadOwner
- Direction
- com.google.devtools.build.lib.analysis.starlark uses com.google.devtools.build.lib.skyframe, so a change to com.google.devtools.build.lib.skyframe can break com.google.devtools.build.lib.analysis.starlark, while a change to com.google.devtools.build.lib.analysis.starlark can't break com.google.devtools.build.lib.skyframe.
- Position
- Below the diagonal: com.google.devtools.build.lib.analysis.starlark uses a module listed above it, which is the healthy direction.
26→25 com.google.devtools.build.lib.analysis.starlark uses com.google.devtools.build.lib.packages✕
- Connections
- 57 pairs of types, where a type in com.google.devtools.build.lib.analysis.starlark uses a type in com.google.devtools.build.lib.packages. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.google.devtools.build.lib.analysis.starlark.Descriptor→com.google.devtools.build.lib.packages.Attributecom.google.devtools.build.lib.analysis.starlark.Descriptor→com.google.devtools.build.lib.packages.AttributeTransitionDatacom.google.devtools.build.lib.analysis.starlark.Descriptor→com.google.devtools.build.lib.packages.AttributeValueSourcecom.google.devtools.build.lib.analysis.starlark.Descriptor→com.google.devtools.build.lib.packages.Typecom.google.devtools.build.lib.analysis.starlark.FunctionPatchTransition→com.google.devtools.build.lib.packages.StructImplcom.google.devtools.build.lib.analysis.starlark.FunctionSplitTransition→com.google.devtools.build.lib.packages.ConfiguredAttributeMappercom.google.devtools.build.lib.analysis.starlark.FunctionSplitTransition→com.google.devtools.build.lib.packages.StructImplcom.google.devtools.build.lib.analysis.starlark.FunctionTransitionUtil→com.google.devtools.build.lib.packages.StructImplcom.google.devtools.build.lib.analysis.starlark.MacroFunction→com.google.devtools.build.lib.packages.Buildercom.google.devtools.build.lib.analysis.starlark.MacroFunction→com.google.devtools.build.lib.packages.MacroClasscom.google.devtools.build.lib.analysis.starlark.MacroFunction→com.google.devtools.build.lib.packages.StarlarkExportablecom.google.devtools.build.lib.analysis.starlark.StarlarkAspectPropagationContext→com.google.devtools.build.lib.packages.Aspectcom.google.devtools.build.lib.analysis.starlark.StarlarkAspectPropagationContext→com.google.devtools.build.lib.packages.ConfiguredAttributeMappercom.google.devtools.build.lib.analysis.starlark.StarlarkAspectPropagationContext→com.google.devtools.build.lib.packages.Rulecom.google.devtools.build.lib.analysis.starlark.StarlarkAspectPropagationContext→com.google.devtools.build.lib.packages.RuleClasscom.google.devtools.build.lib.analysis.starlark.StarlarkAspectPropagationContext→com.google.devtools.build.lib.packages.StructImplcom.google.devtools.build.lib.analysis.starlark.StarlarkAttrModule→com.google.devtools.build.lib.packages.AttributeTransitionDatacom.google.devtools.build.lib.analysis.starlark.StarlarkAttrModule→com.google.devtools.build.lib.packages.Buildercom.google.devtools.build.lib.analysis.starlark.StarlarkAttrModule→com.google.devtools.build.lib.packages.StarlarkProviderIdentifiercom.google.devtools.build.lib.analysis.starlark.StarlarkAttrModule→com.google.devtools.build.lib.packages.Typecom.google.devtools.build.lib.analysis.starlark.StarlarkAttributeTransitionProvider→com.google.devtools.build.lib.packages.AttributeTransitionDatacom.google.devtools.build.lib.analysis.starlark.StarlarkAttributesCollection→com.google.devtools.build.lib.packages.StructImplcom.google.devtools.build.lib.analysis.starlark.StarlarkBuildSettingsDetailsValue→com.google.devtools.build.lib.packages.Typecom.google.devtools.build.lib.analysis.starlark.StarlarkConfig→com.google.devtools.build.lib.packages.BuildSettingcom.google.devtools.build.lib.analysis.starlark.StarlarkGlobalsImpl→com.google.devtools.build.lib.packages.StarlarkGlobals
- Direction
- com.google.devtools.build.lib.analysis.starlark uses com.google.devtools.build.lib.packages, so a change to com.google.devtools.build.lib.packages can break com.google.devtools.build.lib.analysis.starlark, while a change to com.google.devtools.build.lib.analysis.starlark can't break com.google.devtools.build.lib.packages.
- Position
- Below the diagonal: com.google.devtools.build.lib.analysis.starlark uses a module listed above it, which is the healthy direction.
26→29 com.google.devtools.build.lib.analysis.starlark uses com.google.devtools.build.lib.skyframe.serialization part of a loop✕
- Connections
- 1 pair of types, where a type in com.google.devtools.build.lib.analysis.starlark uses a type in com.google.devtools.build.lib.skyframe.serialization.
- The types involved
com.google.devtools.build.lib.analysis.starlark.Codec→com.google.devtools.build.lib.skyframe.serialization.AbstractExportedStarlarkSymbolCodec
- Direction
- com.google.devtools.build.lib.analysis.starlark uses com.google.devtools.build.lib.skyframe.serialization, so a change to com.google.devtools.build.lib.skyframe.serialization can break com.google.devtools.build.lib.analysis.starlark, while a change to com.google.devtools.build.lib.analysis.starlark can't break com.google.devtools.build.lib.skyframe.serialization.
- 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→30 com.google.devtools.build.lib.analysis.starlark uses com.google.devtools.build.lib.collect.nestedset part of a loop✕
- Connections
- 8 pairs of types, where a type in com.google.devtools.build.lib.analysis.starlark uses a type in com.google.devtools.build.lib.collect.nestedset.
- The types involved
com.google.devtools.build.lib.analysis.starlark.Builder→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.analysis.starlark.LazySubstitution→com.google.devtools.build.lib.collect.nestedset.Depsetcom.google.devtools.build.lib.analysis.starlark.MutableArgs→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.analysis.starlark.StarlarkMapActionTemplate→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.analysis.starlark.StarlarkMapActionTemplate→com.google.devtools.build.lib.collect.nestedset.NestedSetBuildercom.google.devtools.build.lib.analysis.starlark.StarlarkRuleConfiguredTargetUtil→com.google.devtools.build.lib.collect.nestedset.Depsetcom.google.devtools.build.lib.analysis.starlark.StarlarkRuleConfiguredTargetUtil→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.analysis.starlark.TemplateDict→com.google.devtools.build.lib.collect.nestedset.Depset
- Direction
- com.google.devtools.build.lib.analysis.starlark uses com.google.devtools.build.lib.collect.nestedset, so a change to com.google.devtools.build.lib.collect.nestedset can break com.google.devtools.build.lib.analysis.starlark, while a change to com.google.devtools.build.lib.analysis.starlark can't break com.google.devtools.build.lib.collect.nestedset.
- 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→31 com.google.devtools.build.lib.analysis.starlark uses com.google.devtools.build.lib.cmdline part of a loop✕
- Connections
- 33 pairs of types, where a type in com.google.devtools.build.lib.analysis.starlark uses a type in com.google.devtools.build.lib.cmdline. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.google.devtools.build.lib.analysis.starlark.1→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.analysis.starlark.AnalysisTestKey→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.analysis.starlark.Args→com.google.devtools.build.lib.cmdline.RepositoryMappingcom.google.devtools.build.lib.analysis.starlark.CacheKey→com.google.devtools.build.lib.cmdline.RepositoryNamecom.google.devtools.build.lib.analysis.starlark.CustomExecScopeValue→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.analysis.starlark.FilesetSymlinkFile→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.analysis.starlark.FrozenArgs→com.google.devtools.build.lib.cmdline.RepositoryMappingcom.google.devtools.build.lib.analysis.starlark.FunctionTransitionUtil→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.analysis.starlark.Key→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.analysis.starlark.MacroFunction→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.analysis.starlark.MaterializationContext→com.google.devtools.build.lib.cmdline.StarlarkThreadContextcom.google.devtools.build.lib.analysis.starlark.MutableArgs→com.google.devtools.build.lib.cmdline.RepositoryMappingcom.google.devtools.build.lib.analysis.starlark.QualifiedRuleKind→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.analysis.starlark.StarlarkActionFactory→com.google.devtools.build.lib.cmdline.RepositoryMappingcom.google.devtools.build.lib.analysis.starlark.StarlarkAspectPropagationContext→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.analysis.starlark.StarlarkAspectPropagationRule→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.analysis.starlark.StarlarkBuildSettingsDetailsValue→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.analysis.starlark.StarlarkCustomCommandLine→com.google.devtools.build.lib.cmdline.RepositoryMappingcom.google.devtools.build.lib.analysis.starlark.StarlarkLateBoundDefault→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.analysis.starlark.StarlarkLateBoundDefault→com.google.devtools.build.lib.cmdline.RepositoryNamecom.google.devtools.build.lib.analysis.starlark.StarlarkMapActionTemplate→com.google.devtools.build.lib.cmdline.RepositoryMappingcom.google.devtools.build.lib.analysis.starlark.StarlarkMaterializerContext→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.analysis.starlark.StarlarkRuleClassFunctions→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.analysis.starlark.StarlarkRuleContext→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.analysis.starlark.StarlarkRuleFunction→com.google.devtools.build.lib.cmdline.Label
- Direction
- com.google.devtools.build.lib.analysis.starlark uses com.google.devtools.build.lib.cmdline, so a change to com.google.devtools.build.lib.cmdline can break com.google.devtools.build.lib.analysis.starlark, while a change to com.google.devtools.build.lib.analysis.starlark can't break com.google.devtools.build.lib.cmdline.
- 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→32 com.google.devtools.build.lib.analysis.starlark uses com.google.devtools.build.lib.analysis.platform part of a loop✕
- Connections
- 2 pairs of types, where a type in com.google.devtools.build.lib.analysis.starlark uses a type in com.google.devtools.build.lib.analysis.platform.
- The types involved
com.google.devtools.build.lib.analysis.starlark.StarlarkActionFactory→com.google.devtools.build.lib.analysis.platform.PlatformInfocom.google.devtools.build.lib.analysis.starlark.StarlarkRuleContext→com.google.devtools.build.lib.analysis.platform.ConstraintValueInfo
- Direction
- com.google.devtools.build.lib.analysis.starlark uses com.google.devtools.build.lib.analysis.platform, so a change to com.google.devtools.build.lib.analysis.platform can break com.google.devtools.build.lib.analysis.starlark, while a change to com.google.devtools.build.lib.analysis.starlark can't break com.google.devtools.build.lib.analysis.platform.
- 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→33 com.google.devtools.build.lib.analysis.starlark uses com.google.devtools.build.lib.analysis.config part of a loop✕
- Connections
- 22 pairs of types, where a type in com.google.devtools.build.lib.analysis.starlark uses a type in com.google.devtools.build.lib.analysis.config.
- The types involved
com.google.devtools.build.lib.analysis.starlark.CommandLineItemMapEachAdaptor→com.google.devtools.build.lib.analysis.config.OutputPathsModecom.google.devtools.build.lib.analysis.starlark.FunctionPatchTransition→com.google.devtools.build.lib.analysis.config.BuildOptionscom.google.devtools.build.lib.analysis.starlark.FunctionPatchTransition→com.google.devtools.build.lib.analysis.config.BuildOptionsViewcom.google.devtools.build.lib.analysis.starlark.FunctionSplitTransition→com.google.devtools.build.lib.analysis.config.BuildOptionscom.google.devtools.build.lib.analysis.starlark.FunctionSplitTransition→com.google.devtools.build.lib.analysis.config.BuildOptionsViewcom.google.devtools.build.lib.analysis.starlark.FunctionSplitTransition→com.google.devtools.build.lib.analysis.config.StarlarkDefinedConfigTransitioncom.google.devtools.build.lib.analysis.starlark.FunctionTransitionUtil→com.google.devtools.build.lib.analysis.config.BuildOptionscom.google.devtools.build.lib.analysis.starlark.FunctionTransitionUtil→com.google.devtools.build.lib.analysis.config.OptionInfocom.google.devtools.build.lib.analysis.starlark.FunctionTransitionUtil→com.google.devtools.build.lib.analysis.config.StarlarkDefinedConfigTransitioncom.google.devtools.build.lib.analysis.starlark.StarlarkAttributeTransitionProvider→com.google.devtools.build.lib.analysis.config.StarlarkDefinedConfigTransitioncom.google.devtools.build.lib.analysis.starlark.StarlarkConfig→com.google.devtools.build.lib.analysis.config.ExecutionTransitionFactorycom.google.devtools.build.lib.analysis.starlark.StarlarkCustomCommandLine→com.google.devtools.build.lib.analysis.config.OutputPathsModecom.google.devtools.build.lib.analysis.starlark.StarlarkRuleClassFunctions→com.google.devtools.build.lib.analysis.config.ToolchainTypeRequirementcom.google.devtools.build.lib.analysis.starlark.StarlarkRuleContext→com.google.devtools.build.lib.analysis.config.BuildConfigurationValuecom.google.devtools.build.lib.analysis.starlark.StarlarkRuleTransitionProvider→com.google.devtools.build.lib.analysis.config.ConfigMatchingProvidercom.google.devtools.build.lib.analysis.starlark.StarlarkRuleTransitionProvider→com.google.devtools.build.lib.analysis.config.StarlarkDefinedConfigTransitioncom.google.devtools.build.lib.analysis.starlark.StarlarkSubrule→com.google.devtools.build.lib.analysis.config.ToolchainTypeRequirementcom.google.devtools.build.lib.analysis.starlark.StarlarkTransition→com.google.devtools.build.lib.analysis.config.BuildOptionDetailscom.google.devtools.build.lib.analysis.starlark.StarlarkTransition→com.google.devtools.build.lib.analysis.config.BuildOptionscom.google.devtools.build.lib.analysis.starlark.StarlarkTransition→com.google.devtools.build.lib.analysis.config.StarlarkDefinedConfigTransitioncom.google.devtools.build.lib.analysis.starlark.SubruleContext→com.google.devtools.build.lib.analysis.config.ToolchainTypeRequirementcom.google.devtools.build.lib.analysis.starlark.VectorArg→com.google.devtools.build.lib.analysis.config.OutputPathsMode
- Direction
- com.google.devtools.build.lib.analysis.starlark uses com.google.devtools.build.lib.analysis.config, so a change to com.google.devtools.build.lib.analysis.config can break com.google.devtools.build.lib.analysis.starlark, while a change to com.google.devtools.build.lib.analysis.starlark can't break com.google.devtools.build.lib.analysis.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.
26→34 com.google.devtools.build.lib.analysis.starlark uses com.google.devtools.build.lib.analysis.actions part of a loop✕
- Connections
- 4 pairs of types, where a type in com.google.devtools.build.lib.analysis.starlark uses a type in com.google.devtools.build.lib.analysis.actions.
- The types involved
com.google.devtools.build.lib.analysis.starlark.StarlarkActionFactory→com.google.devtools.build.lib.analysis.actions.Buildercom.google.devtools.build.lib.analysis.starlark.StarlarkMapActionTemplate→com.google.devtools.build.lib.analysis.actions.Buildercom.google.devtools.build.lib.analysis.starlark.StarlarkTemplateContext→com.google.devtools.build.lib.analysis.actions.Buildercom.google.devtools.build.lib.analysis.starlark.TemplateDict→com.google.devtools.build.lib.analysis.actions.Substitution
- Direction
- com.google.devtools.build.lib.analysis.starlark uses com.google.devtools.build.lib.analysis.actions, so a change to com.google.devtools.build.lib.analysis.actions can break com.google.devtools.build.lib.analysis.starlark, while a change to com.google.devtools.build.lib.analysis.starlark can't break com.google.devtools.build.lib.analysis.actions.
- 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→35 com.google.devtools.build.lib.analysis.starlark uses com.google.devtools.build.lib.analysis part of a loop✕
- Connections
- 29 pairs of types, where a type in com.google.devtools.build.lib.analysis.starlark uses a type in com.google.devtools.build.lib.analysis. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.google.devtools.build.lib.analysis.starlark.StarlarkActionContext→com.google.devtools.build.lib.analysis.FilesToRunProvidercom.google.devtools.build.lib.analysis.starlark.StarlarkActionContext→com.google.devtools.build.lib.analysis.RuleContextcom.google.devtools.build.lib.analysis.starlark.StarlarkActionFactory→com.google.devtools.build.lib.analysis.RuleContextcom.google.devtools.build.lib.analysis.starlark.StarlarkApiProvider→com.google.devtools.build.lib.analysis.ProviderCollectioncom.google.devtools.build.lib.analysis.starlark.StarlarkAspectPropagationContext→com.google.devtools.build.lib.analysis.DependencyKindcom.google.devtools.build.lib.analysis.starlark.StarlarkAttributesCollection→com.google.devtools.build.lib.analysis.FilesToRunProvidercom.google.devtools.build.lib.analysis.starlark.StarlarkAttributesCollection→com.google.devtools.build.lib.analysis.PrerequisitesCollectioncom.google.devtools.build.lib.analysis.starlark.StarlarkErrorReporter→com.google.devtools.build.lib.analysis.RuleErrorConsumercom.google.devtools.build.lib.analysis.starlark.StarlarkExecGroupCollection→com.google.devtools.build.lib.analysis.ResolvedToolchainsDataInterfacecom.google.devtools.build.lib.analysis.starlark.StarlarkExecGroupCollection→com.google.devtools.build.lib.analysis.ToolchainCollectioncom.google.devtools.build.lib.analysis.starlark.StarlarkMaterializer→com.google.devtools.build.lib.analysis.TransitiveInfoCollectioncom.google.devtools.build.lib.analysis.starlark.StarlarkRuleClassFunctions→com.google.devtools.build.lib.analysis.RuleDefinitionEnvironmentcom.google.devtools.build.lib.analysis.starlark.StarlarkRuleConfiguredTargetUtil→com.google.devtools.build.lib.analysis.ConfiguredTargetcom.google.devtools.build.lib.analysis.starlark.StarlarkRuleConfiguredTargetUtil→com.google.devtools.build.lib.analysis.DefaultInfocom.google.devtools.build.lib.analysis.starlark.StarlarkRuleConfiguredTargetUtil→com.google.devtools.build.lib.analysis.RequiredConfigFragmentsProvidercom.google.devtools.build.lib.analysis.starlark.StarlarkRuleConfiguredTargetUtil→com.google.devtools.build.lib.analysis.RuleConfiguredTargetBuildercom.google.devtools.build.lib.analysis.starlark.StarlarkRuleConfiguredTargetUtil→com.google.devtools.build.lib.analysis.RuleContextcom.google.devtools.build.lib.analysis.starlark.StarlarkRuleConfiguredTargetUtil→com.google.devtools.build.lib.analysis.RunEnvironmentInfocom.google.devtools.build.lib.analysis.starlark.StarlarkRuleConfiguredTargetUtil→com.google.devtools.build.lib.analysis.Runfilescom.google.devtools.build.lib.analysis.starlark.StarlarkRuleContext→com.google.devtools.build.lib.analysis.FilesToRunProvidercom.google.devtools.build.lib.analysis.starlark.StarlarkRuleContext→com.google.devtools.build.lib.analysis.FragmentCollectioncom.google.devtools.build.lib.analysis.starlark.StarlarkRuleContext→com.google.devtools.build.lib.analysis.FragmentSuppliercom.google.devtools.build.lib.analysis.starlark.StarlarkRuleContext→com.google.devtools.build.lib.analysis.RuleContextcom.google.devtools.build.lib.analysis.starlark.StarlarkRuleContext→com.google.devtools.build.lib.analysis.Runfilescom.google.devtools.build.lib.analysis.starlark.StarlarkRuleContext→com.google.devtools.build.lib.analysis.TransitiveInfoCollection
- Direction
- com.google.devtools.build.lib.analysis.starlark uses com.google.devtools.build.lib.analysis, so a change to com.google.devtools.build.lib.analysis can break com.google.devtools.build.lib.analysis.starlark, while a change to com.google.devtools.build.lib.analysis.starlark can't break com.google.devtools.build.lib.analysis.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
26→37 com.google.devtools.build.lib.analysis.starlark uses com.google.devtools.build.lib.actions part of a loop✕
- Connections
- 76 pairs of types, where a type in com.google.devtools.build.lib.analysis.starlark uses a type in com.google.devtools.build.lib.actions. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.google.devtools.build.lib.analysis.starlark.Args→com.google.devtools.build.lib.actions.Artifactcom.google.devtools.build.lib.analysis.starlark.Args→com.google.devtools.build.lib.actions.CommandLinecom.google.devtools.build.lib.analysis.starlark.Args→com.google.devtools.build.lib.actions.ParamFileInfocom.google.devtools.build.lib.analysis.starlark.CommandLineItemMapEachAdaptor→com.google.devtools.build.lib.actions.InputMetadataProvidercom.google.devtools.build.lib.analysis.starlark.CommandLineItemMapEachAdaptor→com.google.devtools.build.lib.actions.ParametrizedMapFncom.google.devtools.build.lib.analysis.starlark.FilesetSymlinkFile→com.google.devtools.build.lib.actions.Artifactcom.google.devtools.build.lib.analysis.starlark.FilesetSymlinkFile→com.google.devtools.build.lib.actions.CommandLineItemcom.google.devtools.build.lib.analysis.starlark.FrozenArgs→com.google.devtools.build.lib.actions.Artifactcom.google.devtools.build.lib.analysis.starlark.FrozenArgs→com.google.devtools.build.lib.actions.CommandLinecom.google.devtools.build.lib.analysis.starlark.FrozenArgs→com.google.devtools.build.lib.actions.ParamFileInfocom.google.devtools.build.lib.analysis.starlark.FullExpander→com.google.devtools.build.lib.actions.InputMetadataProvidercom.google.devtools.build.lib.analysis.starlark.GroupedPreprocessedArgs→com.google.devtools.build.lib.actions.PathMappercom.google.devtools.build.lib.analysis.starlark.JoinedPreprocessedVectorArg→com.google.devtools.build.lib.actions.PathMappercom.google.devtools.build.lib.analysis.starlark.MutableArgs→com.google.devtools.build.lib.actions.Artifactcom.google.devtools.build.lib.analysis.starlark.MutableArgs→com.google.devtools.build.lib.actions.CommandLinecom.google.devtools.build.lib.analysis.starlark.MutableArgs→com.google.devtools.build.lib.actions.ParamFileInfocom.google.devtools.build.lib.analysis.starlark.PreprocessedArg→com.google.devtools.build.lib.actions.PathMappercom.google.devtools.build.lib.analysis.starlark.PreprocessedArtifactArg→com.google.devtools.build.lib.actions.PathMappercom.google.devtools.build.lib.analysis.starlark.PreprocessedCommandLine→com.google.devtools.build.lib.actions.ArgChunkcom.google.devtools.build.lib.analysis.starlark.PreprocessedCommandLine→com.google.devtools.build.lib.actions.PathMappercom.google.devtools.build.lib.analysis.starlark.PreprocessedSingleFormattedArg→com.google.devtools.build.lib.actions.PathMappercom.google.devtools.build.lib.analysis.starlark.PreprocessedSingleFormattedArtifactArg→com.google.devtools.build.lib.actions.PathMappercom.google.devtools.build.lib.analysis.starlark.PreprocessedStringArg→com.google.devtools.build.lib.actions.PathMappercom.google.devtools.build.lib.analysis.starlark.StarlarkActionContext→com.google.devtools.build.lib.actions.Artifactcom.google.devtools.build.lib.analysis.starlark.StarlarkActionContext→com.google.devtools.build.lib.actions.ArtifactRoot
- Direction
- com.google.devtools.build.lib.analysis.starlark uses com.google.devtools.build.lib.actions, so a change to com.google.devtools.build.lib.actions can break com.google.devtools.build.lib.analysis.starlark, while a change to com.google.devtools.build.lib.analysis.starlark can't break com.google.devtools.build.lib.actions.
- 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→2 com.google.devtools.build.lib.analysis.test uses com.google.devtools.build.lib.events✕
- Connections
- 3 pairs of types, where a type in com.google.devtools.build.lib.analysis.test uses a type in com.google.devtools.build.lib.events.
- The types involved
com.google.devtools.build.lib.analysis.test.CoverageReportActionFactory→com.google.devtools.build.lib.events.EventHandlercom.google.devtools.build.lib.analysis.test.TestResult→com.google.devtools.build.lib.events.Postablecom.google.devtools.build.lib.analysis.test.TestTrimmingTransition→com.google.devtools.build.lib.events.EventHandler
- Direction
- com.google.devtools.build.lib.analysis.test uses com.google.devtools.build.lib.events, so a change to com.google.devtools.build.lib.events can break com.google.devtools.build.lib.analysis.test, while a change to com.google.devtools.build.lib.analysis.test can't break com.google.devtools.build.lib.events.
- Position
- Below the diagonal: com.google.devtools.build.lib.analysis.test uses a module listed above it, which is the healthy direction.
27→3 com.google.devtools.build.lib.analysis.test uses com.google.devtools.common.options✕
- Connections
- 7 pairs of types, where a type in com.google.devtools.build.lib.analysis.test uses a type in com.google.devtools.common.options.
- The types involved
com.google.devtools.build.lib.analysis.test.Converter→com.google.devtools.common.options.BoolOrEnumConvertercom.google.devtools.build.lib.analysis.test.ShardingStrategyConverter→com.google.devtools.common.options.Contextlesscom.google.devtools.build.lib.analysis.test.TestConfiguration→com.google.devtools.common.options.TriStatecom.google.devtools.build.lib.analysis.test.TestOptions→com.google.devtools.common.options.OptionDefinitioncom.google.devtools.build.lib.analysis.test.TestOptions→com.google.devtools.common.options.TriStatecom.google.devtools.build.lib.analysis.test.TestResourcesConverter→com.google.devtools.common.options.Contextlesscom.google.devtools.build.lib.analysis.test.TestRunnerAction→com.google.devtools.common.options.TriState
- Direction
- com.google.devtools.build.lib.analysis.test uses com.google.devtools.common.options, so a change to com.google.devtools.common.options can break com.google.devtools.build.lib.analysis.test, while a change to com.google.devtools.build.lib.analysis.test can't break com.google.devtools.common.options.
- Position
- Below the diagonal: com.google.devtools.build.lib.analysis.test uses a module listed above it, which is the healthy direction.
27→4 com.google.devtools.build.lib.analysis.test uses net.starlark.java.eval✕
- Connections
- 13 pairs of types, where a type in com.google.devtools.build.lib.analysis.test uses a type in net.starlark.java.eval.
- The types involved
com.google.devtools.build.lib.analysis.test.AnalysisFailure→net.starlark.java.eval.Printercom.google.devtools.build.lib.analysis.test.AnalysisFailure→net.starlark.java.eval.StarlarkSemanticscom.google.devtools.build.lib.analysis.test.CoverageCommon→net.starlark.java.eval.Dictcom.google.devtools.build.lib.analysis.test.CoverageCommon→net.starlark.java.eval.Printercom.google.devtools.build.lib.analysis.test.CoverageCommon→net.starlark.java.eval.Sequencecom.google.devtools.build.lib.analysis.test.CoverageCommon→net.starlark.java.eval.StarlarkSemanticscom.google.devtools.build.lib.analysis.test.CoverageCommon→net.starlark.java.eval.StarlarkThreadcom.google.devtools.build.lib.analysis.test.CoverageCommon→net.starlark.java.eval.Tuplecom.google.devtools.build.lib.analysis.test.ExecutionInfoProvider→net.starlark.java.eval.Dictcom.google.devtools.build.lib.analysis.test.InstrumentedFilesCollector→net.starlark.java.eval.Tuplecom.google.devtools.build.lib.analysis.test.InstrumentedFilesInfo→net.starlark.java.eval.StarlarkThreadcom.google.devtools.build.lib.analysis.test.InstrumentedFilesInfo→net.starlark.java.eval.Tuplecom.google.devtools.build.lib.analysis.test.InstrumentedFilesInfoBuilder→net.starlark.java.eval.Tuple
- Direction
- com.google.devtools.build.lib.analysis.test uses net.starlark.java.eval, so a change to net.starlark.java.eval can break com.google.devtools.build.lib.analysis.test, while a change to com.google.devtools.build.lib.analysis.test can't break net.starlark.java.eval.
- Position
- Below the diagonal: com.google.devtools.build.lib.analysis.test uses a module listed above it, which is the healthy direction.
27→8 com.google.devtools.build.lib.analysis.test uses com.google.devtools.build.lib.vfs✕
- Connections
- 10 pairs of types, where a type in com.google.devtools.build.lib.analysis.test uses a type in com.google.devtools.build.lib.vfs.
- The types involved
com.google.devtools.build.lib.analysis.test.ResolvedPaths→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.analysis.test.ResolvedPaths→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.analysis.test.TestActionContext→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.analysis.test.TestAttempt→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.analysis.test.TestResult→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.analysis.test.TestRunnerAction→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.analysis.test.TestRunnerAction→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.analysis.test.TestStrategy→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.analysis.test.TestStrategy→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.analysis.test.TestTargetExecutionSettings→com.google.devtools.build.lib.vfs.Path
- Direction
- com.google.devtools.build.lib.analysis.test uses com.google.devtools.build.lib.vfs, so a change to com.google.devtools.build.lib.vfs can break com.google.devtools.build.lib.analysis.test, while a change to com.google.devtools.build.lib.analysis.test can't break com.google.devtools.build.lib.vfs.
- Position
- Below the diagonal: com.google.devtools.build.lib.analysis.test uses a module listed above it, which is the healthy direction.
27→11 com.google.devtools.build.lib.analysis.test uses com.google.devtools.build.lib.util✕
- Connections
- 13 pairs of types, where a type in com.google.devtools.build.lib.analysis.test uses a type in com.google.devtools.build.lib.util.
- The types involved
com.google.devtools.build.lib.analysis.test.AnalysisFailurePropagationException→com.google.devtools.build.lib.util.DetailedExitCodecom.google.devtools.build.lib.analysis.test.BaselineCoverageAction→com.google.devtools.build.lib.util.DeterministicWritercom.google.devtools.build.lib.analysis.test.BaselineCoverageAction→com.google.devtools.build.lib.util.Fingerprintcom.google.devtools.build.lib.analysis.test.InstrumentationSpec→com.google.devtools.build.lib.util.FileTypeSetcom.google.devtools.build.lib.analysis.test.InstrumentedFileManifestAction→com.google.devtools.build.lib.util.DeterministicWritercom.google.devtools.build.lib.analysis.test.InstrumentedFileManifestAction→com.google.devtools.build.lib.util.Fingerprintcom.google.devtools.build.lib.analysis.test.TestAttemptResult→com.google.devtools.build.lib.util.DetailedExitCodecom.google.devtools.build.lib.analysis.test.TestOptions→com.google.devtools.build.lib.util.EnvVarcom.google.devtools.build.lib.analysis.test.TestOptions→com.google.devtools.build.lib.util.Paircom.google.devtools.build.lib.analysis.test.TestResourcesConverter→com.google.devtools.build.lib.util.Paircom.google.devtools.build.lib.analysis.test.TestResult→com.google.devtools.build.lib.util.DetailedExitCodecom.google.devtools.build.lib.analysis.test.TestRunnerAction→com.google.devtools.build.lib.util.Fingerprintcom.google.devtools.build.lib.analysis.test.TestTargetExecutionSettings→com.google.devtools.build.lib.util.OS
- Direction
- com.google.devtools.build.lib.analysis.test uses com.google.devtools.build.lib.util, so a change to com.google.devtools.build.lib.util can break com.google.devtools.build.lib.analysis.test, while a change to com.google.devtools.build.lib.analysis.test can't break com.google.devtools.build.lib.util.
- Position
- Below the diagonal: com.google.devtools.build.lib.analysis.test uses a module listed above it, which is the healthy direction.
27→14 com.google.devtools.build.lib.analysis.test uses com.google.devtools.build.lib.buildeventstream✕
- Connections
- 4 pairs of types, where a type in com.google.devtools.build.lib.analysis.test uses a type in com.google.devtools.build.lib.buildeventstream.
- The types involved
com.google.devtools.build.lib.analysis.test.TestAttempt→com.google.devtools.build.lib.buildeventstream.BuildEventContextcom.google.devtools.build.lib.analysis.test.TestAttempt→com.google.devtools.build.lib.buildeventstream.BuildEventWithOrderConstraintcom.google.devtools.build.lib.analysis.test.TestProgress→com.google.devtools.build.lib.buildeventstream.BuildEventcom.google.devtools.build.lib.analysis.test.TestProgress→com.google.devtools.build.lib.buildeventstream.BuildEventContext
- Direction
- com.google.devtools.build.lib.analysis.test uses com.google.devtools.build.lib.buildeventstream, so a change to com.google.devtools.build.lib.buildeventstream can break com.google.devtools.build.lib.analysis.test, while a change to com.google.devtools.build.lib.analysis.test can't break com.google.devtools.build.lib.buildeventstream.
- Position
- Below the diagonal: com.google.devtools.build.lib.analysis.test uses a module listed above it, which is the healthy direction.
27→15 com.google.devtools.build.lib.analysis.test uses com.google.devtools.build.lib.exec✕
- Connections
- 1 pair of types, where a type in com.google.devtools.build.lib.analysis.test uses a type in com.google.devtools.build.lib.exec.
- The types involved
com.google.devtools.build.lib.analysis.test.TestStrategy→com.google.devtools.build.lib.exec.ExecutionOptions
- Direction
- com.google.devtools.build.lib.analysis.test uses com.google.devtools.build.lib.exec, so a change to com.google.devtools.build.lib.exec can break com.google.devtools.build.lib.analysis.test, while a change to com.google.devtools.build.lib.analysis.test can't break com.google.devtools.build.lib.exec.
- Position
- Below the diagonal: com.google.devtools.build.lib.analysis.test uses a module listed above it, which is the healthy direction.
27→24 com.google.devtools.build.lib.analysis.test uses com.google.devtools.build.lib.skyframe✕
- Connections
- 1 pair of types, where a type in com.google.devtools.build.lib.analysis.test uses a type in com.google.devtools.build.lib.skyframe.
- The types involved
com.google.devtools.build.lib.analysis.test.AnalysisFailurePropagationException→com.google.devtools.build.lib.skyframe.AbstractSaneAnalysisException
- Direction
- com.google.devtools.build.lib.analysis.test uses com.google.devtools.build.lib.skyframe, so a change to com.google.devtools.build.lib.skyframe can break com.google.devtools.build.lib.analysis.test, while a change to com.google.devtools.build.lib.analysis.test can't break com.google.devtools.build.lib.skyframe.
- Position
- Below the diagonal: com.google.devtools.build.lib.analysis.test uses a module listed above it, which is the healthy direction.
27→25 com.google.devtools.build.lib.analysis.test uses com.google.devtools.build.lib.packages✕
- Connections
- 19 pairs of types, where a type in com.google.devtools.build.lib.analysis.test uses a type in com.google.devtools.build.lib.packages.
- The types involved
com.google.devtools.build.lib.analysis.test.AnalysisFailureInfo→com.google.devtools.build.lib.packages.Infocom.google.devtools.build.lib.analysis.test.AnalysisFailureInfoProvider→com.google.devtools.build.lib.packages.BuiltinProvidercom.google.devtools.build.lib.analysis.test.AnalysisTestResultInfo→com.google.devtools.build.lib.packages.Infocom.google.devtools.build.lib.analysis.test.ExecutionInfo→com.google.devtools.build.lib.packages.BuiltinProvidercom.google.devtools.build.lib.analysis.test.ExecutionInfo→com.google.devtools.build.lib.packages.NativeInfocom.google.devtools.build.lib.analysis.test.ExecutionInfoProvider→com.google.devtools.build.lib.packages.BuiltinProvidercom.google.devtools.build.lib.analysis.test.InstrumentedFilesCollector→com.google.devtools.build.lib.packages.Attributecom.google.devtools.build.lib.analysis.test.InstrumentedFilesInfo→com.google.devtools.build.lib.packages.NativeInfocom.google.devtools.build.lib.analysis.test.InstrumentedFilesProvider→com.google.devtools.build.lib.packages.BuiltinProvidercom.google.devtools.build.lib.analysis.test.TestConfiguration→com.google.devtools.build.lib.packages.TestSizecom.google.devtools.build.lib.analysis.test.TestConfiguration→com.google.devtools.build.lib.packages.TestTimeoutcom.google.devtools.build.lib.analysis.test.TestOptions→com.google.devtools.build.lib.packages.TestSizecom.google.devtools.build.lib.analysis.test.TestOptions→com.google.devtools.build.lib.packages.TestTimeoutcom.google.devtools.build.lib.analysis.test.TestParams→com.google.devtools.build.lib.packages.TestTimeoutcom.google.devtools.build.lib.analysis.test.TestResourcesConverter→com.google.devtools.build.lib.packages.TestSizecom.google.devtools.build.lib.analysis.test.TestResultInfoProvider→com.google.devtools.build.lib.packages.BuiltinProvidercom.google.devtools.build.lib.analysis.test.TestTargetProperties→com.google.devtools.build.lib.packages.TestSizecom.google.devtools.build.lib.analysis.test.TestTargetProperties→com.google.devtools.build.lib.packages.TestTimeoutcom.google.devtools.build.lib.analysis.test.TestTrimmingTransitionFactory→com.google.devtools.build.lib.packages.RuleTransitionData
- Direction
- com.google.devtools.build.lib.analysis.test uses com.google.devtools.build.lib.packages, so a change to com.google.devtools.build.lib.packages can break com.google.devtools.build.lib.analysis.test, while a change to com.google.devtools.build.lib.analysis.test can't break com.google.devtools.build.lib.packages.
- Position
- Below the diagonal: com.google.devtools.build.lib.analysis.test uses a module listed above it, which is the healthy direction.
27→26 com.google.devtools.build.lib.analysis.test uses com.google.devtools.build.lib.analysis.starlark✕
- Connections
- 1 pair of types, where a type in com.google.devtools.build.lib.analysis.test uses a type in com.google.devtools.build.lib.analysis.starlark.
- The types involved
com.google.devtools.build.lib.analysis.test.CoverageCommon→com.google.devtools.build.lib.analysis.starlark.StarlarkRuleContext
- Direction
- com.google.devtools.build.lib.analysis.test uses com.google.devtools.build.lib.analysis.starlark, so a change to com.google.devtools.build.lib.analysis.starlark can break com.google.devtools.build.lib.analysis.test, while a change to com.google.devtools.build.lib.analysis.test can't break com.google.devtools.build.lib.analysis.starlark.
- Position
- Below the diagonal: com.google.devtools.build.lib.analysis.test uses a module listed above it, which is the healthy direction.
27→28 com.google.devtools.build.lib.analysis.test uses com.google.devtools.build.lib.runtime part of a loop✕
- Connections
- 1 pair of types, where a type in com.google.devtools.build.lib.analysis.test uses a type in com.google.devtools.build.lib.runtime.
- The types involved
com.google.devtools.build.lib.analysis.test.TestStrategy→com.google.devtools.build.lib.runtime.TestSummaryOptions
- Direction
- com.google.devtools.build.lib.analysis.test uses com.google.devtools.build.lib.runtime, so a change to com.google.devtools.build.lib.runtime can break com.google.devtools.build.lib.analysis.test, while a change to com.google.devtools.build.lib.analysis.test can't break com.google.devtools.build.lib.runtime.
- 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→30 com.google.devtools.build.lib.analysis.test uses com.google.devtools.build.lib.collect.nestedset part of a loop✕
- Connections
- 12 pairs of types, where a type in com.google.devtools.build.lib.analysis.test uses a type in com.google.devtools.build.lib.collect.nestedset.
- The types involved
com.google.devtools.build.lib.analysis.test.AnalysisFailureInfo→com.google.devtools.build.lib.collect.nestedset.Depsetcom.google.devtools.build.lib.analysis.test.AnalysisFailureInfo→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.analysis.test.BaselineCoverageAction→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.analysis.test.CoverageCommon→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.analysis.test.InstrumentedFileManifestAction→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.analysis.test.InstrumentedFilesCollector→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.analysis.test.InstrumentedFilesInfo→com.google.devtools.build.lib.collect.nestedset.Depsetcom.google.devtools.build.lib.analysis.test.InstrumentedFilesInfo→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.analysis.test.InstrumentedFilesInfoBuilder→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.analysis.test.InstrumentedFilesInfoBuilder→com.google.devtools.build.lib.collect.nestedset.NestedSetBuildercom.google.devtools.build.lib.analysis.test.TestActionBuilder→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.analysis.test.TestRunnerAction→com.google.devtools.build.lib.collect.nestedset.NestedSet
- Direction
- com.google.devtools.build.lib.analysis.test uses com.google.devtools.build.lib.collect.nestedset, so a change to com.google.devtools.build.lib.collect.nestedset can break com.google.devtools.build.lib.analysis.test, while a change to com.google.devtools.build.lib.analysis.test can't break com.google.devtools.build.lib.collect.nestedset.
- 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→31 com.google.devtools.build.lib.analysis.test uses com.google.devtools.build.lib.cmdline part of a loop✕
- Connections
- 10 pairs of types, where a type in com.google.devtools.build.lib.analysis.test uses a type in com.google.devtools.build.lib.cmdline.
- The types involved
com.google.devtools.build.lib.analysis.test.AnalysisFailure→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.analysis.test.AnalysisFailurePropagationException→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.analysis.test.CoverageConfiguration→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.analysis.test.CoverageOptions→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.analysis.test.InstrumentedFilesCollector→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.analysis.test.TestConfiguration→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.analysis.test.TestOptions→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.analysis.test.TestStrategy→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.analysis.test.TestTargetProperties→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.analysis.test.TestTrimmingTransitionFactory→com.google.devtools.build.lib.cmdline.Label
- Direction
- com.google.devtools.build.lib.analysis.test uses com.google.devtools.build.lib.cmdline, so a change to com.google.devtools.build.lib.cmdline can break com.google.devtools.build.lib.analysis.test, while a change to com.google.devtools.build.lib.analysis.test can't break com.google.devtools.build.lib.cmdline.
- 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→32 com.google.devtools.build.lib.analysis.test uses com.google.devtools.build.lib.analysis.platform part of a loop✕
- Connections
- 1 pair of types, where a type in com.google.devtools.build.lib.analysis.test uses a type in com.google.devtools.build.lib.analysis.platform.
- The types involved
com.google.devtools.build.lib.analysis.test.TestTargetExecutionSettings→com.google.devtools.build.lib.analysis.platform.PlatformInfo
- Direction
- com.google.devtools.build.lib.analysis.test uses com.google.devtools.build.lib.analysis.platform, so a change to com.google.devtools.build.lib.analysis.platform can break com.google.devtools.build.lib.analysis.test, while a change to com.google.devtools.build.lib.analysis.test can't break com.google.devtools.build.lib.analysis.platform.
- 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→33 com.google.devtools.build.lib.analysis.test uses com.google.devtools.build.lib.analysis.config part of a loop✕
- Connections
- 18 pairs of types, where a type in com.google.devtools.build.lib.analysis.test uses a type in com.google.devtools.build.lib.analysis.config.
- The types involved
com.google.devtools.build.lib.analysis.test.CoverageConfiguration→com.google.devtools.build.lib.analysis.config.BuildOptionscom.google.devtools.build.lib.analysis.test.CoverageConfiguration→com.google.devtools.build.lib.analysis.config.Fragmentcom.google.devtools.build.lib.analysis.test.CoverageOptions→com.google.devtools.build.lib.analysis.config.FragmentOptionscom.google.devtools.build.lib.analysis.test.InstrumentedFilesCollector→com.google.devtools.build.lib.analysis.config.BuildConfigurationValuecom.google.devtools.build.lib.analysis.test.RunsPerTestConverter→com.google.devtools.build.lib.analysis.config.PerLabelOptionscom.google.devtools.build.lib.analysis.test.RunsPerTestConverter→com.google.devtools.build.lib.analysis.config.PerLabelOptionsConvertercom.google.devtools.build.lib.analysis.test.TestConfiguration→com.google.devtools.build.lib.analysis.config.BuildOptionscom.google.devtools.build.lib.analysis.test.TestConfiguration→com.google.devtools.build.lib.analysis.config.Fragmentcom.google.devtools.build.lib.analysis.test.TestOptions→com.google.devtools.build.lib.analysis.config.FragmentOptionscom.google.devtools.build.lib.analysis.test.TestOptions→com.google.devtools.build.lib.analysis.config.PerLabelOptionscom.google.devtools.build.lib.analysis.test.TestRunnerAction→com.google.devtools.build.lib.analysis.config.BuildConfigurationValuecom.google.devtools.build.lib.analysis.test.TestTargetExecutionSettings→com.google.devtools.build.lib.analysis.config.RunUndercom.google.devtools.build.lib.analysis.test.TestTrimmingLogic→com.google.devtools.build.lib.analysis.config.BuildOptionscom.google.devtools.build.lib.analysis.test.TestTrimmingLogic→com.google.devtools.build.lib.analysis.config.BuildOptionsViewcom.google.devtools.build.lib.analysis.test.TestTrimmingTransition→com.google.devtools.build.lib.analysis.config.BuildOptionscom.google.devtools.build.lib.analysis.test.TestTrimmingTransition→com.google.devtools.build.lib.analysis.config.BuildOptionsViewcom.google.devtools.build.lib.analysis.test.TestTrimmingTransition→com.google.devtools.build.lib.analysis.config.FragmentOptionscom.google.devtools.build.lib.analysis.test.TestTrimmingTransitionFactory→com.google.devtools.build.lib.analysis.config.FragmentOptions
- Direction
- com.google.devtools.build.lib.analysis.test uses com.google.devtools.build.lib.analysis.config, so a change to com.google.devtools.build.lib.analysis.config can break com.google.devtools.build.lib.analysis.test, while a change to com.google.devtools.build.lib.analysis.test can't break com.google.devtools.build.lib.analysis.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.
27→34 com.google.devtools.build.lib.analysis.test uses com.google.devtools.build.lib.analysis.actions part of a loop✕
- Connections
- 3 pairs of types, where a type in com.google.devtools.build.lib.analysis.test uses a type in com.google.devtools.build.lib.analysis.actions.
- The types involved
com.google.devtools.build.lib.analysis.test.AnalysisTestActionBuilder→com.google.devtools.build.lib.analysis.actions.ActionConstructionContextcom.google.devtools.build.lib.analysis.test.BaselineCoverageAction→com.google.devtools.build.lib.analysis.actions.AbstractFileWriteActioncom.google.devtools.build.lib.analysis.test.InstrumentedFileManifestAction→com.google.devtools.build.lib.analysis.actions.AbstractFileWriteAction
- Direction
- com.google.devtools.build.lib.analysis.test uses com.google.devtools.build.lib.analysis.actions, so a change to com.google.devtools.build.lib.analysis.actions can break com.google.devtools.build.lib.analysis.test, while a change to com.google.devtools.build.lib.analysis.test can't break com.google.devtools.build.lib.analysis.actions.
- 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→35 com.google.devtools.build.lib.analysis.test uses com.google.devtools.build.lib.analysis part of a loop✕
- Connections
- 21 pairs of types, where a type in com.google.devtools.build.lib.analysis.test uses a type in com.google.devtools.build.lib.analysis.
- The types involved
com.google.devtools.build.lib.analysis.test.CoverageCommon→com.google.devtools.build.lib.analysis.RuleContextcom.google.devtools.build.lib.analysis.test.CoverageParams→com.google.devtools.build.lib.analysis.FilesToRunProvidercom.google.devtools.build.lib.analysis.test.CoverageReportActionFactory→com.google.devtools.build.lib.analysis.BlazeDirectoriescom.google.devtools.build.lib.analysis.test.CoverageReportActionFactory→com.google.devtools.build.lib.analysis.ConfiguredTargetcom.google.devtools.build.lib.analysis.test.InstrumentedFilesCollector→com.google.devtools.build.lib.analysis.RuleContextcom.google.devtools.build.lib.analysis.test.InstrumentedFilesCollector→com.google.devtools.build.lib.analysis.TransitiveInfoCollectioncom.google.devtools.build.lib.analysis.test.InstrumentedFilesInfoBuilder→com.google.devtools.build.lib.analysis.RuleContextcom.google.devtools.build.lib.analysis.test.InstrumentedFilesInfoBuilder→com.google.devtools.build.lib.analysis.TransitiveInfoCollectioncom.google.devtools.build.lib.analysis.test.TestActionBuilder→com.google.devtools.build.lib.analysis.FilesToRunProvidercom.google.devtools.build.lib.analysis.test.TestActionBuilder→com.google.devtools.build.lib.analysis.RuleContextcom.google.devtools.build.lib.analysis.test.TestActionBuilder→com.google.devtools.build.lib.analysis.RunfilesSupportcom.google.devtools.build.lib.analysis.test.TestConfiguration→com.google.devtools.build.lib.analysis.OptionsDiffPredicatecom.google.devtools.build.lib.analysis.test.TestParams→com.google.devtools.build.lib.analysis.FilesToRunProvidercom.google.devtools.build.lib.analysis.test.TestProvider→com.google.devtools.build.lib.analysis.TransitiveInfoCollectioncom.google.devtools.build.lib.analysis.test.TestProvider→com.google.devtools.build.lib.analysis.TransitiveInfoProvidercom.google.devtools.build.lib.analysis.test.TestRunnerAction→com.google.devtools.build.lib.analysis.FilesToRunProvidercom.google.devtools.build.lib.analysis.test.TestTagsProvider→com.google.devtools.build.lib.analysis.TransitiveInfoProvidercom.google.devtools.build.lib.analysis.test.TestTargetExecutionSettings→com.google.devtools.build.lib.analysis.RuleContextcom.google.devtools.build.lib.analysis.test.TestTargetExecutionSettings→com.google.devtools.build.lib.analysis.Runfilescom.google.devtools.build.lib.analysis.test.TestTargetExecutionSettings→com.google.devtools.build.lib.analysis.RunfilesSupportcom.google.devtools.build.lib.analysis.test.TestTargetProperties→com.google.devtools.build.lib.analysis.RuleContext
- Direction
- com.google.devtools.build.lib.analysis.test uses com.google.devtools.build.lib.analysis, so a change to com.google.devtools.build.lib.analysis can break com.google.devtools.build.lib.analysis.test, while a change to com.google.devtools.build.lib.analysis.test can't break com.google.devtools.build.lib.analysis.
- 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→37 com.google.devtools.build.lib.analysis.test uses com.google.devtools.build.lib.actions part of a loop✕
- Connections
- 58 pairs of types, where a type in com.google.devtools.build.lib.analysis.test uses a type in com.google.devtools.build.lib.actions. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.google.devtools.build.lib.analysis.test.AnalysisTestActionBuilder→com.google.devtools.build.lib.actions.Artifactcom.google.devtools.build.lib.analysis.test.BaselineCoverageAction→com.google.devtools.build.lib.actions.ActionExecutionContextcom.google.devtools.build.lib.analysis.test.BaselineCoverageAction→com.google.devtools.build.lib.actions.ActionKeyContextcom.google.devtools.build.lib.analysis.test.BaselineCoverageAction→com.google.devtools.build.lib.actions.ActionOwnercom.google.devtools.build.lib.analysis.test.BaselineCoverageAction→com.google.devtools.build.lib.actions.Artifactcom.google.devtools.build.lib.analysis.test.BaselineCoverageAction→com.google.devtools.build.lib.actions.InputMetadataProvidercom.google.devtools.build.lib.analysis.test.CoverageArtifactsKnownEvent→com.google.devtools.build.lib.actions.Artifactcom.google.devtools.build.lib.analysis.test.CoverageCommon→com.google.devtools.build.lib.actions.Artifactcom.google.devtools.build.lib.analysis.test.CoverageParams→com.google.devtools.build.lib.actions.ActionOwnercom.google.devtools.build.lib.analysis.test.CoverageParams→com.google.devtools.build.lib.actions.Artifactcom.google.devtools.build.lib.analysis.test.CoverageReportActionFactory→com.google.devtools.build.lib.actions.ActionKeyContextcom.google.devtools.build.lib.analysis.test.CoverageReportActionFactory→com.google.devtools.build.lib.actions.ActionLookupKeycom.google.devtools.build.lib.analysis.test.CoverageReportActionFactory→com.google.devtools.build.lib.actions.ArtifactFactorycom.google.devtools.build.lib.analysis.test.CoverageReportActionsWrapper→com.google.devtools.build.lib.actions.ActionAnalysisMetadatacom.google.devtools.build.lib.analysis.test.CoverageReportActionsWrapper→com.google.devtools.build.lib.actions.ActionKeyContextcom.google.devtools.build.lib.analysis.test.CoverageReportActionsWrapper→com.google.devtools.build.lib.actions.Artifactcom.google.devtools.build.lib.analysis.test.InstrumentedFileManifestAction→com.google.devtools.build.lib.actions.ActionExecutionContextcom.google.devtools.build.lib.analysis.test.InstrumentedFileManifestAction→com.google.devtools.build.lib.actions.ActionKeyContextcom.google.devtools.build.lib.analysis.test.InstrumentedFileManifestAction→com.google.devtools.build.lib.actions.ActionOwnercom.google.devtools.build.lib.analysis.test.InstrumentedFileManifestAction→com.google.devtools.build.lib.actions.Artifactcom.google.devtools.build.lib.analysis.test.InstrumentedFileManifestAction→com.google.devtools.build.lib.actions.InputMetadataProvidercom.google.devtools.build.lib.analysis.test.InstrumentedFilesCollector→com.google.devtools.build.lib.actions.Artifactcom.google.devtools.build.lib.analysis.test.InstrumentedFilesInfo→com.google.devtools.build.lib.actions.Artifactcom.google.devtools.build.lib.analysis.test.InstrumentedFilesInfoBuilder→com.google.devtools.build.lib.actions.Artifactcom.google.devtools.build.lib.analysis.test.ShardKey→com.google.devtools.build.lib.actions.ActionOwner
- Direction
- com.google.devtools.build.lib.analysis.test uses com.google.devtools.build.lib.actions, so a change to com.google.devtools.build.lib.actions can break com.google.devtools.build.lib.analysis.test, while a change to com.google.devtools.build.lib.analysis.test can't break com.google.devtools.build.lib.actions.
- 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→1 com.google.devtools.build.lib.runtime uses net.starlark.java.syntax✕
- Connections
- 1 pair of types, where a type in com.google.devtools.build.lib.runtime uses a type in net.starlark.java.syntax.
- The types involved
com.google.devtools.build.lib.runtime.LocationPrinter→net.starlark.java.syntax.Location
- Direction
- com.google.devtools.build.lib.runtime uses net.starlark.java.syntax, so a change to net.starlark.java.syntax can break com.google.devtools.build.lib.runtime, while a change to com.google.devtools.build.lib.runtime can't break net.starlark.java.syntax.
- Position
- Below the diagonal: com.google.devtools.build.lib.runtime uses a module listed above it, which is the healthy direction.
28→2 com.google.devtools.build.lib.runtime uses com.google.devtools.build.lib.events✕
- Connections
- 27 pairs of types, where a type in com.google.devtools.build.lib.runtime uses a type in com.google.devtools.build.lib.events. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.google.devtools.build.lib.runtime.BlazeCommandDispatcher→com.google.devtools.build.lib.events.Eventcom.google.devtools.build.lib.runtime.BlazeCommandDispatcher→com.google.devtools.build.lib.events.Reportercom.google.devtools.build.lib.runtime.BlazeCommandDispatcher→com.google.devtools.build.lib.events.StoredEventHandlercom.google.devtools.build.lib.runtime.BlazeOptionHandler→com.google.devtools.build.lib.events.EventHandlercom.google.devtools.build.lib.runtime.BlazeOptionHandler→com.google.devtools.build.lib.events.ExtendedEventHandlercom.google.devtools.build.lib.runtime.BlazeRuntime→com.google.devtools.build.lib.events.ExtendedEventHandlercom.google.devtools.build.lib.runtime.BlazeWorkspace→com.google.devtools.build.lib.events.Reportercom.google.devtools.build.lib.runtime.BuildSummaryStatsModule→com.google.devtools.build.lib.events.Reportercom.google.devtools.build.lib.runtime.CommandEnvironment→com.google.devtools.build.lib.events.Reportercom.google.devtools.build.lib.runtime.ConfigExpander→com.google.devtools.build.lib.events.EventHandlercom.google.devtools.build.lib.runtime.EventFiltersConverter→com.google.devtools.build.lib.events.EventKindcom.google.devtools.build.lib.runtime.EventKindFilters→com.google.devtools.build.lib.events.EventKindcom.google.devtools.build.lib.runtime.InstrumentationOutputFactory→com.google.devtools.build.lib.events.EventHandlercom.google.devtools.build.lib.runtime.NonPostingEventHandler→com.google.devtools.build.lib.events.Eventcom.google.devtools.build.lib.runtime.NonPostingEventHandler→com.google.devtools.build.lib.events.ExtendedEventHandlercom.google.devtools.build.lib.runtime.NonPostingEventHandler→com.google.devtools.build.lib.events.Postablecom.google.devtools.build.lib.runtime.ProjectFile→com.google.devtools.build.lib.events.EventHandlercom.google.devtools.build.lib.runtime.ProjectFileSupport→com.google.devtools.build.lib.events.ExtendedEventHandlercom.google.devtools.build.lib.runtime.RemoteRepoContentsCache→com.google.devtools.build.lib.events.ExtendedEventHandlercom.google.devtools.build.lib.runtime.SkyframeExecutorTargetLoader→com.google.devtools.build.lib.events.ExtendedEventHandlercom.google.devtools.build.lib.runtime.SkymeldUiStateTracker→com.google.devtools.build.lib.events.Eventcom.google.devtools.build.lib.runtime.TargetProviderForQueryEnvironment→com.google.devtools.build.lib.events.ExtendedEventHandlercom.google.devtools.build.lib.runtime.UiEventHandler→com.google.devtools.build.lib.events.Eventcom.google.devtools.build.lib.runtime.UiEventHandler→com.google.devtools.build.lib.events.EventHandlercom.google.devtools.build.lib.runtime.UiEventHandler→com.google.devtools.build.lib.events.EventKind
- Direction
- com.google.devtools.build.lib.runtime uses com.google.devtools.build.lib.events, so a change to com.google.devtools.build.lib.events can break com.google.devtools.build.lib.runtime, while a change to com.google.devtools.build.lib.runtime can't break com.google.devtools.build.lib.events.
- Position
- Below the diagonal: com.google.devtools.build.lib.runtime uses a module listed above it, which is the healthy direction.
28→3 com.google.devtools.build.lib.runtime uses com.google.devtools.common.options✕
- Connections
- 74 pairs of types, where a type in com.google.devtools.build.lib.runtime uses a type in com.google.devtools.common.options. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.google.devtools.build.lib.runtime.3031→com.google.devtools.common.options.EnumConvertercom.google.devtools.build.lib.runtime.BazelCommandLineEvent→com.google.devtools.common.options.OptionDefinitioncom.google.devtools.build.lib.runtime.BazelCommandLineEvent→com.google.devtools.common.options.OptionEffectTagcom.google.devtools.build.lib.runtime.BazelCommandLineEvent→com.google.devtools.common.options.OptionMetadataTagcom.google.devtools.build.lib.runtime.BazelCommandLineEvent→com.google.devtools.common.options.OptionsParsingResultcom.google.devtools.build.lib.runtime.BazelCommandLineEvent→com.google.devtools.common.options.ParsedOptionDescriptioncom.google.devtools.build.lib.runtime.BlazeCommand→com.google.devtools.common.options.OptionsParsercom.google.devtools.build.lib.runtime.BlazeCommand→com.google.devtools.common.options.OptionsParsingResultcom.google.devtools.build.lib.runtime.BlazeCommandDispatcher→com.google.devtools.common.options.OpaqueOptionsDatacom.google.devtools.build.lib.runtime.BlazeCommandDispatcher→com.google.devtools.common.options.OptionsParsercom.google.devtools.build.lib.runtime.BlazeCommandUtils→com.google.devtools.common.options.HelpVerbositycom.google.devtools.build.lib.runtime.BlazeCommandUtils→com.google.devtools.common.options.OptionsBasecom.google.devtools.build.lib.runtime.BlazeModule→com.google.devtools.common.options.OptionsBasecom.google.devtools.build.lib.runtime.BlazeModule→com.google.devtools.common.options.OptionsParsingResultcom.google.devtools.build.lib.runtime.BlazeModule→com.google.devtools.common.options.OptionsProvidercom.google.devtools.build.lib.runtime.BlazeOptionHandler→com.google.devtools.common.options.OptionAndRawValuecom.google.devtools.build.lib.runtime.BlazeOptionHandler→com.google.devtools.common.options.OptionsBasecom.google.devtools.build.lib.runtime.BlazeOptionHandler→com.google.devtools.common.options.OptionsParsercom.google.devtools.build.lib.runtime.BlazeOptionHandler→com.google.devtools.common.options.OptionsParsingExceptioncom.google.devtools.build.lib.runtime.BlazeOptionHandler→com.google.devtools.common.options.OptionsParsingResultcom.google.devtools.build.lib.runtime.BlazeRuntime→com.google.devtools.common.options.OptionsParsingResultcom.google.devtools.build.lib.runtime.BlazeRuntime→com.google.devtools.common.options.OptionsProvidercom.google.devtools.build.lib.runtime.BlazeServerStartupOptions→com.google.devtools.common.options.OptionsBasecom.google.devtools.build.lib.runtime.BlazeService→com.google.devtools.common.options.OptionsBasecom.google.devtools.build.lib.runtime.BlazeService→com.google.devtools.common.options.OptionsProvider
- Direction
- com.google.devtools.build.lib.runtime uses com.google.devtools.common.options, so a change to com.google.devtools.common.options can break com.google.devtools.build.lib.runtime, while a change to com.google.devtools.build.lib.runtime can't break com.google.devtools.common.options.
- Position
- Below the diagonal: com.google.devtools.build.lib.runtime uses a module listed above it, which is the healthy direction.
28→6 com.google.devtools.build.lib.runtime uses com.google.devtools.build.skyframe✕
- Connections
- 6 pairs of types, where a type in com.google.devtools.build.lib.runtime uses a type in com.google.devtools.build.skyframe.
- The types involved
com.google.devtools.build.lib.runtime.ExecutionGraphModule→com.google.devtools.build.skyframe.WalkableGraphcom.google.devtools.build.lib.runtime.RemoteRepoContentsCache→com.google.devtools.build.skyframe.Environmentcom.google.devtools.build.lib.runtime.TargetProviderForQueryEnvironment→com.google.devtools.build.skyframe.SkyKeycom.google.devtools.build.lib.runtime.TargetProviderForQueryEnvironment→com.google.devtools.build.skyframe.WalkableGraphcom.google.devtools.build.lib.runtime.WorkspaceBuilder→com.google.devtools.build.skyframe.SkyFunctioncom.google.devtools.build.lib.runtime.WorkspaceBuilder→com.google.devtools.build.skyframe.SkyFunctionName
- Direction
- com.google.devtools.build.lib.runtime uses com.google.devtools.build.skyframe, so a change to com.google.devtools.build.skyframe can break com.google.devtools.build.lib.runtime, while a change to com.google.devtools.build.lib.runtime can't break com.google.devtools.build.skyframe.
- Position
- Below the diagonal: com.google.devtools.build.lib.runtime uses a module listed above it, which is the healthy direction.
28→8 com.google.devtools.build.lib.runtime uses com.google.devtools.build.lib.vfs✕
- Connections
- 56 pairs of types, where a type in com.google.devtools.build.lib.runtime uses a type in com.google.devtools.build.lib.vfs. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.google.devtools.build.lib.runtime.1PathAndMtime→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.runtime.ActionDumpFileCreationException→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.runtime.AsyncDirectoryCleaner→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.runtime.BlazeModule→com.google.devtools.build.lib.vfs.FileSystemcom.google.devtools.build.lib.runtime.BlazeModule→com.google.devtools.build.lib.vfs.OutputServicecom.google.devtools.build.lib.runtime.BlazeModuleEnvironment→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.runtime.BlazeOptionHandler→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.runtime.BlazeRuntime→com.google.devtools.build.lib.vfs.FileSystemcom.google.devtools.build.lib.runtime.BlazeRuntime→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.runtime.BlazeServerStartupOptions→com.google.devtools.build.lib.vfs.DigestHashFunctioncom.google.devtools.build.lib.runtime.BlazeServerStartupOptions→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.runtime.BlazeWorkspace→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.runtime.BlazeWorkspace→com.google.devtools.build.lib.vfs.SyscallCachecom.google.devtools.build.lib.runtime.Builder→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.runtime.CommandEnvironment→com.google.devtools.build.lib.vfs.OutputServicecom.google.devtools.build.lib.runtime.CommandEnvironment→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.runtime.CommandEnvironment→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.runtime.CommandEnvironment→com.google.devtools.build.lib.vfs.SyscallCachecom.google.devtools.build.lib.runtime.CommandEnvironment→com.google.devtools.build.lib.vfs.XattrProvidercom.google.devtools.build.lib.runtime.CommandLineBuilder→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.runtime.CommandLinePathFactory→com.google.devtools.build.lib.vfs.FileSystemcom.google.devtools.build.lib.runtime.CommandLinePathFactory→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.runtime.CommandLogModule→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.runtime.CommonCommandOptions→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.runtime.ExecRootEvent→com.google.devtools.build.lib.vfs.Path
- Direction
- com.google.devtools.build.lib.runtime uses com.google.devtools.build.lib.vfs, so a change to com.google.devtools.build.lib.vfs can break com.google.devtools.build.lib.runtime, while a change to com.google.devtools.build.lib.runtime can't break com.google.devtools.build.lib.vfs.
- Position
- Below the diagonal: com.google.devtools.build.lib.runtime uses a module listed above it, which is the healthy direction.
28→11 com.google.devtools.build.lib.runtime uses com.google.devtools.build.lib.util✕
- Connections
- 25 pairs of types, where a type in com.google.devtools.build.lib.runtime uses a type in com.google.devtools.build.lib.util.
- The types involved
com.google.devtools.build.lib.runtime.AggregatingTestListener→com.google.devtools.build.lib.util.DetailedExitCodecom.google.devtools.build.lib.runtime.BlazeCommandDispatcher→com.google.devtools.build.lib.util.Paircom.google.devtools.build.lib.runtime.BlazeCommandResult→com.google.devtools.build.lib.util.DetailedExitCodecom.google.devtools.build.lib.runtime.BlazeCommandResult→com.google.devtools.build.lib.util.ExitCodecom.google.devtools.build.lib.runtime.BlazeModule→com.google.devtools.build.lib.util.DetailedExitCodecom.google.devtools.build.lib.runtime.BlazeModuleEnvironment→com.google.devtools.build.lib.util.AbruptExitExceptioncom.google.devtools.build.lib.runtime.BlazeOptionHandler→com.google.devtools.build.lib.util.DetailedExitCodecom.google.devtools.build.lib.runtime.BlazeRuntime→com.google.devtools.build.lib.util.AbruptExitExceptioncom.google.devtools.build.lib.runtime.BlazeRuntime→com.google.devtools.build.lib.util.DetailedExitCodecom.google.devtools.build.lib.runtime.BlazeRuntime→com.google.devtools.build.lib.util.FileSystemLockcom.google.devtools.build.lib.runtime.BuildEventStreamer→com.google.devtools.build.lib.util.Paircom.google.devtools.build.lib.runtime.Builder→com.google.devtools.build.lib.util.DetailedExitCodecom.google.devtools.build.lib.runtime.CommandCompleteEvent→com.google.devtools.build.lib.util.DetailedExitCodecom.google.devtools.build.lib.runtime.CommandDispatcher→com.google.devtools.build.lib.util.Paircom.google.devtools.build.lib.runtime.CommandEnvironment→com.google.devtools.build.lib.util.AbruptExitExceptioncom.google.devtools.build.lib.runtime.CommandEnvironment→com.google.devtools.build.lib.util.DetailedExitCodecom.google.devtools.build.lib.runtime.CommonCommandOptions→com.google.devtools.build.lib.util.EnvVarcom.google.devtools.build.lib.runtime.DetailedParseResults→com.google.devtools.build.lib.util.DetailedExitCodecom.google.devtools.build.lib.runtime.LoadingPhaseThreadCountConverter→com.google.devtools.build.lib.util.IntegerConvertercom.google.devtools.build.lib.runtime.ModuleEnvironment→com.google.devtools.build.lib.util.AbruptExitExceptioncom.google.devtools.build.lib.runtime.OriginalCommandLineEvent→com.google.devtools.build.lib.util.Paircom.google.devtools.build.lib.runtime.StarlarkOptionsParser→com.google.devtools.build.lib.util.Paircom.google.devtools.build.lib.runtime.TaskException→com.google.devtools.build.lib.util.AbruptExitExceptioncom.google.devtools.build.lib.runtime.TestSummary→com.google.devtools.build.lib.util.DetailedExitCodecom.google.devtools.build.lib.runtime.ThreadDumpModule→com.google.devtools.build.lib.util.AbruptExitException
- Direction
- com.google.devtools.build.lib.runtime uses com.google.devtools.build.lib.util, so a change to com.google.devtools.build.lib.util can break com.google.devtools.build.lib.runtime, while a change to com.google.devtools.build.lib.runtime can't break com.google.devtools.build.lib.util.
- Position
- Below the diagonal: com.google.devtools.build.lib.runtime uses a module listed above it, which is the healthy direction.
28→14 com.google.devtools.build.lib.runtime uses com.google.devtools.build.lib.buildeventstream✕
- Connections
- 37 pairs of types, where a type in com.google.devtools.build.lib.runtime uses a type in com.google.devtools.build.lib.buildeventstream. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.google.devtools.build.lib.runtime.BlazeRuntime→com.google.devtools.build.lib.buildeventstream.BuildEventArtifactUploadercom.google.devtools.build.lib.runtime.BuildEventArtifactInstrumentationOutput→com.google.devtools.build.lib.buildeventstream.BuildEventArtifactUploadercom.google.devtools.build.lib.runtime.BuildEventArtifactUploaderFactory→com.google.devtools.build.lib.buildeventstream.BuildEventArtifactUploadercom.google.devtools.build.lib.runtime.BuildEventStreamer→com.google.devtools.build.lib.buildeventstream.BuildEventcom.google.devtools.build.lib.runtime.BuildEventStreamer→com.google.devtools.build.lib.buildeventstream.BuildEventTransportcom.google.devtools.build.lib.runtime.BuildEventStreamer→com.google.devtools.build.lib.buildeventstream.ChainableEventcom.google.devtools.build.lib.runtime.BuildMetadataEvent→com.google.devtools.build.lib.buildeventstream.BuildEventContextcom.google.devtools.build.lib.runtime.BuildMetadataEvent→com.google.devtools.build.lib.buildeventstream.BuildEventWithOrderConstraintcom.google.devtools.build.lib.runtime.CanonicalCommandLineEvent→com.google.devtools.build.lib.buildeventstream.BuildEventContextcom.google.devtools.build.lib.runtime.CanonicalCommandLineEvent→com.google.devtools.build.lib.buildeventstream.ReplaceableBuildEventcom.google.devtools.build.lib.runtime.CommandLineEvent→com.google.devtools.build.lib.buildeventstream.BuildEventWithOrderConstraintcom.google.devtools.build.lib.runtime.CountingArtifactGroupNamer→com.google.devtools.build.lib.buildeventstream.ArtifactGroupNamercom.google.devtools.build.lib.runtime.ExecRootEvent→com.google.devtools.build.lib.buildeventstream.BuildEventcom.google.devtools.build.lib.runtime.ExecRootEvent→com.google.devtools.build.lib.buildeventstream.BuildEventContextcom.google.devtools.build.lib.runtime.ExecutionGraphModule→com.google.devtools.build.lib.buildeventstream.BuildEventArtifactUploadercom.google.devtools.build.lib.runtime.ExecutionGraphModule→com.google.devtools.build.lib.buildeventstream.BuildEventProtocolOptionscom.google.devtools.build.lib.runtime.GotOptionsEvent→com.google.devtools.build.lib.buildeventstream.BuildEventContextcom.google.devtools.build.lib.runtime.GotOptionsEvent→com.google.devtools.build.lib.buildeventstream.BuildEventWithOrderConstraintcom.google.devtools.build.lib.runtime.InstrumentationOutputFactory→com.google.devtools.build.lib.buildeventstream.BuildEventArtifactUploadercom.google.devtools.build.lib.runtime.NamedArtifactGroup→com.google.devtools.build.lib.buildeventstream.BuildEventcom.google.devtools.build.lib.runtime.NamedArtifactGroup→com.google.devtools.build.lib.buildeventstream.BuildEventContextcom.google.devtools.build.lib.runtime.OriginalCommandLineEvent→com.google.devtools.build.lib.buildeventstream.BuildEventContextcom.google.devtools.build.lib.runtime.OriginalUnstructuredCommandLineEvent→com.google.devtools.build.lib.buildeventstream.BuildEventContextcom.google.devtools.build.lib.runtime.OriginalUnstructuredCommandLineEvent→com.google.devtools.build.lib.buildeventstream.BuildEventWithOrderConstraintcom.google.devtools.build.lib.runtime.TargetSummaryEvent→com.google.devtools.build.lib.buildeventstream.BuildEventContext
- Direction
- com.google.devtools.build.lib.runtime uses com.google.devtools.build.lib.buildeventstream, so a change to com.google.devtools.build.lib.buildeventstream can break com.google.devtools.build.lib.runtime, while a change to com.google.devtools.build.lib.runtime can't break com.google.devtools.build.lib.buildeventstream.
- Position
- Below the diagonal: com.google.devtools.build.lib.runtime uses a module listed above it, which is the healthy direction.
28→15 com.google.devtools.build.lib.runtime uses com.google.devtools.build.lib.exec✕
- Connections
- 10 pairs of types, where a type in com.google.devtools.build.lib.runtime uses a type in com.google.devtools.build.lib.exec.
- The types involved
com.google.devtools.build.lib.runtime.AggregatingTestListener→com.google.devtools.build.lib.exec.ExecutionOptionscom.google.devtools.build.lib.runtime.BlazeModule→com.google.devtools.build.lib.exec.Buildercom.google.devtools.build.lib.runtime.BlazeModule→com.google.devtools.build.lib.exec.ExecutorBuildercom.google.devtools.build.lib.runtime.BlazeRuntime→com.google.devtools.build.lib.exec.BinToolscom.google.devtools.build.lib.runtime.BlazeWorkspace→com.google.devtools.build.lib.exec.BinToolscom.google.devtools.build.lib.runtime.BuildSummaryStatsModule→com.google.devtools.build.lib.exec.ExecutorBuildercom.google.devtools.build.lib.runtime.CacheFileDigestsModule→com.google.devtools.build.lib.exec.ExecutorBuildercom.google.devtools.build.lib.runtime.CommandEnvironment→com.google.devtools.build.lib.exec.RunfilesTreeUpdatercom.google.devtools.build.lib.runtime.NoSpawnCacheModule→com.google.devtools.build.lib.exec.Buildercom.google.devtools.build.lib.runtime.WorkspaceBuilder→com.google.devtools.build.lib.exec.BinTools
- Direction
- com.google.devtools.build.lib.runtime uses com.google.devtools.build.lib.exec, so a change to com.google.devtools.build.lib.exec can break com.google.devtools.build.lib.runtime, while a change to com.google.devtools.build.lib.runtime can't break com.google.devtools.build.lib.exec.
- Position
- Below the diagonal: com.google.devtools.build.lib.runtime uses a module listed above it, which is the healthy direction.
28→16 com.google.devtools.build.lib.runtime uses com.google.devtools.build.lib.query2.common✕
- Connections
- 2 pairs of types, where a type in com.google.devtools.build.lib.runtime uses a type in com.google.devtools.build.lib.query2.common.
- The types involved
com.google.devtools.build.lib.runtime.Factory→com.google.devtools.build.lib.query2.common.CommonQueryOptionscom.google.devtools.build.lib.runtime.StdoutQueryRuntimeHelperFactory→com.google.devtools.build.lib.query2.common.CommonQueryOptions
- Direction
- com.google.devtools.build.lib.runtime uses com.google.devtools.build.lib.query2.common, so a change to com.google.devtools.build.lib.query2.common can break com.google.devtools.build.lib.runtime, while a change to com.google.devtools.build.lib.runtime can't break com.google.devtools.build.lib.query2.common.
- Position
- Below the diagonal: com.google.devtools.build.lib.runtime uses a module listed above it, which is the healthy direction.
28→18 com.google.devtools.build.lib.runtime uses com.google.devtools.build.lib.pkgcache✕
- Connections
- 11 pairs of types, where a type in com.google.devtools.build.lib.runtime uses a type in com.google.devtools.build.lib.pkgcache.
- The types involved
com.google.devtools.build.lib.runtime.BlazeWorkspace→com.google.devtools.build.lib.pkgcache.PathPackageLocatorcom.google.devtools.build.lib.runtime.CommandEnvironment→com.google.devtools.build.lib.pkgcache.PackageManagercom.google.devtools.build.lib.runtime.CommandEnvironment→com.google.devtools.build.lib.pkgcache.PathPackageLocatorcom.google.devtools.build.lib.runtime.LocationPrinter→com.google.devtools.build.lib.pkgcache.PathPackageLocatorcom.google.devtools.build.lib.runtime.MemoryPressureModule→com.google.devtools.build.lib.pkgcache.TargetParsingCompleteEventcom.google.devtools.build.lib.runtime.SkymeldUiStateTracker→com.google.devtools.build.lib.pkgcache.LoadingPhaseCompleteEventcom.google.devtools.build.lib.runtime.TargetProviderForQueryEnvironment→com.google.devtools.build.lib.pkgcache.PackageProvidercom.google.devtools.build.lib.runtime.TargetProviderForQueryEnvironment→com.google.devtools.build.lib.pkgcache.TargetProvidercom.google.devtools.build.lib.runtime.UiEventHandler→com.google.devtools.build.lib.pkgcache.LoadingPhaseCompleteEventcom.google.devtools.build.lib.runtime.UiEventHandler→com.google.devtools.build.lib.pkgcache.PathPackageLocatorcom.google.devtools.build.lib.runtime.UiStateTracker→com.google.devtools.build.lib.pkgcache.LoadingPhaseCompleteEvent
- Direction
- com.google.devtools.build.lib.runtime uses com.google.devtools.build.lib.pkgcache, so a change to com.google.devtools.build.lib.pkgcache can break com.google.devtools.build.lib.runtime, while a change to com.google.devtools.build.lib.runtime can't break com.google.devtools.build.lib.pkgcache.
- Position
- Below the diagonal: com.google.devtools.build.lib.runtime uses a module listed above it, which is the healthy direction.
28→19 com.google.devtools.build.lib.runtime uses com.google.devtools.build.lib.skyframe.serialization.analysis✕
- Connections
- 3 pairs of types, where a type in com.google.devtools.build.lib.runtime uses a type in com.google.devtools.build.lib.skyframe.serialization.analysis.
- The types involved
com.google.devtools.build.lib.runtime.BlazeWorkspace→com.google.devtools.build.lib.skyframe.serialization.analysis.RemoteAnalysisCachingServicesSuppliercom.google.devtools.build.lib.runtime.CommandEnvironment→com.google.devtools.build.lib.skyframe.serialization.analysis.RemoteAnalysisCachingEventListenercom.google.devtools.build.lib.runtime.WorkspaceBuilder→com.google.devtools.build.lib.skyframe.serialization.analysis.RemoteAnalysisCachingServicesSupplier
- Direction
- com.google.devtools.build.lib.runtime uses com.google.devtools.build.lib.skyframe.serialization.analysis, so a change to com.google.devtools.build.lib.skyframe.serialization.analysis can break com.google.devtools.build.lib.runtime, while a change to com.google.devtools.build.lib.runtime can't break com.google.devtools.build.lib.skyframe.serialization.analysis.
- Position
- Below the diagonal: com.google.devtools.build.lib.runtime uses a module listed above it, which is the healthy direction.
28→21 com.google.devtools.build.lib.runtime uses com.google.devtools.build.lib.query2✕
- Connections
- 2 pairs of types, where a type in com.google.devtools.build.lib.runtime uses a type in com.google.devtools.build.lib.query2.
- The types involved
com.google.devtools.build.lib.runtime.BlazeRuntime→com.google.devtools.build.lib.query2.QueryEnvironmentFactorycom.google.devtools.build.lib.runtime.ServerBuilder→com.google.devtools.build.lib.query2.QueryEnvironmentFactory
- Direction
- com.google.devtools.build.lib.runtime uses com.google.devtools.build.lib.query2, so a change to com.google.devtools.build.lib.query2 can break com.google.devtools.build.lib.runtime, while a change to com.google.devtools.build.lib.runtime can't break com.google.devtools.build.lib.query2.
- Position
- Below the diagonal: com.google.devtools.build.lib.runtime uses a module listed above it, which is the healthy direction.
28→23 com.google.devtools.build.lib.runtime uses com.google.devtools.build.lib.buildtool✕
- Connections
- 5 pairs of types, where a type in com.google.devtools.build.lib.runtime uses a type in com.google.devtools.build.lib.buildtool.
- The types involved
com.google.devtools.build.lib.runtime.BlazeModule→com.google.devtools.build.lib.buildtool.BuildRequestcom.google.devtools.build.lib.runtime.BuildSummaryStatsModule→com.google.devtools.build.lib.buildtool.BuildRequestcom.google.devtools.build.lib.runtime.CacheFileDigestsModule→com.google.devtools.build.lib.buildtool.BuildRequestcom.google.devtools.build.lib.runtime.NoSpawnCacheModule→com.google.devtools.build.lib.buildtool.BuildRequestcom.google.devtools.build.lib.runtime.UiStateTracker→com.google.devtools.build.lib.buildtool.ExecutionProgressReceiver
- Direction
- com.google.devtools.build.lib.runtime uses com.google.devtools.build.lib.buildtool, so a change to com.google.devtools.build.lib.buildtool can break com.google.devtools.build.lib.runtime, while a change to com.google.devtools.build.lib.runtime can't break com.google.devtools.build.lib.buildtool.
- Position
- Below the diagonal: com.google.devtools.build.lib.runtime uses a module listed above it, which is the healthy direction.
28→24 com.google.devtools.build.lib.runtime uses com.google.devtools.build.lib.skyframe✕
- Connections
- 23 pairs of types, where a type in com.google.devtools.build.lib.runtime uses a type in com.google.devtools.build.lib.skyframe.
- The types involved
com.google.devtools.build.lib.runtime.AggregatingTestListener→com.google.devtools.build.lib.skyframe.ConfiguredTargetKeycom.google.devtools.build.lib.runtime.BlazeModule→com.google.devtools.build.lib.skyframe.Injectedcom.google.devtools.build.lib.runtime.BlazeWorkspace→com.google.devtools.build.lib.skyframe.SkyframeExecutorcom.google.devtools.build.lib.runtime.BuildSummaryStatsModule→com.google.devtools.build.lib.skyframe.ExecutionFinishedEventcom.google.devtools.build.lib.runtime.CommandEnvironment→com.google.devtools.build.lib.skyframe.BuildResultListenercom.google.devtools.build.lib.runtime.CommandEnvironment→com.google.devtools.build.lib.skyframe.SkyframeBuildViewcom.google.devtools.build.lib.runtime.CommandEnvironment→com.google.devtools.build.lib.skyframe.SkyframeExecutorcom.google.devtools.build.lib.runtime.CommandEnvironment→com.google.devtools.build.lib.skyframe.WorkspaceInfoFromDiffcom.google.devtools.build.lib.runtime.MemoryPressureModule→com.google.devtools.build.lib.skyframe.HighWaterMarkLimitercom.google.devtools.build.lib.runtime.SkyframeExecutorTargetLoader→com.google.devtools.build.lib.skyframe.SkyframeExecutorcom.google.devtools.build.lib.runtime.SkymeldUiStateTracker→com.google.devtools.build.lib.skyframe.ConfigurationPhaseStartedEventcom.google.devtools.build.lib.runtime.SkymeldUiStateTracker→com.google.devtools.build.lib.skyframe.LoadingPhaseStartedEventcom.google.devtools.build.lib.runtime.TargetSummaryPublisher→com.google.devtools.build.lib.skyframe.ConfiguredTargetKeycom.google.devtools.build.lib.runtime.TargetSummaryPublisher→com.google.devtools.build.lib.skyframe.ToplevelAspectsIdentifiedEventcom.google.devtools.build.lib.runtime.UiEventHandler→com.google.devtools.build.lib.skyframe.ConfigurationPhaseStartedEventcom.google.devtools.build.lib.runtime.UiEventHandler→com.google.devtools.build.lib.skyframe.LoadingPhaseStartedEventcom.google.devtools.build.lib.runtime.UiStateTracker→com.google.devtools.build.lib.skyframe.AnalysisProgressReceivercom.google.devtools.build.lib.runtime.UiStateTracker→com.google.devtools.build.lib.skyframe.ConfigurationPhaseStartedEventcom.google.devtools.build.lib.runtime.UiStateTracker→com.google.devtools.build.lib.skyframe.LoadingPhaseStartedEventcom.google.devtools.build.lib.runtime.UiStateTracker→com.google.devtools.build.lib.skyframe.PackageProgressReceivercom.google.devtools.build.lib.runtime.WorkspaceBuilder→com.google.devtools.build.lib.skyframe.Factorycom.google.devtools.build.lib.runtime.WorkspaceBuilder→com.google.devtools.build.lib.skyframe.SkyKeyStateReceivercom.google.devtools.build.lib.runtime.WorkspaceBuilder→com.google.devtools.build.lib.skyframe.SkyframeExecutorFactory
- Direction
- com.google.devtools.build.lib.runtime uses com.google.devtools.build.lib.skyframe, so a change to com.google.devtools.build.lib.skyframe can break com.google.devtools.build.lib.runtime, while a change to com.google.devtools.build.lib.runtime can't break com.google.devtools.build.lib.skyframe.
- Position
- Below the diagonal: com.google.devtools.build.lib.runtime uses a module listed above it, which is the healthy direction.
28→25 com.google.devtools.build.lib.runtime uses com.google.devtools.build.lib.packages✕
- Connections
- 13 pairs of types, where a type in com.google.devtools.build.lib.runtime uses a type in com.google.devtools.build.lib.packages.
- The types involved
com.google.devtools.build.lib.runtime.BlazeModule→com.google.devtools.build.lib.packages.PackageLoadingListenercom.google.devtools.build.lib.runtime.BlazeModule→com.google.devtools.build.lib.packages.PackageOverheadEstimatorcom.google.devtools.build.lib.runtime.BlazeModule→com.google.devtools.build.lib.packages.PackageValidatorcom.google.devtools.build.lib.runtime.BlazeRuntime→com.google.devtools.build.lib.packages.PackageFactorycom.google.devtools.build.lib.runtime.BlazeRuntime→com.google.devtools.build.lib.packages.PackageLoadingListenercom.google.devtools.build.lib.runtime.BuildSettingLoader→com.google.devtools.build.lib.packages.Targetcom.google.devtools.build.lib.runtime.SkyframeExecutorTargetLoader→com.google.devtools.build.lib.packages.Targetcom.google.devtools.build.lib.runtime.StarlarkOptionsParser→com.google.devtools.build.lib.packages.BuildSettingcom.google.devtools.build.lib.runtime.StarlarkOptionsParser→com.google.devtools.build.lib.packages.Targetcom.google.devtools.build.lib.runtime.StarlarkOptionsParser→com.google.devtools.build.lib.packages.Typecom.google.devtools.build.lib.runtime.TargetProviderForQueryEnvironment→com.google.devtools.build.lib.packages.InputFilecom.google.devtools.build.lib.runtime.TargetProviderForQueryEnvironment→com.google.devtools.build.lib.packages.Targetcom.google.devtools.build.lib.runtime.WorkspaceBuilder→com.google.devtools.build.lib.packages.PackageFactory
- Direction
- com.google.devtools.build.lib.runtime uses com.google.devtools.build.lib.packages, so a change to com.google.devtools.build.lib.packages can break com.google.devtools.build.lib.runtime, while a change to com.google.devtools.build.lib.runtime can't break com.google.devtools.build.lib.packages.
- Position
- Below the diagonal: com.google.devtools.build.lib.runtime uses a module listed above it, which is the healthy direction.
28→27 com.google.devtools.build.lib.runtime uses com.google.devtools.build.lib.analysis.test✕
- Connections
- 4 pairs of types, where a type in com.google.devtools.build.lib.runtime uses a type in com.google.devtools.build.lib.analysis.test.
- The types involved
com.google.devtools.build.lib.runtime.AggregatingTestListener→com.google.devtools.build.lib.analysis.test.TestResultcom.google.devtools.build.lib.runtime.BlazeModule→com.google.devtools.build.lib.analysis.test.CoverageReportActionFactorycom.google.devtools.build.lib.runtime.BlazeRuntime→com.google.devtools.build.lib.analysis.test.CoverageReportActionFactorycom.google.devtools.build.lib.runtime.TestResultAggregator→com.google.devtools.build.lib.analysis.test.TestResult
- Direction
- com.google.devtools.build.lib.runtime uses com.google.devtools.build.lib.analysis.test, so a change to com.google.devtools.build.lib.analysis.test can break com.google.devtools.build.lib.runtime, while a change to com.google.devtools.build.lib.runtime can't break com.google.devtools.build.lib.analysis.test.
- Position
- Below the diagonal: com.google.devtools.build.lib.runtime uses a module listed above it, which is the healthy direction.
28→29 com.google.devtools.build.lib.runtime uses com.google.devtools.build.lib.skyframe.serialization part of a loop✕
- Connections
- 4 pairs of types, where a type in com.google.devtools.build.lib.runtime uses a type in com.google.devtools.build.lib.skyframe.serialization.
- The types involved
com.google.devtools.build.lib.runtime.BlazeWorkspace→com.google.devtools.build.lib.skyframe.serialization.Fingerprintercom.google.devtools.build.lib.runtime.BlazeWorkspace→com.google.devtools.build.lib.skyframe.serialization.ObjectCodecRegistrycom.google.devtools.build.lib.runtime.WorkspaceBuilder→com.google.devtools.build.lib.skyframe.serialization.Fingerprintercom.google.devtools.build.lib.runtime.WorkspaceBuilder→com.google.devtools.build.lib.skyframe.serialization.ObjectCodecRegistry
- Direction
- com.google.devtools.build.lib.runtime uses com.google.devtools.build.lib.skyframe.serialization, so a change to com.google.devtools.build.lib.skyframe.serialization can break com.google.devtools.build.lib.runtime, while a change to com.google.devtools.build.lib.runtime can't break com.google.devtools.build.lib.skyframe.serialization.
- 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→30 com.google.devtools.build.lib.runtime uses com.google.devtools.build.lib.collect.nestedset part of a loop✕
- Connections
- 4 pairs of types, where a type in com.google.devtools.build.lib.runtime uses a type in com.google.devtools.build.lib.collect.nestedset.
- The types involved
com.google.devtools.build.lib.runtime.BuildEventStreamer→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.runtime.CountingArtifactGroupNamer→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.runtime.CountingArtifactGroupNamer→com.google.devtools.build.lib.collect.nestedset.Nodecom.google.devtools.build.lib.runtime.NamedArtifactGroup→com.google.devtools.build.lib.collect.nestedset.NestedSet
- Direction
- com.google.devtools.build.lib.runtime uses com.google.devtools.build.lib.collect.nestedset, so a change to com.google.devtools.build.lib.collect.nestedset can break com.google.devtools.build.lib.runtime, while a change to com.google.devtools.build.lib.runtime can't break com.google.devtools.build.lib.collect.nestedset.
- 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→31 com.google.devtools.build.lib.runtime uses com.google.devtools.build.lib.cmdline part of a loop✕
- Connections
- 11 pairs of types, where a type in com.google.devtools.build.lib.runtime uses a type in com.google.devtools.build.lib.cmdline.
- The types involved
com.google.devtools.build.lib.runtime.BlazeModuleEnvironment→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.runtime.ModuleEnvironment→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.runtime.RemoteRepoContentsCache→com.google.devtools.build.lib.cmdline.RepositoryNamecom.google.devtools.build.lib.runtime.StarlarkOptionsParser→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.runtime.TargetProviderForQueryEnvironment→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.runtime.TargetProviderForQueryEnvironment→com.google.devtools.build.lib.cmdline.PackageIdentifiercom.google.devtools.build.lib.runtime.TerminalTestResultNotifier→com.google.devtools.build.lib.cmdline.RepositoryMappingcom.google.devtools.build.lib.runtime.TestSummary→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.runtime.TestSummaryPrinter→com.google.devtools.build.lib.cmdline.RepositoryMappingcom.google.devtools.build.lib.runtime.UiStateTracker→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.runtime.UiStateTracker→com.google.devtools.build.lib.cmdline.RepositoryMapping
- Direction
- com.google.devtools.build.lib.runtime uses com.google.devtools.build.lib.cmdline, so a change to com.google.devtools.build.lib.cmdline can break com.google.devtools.build.lib.runtime, while a change to com.google.devtools.build.lib.runtime can't break com.google.devtools.build.lib.cmdline.
- 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→33 com.google.devtools.build.lib.runtime uses com.google.devtools.build.lib.analysis.config part of a loop✕
- Connections
- 8 pairs of types, where a type in com.google.devtools.build.lib.runtime uses a type in com.google.devtools.build.lib.analysis.config.
- The types involved
com.google.devtools.build.lib.runtime.BlazeModule→com.google.devtools.build.lib.analysis.config.BuildOptionscom.google.devtools.build.lib.runtime.BlazeRuntime→com.google.devtools.build.lib.analysis.config.BuildOptionscom.google.devtools.build.lib.runtime.Builder→com.google.devtools.build.lib.analysis.config.BuildConfigurationValuecom.google.devtools.build.lib.runtime.CommandEnvironment→com.google.devtools.build.lib.analysis.config.AdditionalConfigurationChangeEventcom.google.devtools.build.lib.runtime.CommandLogInfoItem→com.google.devtools.build.lib.analysis.config.BuildConfigurationValuecom.google.devtools.build.lib.runtime.InfoItem→com.google.devtools.build.lib.analysis.config.BuildConfigurationValuecom.google.devtools.build.lib.runtime.TestResultAggregator→com.google.devtools.build.lib.analysis.config.BuildConfigurationValuecom.google.devtools.build.lib.runtime.TestSummary→com.google.devtools.build.lib.analysis.config.BuildConfigurationValue
- Direction
- com.google.devtools.build.lib.runtime uses com.google.devtools.build.lib.analysis.config, so a change to com.google.devtools.build.lib.analysis.config can break com.google.devtools.build.lib.runtime, while a change to com.google.devtools.build.lib.runtime can't break com.google.devtools.build.lib.analysis.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.
28→35 com.google.devtools.build.lib.runtime uses com.google.devtools.build.lib.analysis part of a loop✕
- Connections
- 36 pairs of types, where a type in com.google.devtools.build.lib.runtime uses a type in com.google.devtools.build.lib.analysis. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.google.devtools.build.lib.runtime.AggregatingTestListener→com.google.devtools.build.lib.analysis.AnalysisFailureEventcom.google.devtools.build.lib.runtime.AggregatingTestListener→com.google.devtools.build.lib.analysis.ConfiguredTargetcom.google.devtools.build.lib.runtime.AggregatingTestListener→com.google.devtools.build.lib.analysis.TargetCompleteEventcom.google.devtools.build.lib.runtime.BlazeCommandDispatcher→com.google.devtools.build.lib.analysis.NoBuildEventcom.google.devtools.build.lib.runtime.BlazeCommandUtils→com.google.devtools.build.lib.analysis.ConfiguredRuleClassProvidercom.google.devtools.build.lib.runtime.BlazeModule→com.google.devtools.build.lib.analysis.AnalysisResultcom.google.devtools.build.lib.runtime.BlazeModule→com.google.devtools.build.lib.analysis.BlazeDirectoriescom.google.devtools.build.lib.runtime.BlazeModule→com.google.devtools.build.lib.analysis.BlazeVersionInfocom.google.devtools.build.lib.runtime.BlazeModule→com.google.devtools.build.lib.analysis.Buildercom.google.devtools.build.lib.runtime.BlazeModule→com.google.devtools.build.lib.analysis.ConfiguredAspectcom.google.devtools.build.lib.runtime.BlazeModule→com.google.devtools.build.lib.analysis.ConfiguredRuleClassProvidercom.google.devtools.build.lib.runtime.BlazeModule→com.google.devtools.build.lib.analysis.ConfiguredTargetcom.google.devtools.build.lib.runtime.BlazeModule→com.google.devtools.build.lib.analysis.ServerDirectoriescom.google.devtools.build.lib.runtime.BlazeRuntime→com.google.devtools.build.lib.analysis.BlazeDirectoriescom.google.devtools.build.lib.runtime.BlazeRuntime→com.google.devtools.build.lib.analysis.ConfiguredRuleClassProvidercom.google.devtools.build.lib.runtime.BlazeWorkspace→com.google.devtools.build.lib.analysis.BlazeDirectoriescom.google.devtools.build.lib.runtime.BlazeWorkspace→com.google.devtools.build.lib.analysis.Factorycom.google.devtools.build.lib.runtime.Builder→com.google.devtools.build.lib.analysis.ConfiguredTargetcom.google.devtools.build.lib.runtime.CommandEnvironment→com.google.devtools.build.lib.analysis.BlazeDirectoriescom.google.devtools.build.lib.runtime.CommandEnvironment→com.google.devtools.build.lib.analysis.BuildInfoEventcom.google.devtools.build.lib.runtime.CommandLinePathFactory→com.google.devtools.build.lib.analysis.BlazeDirectoriescom.google.devtools.build.lib.runtime.PassiveExperimentalEventHandler→com.google.devtools.build.lib.analysis.NoBuildEventcom.google.devtools.build.lib.runtime.PassiveExperimentalEventHandler→com.google.devtools.build.lib.analysis.NoBuildRequestFinishedEventcom.google.devtools.build.lib.runtime.TargetSummaryAggregator→com.google.devtools.build.lib.analysis.ConfiguredTargetcom.google.devtools.build.lib.runtime.TargetSummaryEvent→com.google.devtools.build.lib.analysis.ConfiguredTarget
- Direction
- com.google.devtools.build.lib.runtime uses com.google.devtools.build.lib.analysis, so a change to com.google.devtools.build.lib.analysis can break com.google.devtools.build.lib.runtime, while a change to com.google.devtools.build.lib.runtime can't break com.google.devtools.build.lib.analysis.
- 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→37 com.google.devtools.build.lib.runtime uses com.google.devtools.build.lib.actions part of a loop✕
- Connections
- 71 pairs of types, where a type in com.google.devtools.build.lib.runtime uses a type in com.google.devtools.build.lib.actions. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.google.devtools.build.lib.runtime.1→com.google.devtools.build.lib.actions.Artifactcom.google.devtools.build.lib.runtime.1→com.google.devtools.build.lib.actions.FileArtifactValuecom.google.devtools.build.lib.runtime.1→com.google.devtools.build.lib.actions.FilesetOutputSymlinkcom.google.devtools.build.lib.runtime.ActionDumpWriter→com.google.devtools.build.lib.actions.Actioncom.google.devtools.build.lib.runtime.ActionDumpWriter→com.google.devtools.build.lib.actions.ActionExecutionMetadatacom.google.devtools.build.lib.runtime.ActionDumpWriter→com.google.devtools.build.lib.actions.ActionInputcom.google.devtools.build.lib.runtime.ActionDumpWriter→com.google.devtools.build.lib.actions.ActionOwnercom.google.devtools.build.lib.runtime.ActionDumpWriter→com.google.devtools.build.lib.actions.Artifactcom.google.devtools.build.lib.runtime.ActionDumpWriter→com.google.devtools.build.lib.actions.Buildercom.google.devtools.build.lib.runtime.ActionDumpWriter→com.google.devtools.build.lib.actions.DiscoveredInputsEventcom.google.devtools.build.lib.runtime.ActionDumpWriter→com.google.devtools.build.lib.actions.InputMetadataProvidercom.google.devtools.build.lib.runtime.ActionDumpWriter→com.google.devtools.build.lib.actions.SharedActionEventcom.google.devtools.build.lib.runtime.ActionDumpWriter→com.google.devtools.build.lib.actions.SpawnExecutedEventcom.google.devtools.build.lib.runtime.ActionDumpWriter→com.google.devtools.build.lib.actions.SpawnInputscom.google.devtools.build.lib.runtime.ActionState→com.google.devtools.build.lib.actions.ActionExecutionMetadatacom.google.devtools.build.lib.runtime.ActionState→com.google.devtools.build.lib.actions.ActionProgressEventcom.google.devtools.build.lib.runtime.BlazeModule→com.google.devtools.build.lib.actions.Artifactcom.google.devtools.build.lib.runtime.BlazeRuntime→com.google.devtools.build.lib.actions.ActionKeyContextcom.google.devtools.build.lib.runtime.BuildEventStreamer→com.google.devtools.build.lib.actions.ActionExecutedEventcom.google.devtools.build.lib.runtime.BuildEventStreamer→com.google.devtools.build.lib.actions.CompletionContextcom.google.devtools.build.lib.runtime.BuildSummaryStatsModule→com.google.devtools.build.lib.actions.ActionCompletionEventcom.google.devtools.build.lib.runtime.BuildSummaryStatsModule→com.google.devtools.build.lib.actions.ActionKeyContextcom.google.devtools.build.lib.runtime.BuildSummaryStatsModule→com.google.devtools.build.lib.actions.ActionResultReceivedEventcom.google.devtools.build.lib.runtime.CommandEnvironment→com.google.devtools.build.lib.actions.ActionOutputDirectoryHelpercom.google.devtools.build.lib.runtime.CommandEnvironment→com.google.devtools.build.lib.actions.InputMetadataProvider
- Direction
- com.google.devtools.build.lib.runtime uses com.google.devtools.build.lib.actions, so a change to com.google.devtools.build.lib.actions can break com.google.devtools.build.lib.runtime, while a change to com.google.devtools.build.lib.runtime can't break com.google.devtools.build.lib.actions.
- 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→6 com.google.devtools.build.lib.skyframe.serialization uses com.google.devtools.build.skyframe✕
- Connections
- 10 pairs of types, where a type in com.google.devtools.build.lib.skyframe.serialization uses a type in com.google.devtools.build.skyframe.
- The types involved
com.google.devtools.build.lib.skyframe.serialization.AsyncDeserializationContext→com.google.devtools.build.skyframe.SkyKeycom.google.devtools.build.lib.skyframe.serialization.DeserializationContext→com.google.devtools.build.skyframe.SkyKeycom.google.devtools.build.lib.skyframe.serialization.DeserializedSkyValue→com.google.devtools.build.skyframe.SkyValuecom.google.devtools.build.lib.skyframe.serialization.FingerprintValueService→com.google.devtools.build.skyframe.SkyKeycom.google.devtools.build.lib.skyframe.serialization.FrontierNodeVersion→com.google.devtools.build.skyframe.IntVersioncom.google.devtools.build.lib.skyframe.serialization.RetrievedValue→com.google.devtools.build.skyframe.SkyValuecom.google.devtools.build.lib.skyframe.serialization.SharedValueDeserializationContext→com.google.devtools.build.skyframe.SkyKeycom.google.devtools.build.lib.skyframe.serialization.SkyValueRetriever→com.google.devtools.build.skyframe.SkyKeycom.google.devtools.build.lib.skyframe.serialization.SkyframeLookup→com.google.devtools.build.skyframe.SkyKeycom.google.devtools.build.lib.skyframe.serialization.SkyframeLookup→com.google.devtools.build.skyframe.SkyValue
- Direction
- com.google.devtools.build.lib.skyframe.serialization uses com.google.devtools.build.skyframe, so a change to com.google.devtools.build.skyframe can break com.google.devtools.build.lib.skyframe.serialization, while a change to com.google.devtools.build.lib.skyframe.serialization can't break com.google.devtools.build.skyframe.
- Position
- Below the diagonal: com.google.devtools.build.lib.skyframe.serialization uses a module listed above it, which is the healthy direction.
29→11 com.google.devtools.build.lib.skyframe.serialization uses com.google.devtools.build.lib.util✕
- Connections
- 3 pairs of types, where a type in com.google.devtools.build.lib.skyframe.serialization uses a type in com.google.devtools.build.lib.util.
- The types involved
com.google.devtools.build.lib.skyframe.serialization.FingerprintValueService→com.google.devtools.build.lib.util.DecimalBucketercom.google.devtools.build.lib.skyframe.serialization.Stats→com.google.devtools.build.lib.util.Bucketcom.google.devtools.build.lib.skyframe.serialization.StatsImpl→com.google.devtools.build.lib.util.Bucket
- Direction
- com.google.devtools.build.lib.skyframe.serialization uses com.google.devtools.build.lib.util, so a change to com.google.devtools.build.lib.util can break com.google.devtools.build.lib.skyframe.serialization, while a change to com.google.devtools.build.lib.skyframe.serialization can't break com.google.devtools.build.lib.util.
- Position
- Below the diagonal: com.google.devtools.build.lib.skyframe.serialization uses a module listed above it, which is the healthy direction.
29→19 com.google.devtools.build.lib.skyframe.serialization uses com.google.devtools.build.lib.skyframe.serialization.analysis✕
- Connections
- 7 pairs of types, where a type in com.google.devtools.build.lib.skyframe.serialization uses a type in com.google.devtools.build.lib.skyframe.serialization.analysis.
- The types involved
com.google.devtools.build.lib.skyframe.serialization.FrontierNodeVersion→com.google.devtools.build.lib.skyframe.serialization.analysis.ClientIdcom.google.devtools.build.lib.skyframe.serialization.InMemoryRemoteAnalysisCachingServicesSupplier→com.google.devtools.build.lib.skyframe.serialization.analysis.RemoteAnalysisCachingServicesSuppliercom.google.devtools.build.lib.skyframe.serialization.SerializationModule→com.google.devtools.build.lib.skyframe.serialization.analysis.RemoteAnalysisCachingServicesSuppliercom.google.devtools.build.lib.skyframe.serialization.SkyValueRetriever→com.google.devtools.build.lib.skyframe.serialization.analysis.FileOpNodeMemoizingLookupcom.google.devtools.build.lib.skyframe.serialization.SkyValueRetriever→com.google.devtools.build.lib.skyframe.serialization.analysis.RemoteAnalysisCacheClientcom.google.devtools.build.lib.skyframe.serialization.SkyValueRetriever→com.google.devtools.build.lib.skyframe.serialization.analysis.SkycacheChannelStateAdvisorcom.google.devtools.build.lib.skyframe.serialization.WaitingForCacheServiceResponse→com.google.devtools.build.lib.skyframe.serialization.analysis.LookupResult
- Direction
- com.google.devtools.build.lib.skyframe.serialization uses com.google.devtools.build.lib.skyframe.serialization.analysis, so a change to com.google.devtools.build.lib.skyframe.serialization.analysis can break com.google.devtools.build.lib.skyframe.serialization, while a change to com.google.devtools.build.lib.skyframe.serialization can't break com.google.devtools.build.lib.skyframe.serialization.analysis.
- Position
- Below the diagonal: com.google.devtools.build.lib.skyframe.serialization uses a module listed above it, which is the healthy direction.
29→24 com.google.devtools.build.lib.skyframe.serialization uses com.google.devtools.build.lib.skyframe✕
- Connections
- 1 pair of types, where a type in com.google.devtools.build.lib.skyframe.serialization uses a type in com.google.devtools.build.lib.skyframe.
- The types involved
com.google.devtools.build.lib.skyframe.serialization.DeserializationBuilder→com.google.devtools.build.lib.skyframe.BzlLoadValue
- Direction
- com.google.devtools.build.lib.skyframe.serialization uses com.google.devtools.build.lib.skyframe, so a change to com.google.devtools.build.lib.skyframe can break com.google.devtools.build.lib.skyframe.serialization, while a change to com.google.devtools.build.lib.skyframe.serialization can't break com.google.devtools.build.lib.skyframe.
- Position
- Below the diagonal: com.google.devtools.build.lib.skyframe.serialization uses a module listed above it, which is the healthy direction.
29→28 com.google.devtools.build.lib.skyframe.serialization uses com.google.devtools.build.lib.runtime✕
- Connections
- 3 pairs of types, where a type in com.google.devtools.build.lib.skyframe.serialization uses a type in com.google.devtools.build.lib.runtime.
- The types involved
com.google.devtools.build.lib.skyframe.serialization.SerializationModule→com.google.devtools.build.lib.runtime.BlazeModulecom.google.devtools.build.lib.skyframe.serialization.SerializationModule→com.google.devtools.build.lib.runtime.BlazeRuntimecom.google.devtools.build.lib.skyframe.serialization.SerializationModule→com.google.devtools.build.lib.runtime.WorkspaceBuilder
- Direction
- com.google.devtools.build.lib.skyframe.serialization uses com.google.devtools.build.lib.runtime, so a change to com.google.devtools.build.lib.runtime can break com.google.devtools.build.lib.skyframe.serialization, while a change to com.google.devtools.build.lib.skyframe.serialization can't break com.google.devtools.build.lib.runtime.
- Position
- Below the diagonal: com.google.devtools.build.lib.skyframe.serialization uses a module listed above it, which is the healthy direction.
29→31 com.google.devtools.build.lib.skyframe.serialization uses com.google.devtools.build.lib.cmdline part of a loop✕
- Connections
- 1 pair of types, where a type in com.google.devtools.build.lib.skyframe.serialization uses a type in com.google.devtools.build.lib.cmdline.
- The types involved
com.google.devtools.build.lib.skyframe.serialization.PlatformConfigurationProvider→com.google.devtools.build.lib.cmdline.Label
- Direction
- com.google.devtools.build.lib.skyframe.serialization uses com.google.devtools.build.lib.cmdline, so a change to com.google.devtools.build.lib.cmdline can break com.google.devtools.build.lib.skyframe.serialization, while a change to com.google.devtools.build.lib.skyframe.serialization can't break com.google.devtools.build.lib.cmdline.
- 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→33 com.google.devtools.build.lib.skyframe.serialization uses com.google.devtools.build.lib.analysis.config part of a loop✕
- Connections
- 1 pair of types, where a type in com.google.devtools.build.lib.skyframe.serialization uses a type in com.google.devtools.build.lib.analysis.config.
- The types involved
com.google.devtools.build.lib.skyframe.serialization.PlatformConfigurationProvider→com.google.devtools.build.lib.analysis.config.BuildOptions
- Direction
- com.google.devtools.build.lib.skyframe.serialization uses com.google.devtools.build.lib.analysis.config, so a change to com.google.devtools.build.lib.analysis.config can break com.google.devtools.build.lib.skyframe.serialization, while a change to com.google.devtools.build.lib.skyframe.serialization can't break com.google.devtools.build.lib.analysis.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.
29→35 com.google.devtools.build.lib.skyframe.serialization uses com.google.devtools.build.lib.analysis part of a loop✕
- Connections
- 3 pairs of types, where a type in com.google.devtools.build.lib.skyframe.serialization uses a type in com.google.devtools.build.lib.analysis.
- The types involved
com.google.devtools.build.lib.skyframe.serialization.SerializationModule→com.google.devtools.build.lib.analysis.BlazeDirectoriescom.google.devtools.build.lib.skyframe.serialization.SerializationRegistrySetupHelpers→com.google.devtools.build.lib.analysis.BlazeDirectoriescom.google.devtools.build.lib.skyframe.serialization.SerializationRegistrySetupHelpers→com.google.devtools.build.lib.analysis.ConfiguredRuleClassProvider
- Direction
- com.google.devtools.build.lib.skyframe.serialization uses com.google.devtools.build.lib.analysis, so a change to com.google.devtools.build.lib.analysis can break com.google.devtools.build.lib.skyframe.serialization, while a change to com.google.devtools.build.lib.skyframe.serialization can't break com.google.devtools.build.lib.analysis.
- 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→4 com.google.devtools.build.lib.collect.nestedset uses net.starlark.java.eval✕
- Connections
- 8 pairs of types, where a type in com.google.devtools.build.lib.collect.nestedset uses a type in net.starlark.java.eval.
- The types involved
com.google.devtools.build.lib.collect.nestedset.Depset→net.starlark.java.eval.DebugAttributecom.google.devtools.build.lib.collect.nestedset.Depset→net.starlark.java.eval.Printercom.google.devtools.build.lib.collect.nestedset.Depset→net.starlark.java.eval.StarlarkListcom.google.devtools.build.lib.collect.nestedset.Depset→net.starlark.java.eval.StarlarkSemanticscom.google.devtools.build.lib.collect.nestedset.Depset→net.starlark.java.eval.StarlarkThreadcom.google.devtools.build.lib.collect.nestedset.Depset→net.starlark.java.eval.StarlarkValuecom.google.devtools.build.lib.collect.nestedset.Depset→net.starlark.java.eval.ValueWithDebugAttributescom.google.devtools.build.lib.collect.nestedset.DepsetLibrary→net.starlark.java.eval.StarlarkThread
- Direction
- com.google.devtools.build.lib.collect.nestedset uses net.starlark.java.eval, so a change to net.starlark.java.eval can break com.google.devtools.build.lib.collect.nestedset, while a change to com.google.devtools.build.lib.collect.nestedset can't break net.starlark.java.eval.
- Position
- Below the diagonal: com.google.devtools.build.lib.collect.nestedset uses a module listed above it, which is the healthy direction.
30→6 com.google.devtools.build.lib.collect.nestedset uses com.google.devtools.build.skyframe✕
- Connections
- 3 pairs of types, where a type in com.google.devtools.build.lib.collect.nestedset uses a type in com.google.devtools.build.skyframe.
- The types involved
com.google.devtools.build.lib.collect.nestedset.ArtifactNestedSetKey→com.google.devtools.build.skyframe.ExecutionPhaseSkyKeycom.google.devtools.build.lib.collect.nestedset.ArtifactNestedSetKey→com.google.devtools.build.skyframe.SkyFunctionNamecom.google.devtools.build.lib.collect.nestedset.ArtifactNestedSetKey→com.google.devtools.build.skyframe.SkyKey
- Direction
- com.google.devtools.build.lib.collect.nestedset uses com.google.devtools.build.skyframe, so a change to com.google.devtools.build.skyframe can break com.google.devtools.build.lib.collect.nestedset, while a change to com.google.devtools.build.lib.collect.nestedset can't break com.google.devtools.build.skyframe.
- Position
- Below the diagonal: com.google.devtools.build.lib.collect.nestedset uses a module listed above it, which is the healthy direction.
30→8 com.google.devtools.build.lib.collect.nestedset uses com.google.devtools.build.lib.vfs✕
- Connections
- 1 pair of types, where a type in com.google.devtools.build.lib.collect.nestedset uses a type in com.google.devtools.build.lib.vfs.
- The types involved
com.google.devtools.build.lib.collect.nestedset.DigestMap→com.google.devtools.build.lib.vfs.DigestHashFunction
- Direction
- com.google.devtools.build.lib.collect.nestedset uses com.google.devtools.build.lib.vfs, so a change to com.google.devtools.build.lib.vfs can break com.google.devtools.build.lib.collect.nestedset, while a change to com.google.devtools.build.lib.collect.nestedset can't break com.google.devtools.build.lib.vfs.
- Position
- Below the diagonal: com.google.devtools.build.lib.collect.nestedset uses a module listed above it, which is the healthy direction.
30→11 com.google.devtools.build.lib.collect.nestedset uses com.google.devtools.build.lib.util✕
- Connections
- 5 pairs of types, where a type in com.google.devtools.build.lib.collect.nestedset uses a type in com.google.devtools.build.lib.util.
- The types involved
com.google.devtools.build.lib.collect.nestedset.DigestMap→com.google.devtools.build.lib.util.BytesSinkcom.google.devtools.build.lib.collect.nestedset.DigestMap→com.google.devtools.build.lib.util.Fingerprintcom.google.devtools.build.lib.collect.nestedset.DigestReference→com.google.devtools.build.lib.util.BytesSinkcom.google.devtools.build.lib.collect.nestedset.DigestReference→com.google.devtools.build.lib.util.Fingerprintcom.google.devtools.build.lib.collect.nestedset.NestedSetFingerprintCache→com.google.devtools.build.lib.util.Fingerprint
- Direction
- com.google.devtools.build.lib.collect.nestedset uses com.google.devtools.build.lib.util, so a change to com.google.devtools.build.lib.util can break com.google.devtools.build.lib.collect.nestedset, while a change to com.google.devtools.build.lib.collect.nestedset can't break com.google.devtools.build.lib.util.
- Position
- Below the diagonal: com.google.devtools.build.lib.collect.nestedset uses a module listed above it, which is the healthy direction.
30→29 com.google.devtools.build.lib.collect.nestedset uses com.google.devtools.build.lib.skyframe.serialization✕
- Connections
- 21 pairs of types, where a type in com.google.devtools.build.lib.collect.nestedset uses a type in com.google.devtools.build.lib.skyframe.serialization.
- The types involved
com.google.devtools.build.lib.collect.nestedset.ArrayFieldSetter→com.google.devtools.build.lib.skyframe.serialization.FieldSettercom.google.devtools.build.lib.collect.nestedset.DeferredNestedSetCodec→com.google.devtools.build.lib.skyframe.serialization.AsyncDeserializationContextcom.google.devtools.build.lib.collect.nestedset.DeferredNestedSetCodec→com.google.devtools.build.lib.skyframe.serialization.DeferredObjectCodeccom.google.devtools.build.lib.collect.nestedset.DeferredNestedSetCodec→com.google.devtools.build.lib.skyframe.serialization.SerializationContextcom.google.devtools.build.lib.collect.nestedset.FingerprintKey→com.google.devtools.build.lib.skyframe.serialization.PackedFingerprintcom.google.devtools.build.lib.collect.nestedset.NestedArrayCodec→com.google.devtools.build.lib.skyframe.serialization.AsyncDeserializationContextcom.google.devtools.build.lib.collect.nestedset.NestedArrayCodec→com.google.devtools.build.lib.skyframe.serialization.DeferredObjectCodeccom.google.devtools.build.lib.collect.nestedset.NestedArrayCodec→com.google.devtools.build.lib.skyframe.serialization.SerializationContextcom.google.devtools.build.lib.collect.nestedset.NestedSetCodecTestUtils→com.google.devtools.build.lib.skyframe.serialization.ObjectCodecscom.google.devtools.build.lib.collect.nestedset.NestedSetCodecTestUtils→com.google.devtools.build.lib.skyframe.serialization.SerializationContextcom.google.devtools.build.lib.collect.nestedset.NestedSetCodecWithStore→com.google.devtools.build.lib.skyframe.serialization.DeserializationContextcom.google.devtools.build.lib.collect.nestedset.NestedSetCodecWithStore→com.google.devtools.build.lib.skyframe.serialization.ObjectCodeccom.google.devtools.build.lib.collect.nestedset.NestedSetCodecWithStore→com.google.devtools.build.lib.skyframe.serialization.SerializationContextcom.google.devtools.build.lib.collect.nestedset.NestedSetSerializationCache→com.google.devtools.build.lib.skyframe.serialization.PackedFingerprintcom.google.devtools.build.lib.collect.nestedset.NestedSetSerializationCache→com.google.devtools.build.lib.skyframe.serialization.PutOperationcom.google.devtools.build.lib.collect.nestedset.NestedSetStore→com.google.devtools.build.lib.skyframe.serialization.DeserializationContextcom.google.devtools.build.lib.collect.nestedset.NestedSetStore→com.google.devtools.build.lib.skyframe.serialization.FingerprintValueStorecom.google.devtools.build.lib.collect.nestedset.NestedSetStore→com.google.devtools.build.lib.skyframe.serialization.PackedFingerprintcom.google.devtools.build.lib.collect.nestedset.NestedSetStore→com.google.devtools.build.lib.skyframe.serialization.PutOperationcom.google.devtools.build.lib.collect.nestedset.NestedSetStore→com.google.devtools.build.lib.skyframe.serialization.SerializationContextcom.google.devtools.build.lib.collect.nestedset.NestedSetStore→com.google.devtools.build.lib.skyframe.serialization.SerializationDependencyProvider
- Direction
- com.google.devtools.build.lib.collect.nestedset uses com.google.devtools.build.lib.skyframe.serialization, so a change to com.google.devtools.build.lib.skyframe.serialization can break com.google.devtools.build.lib.collect.nestedset, while a change to com.google.devtools.build.lib.collect.nestedset can't break com.google.devtools.build.lib.skyframe.serialization.
- Position
- Below the diagonal: com.google.devtools.build.lib.collect.nestedset uses a module listed above it, which is the healthy direction.
30→37 com.google.devtools.build.lib.collect.nestedset uses com.google.devtools.build.lib.actions part of a loop✕
- Connections
- 4 pairs of types, where a type in com.google.devtools.build.lib.collect.nestedset uses a type in com.google.devtools.build.lib.actions.
- The types involved
com.google.devtools.build.lib.collect.nestedset.ArtifactNestedSetKey→com.google.devtools.build.lib.actions.ActionInputcom.google.devtools.build.lib.collect.nestedset.ArtifactNestedSetKey→com.google.devtools.build.lib.actions.Artifactcom.google.devtools.build.lib.collect.nestedset.DirectArtifactConsumer→com.google.devtools.build.lib.actions.Artifactcom.google.devtools.build.lib.collect.nestedset.NestedSetFingerprintCache→com.google.devtools.build.lib.actions.MapFn
- Direction
- com.google.devtools.build.lib.collect.nestedset uses com.google.devtools.build.lib.actions, so a change to com.google.devtools.build.lib.actions can break com.google.devtools.build.lib.collect.nestedset, while a change to com.google.devtools.build.lib.collect.nestedset can't break com.google.devtools.build.lib.actions.
- 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→1 com.google.devtools.build.lib.cmdline uses net.starlark.java.syntax✕
- Connections
- 2 pairs of types, where a type in com.google.devtools.build.lib.cmdline uses a type in net.starlark.java.syntax.
- The types involved
com.google.devtools.build.lib.cmdline.BazelModuleContext→net.starlark.java.syntax.Commentcom.google.devtools.build.lib.cmdline.BazelModuleContext→net.starlark.java.syntax.DocComments
- Direction
- com.google.devtools.build.lib.cmdline uses net.starlark.java.syntax, so a change to net.starlark.java.syntax can break com.google.devtools.build.lib.cmdline, while a change to com.google.devtools.build.lib.cmdline can't break net.starlark.java.syntax.
- Position
- Below the diagonal: com.google.devtools.build.lib.cmdline uses a module listed above it, which is the healthy direction.
31→4 com.google.devtools.build.lib.cmdline uses net.starlark.java.eval✕
- Connections
- 7 pairs of types, where a type in com.google.devtools.build.lib.cmdline uses a type in net.starlark.java.eval.
- The types involved
com.google.devtools.build.lib.cmdline.BazelModuleContext→net.starlark.java.eval.StarlarkThreadcom.google.devtools.build.lib.cmdline.Label→net.starlark.java.eval.Printercom.google.devtools.build.lib.cmdline.Label→net.starlark.java.eval.StarlarkSemanticscom.google.devtools.build.lib.cmdline.Label→net.starlark.java.eval.StarlarkThreadcom.google.devtools.build.lib.cmdline.Label→net.starlark.java.eval.StarlarkValuecom.google.devtools.build.lib.cmdline.RepoMappingRecorder→net.starlark.java.eval.StarlarkThreadcom.google.devtools.build.lib.cmdline.StarlarkThreadContext→net.starlark.java.eval.StarlarkThread
- Direction
- com.google.devtools.build.lib.cmdline uses net.starlark.java.eval, so a change to net.starlark.java.eval can break com.google.devtools.build.lib.cmdline, while a change to com.google.devtools.build.lib.cmdline can't break net.starlark.java.eval.
- Position
- Below the diagonal: com.google.devtools.build.lib.cmdline uses a module listed above it, which is the healthy direction.
31→6 com.google.devtools.build.lib.cmdline uses com.google.devtools.build.skyframe✕
- Connections
- 7 pairs of types, where a type in com.google.devtools.build.lib.cmdline uses a type in com.google.devtools.build.skyframe.
- The types involved
com.google.devtools.build.lib.cmdline.BazelModuleKey→com.google.devtools.build.skyframe.SkyFunctionNamecom.google.devtools.build.lib.cmdline.BazelModuleKey→com.google.devtools.build.skyframe.SkyKeycom.google.devtools.build.lib.cmdline.FakeModuleKey→com.google.devtools.build.skyframe.SkyFunctionNamecom.google.devtools.build.lib.cmdline.Label→com.google.devtools.build.skyframe.SkyFunctionNamecom.google.devtools.build.lib.cmdline.Label→com.google.devtools.build.skyframe.SkyKeycom.google.devtools.build.lib.cmdline.PackageIdentifier→com.google.devtools.build.skyframe.SkyFunctionNamecom.google.devtools.build.lib.cmdline.PackageIdentifier→com.google.devtools.build.skyframe.SkyKey
- Direction
- com.google.devtools.build.lib.cmdline uses com.google.devtools.build.skyframe, so a change to com.google.devtools.build.skyframe can break com.google.devtools.build.lib.cmdline, while a change to com.google.devtools.build.lib.cmdline can't break com.google.devtools.build.skyframe.
- Position
- Below the diagonal: com.google.devtools.build.lib.cmdline uses a module listed above it, which is the healthy direction.
31→8 com.google.devtools.build.lib.cmdline uses com.google.devtools.build.lib.vfs✕
- Connections
- 13 pairs of types, where a type in com.google.devtools.build.lib.cmdline uses a type in com.google.devtools.build.lib.vfs.
- The types involved
com.google.devtools.build.lib.cmdline.IgnoredSubdirectories→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.cmdline.InterpretPathAsTarget→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.cmdline.Label→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.cmdline.LabelConstants→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.cmdline.PackageContext→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.cmdline.PackageIdentifier→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.cmdline.Parser→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.cmdline.RepositoryName→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.cmdline.SingleTarget→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.cmdline.TargetPattern→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.cmdline.TargetPatternResolver→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.cmdline.TargetsBelowDirectory→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.cmdline.TargetsInPackage→com.google.devtools.build.lib.vfs.PathFragment
- Direction
- com.google.devtools.build.lib.cmdline uses com.google.devtools.build.lib.vfs, so a change to com.google.devtools.build.lib.vfs can break com.google.devtools.build.lib.cmdline, while a change to com.google.devtools.build.lib.cmdline can't break com.google.devtools.build.lib.vfs.
- Position
- Below the diagonal: com.google.devtools.build.lib.cmdline uses a module listed above it, which is the healthy direction.
31→11 com.google.devtools.build.lib.cmdline uses com.google.devtools.build.lib.util✕
- Connections
- 2 pairs of types, where a type in com.google.devtools.build.lib.cmdline uses a type in com.google.devtools.build.lib.util.
- The types involved
com.google.devtools.build.lib.cmdline.RepositoryName→com.google.devtools.build.lib.util.Paircom.google.devtools.build.lib.cmdline.TargetParsingException→com.google.devtools.build.lib.util.DetailedExitCode
- Direction
- com.google.devtools.build.lib.cmdline uses com.google.devtools.build.lib.util, so a change to com.google.devtools.build.lib.util can break com.google.devtools.build.lib.cmdline, while a change to com.google.devtools.build.lib.cmdline can't break com.google.devtools.build.lib.util.
- Position
- Below the diagonal: com.google.devtools.build.lib.cmdline uses a module listed above it, which is the healthy direction.
31→24 com.google.devtools.build.lib.cmdline uses com.google.devtools.build.lib.skyframe✕
- Connections
- 1 pair of types, where a type in com.google.devtools.build.lib.cmdline uses a type in com.google.devtools.build.lib.skyframe.
- The types involved
com.google.devtools.build.lib.cmdline.TargetParsingException→com.google.devtools.build.lib.skyframe.DetailedException
- Direction
- com.google.devtools.build.lib.cmdline uses com.google.devtools.build.lib.skyframe, so a change to com.google.devtools.build.lib.skyframe can break com.google.devtools.build.lib.cmdline, while a change to com.google.devtools.build.lib.cmdline can't break com.google.devtools.build.lib.skyframe.
- Position
- Below the diagonal: com.google.devtools.build.lib.cmdline uses a module listed above it, which is the healthy direction.
31→29 com.google.devtools.build.lib.cmdline uses com.google.devtools.build.lib.skyframe.serialization✕
- Connections
- 15 pairs of types, where a type in com.google.devtools.build.lib.cmdline uses a type in com.google.devtools.build.lib.skyframe.serialization.
- The types involved
com.google.devtools.build.lib.cmdline.Codec→com.google.devtools.build.lib.skyframe.serialization.LeafDeserializationContextcom.google.devtools.build.lib.cmdline.Codec→com.google.devtools.build.lib.skyframe.serialization.LeafObjectCodeccom.google.devtools.build.lib.cmdline.Codec→com.google.devtools.build.lib.skyframe.serialization.LeafSerializationContextcom.google.devtools.build.lib.cmdline.IgnoredSubdirectories→com.google.devtools.build.lib.skyframe.serialization.ObjectCodeccom.google.devtools.build.lib.cmdline.Label→com.google.devtools.build.lib.skyframe.serialization.DeferredObjectCodeccom.google.devtools.build.lib.cmdline.LabelDeferredCodec→com.google.devtools.build.lib.skyframe.serialization.AsyncDeserializationContextcom.google.devtools.build.lib.cmdline.LabelDeferredCodec→com.google.devtools.build.lib.skyframe.serialization.DeferredObjectCodeccom.google.devtools.build.lib.cmdline.LabelDeferredCodec→com.google.devtools.build.lib.skyframe.serialization.SerializationContextcom.google.devtools.build.lib.cmdline.PackageIdentifier→com.google.devtools.build.lib.skyframe.serialization.DeferredObjectCodeccom.google.devtools.build.lib.cmdline.PackageIdentifierDeferredCodec→com.google.devtools.build.lib.skyframe.serialization.AsyncDeserializationContextcom.google.devtools.build.lib.cmdline.PackageIdentifierDeferredCodec→com.google.devtools.build.lib.skyframe.serialization.DeferredObjectCodeccom.google.devtools.build.lib.cmdline.PackageIdentifierDeferredCodec→com.google.devtools.build.lib.skyframe.serialization.SerializationContextcom.google.devtools.build.lib.cmdline.PackageIdentifierLeafCodec→com.google.devtools.build.lib.skyframe.serialization.LeafDeserializationContextcom.google.devtools.build.lib.cmdline.PackageIdentifierLeafCodec→com.google.devtools.build.lib.skyframe.serialization.LeafObjectCodeccom.google.devtools.build.lib.cmdline.PackageIdentifierLeafCodec→com.google.devtools.build.lib.skyframe.serialization.LeafSerializationContext
- Direction
- com.google.devtools.build.lib.cmdline uses com.google.devtools.build.lib.skyframe.serialization, so a change to com.google.devtools.build.lib.skyframe.serialization can break com.google.devtools.build.lib.cmdline, while a change to com.google.devtools.build.lib.cmdline can't break com.google.devtools.build.lib.skyframe.serialization.
- Position
- Below the diagonal: com.google.devtools.build.lib.cmdline uses a module listed above it, which is the healthy direction.
31→30 com.google.devtools.build.lib.cmdline uses com.google.devtools.build.lib.collect.nestedset✕
- Connections
- 1 pair of types, where a type in com.google.devtools.build.lib.cmdline uses a type in com.google.devtools.build.lib.collect.nestedset.
- The types involved
com.google.devtools.build.lib.cmdline.Label→com.google.devtools.build.lib.collect.nestedset.NestedSetsShouldBeInternedByEquality
- Direction
- com.google.devtools.build.lib.cmdline uses com.google.devtools.build.lib.collect.nestedset, so a change to com.google.devtools.build.lib.collect.nestedset can break com.google.devtools.build.lib.cmdline, while a change to com.google.devtools.build.lib.cmdline can't break com.google.devtools.build.lib.collect.nestedset.
- Position
- Below the diagonal: com.google.devtools.build.lib.cmdline uses a module listed above it, which is the healthy direction.
31→37 com.google.devtools.build.lib.cmdline uses com.google.devtools.build.lib.actions part of a loop✕
- Connections
- 1 pair of types, where a type in com.google.devtools.build.lib.cmdline uses a type in com.google.devtools.build.lib.actions.
- The types involved
com.google.devtools.build.lib.cmdline.Label→com.google.devtools.build.lib.actions.CommandLineItem
- Direction
- com.google.devtools.build.lib.cmdline uses com.google.devtools.build.lib.actions, so a change to com.google.devtools.build.lib.actions can break com.google.devtools.build.lib.cmdline, while a change to com.google.devtools.build.lib.cmdline can't break com.google.devtools.build.lib.actions.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
32→4 com.google.devtools.build.lib.analysis.platform uses net.starlark.java.eval✕
- Connections
- 12 pairs of types, where a type in com.google.devtools.build.lib.analysis.platform uses a type in net.starlark.java.eval.
- The types involved
com.google.devtools.build.lib.analysis.platform.ConstraintCollection→net.starlark.java.eval.Printercom.google.devtools.build.lib.analysis.platform.ConstraintCollection→net.starlark.java.eval.Sequencecom.google.devtools.build.lib.analysis.platform.ConstraintCollection→net.starlark.java.eval.StarlarkSemanticscom.google.devtools.build.lib.analysis.platform.ConstraintSettingInfo→net.starlark.java.eval.Printercom.google.devtools.build.lib.analysis.platform.ConstraintSettingInfo→net.starlark.java.eval.StarlarkSemanticscom.google.devtools.build.lib.analysis.platform.ConstraintValueInfo→net.starlark.java.eval.Printercom.google.devtools.build.lib.analysis.platform.ConstraintValueInfo→net.starlark.java.eval.StarlarkSemanticscom.google.devtools.build.lib.analysis.platform.PlatformInfo→net.starlark.java.eval.Printercom.google.devtools.build.lib.analysis.platform.PlatformInfo→net.starlark.java.eval.StarlarkSemanticscom.google.devtools.build.lib.analysis.platform.Provider→net.starlark.java.eval.Dictcom.google.devtools.build.lib.analysis.platform.ToolchainTypeInfo→net.starlark.java.eval.Printercom.google.devtools.build.lib.analysis.platform.ToolchainTypeInfo→net.starlark.java.eval.StarlarkSemantics
- Direction
- com.google.devtools.build.lib.analysis.platform uses net.starlark.java.eval, so a change to net.starlark.java.eval can break com.google.devtools.build.lib.analysis.platform, while a change to com.google.devtools.build.lib.analysis.platform can't break net.starlark.java.eval.
- Position
- Below the diagonal: com.google.devtools.build.lib.analysis.platform uses a module listed above it, which is the healthy direction.
32→6 com.google.devtools.build.lib.analysis.platform uses com.google.devtools.build.skyframe✕
- Connections
- 8 pairs of types, where a type in com.google.devtools.build.lib.analysis.platform uses a type in com.google.devtools.build.skyframe.
- The types involved
com.google.devtools.build.lib.analysis.platform.Key→com.google.devtools.build.skyframe.SkyFunctionNamecom.google.devtools.build.lib.analysis.platform.Key→com.google.devtools.build.skyframe.SkyKeycom.google.devtools.build.lib.analysis.platform.PlatformFunction→com.google.devtools.build.skyframe.SkyFunctioncom.google.devtools.build.lib.analysis.platform.PlatformFunction→com.google.devtools.build.skyframe.SkyKeycom.google.devtools.build.lib.analysis.platform.PlatformFunctionException→com.google.devtools.build.skyframe.SkyFunctionExceptioncom.google.devtools.build.lib.analysis.platform.PlatformValue→com.google.devtools.build.skyframe.SkyValuecom.google.devtools.build.lib.analysis.platform.SkyframeEvaluator→com.google.devtools.build.skyframe.SkyKeycom.google.devtools.build.lib.analysis.platform.SkyframeEvaluator→com.google.devtools.build.skyframe.SkyValue
- Direction
- com.google.devtools.build.lib.analysis.platform uses com.google.devtools.build.skyframe, so a change to com.google.devtools.build.skyframe can break com.google.devtools.build.lib.analysis.platform, while a change to com.google.devtools.build.lib.analysis.platform can't break com.google.devtools.build.skyframe.
- Position
- Below the diagonal: com.google.devtools.build.lib.analysis.platform uses a module listed above it, which is the healthy direction.
32→10 com.google.devtools.build.lib.analysis.platform uses com.google.devtools.build.lib.skyframe.config✕
- Connections
- 1 pair of types, where a type in com.google.devtools.build.lib.analysis.platform uses a type in com.google.devtools.build.lib.skyframe.config.
- The types involved
com.google.devtools.build.lib.analysis.platform.PlatformValue→com.google.devtools.build.lib.skyframe.config.ParsedFlagsValue
- Direction
- com.google.devtools.build.lib.analysis.platform uses com.google.devtools.build.lib.skyframe.config, so a change to com.google.devtools.build.lib.skyframe.config can break com.google.devtools.build.lib.analysis.platform, while a change to com.google.devtools.build.lib.analysis.platform can't break com.google.devtools.build.lib.skyframe.config.
- Position
- Below the diagonal: com.google.devtools.build.lib.analysis.platform uses a module listed above it, which is the healthy direction.
32→11 com.google.devtools.build.lib.analysis.platform uses com.google.devtools.build.lib.util✕
- Connections
- 4 pairs of types, where a type in com.google.devtools.build.lib.analysis.platform uses a type in com.google.devtools.build.lib.util.
- The types involved
com.google.devtools.build.lib.analysis.platform.ConstraintCollection→com.google.devtools.build.lib.util.Fingerprintcom.google.devtools.build.lib.analysis.platform.ConstraintSettingInfo→com.google.devtools.build.lib.util.Fingerprintcom.google.devtools.build.lib.analysis.platform.ConstraintValueInfo→com.google.devtools.build.lib.util.Fingerprintcom.google.devtools.build.lib.analysis.platform.PlatformInfo→com.google.devtools.build.lib.util.Fingerprint
- Direction
- com.google.devtools.build.lib.analysis.platform uses com.google.devtools.build.lib.util, so a change to com.google.devtools.build.lib.util can break com.google.devtools.build.lib.analysis.platform, while a change to com.google.devtools.build.lib.analysis.platform can't break com.google.devtools.build.lib.util.
- Position
- Below the diagonal: com.google.devtools.build.lib.analysis.platform uses a module listed above it, which is the healthy direction.
32→24 com.google.devtools.build.lib.analysis.platform uses com.google.devtools.build.lib.skyframe✕
- Connections
- 1 pair of types, where a type in com.google.devtools.build.lib.analysis.platform uses a type in com.google.devtools.build.lib.skyframe.
- The types involved
com.google.devtools.build.lib.analysis.platform.PlatformFunction→com.google.devtools.build.lib.skyframe.ConfiguredTargetKey
- Direction
- com.google.devtools.build.lib.analysis.platform uses com.google.devtools.build.lib.skyframe, so a change to com.google.devtools.build.lib.skyframe can break com.google.devtools.build.lib.analysis.platform, while a change to com.google.devtools.build.lib.analysis.platform can't break com.google.devtools.build.lib.skyframe.
- Position
- Below the diagonal: com.google.devtools.build.lib.analysis.platform uses a module listed above it, which is the healthy direction.
32→25 com.google.devtools.build.lib.analysis.platform uses com.google.devtools.build.lib.packages✕
- Connections
- 13 pairs of types, where a type in com.google.devtools.build.lib.analysis.platform uses a type in com.google.devtools.build.lib.packages.
- The types involved
com.google.devtools.build.lib.analysis.platform.1→com.google.devtools.build.lib.packages.BuiltinProvidercom.google.devtools.build.lib.analysis.platform.1929→com.google.devtools.build.lib.packages.BuiltinProvidercom.google.devtools.build.lib.analysis.platform.ConstraintSettingInfo→com.google.devtools.build.lib.packages.BuiltinProvidercom.google.devtools.build.lib.analysis.platform.ConstraintSettingInfo→com.google.devtools.build.lib.packages.NativeInfocom.google.devtools.build.lib.analysis.platform.ConstraintValueInfo→com.google.devtools.build.lib.packages.BuiltinProvidercom.google.devtools.build.lib.analysis.platform.ConstraintValueInfo→com.google.devtools.build.lib.packages.NativeInfocom.google.devtools.build.lib.analysis.platform.PlatformInfo→com.google.devtools.build.lib.packages.BuiltinProvidercom.google.devtools.build.lib.analysis.platform.PlatformInfo→com.google.devtools.build.lib.packages.NativeInfocom.google.devtools.build.lib.analysis.platform.Provider→com.google.devtools.build.lib.packages.BuiltinProvidercom.google.devtools.build.lib.analysis.platform.ToolchainInfo→com.google.devtools.build.lib.packages.BuiltinProvidercom.google.devtools.build.lib.analysis.platform.ToolchainInfo→com.google.devtools.build.lib.packages.StructImplcom.google.devtools.build.lib.analysis.platform.ToolchainTypeInfo→com.google.devtools.build.lib.packages.BuiltinProvidercom.google.devtools.build.lib.analysis.platform.ToolchainTypeInfo→com.google.devtools.build.lib.packages.NativeInfo
- Direction
- com.google.devtools.build.lib.analysis.platform uses com.google.devtools.build.lib.packages, so a change to com.google.devtools.build.lib.packages can break com.google.devtools.build.lib.analysis.platform, while a change to com.google.devtools.build.lib.analysis.platform can't break com.google.devtools.build.lib.packages.
- Position
- Below the diagonal: com.google.devtools.build.lib.analysis.platform uses a module listed above it, which is the healthy direction.
32→31 com.google.devtools.build.lib.analysis.platform uses com.google.devtools.build.lib.cmdline✕
- Connections
- 10 pairs of types, where a type in com.google.devtools.build.lib.analysis.platform uses a type in com.google.devtools.build.lib.cmdline.
- The types involved
com.google.devtools.build.lib.analysis.platform.ConstraintSettingInfo→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.analysis.platform.ConstraintValueInfo→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.analysis.platform.DeclaredToolchainInfo→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.analysis.platform.Key→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.analysis.platform.PlatformConstants→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.analysis.platform.PlatformFunction→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.analysis.platform.PlatformInfo→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.analysis.platform.PlatformValue→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.analysis.platform.PlatformValue→com.google.devtools.build.lib.cmdline.RepositoryMappingcom.google.devtools.build.lib.analysis.platform.ToolchainTypeInfo→com.google.devtools.build.lib.cmdline.Label
- Direction
- com.google.devtools.build.lib.analysis.platform uses com.google.devtools.build.lib.cmdline, so a change to com.google.devtools.build.lib.cmdline can break com.google.devtools.build.lib.analysis.platform, while a change to com.google.devtools.build.lib.analysis.platform can't break com.google.devtools.build.lib.cmdline.
- Position
- Below the diagonal: com.google.devtools.build.lib.analysis.platform uses a module listed above it, which is the healthy direction.
32→33 com.google.devtools.build.lib.analysis.platform uses com.google.devtools.build.lib.analysis.config part of a loop✕
- Connections
- 3 pairs of types, where a type in com.google.devtools.build.lib.analysis.platform uses a type in com.google.devtools.build.lib.analysis.config.
- The types involved
com.google.devtools.build.lib.analysis.platform.ConstraintValueInfo→com.google.devtools.build.lib.analysis.config.ConfigMatchingProvidercom.google.devtools.build.lib.analysis.platform.DeclaredToolchainInfo→com.google.devtools.build.lib.analysis.config.ConfigMatchingProvidercom.google.devtools.build.lib.analysis.platform.PlatformInfo→com.google.devtools.build.lib.analysis.config.ConfigMatchingProvider
- Direction
- com.google.devtools.build.lib.analysis.platform uses com.google.devtools.build.lib.analysis.config, so a change to com.google.devtools.build.lib.analysis.config can break com.google.devtools.build.lib.analysis.platform, while a change to com.google.devtools.build.lib.analysis.platform can't break com.google.devtools.build.lib.analysis.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.
32→35 com.google.devtools.build.lib.analysis.platform uses com.google.devtools.build.lib.analysis part of a loop✕
- Connections
- 3 pairs of types, where a type in com.google.devtools.build.lib.analysis.platform uses a type in com.google.devtools.build.lib.analysis.
- The types involved
com.google.devtools.build.lib.analysis.platform.DeclaredToolchainInfo→com.google.devtools.build.lib.analysis.TransitiveInfoProvidercom.google.devtools.build.lib.analysis.platform.PlatformProviderUtils→com.google.devtools.build.lib.analysis.ProviderCollectioncom.google.devtools.build.lib.analysis.platform.ToolchainInfo→com.google.devtools.build.lib.analysis.ResolvedToolchainData
- Direction
- com.google.devtools.build.lib.analysis.platform uses com.google.devtools.build.lib.analysis, so a change to com.google.devtools.build.lib.analysis can break com.google.devtools.build.lib.analysis.platform, while a change to com.google.devtools.build.lib.analysis.platform can't break com.google.devtools.build.lib.analysis.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
32→37 com.google.devtools.build.lib.analysis.platform uses com.google.devtools.build.lib.actions part of a loop✕
- Connections
- 1 pair of types, where a type in com.google.devtools.build.lib.analysis.platform uses a type in com.google.devtools.build.lib.actions.
- The types involved
com.google.devtools.build.lib.analysis.platform.PlatformUtils→com.google.devtools.build.lib.actions.Spawn
- Direction
- com.google.devtools.build.lib.analysis.platform uses com.google.devtools.build.lib.actions, so a change to com.google.devtools.build.lib.actions can break com.google.devtools.build.lib.analysis.platform, while a change to com.google.devtools.build.lib.analysis.platform can't break com.google.devtools.build.lib.actions.
- 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→1 com.google.devtools.build.lib.analysis.config uses net.starlark.java.syntax✕
- Connections
- 5 pairs of types, where a type in com.google.devtools.build.lib.analysis.config uses a type in net.starlark.java.syntax.
- The types involved
com.google.devtools.build.lib.analysis.config.AnalysisTestTransition→net.starlark.java.syntax.Locationcom.google.devtools.build.lib.analysis.config.DependencyEvaluationException→net.starlark.java.syntax.Locationcom.google.devtools.build.lib.analysis.config.ExecTransition→net.starlark.java.syntax.Locationcom.google.devtools.build.lib.analysis.config.RegularTransition→net.starlark.java.syntax.Locationcom.google.devtools.build.lib.analysis.config.StarlarkDefinedConfigTransition→net.starlark.java.syntax.Location
- Direction
- com.google.devtools.build.lib.analysis.config uses net.starlark.java.syntax, so a change to net.starlark.java.syntax can break com.google.devtools.build.lib.analysis.config, while a change to com.google.devtools.build.lib.analysis.config can't break net.starlark.java.syntax.
- Position
- Below the diagonal: com.google.devtools.build.lib.analysis.config uses a module listed above it, which is the healthy direction.
33→2 com.google.devtools.build.lib.analysis.config uses com.google.devtools.build.lib.events✕
- Connections
- 8 pairs of types, where a type in com.google.devtools.build.lib.analysis.config uses a type in com.google.devtools.build.lib.events.
- The types involved
com.google.devtools.build.lib.analysis.config.AnalysisTestTransition→com.google.devtools.build.lib.events.EventHandlercom.google.devtools.build.lib.analysis.config.BuildConfigurationValue→com.google.devtools.build.lib.events.EventHandlercom.google.devtools.build.lib.analysis.config.ExecTransitionFinalizer→com.google.devtools.build.lib.events.EventHandlercom.google.devtools.build.lib.analysis.config.Fragment→com.google.devtools.build.lib.events.EventHandlercom.google.devtools.build.lib.analysis.config.RegularTransition→com.google.devtools.build.lib.events.EventHandlercom.google.devtools.build.lib.analysis.config.StarlarkDefinedConfigTransition→com.google.devtools.build.lib.events.EventHandlercom.google.devtools.build.lib.analysis.config.StarlarkTransitionCache→com.google.devtools.build.lib.events.ExtendedEventHandlercom.google.devtools.build.lib.analysis.config.Value→com.google.devtools.build.lib.events.StoredEventHandler
- Direction
- com.google.devtools.build.lib.analysis.config uses com.google.devtools.build.lib.events, so a change to com.google.devtools.build.lib.events can break com.google.devtools.build.lib.analysis.config, while a change to com.google.devtools.build.lib.analysis.config can't break com.google.devtools.build.lib.events.
- Position
- Below the diagonal: com.google.devtools.build.lib.analysis.config uses a module listed above it, which is the healthy direction.
33→3 com.google.devtools.build.lib.analysis.config uses com.google.devtools.common.options✕
- Connections
- 25 pairs of types, where a type in com.google.devtools.build.lib.analysis.config uses a type in com.google.devtools.common.options.
- The types involved
com.google.devtools.build.lib.analysis.config.AutoCpuConverter→com.google.devtools.common.options.Contextlesscom.google.devtools.build.lib.analysis.config.BuildOptions→com.google.devtools.common.options.OptionsParsingResultcom.google.devtools.build.lib.analysis.config.BuildOptions→com.google.devtools.common.options.OptionsProvidercom.google.devtools.build.lib.analysis.config.CoreOptionConverters→com.google.devtools.common.options.Convertercom.google.devtools.build.lib.analysis.config.CoreOptions→com.google.devtools.common.options.TriStatecom.google.devtools.build.lib.analysis.config.CustomFlagConverter→com.google.devtools.common.options.Convertercom.google.devtools.build.lib.analysis.config.EmptyToNullLabelConverter→com.google.devtools.common.options.Convertercom.google.devtools.build.lib.analysis.config.FlagAliasConverter→com.google.devtools.common.options.Convertercom.google.devtools.build.lib.analysis.config.FragmentOptions→com.google.devtools.common.options.OptionsBasecom.google.devtools.build.lib.analysis.config.IncludeConfigFragmentsEnumConverter→com.google.devtools.common.options.EnumConvertercom.google.devtools.build.lib.analysis.config.LabelConverter→com.google.devtools.common.options.Convertercom.google.devtools.build.lib.analysis.config.LabelListConverter→com.google.devtools.common.options.Convertercom.google.devtools.build.lib.analysis.config.LabelMapConverter→com.google.devtools.common.options.Convertercom.google.devtools.build.lib.analysis.config.LabelToStringEntryConverter→com.google.devtools.common.options.Convertercom.google.devtools.build.lib.analysis.config.OptionInfo→com.google.devtools.common.options.OptionDefinitioncom.google.devtools.build.lib.analysis.config.OptionInfo→com.google.devtools.common.options.OptionMetadataTagcom.google.devtools.build.lib.analysis.config.OptionRef→com.google.devtools.common.options.OptionDefinitioncom.google.devtools.build.lib.analysis.config.OptionRef→com.google.devtools.common.options.OptionsBasecom.google.devtools.build.lib.analysis.config.OptionsDiff→com.google.devtools.common.options.OptionDefinitioncom.google.devtools.build.lib.analysis.config.OutputPathsConverter→com.google.devtools.common.options.EnumConvertercom.google.devtools.build.lib.analysis.config.PerLabelOptionsConverter→com.google.devtools.common.options.Contextlesscom.google.devtools.build.lib.analysis.config.RunUnderConverter→com.google.devtools.common.options.Convertercom.google.devtools.build.lib.analysis.config.StarlarkIntConverter→com.google.devtools.common.options.Contextlesscom.google.devtools.build.lib.analysis.config.StrictDepsConverter→com.google.devtools.common.options.EnumConvertercom.google.devtools.build.lib.analysis.config.StringSetConverter→com.google.devtools.common.options.Contextless
- Direction
- com.google.devtools.build.lib.analysis.config uses com.google.devtools.common.options, so a change to com.google.devtools.common.options can break com.google.devtools.build.lib.analysis.config, while a change to com.google.devtools.build.lib.analysis.config can't break com.google.devtools.common.options.
- Position
- Below the diagonal: com.google.devtools.build.lib.analysis.config uses a module listed above it, which is the healthy direction.
33→4 com.google.devtools.build.lib.analysis.config uses net.starlark.java.eval✕
- Connections
- 16 pairs of types, where a type in com.google.devtools.build.lib.analysis.config uses a type in net.starlark.java.eval.
- The types involved
com.google.devtools.build.lib.analysis.config.AnalysisTestTransition→net.starlark.java.eval.Printercom.google.devtools.build.lib.analysis.config.AnalysisTestTransition→net.starlark.java.eval.StarlarkSemanticscom.google.devtools.build.lib.analysis.config.BuildConfigurationValue→net.starlark.java.eval.StarlarkSetcom.google.devtools.build.lib.analysis.config.BuildConfigurationValue→net.starlark.java.eval.StarlarkThreadcom.google.devtools.build.lib.analysis.config.DependencyEvaluationException→net.starlark.java.eval.EvalExceptioncom.google.devtools.build.lib.analysis.config.ExecTransition→net.starlark.java.eval.StarlarkCallablecom.google.devtools.build.lib.analysis.config.ExecTransition→net.starlark.java.eval.StarlarkSemanticscom.google.devtools.build.lib.analysis.config.Fragment→net.starlark.java.eval.StarlarkValuecom.google.devtools.build.lib.analysis.config.RegularTransition→net.starlark.java.eval.Dictcom.google.devtools.build.lib.analysis.config.RegularTransition→net.starlark.java.eval.Mutabilitycom.google.devtools.build.lib.analysis.config.RegularTransition→net.starlark.java.eval.Printercom.google.devtools.build.lib.analysis.config.RegularTransition→net.starlark.java.eval.StarlarkCallablecom.google.devtools.build.lib.analysis.config.RegularTransition→net.starlark.java.eval.StarlarkSemanticscom.google.devtools.build.lib.analysis.config.StarlarkDefinedConfigTransition→net.starlark.java.eval.StarlarkCallablecom.google.devtools.build.lib.analysis.config.StarlarkDefinedConfigTransition→net.starlark.java.eval.StarlarkSemanticscom.google.devtools.build.lib.analysis.config.StarlarkIntConverter→net.starlark.java.eval.StarlarkInt
- Direction
- com.google.devtools.build.lib.analysis.config uses net.starlark.java.eval, so a change to net.starlark.java.eval can break com.google.devtools.build.lib.analysis.config, while a change to com.google.devtools.build.lib.analysis.config can't break net.starlark.java.eval.
- Position
- Below the diagonal: com.google.devtools.build.lib.analysis.config uses a module listed above it, which is the healthy direction.
33→6 com.google.devtools.build.lib.analysis.config uses com.google.devtools.build.skyframe✕
- Connections
- 1 pair of types, where a type in com.google.devtools.build.lib.analysis.config uses a type in com.google.devtools.build.skyframe.
- The types involved
com.google.devtools.build.lib.analysis.config.BuildConfigurationValue→com.google.devtools.build.skyframe.SkyValue
- Direction
- com.google.devtools.build.lib.analysis.config uses com.google.devtools.build.skyframe, so a change to com.google.devtools.build.skyframe can break com.google.devtools.build.lib.analysis.config, while a change to com.google.devtools.build.lib.analysis.config can't break com.google.devtools.build.skyframe.
- Position
- Below the diagonal: com.google.devtools.build.lib.analysis.config uses a module listed above it, which is the healthy direction.
33→8 com.google.devtools.build.lib.analysis.config uses com.google.devtools.build.lib.vfs✕
- Connections
- 3 pairs of types, where a type in com.google.devtools.build.lib.analysis.config uses a type in com.google.devtools.build.lib.vfs.
- The types involved
com.google.devtools.build.lib.analysis.config.BuildConfigurationValue→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.analysis.config.OutputDirectories→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.analysis.config.SymlinkDefinition→com.google.devtools.build.lib.vfs.Path
- Direction
- com.google.devtools.build.lib.analysis.config uses com.google.devtools.build.lib.vfs, so a change to com.google.devtools.build.lib.vfs can break com.google.devtools.build.lib.analysis.config, while a change to com.google.devtools.build.lib.analysis.config can't break com.google.devtools.build.lib.vfs.
- Position
- Below the diagonal: com.google.devtools.build.lib.analysis.config uses a module listed above it, which is the healthy direction.
33→10 com.google.devtools.build.lib.analysis.config uses com.google.devtools.build.lib.skyframe.config✕
- Connections
- 1 pair of types, where a type in com.google.devtools.build.lib.analysis.config uses a type in com.google.devtools.build.lib.skyframe.config.
- The types involved
com.google.devtools.build.lib.analysis.config.BuildConfigurationValue→com.google.devtools.build.lib.skyframe.config.BuildConfigurationKey
- Direction
- com.google.devtools.build.lib.analysis.config uses com.google.devtools.build.lib.skyframe.config, so a change to com.google.devtools.build.lib.skyframe.config can break com.google.devtools.build.lib.analysis.config, while a change to com.google.devtools.build.lib.analysis.config can't break com.google.devtools.build.lib.skyframe.config.
- Position
- Below the diagonal: com.google.devtools.build.lib.analysis.config uses a module listed above it, which is the healthy direction.
33→11 com.google.devtools.build.lib.analysis.config uses com.google.devtools.build.lib.util✕
- Connections
- 9 pairs of types, where a type in com.google.devtools.build.lib.analysis.config uses a type in com.google.devtools.build.lib.util.
- The types involved
com.google.devtools.build.lib.analysis.config.BuildConfigurationValue→com.google.devtools.build.lib.util.RegexFiltercom.google.devtools.build.lib.analysis.config.CoreOptions→com.google.devtools.build.lib.util.EnvVarcom.google.devtools.build.lib.analysis.config.CoreOptions→com.google.devtools.build.lib.util.RegexFiltercom.google.devtools.build.lib.analysis.config.DependencyEvaluationException→com.google.devtools.build.lib.util.DetailedExitCodecom.google.devtools.build.lib.analysis.config.ExecutionTransitionFactory→com.google.devtools.build.lib.util.Paircom.google.devtools.build.lib.analysis.config.FragmentOptions→com.google.devtools.build.lib.util.EnvVarcom.google.devtools.build.lib.analysis.config.FragmentOptions→com.google.devtools.build.lib.util.Fingerprintcom.google.devtools.build.lib.analysis.config.InvalidConfigurationException→com.google.devtools.build.lib.util.DetailedExitCodecom.google.devtools.build.lib.analysis.config.PerLabelOptions→com.google.devtools.build.lib.util.RegexFilter
- Direction
- com.google.devtools.build.lib.analysis.config uses com.google.devtools.build.lib.util, so a change to com.google.devtools.build.lib.util can break com.google.devtools.build.lib.analysis.config, while a change to com.google.devtools.build.lib.analysis.config can't break com.google.devtools.build.lib.util.
- Position
- Below the diagonal: com.google.devtools.build.lib.analysis.config uses a module listed above it, which is the healthy direction.
33→14 com.google.devtools.build.lib.analysis.config uses com.google.devtools.build.lib.buildeventstream✕
- Connections
- 1 pair of types, where a type in com.google.devtools.build.lib.analysis.config uses a type in com.google.devtools.build.lib.buildeventstream.
- The types involved
com.google.devtools.build.lib.analysis.config.BuildConfigurationValue→com.google.devtools.build.lib.buildeventstream.BuildEvent
- Direction
- com.google.devtools.build.lib.analysis.config uses com.google.devtools.build.lib.buildeventstream, so a change to com.google.devtools.build.lib.buildeventstream can break com.google.devtools.build.lib.analysis.config, while a change to com.google.devtools.build.lib.analysis.config can't break com.google.devtools.build.lib.buildeventstream.
- Position
- Below the diagonal: com.google.devtools.build.lib.analysis.config uses a module listed above it, which is the healthy direction.
33→23 com.google.devtools.build.lib.analysis.config uses com.google.devtools.build.lib.buildtool✕
- Connections
- 1 pair of types, where a type in com.google.devtools.build.lib.analysis.config uses a type in com.google.devtools.build.lib.buildtool.
- The types involved
com.google.devtools.build.lib.analysis.config.SymlinkDefinition→com.google.devtools.build.lib.buildtool.BuildRequestOptions
- Direction
- com.google.devtools.build.lib.analysis.config uses com.google.devtools.build.lib.buildtool, so a change to com.google.devtools.build.lib.buildtool can break com.google.devtools.build.lib.analysis.config, while a change to com.google.devtools.build.lib.analysis.config can't break com.google.devtools.build.lib.buildtool.
- Position
- Below the diagonal: com.google.devtools.build.lib.analysis.config uses a module listed above it, which is the healthy direction.
33→24 com.google.devtools.build.lib.analysis.config uses com.google.devtools.build.lib.skyframe✕
- Connections
- 5 pairs of types, where a type in com.google.devtools.build.lib.analysis.config uses a type in com.google.devtools.build.lib.skyframe.
- The types involved
com.google.devtools.build.lib.analysis.config.BzlFileLoader→com.google.devtools.build.lib.skyframe.BzlLoadValuecom.google.devtools.build.lib.analysis.config.BzlFileLoader→com.google.devtools.build.lib.skyframe.Keycom.google.devtools.build.lib.analysis.config.ConfigConditions→com.google.devtools.build.lib.skyframe.ConfiguredTargetAndDatacom.google.devtools.build.lib.analysis.config.DependencyEvaluationException→com.google.devtools.build.lib.skyframe.ConfiguredValueCreationExceptioncom.google.devtools.build.lib.analysis.config.InvalidConfigurationException→com.google.devtools.build.lib.skyframe.DetailedException
- Direction
- com.google.devtools.build.lib.analysis.config uses com.google.devtools.build.lib.skyframe, so a change to com.google.devtools.build.lib.skyframe can break com.google.devtools.build.lib.analysis.config, while a change to com.google.devtools.build.lib.analysis.config can't break com.google.devtools.build.lib.skyframe.
- Position
- Below the diagonal: com.google.devtools.build.lib.analysis.config uses a module listed above it, which is the healthy direction.
33→25 com.google.devtools.build.lib.analysis.config uses com.google.devtools.build.lib.packages✕
- Connections
- 7 pairs of types, where a type in com.google.devtools.build.lib.analysis.config uses a type in com.google.devtools.build.lib.packages.
- The types involved
com.google.devtools.build.lib.analysis.config.AnalysisTestTransition→com.google.devtools.build.lib.packages.StructImplcom.google.devtools.build.lib.analysis.config.ConfigAwareAspectBuilder→com.google.devtools.build.lib.packages.Buildercom.google.devtools.build.lib.analysis.config.CoreOptionConverters→com.google.devtools.build.lib.packages.Typecom.google.devtools.build.lib.analysis.config.ExecutionTransitionFactory→com.google.devtools.build.lib.packages.AttributeTransitionDatacom.google.devtools.build.lib.analysis.config.RegularTransition→com.google.devtools.build.lib.packages.StructImplcom.google.devtools.build.lib.analysis.config.StarlarkDefinedConfigTransition→com.google.devtools.build.lib.packages.RuleTransitionDatacom.google.devtools.build.lib.analysis.config.StarlarkDefinedConfigTransition→com.google.devtools.build.lib.packages.StructImpl
- Direction
- com.google.devtools.build.lib.analysis.config uses com.google.devtools.build.lib.packages, so a change to com.google.devtools.build.lib.packages can break com.google.devtools.build.lib.analysis.config, while a change to com.google.devtools.build.lib.analysis.config can't break com.google.devtools.build.lib.packages.
- Position
- Below the diagonal: com.google.devtools.build.lib.analysis.config uses a module listed above it, which is the healthy direction.
33→26 com.google.devtools.build.lib.analysis.config uses com.google.devtools.build.lib.analysis.starlark✕
- Connections
- 4 pairs of types, where a type in com.google.devtools.build.lib.analysis.config uses a type in com.google.devtools.build.lib.analysis.starlark.
- The types involved
com.google.devtools.build.lib.analysis.config.Key→com.google.devtools.build.lib.analysis.starlark.StarlarkBuildSettingsDetailsValuecom.google.devtools.build.lib.analysis.config.StarlarkExecTransitionLoader→com.google.devtools.build.lib.analysis.starlark.StarlarkAttributeTransitionProvidercom.google.devtools.build.lib.analysis.config.StarlarkExecTransitionProvider→com.google.devtools.build.lib.analysis.starlark.StarlarkAttributeTransitionProvidercom.google.devtools.build.lib.analysis.config.StarlarkTransitionCache→com.google.devtools.build.lib.analysis.starlark.StarlarkBuildSettingsDetailsValue
- Direction
- com.google.devtools.build.lib.analysis.config uses com.google.devtools.build.lib.analysis.starlark, so a change to com.google.devtools.build.lib.analysis.starlark can break com.google.devtools.build.lib.analysis.config, while a change to com.google.devtools.build.lib.analysis.config can't break com.google.devtools.build.lib.analysis.starlark.
- Position
- Below the diagonal: com.google.devtools.build.lib.analysis.config uses a module listed above it, which is the healthy direction.
33→29 com.google.devtools.build.lib.analysis.config uses com.google.devtools.build.lib.skyframe.serialization✕
- Connections
- 11 pairs of types, where a type in com.google.devtools.build.lib.analysis.config uses a type in com.google.devtools.build.lib.skyframe.serialization.
- The types involved
com.google.devtools.build.lib.analysis.config.Codec→com.google.devtools.build.lib.skyframe.serialization.LeafDeserializationContextcom.google.devtools.build.lib.analysis.config.Codec→com.google.devtools.build.lib.skyframe.serialization.LeafObjectCodeccom.google.devtools.build.lib.analysis.config.Codec→com.google.devtools.build.lib.skyframe.serialization.LeafSerializationContextcom.google.devtools.build.lib.analysis.config.DeserializationBuilder→com.google.devtools.build.lib.skyframe.serialization.DeferredValuecom.google.devtools.build.lib.analysis.config.OptionsDiffCodec→com.google.devtools.build.lib.skyframe.serialization.AsyncDeserializationContextcom.google.devtools.build.lib.analysis.config.OptionsDiffCodec→com.google.devtools.build.lib.skyframe.serialization.DeferredObjectCodeccom.google.devtools.build.lib.analysis.config.OptionsDiffCodec→com.google.devtools.build.lib.skyframe.serialization.DeferredValuecom.google.devtools.build.lib.analysis.config.OptionsDiffCodec→com.google.devtools.build.lib.skyframe.serialization.SerializationContextcom.google.devtools.build.lib.analysis.config.ValueSharingCodec→com.google.devtools.build.lib.skyframe.serialization.AsyncDeserializationContextcom.google.devtools.build.lib.analysis.config.ValueSharingCodec→com.google.devtools.build.lib.skyframe.serialization.DeferredObjectCodeccom.google.devtools.build.lib.analysis.config.ValueSharingCodec→com.google.devtools.build.lib.skyframe.serialization.SerializationContext
- Direction
- com.google.devtools.build.lib.analysis.config uses com.google.devtools.build.lib.skyframe.serialization, so a change to com.google.devtools.build.lib.skyframe.serialization can break com.google.devtools.build.lib.analysis.config, while a change to com.google.devtools.build.lib.analysis.config can't break com.google.devtools.build.lib.skyframe.serialization.
- Position
- Below the diagonal: com.google.devtools.build.lib.analysis.config uses a module listed above it, which is the healthy direction.
33→31 com.google.devtools.build.lib.analysis.config uses com.google.devtools.build.lib.cmdline✕
- Connections
- 35 pairs of types, where a type in com.google.devtools.build.lib.analysis.config uses a type in com.google.devtools.build.lib.cmdline. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.google.devtools.build.lib.analysis.config.AccumulateResults→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.analysis.config.AnalysisTestTransition→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.analysis.config.AnalysisTestTransition→com.google.devtools.build.lib.cmdline.RepositoryMappingcom.google.devtools.build.lib.analysis.config.BuildConfigurationValue→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.analysis.config.BuildOptionDetails→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.analysis.config.BuildOptions→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.analysis.config.Builder→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.analysis.config.ConfigConditions→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.analysis.config.ConfigMatchingProvider→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.analysis.config.CoreOptionConverters→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.analysis.config.CoreOptions→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.analysis.config.DeserializationBuilder→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.analysis.config.Diff→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.analysis.config.EmptyToNullLabelConverter→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.analysis.config.ExecTransition→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.analysis.config.ExecTransition→com.google.devtools.build.lib.cmdline.RepositoryMappingcom.google.devtools.build.lib.analysis.config.ExecTransitionFinalizer→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.analysis.config.ExecutionTransitionFactory→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.analysis.config.FlagAliasConverter→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.analysis.config.LabelConverter→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.analysis.config.LabelListConverter→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.analysis.config.LabelMapConverter→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.analysis.config.LabelOrderedSetConverter→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.analysis.config.LabelRunUnder→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.analysis.config.LabelToStringEntryConverter→com.google.devtools.build.lib.cmdline.Label
- Direction
- com.google.devtools.build.lib.analysis.config uses com.google.devtools.build.lib.cmdline, so a change to com.google.devtools.build.lib.cmdline can break com.google.devtools.build.lib.analysis.config, while a change to com.google.devtools.build.lib.analysis.config can't break com.google.devtools.build.lib.cmdline.
- Position
- Below the diagonal: com.google.devtools.build.lib.analysis.config uses a module listed above it, which is the healthy direction.
33→32 com.google.devtools.build.lib.analysis.config uses com.google.devtools.build.lib.analysis.platform✕
- Connections
- 1 pair of types, where a type in com.google.devtools.build.lib.analysis.config uses a type in com.google.devtools.build.lib.analysis.platform.
- The types involved
com.google.devtools.build.lib.analysis.config.ConfigConditions→com.google.devtools.build.lib.analysis.platform.PlatformInfo
- Direction
- com.google.devtools.build.lib.analysis.config uses com.google.devtools.build.lib.analysis.platform, so a change to com.google.devtools.build.lib.analysis.platform can break com.google.devtools.build.lib.analysis.config, while a change to com.google.devtools.build.lib.analysis.config can't break com.google.devtools.build.lib.analysis.platform.
- Position
- Below the diagonal: com.google.devtools.build.lib.analysis.config uses a module listed above it, which is the healthy direction.
33→35 com.google.devtools.build.lib.analysis.config uses com.google.devtools.build.lib.analysis part of a loop✕
- Connections
- 7 pairs of types, where a type in com.google.devtools.build.lib.analysis.config uses a type in com.google.devtools.build.lib.analysis.
- The types involved
com.google.devtools.build.lib.analysis.config.BuildConfigurationValue→com.google.devtools.build.lib.analysis.BlazeDirectoriescom.google.devtools.build.lib.analysis.config.ConfigMatchingProvider→com.google.devtools.build.lib.analysis.TransitiveInfoProvidercom.google.devtools.build.lib.analysis.config.DependencyEvaluationException→com.google.devtools.build.lib.analysis.InconsistentAspectOrderExceptioncom.google.devtools.build.lib.analysis.config.OutputDirectories→com.google.devtools.build.lib.analysis.BlazeDirectoriescom.google.devtools.build.lib.analysis.config.OutputDirectories→com.google.devtools.build.lib.analysis.PlatformOptionscom.google.devtools.build.lib.analysis.config.OutputDirectory→com.google.devtools.build.lib.analysis.BlazeDirectoriescom.google.devtools.build.lib.analysis.config.OutputPathMnemonicComputer→com.google.devtools.build.lib.analysis.PlatformOptions
- Direction
- com.google.devtools.build.lib.analysis.config uses com.google.devtools.build.lib.analysis, so a change to com.google.devtools.build.lib.analysis can break com.google.devtools.build.lib.analysis.config, while a change to com.google.devtools.build.lib.analysis.config can't break com.google.devtools.build.lib.analysis.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
33→37 com.google.devtools.build.lib.analysis.config uses com.google.devtools.build.lib.actions part of a loop✕
- Connections
- 12 pairs of types, where a type in com.google.devtools.build.lib.analysis.config uses a type in com.google.devtools.build.lib.actions.
- The types involved
com.google.devtools.build.lib.analysis.config.AutoBuildConfigurationInfo→com.google.devtools.build.lib.actions.BuildConfigurationEventcom.google.devtools.build.lib.analysis.config.AutoBuildConfigurationInfo→com.google.devtools.build.lib.actions.CommandLineLimitscom.google.devtools.build.lib.analysis.config.BuildConfigurationInfo→com.google.devtools.build.lib.actions.BuildConfigurationEventcom.google.devtools.build.lib.analysis.config.BuildConfigurationInfo→com.google.devtools.build.lib.actions.CommandLineLimitscom.google.devtools.build.lib.analysis.config.BuildConfigurationValue→com.google.devtools.build.lib.actions.ActionEnvironmentcom.google.devtools.build.lib.analysis.config.BuildConfigurationValue→com.google.devtools.build.lib.actions.ArtifactRootcom.google.devtools.build.lib.analysis.config.BuildConfigurationValue→com.google.devtools.build.lib.actions.BuildConfigurationEventcom.google.devtools.build.lib.analysis.config.BuildConfigurationValue→com.google.devtools.build.lib.actions.CommandLineLimitscom.google.devtools.build.lib.analysis.config.GlobalStateProvider→com.google.devtools.build.lib.actions.ActionEnvironmentcom.google.devtools.build.lib.analysis.config.OutputDirectories→com.google.devtools.build.lib.actions.ArtifactRootcom.google.devtools.build.lib.analysis.config.OutputDirectory→com.google.devtools.build.lib.actions.ArtifactRootcom.google.devtools.build.lib.analysis.config.PerLabelOptions→com.google.devtools.build.lib.actions.Artifact
- Direction
- com.google.devtools.build.lib.analysis.config uses com.google.devtools.build.lib.actions, so a change to com.google.devtools.build.lib.actions can break com.google.devtools.build.lib.analysis.config, while a change to com.google.devtools.build.lib.analysis.config can't break com.google.devtools.build.lib.actions.
- 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.
34→2 com.google.devtools.build.lib.analysis.actions uses com.google.devtools.build.lib.events✕
- Connections
- 3 pairs of types, where a type in com.google.devtools.build.lib.analysis.actions uses a type in com.google.devtools.build.lib.events.
- The types involved
com.google.devtools.build.lib.analysis.actions.FileContentsProvider→com.google.devtools.build.lib.events.EventHandlercom.google.devtools.build.lib.analysis.actions.FileWriteAction→com.google.devtools.build.lib.events.EventHandlercom.google.devtools.build.lib.analysis.actions.SpawnActionTemplate→com.google.devtools.build.lib.events.EventHandler
- Direction
- com.google.devtools.build.lib.analysis.actions uses com.google.devtools.build.lib.events, so a change to com.google.devtools.build.lib.events can break com.google.devtools.build.lib.analysis.actions, while a change to com.google.devtools.build.lib.analysis.actions can't break com.google.devtools.build.lib.events.
- Position
- Below the diagonal: com.google.devtools.build.lib.analysis.actions uses a module listed above it, which is the healthy direction.
34→4 com.google.devtools.build.lib.analysis.actions uses net.starlark.java.eval✕
- Connections
- 6 pairs of types, where a type in com.google.devtools.build.lib.analysis.actions uses a type in net.starlark.java.eval.
- The types involved
com.google.devtools.build.lib.analysis.actions.BuildInfoFileWriteAction→net.starlark.java.eval.StarlarkFunctioncom.google.devtools.build.lib.analysis.actions.BuildInfoFileWriteAction→net.starlark.java.eval.StarlarkSemanticscom.google.devtools.build.lib.analysis.actions.LazyWriteNestedSetOfTupleAction→net.starlark.java.eval.Tuplecom.google.devtools.build.lib.analysis.actions.SpawnAction→net.starlark.java.eval.Sequencecom.google.devtools.build.lib.analysis.actions.TemplateExpansionAction→net.starlark.java.eval.Dictcom.google.devtools.build.lib.analysis.actions.TemplateExpansionException→net.starlark.java.eval.EvalException
- Direction
- com.google.devtools.build.lib.analysis.actions uses net.starlark.java.eval, so a change to net.starlark.java.eval can break com.google.devtools.build.lib.analysis.actions, while a change to com.google.devtools.build.lib.analysis.actions can't break net.starlark.java.eval.
- Position
- Below the diagonal: com.google.devtools.build.lib.analysis.actions uses a module listed above it, which is the healthy direction.
34→8 com.google.devtools.build.lib.analysis.actions uses com.google.devtools.build.lib.vfs✕
- Connections
- 7 pairs of types, where a type in com.google.devtools.build.lib.analysis.actions uses a type in com.google.devtools.build.lib.vfs.
- The types involved
com.google.devtools.build.lib.analysis.actions.ActionConstructionContext→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.analysis.actions.OutputPathMapper→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.analysis.actions.ShellCommand→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.analysis.actions.StrippingPathMapper→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.analysis.actions.SymlinkAction→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.analysis.actions.SymlinkAction→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.analysis.actions.SymlinkAction→com.google.devtools.build.lib.vfs.SymlinkTargetType
- Direction
- com.google.devtools.build.lib.analysis.actions uses com.google.devtools.build.lib.vfs, so a change to com.google.devtools.build.lib.vfs can break com.google.devtools.build.lib.analysis.actions, while a change to com.google.devtools.build.lib.analysis.actions can't break com.google.devtools.build.lib.vfs.
- Position
- Below the diagonal: com.google.devtools.build.lib.analysis.actions uses a module listed above it, which is the healthy direction.
34→11 com.google.devtools.build.lib.analysis.actions uses com.google.devtools.build.lib.util✕
- Connections
- 33 pairs of types, where a type in com.google.devtools.build.lib.analysis.actions uses a type in com.google.devtools.build.lib.util. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.google.devtools.build.lib.analysis.actions.1→com.google.devtools.build.lib.util.OnDemandStringcom.google.devtools.build.lib.analysis.actions.2→com.google.devtools.build.lib.util.OnDemandStringcom.google.devtools.build.lib.analysis.actions.3→com.google.devtools.build.lib.util.OnDemandStringcom.google.devtools.build.lib.analysis.actions.AbstractFileWriteAction→com.google.devtools.build.lib.util.DeterministicWritercom.google.devtools.build.lib.analysis.actions.ArgvFragment→com.google.devtools.build.lib.util.Fingerprintcom.google.devtools.build.lib.analysis.actions.BinaryFileWriteAction→com.google.devtools.build.lib.util.DeterministicWritercom.google.devtools.build.lib.analysis.actions.BinaryFileWriteAction→com.google.devtools.build.lib.util.Fingerprintcom.google.devtools.build.lib.analysis.actions.BuildInfoFileWriteAction→com.google.devtools.build.lib.util.Fingerprintcom.google.devtools.build.lib.analysis.actions.CompressedFileWriteAction→com.google.devtools.build.lib.util.DeterministicWritercom.google.devtools.build.lib.analysis.actions.CompressedFileWriteAction→com.google.devtools.build.lib.util.Fingerprintcom.google.devtools.build.lib.analysis.actions.CustomCommandLine→com.google.devtools.build.lib.util.Fingerprintcom.google.devtools.build.lib.analysis.actions.ExpandedTreeArtifactArg→com.google.devtools.build.lib.util.Fingerprintcom.google.devtools.build.lib.analysis.actions.FileWriteActionContext→com.google.devtools.build.lib.util.DeterministicWritercom.google.devtools.build.lib.analysis.actions.FormatArg→com.google.devtools.build.lib.util.Fingerprintcom.google.devtools.build.lib.analysis.actions.LazyWriteNestedSetOfTupleAction→com.google.devtools.build.lib.util.DeterministicWritercom.google.devtools.build.lib.analysis.actions.LazyWriteNestedSetOfTupleAction→com.google.devtools.build.lib.util.Fingerprintcom.google.devtools.build.lib.analysis.actions.LazyWritePathsFileAction→com.google.devtools.build.lib.util.DeterministicWritercom.google.devtools.build.lib.analysis.actions.LazyWritePathsFileAction→com.google.devtools.build.lib.util.Fingerprintcom.google.devtools.build.lib.analysis.actions.ParamFileWriter→com.google.devtools.build.lib.util.DeterministicWritercom.google.devtools.build.lib.analysis.actions.ParameterFileWriteAction→com.google.devtools.build.lib.util.DeterministicWritercom.google.devtools.build.lib.analysis.actions.ParameterFileWriteAction→com.google.devtools.build.lib.util.Fingerprintcom.google.devtools.build.lib.analysis.actions.PathMappers→com.google.devtools.build.lib.util.Fingerprintcom.google.devtools.build.lib.analysis.actions.PrefixArg→com.google.devtools.build.lib.util.Fingerprintcom.google.devtools.build.lib.analysis.actions.RegularFileWriteAction→com.google.devtools.build.lib.util.DeterministicWritercom.google.devtools.build.lib.analysis.actions.RegularFileWriteAction→com.google.devtools.build.lib.util.Fingerprint
- Direction
- com.google.devtools.build.lib.analysis.actions uses com.google.devtools.build.lib.util, so a change to com.google.devtools.build.lib.util can break com.google.devtools.build.lib.analysis.actions, while a change to com.google.devtools.build.lib.analysis.actions can't break com.google.devtools.build.lib.util.
- Position
- Below the diagonal: com.google.devtools.build.lib.analysis.actions uses a module listed above it, which is the healthy direction.
34→25 com.google.devtools.build.lib.analysis.actions uses com.google.devtools.build.lib.packages✕
- Connections
- 1 pair of types, where a type in com.google.devtools.build.lib.analysis.actions uses a type in com.google.devtools.build.lib.packages.
- The types involved
com.google.devtools.build.lib.analysis.actions.ActionConstructionContext→com.google.devtools.build.lib.packages.ImplicitOutputsFunction
- Direction
- com.google.devtools.build.lib.analysis.actions uses com.google.devtools.build.lib.packages, so a change to com.google.devtools.build.lib.packages can break com.google.devtools.build.lib.analysis.actions, while a change to com.google.devtools.build.lib.analysis.actions can't break com.google.devtools.build.lib.packages.
- Position
- Below the diagonal: com.google.devtools.build.lib.analysis.actions uses a module listed above it, which is the healthy direction.
34→30 com.google.devtools.build.lib.analysis.actions uses com.google.devtools.build.lib.collect.nestedset✕
- Connections
- 18 pairs of types, where a type in com.google.devtools.build.lib.analysis.actions uses a type in com.google.devtools.build.lib.collect.nestedset.
- The types involved
com.google.devtools.build.lib.analysis.actions.AbstractFileWriteAction→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.analysis.actions.ActionSpawn→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.analysis.actions.CompressedFileWriteAction→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.analysis.actions.EnhancedStarlarkAction→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.analysis.actions.ExpandedSpawnAction→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.analysis.actions.FileWriteAction→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.analysis.actions.LazyWriteNestedSetOfTupleAction→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.analysis.actions.LazyWritePathsFileAction→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.analysis.actions.ParameterFileWriteAction→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.analysis.actions.PathMappers→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.analysis.actions.RegularFileWriteAction→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.analysis.actions.SimpleVectorArg→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.analysis.actions.SpawnAction→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.analysis.actions.SpawnActionTemplate→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.analysis.actions.StarlarkAction→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.analysis.actions.SymlinkTreeAction→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.analysis.actions.TemplateExpansionAction→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.analysis.actions.VectorArg→com.google.devtools.build.lib.collect.nestedset.NestedSet
- Direction
- com.google.devtools.build.lib.analysis.actions uses com.google.devtools.build.lib.collect.nestedset, so a change to com.google.devtools.build.lib.collect.nestedset can break com.google.devtools.build.lib.analysis.actions, while a change to com.google.devtools.build.lib.analysis.actions can't break com.google.devtools.build.lib.collect.nestedset.
- Position
- Below the diagonal: com.google.devtools.build.lib.analysis.actions uses a module listed above it, which is the healthy direction.
34→31 com.google.devtools.build.lib.analysis.actions uses com.google.devtools.build.lib.cmdline✕
- Connections
- 1 pair of types, where a type in com.google.devtools.build.lib.analysis.actions uses a type in com.google.devtools.build.lib.cmdline.
- The types involved
com.google.devtools.build.lib.analysis.actions.PrefixArg→com.google.devtools.build.lib.cmdline.RepositoryMapping
- Direction
- com.google.devtools.build.lib.analysis.actions uses com.google.devtools.build.lib.cmdline, so a change to com.google.devtools.build.lib.cmdline can break com.google.devtools.build.lib.analysis.actions, while a change to com.google.devtools.build.lib.analysis.actions can't break com.google.devtools.build.lib.cmdline.
- Position
- Below the diagonal: com.google.devtools.build.lib.analysis.actions uses a module listed above it, which is the healthy direction.
34→32 com.google.devtools.build.lib.analysis.actions uses com.google.devtools.build.lib.analysis.platform✕
- Connections
- 2 pairs of types, where a type in com.google.devtools.build.lib.analysis.actions uses a type in com.google.devtools.build.lib.analysis.platform.
- The types involved
com.google.devtools.build.lib.analysis.actions.ActionConstructionContext→com.google.devtools.build.lib.analysis.platform.PlatformInfocom.google.devtools.build.lib.analysis.actions.SymlinkAction→com.google.devtools.build.lib.analysis.platform.PlatformInfo
- Direction
- com.google.devtools.build.lib.analysis.actions uses com.google.devtools.build.lib.analysis.platform, so a change to com.google.devtools.build.lib.analysis.platform can break com.google.devtools.build.lib.analysis.actions, while a change to com.google.devtools.build.lib.analysis.actions can't break com.google.devtools.build.lib.analysis.platform.
- Position
- Below the diagonal: com.google.devtools.build.lib.analysis.actions uses a module listed above it, which is the healthy direction.
34→33 com.google.devtools.build.lib.analysis.actions uses com.google.devtools.build.lib.analysis.config✕
- Connections
- 6 pairs of types, where a type in com.google.devtools.build.lib.analysis.actions uses a type in com.google.devtools.build.lib.analysis.config.
- The types involved
com.google.devtools.build.lib.analysis.actions.ActionConstructionContext→com.google.devtools.build.lib.analysis.config.BuildConfigurationValuecom.google.devtools.build.lib.analysis.actions.CustomCommandLine→com.google.devtools.build.lib.analysis.config.OutputPathsModecom.google.devtools.build.lib.analysis.actions.ParameterFileWriteAction→com.google.devtools.build.lib.analysis.config.OutputPathsModecom.google.devtools.build.lib.analysis.actions.PathMappers→com.google.devtools.build.lib.analysis.config.BuildConfigurationValuecom.google.devtools.build.lib.analysis.actions.SpawnAction→com.google.devtools.build.lib.analysis.config.BuildConfigurationValuecom.google.devtools.build.lib.analysis.actions.SymlinkTreeAction→com.google.devtools.build.lib.analysis.config.BuildConfigurationValue
- Direction
- com.google.devtools.build.lib.analysis.actions uses com.google.devtools.build.lib.analysis.config, so a change to com.google.devtools.build.lib.analysis.config can break com.google.devtools.build.lib.analysis.actions, while a change to com.google.devtools.build.lib.analysis.actions can't break com.google.devtools.build.lib.analysis.config.
- Position
- Below the diagonal: com.google.devtools.build.lib.analysis.actions uses a module listed above it, which is the healthy direction.
34→35 com.google.devtools.build.lib.analysis.actions uses com.google.devtools.build.lib.analysis part of a loop✕
- Connections
- 3 pairs of types, where a type in com.google.devtools.build.lib.analysis.actions uses a type in com.google.devtools.build.lib.analysis.
- The types involved
com.google.devtools.build.lib.analysis.actions.ActionConstructionContext→com.google.devtools.build.lib.analysis.AnalysisEnvironmentcom.google.devtools.build.lib.analysis.actions.ActionConstructionContext→com.google.devtools.build.lib.analysis.RuleErrorConsumercom.google.devtools.build.lib.analysis.actions.SymlinkTreeAction→com.google.devtools.build.lib.analysis.Runfiles
- Direction
- com.google.devtools.build.lib.analysis.actions uses com.google.devtools.build.lib.analysis, so a change to com.google.devtools.build.lib.analysis can break com.google.devtools.build.lib.analysis.actions, while a change to com.google.devtools.build.lib.analysis.actions can't break com.google.devtools.build.lib.analysis.
- 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.
34→37 com.google.devtools.build.lib.analysis.actions uses com.google.devtools.build.lib.actions part of a loop✕
- Connections
- 190 pairs of types, where a type in com.google.devtools.build.lib.analysis.actions uses a type in com.google.devtools.build.lib.actions. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.google.devtools.build.lib.analysis.actions.AbstractFileWriteAction→com.google.devtools.build.lib.actions.AbstractActioncom.google.devtools.build.lib.analysis.actions.AbstractFileWriteAction→com.google.devtools.build.lib.actions.ActionExecutionContextcom.google.devtools.build.lib.analysis.actions.AbstractFileWriteAction→com.google.devtools.build.lib.actions.ActionOwnercom.google.devtools.build.lib.analysis.actions.AbstractFileWriteAction→com.google.devtools.build.lib.actions.ActionResultcom.google.devtools.build.lib.analysis.actions.AbstractFileWriteAction→com.google.devtools.build.lib.actions.Artifactcom.google.devtools.build.lib.analysis.actions.ActionConstructionContext→com.google.devtools.build.lib.actions.ActionKeyContextcom.google.devtools.build.lib.analysis.actions.ActionConstructionContext→com.google.devtools.build.lib.actions.ActionOwnercom.google.devtools.build.lib.analysis.actions.ActionConstructionContext→com.google.devtools.build.lib.actions.ActionRegistrycom.google.devtools.build.lib.analysis.actions.ActionConstructionContext→com.google.devtools.build.lib.actions.Artifactcom.google.devtools.build.lib.analysis.actions.ActionConstructionContext→com.google.devtools.build.lib.actions.ArtifactRootcom.google.devtools.build.lib.analysis.actions.ActionSpawn→com.google.devtools.build.lib.actions.ActionInputcom.google.devtools.build.lib.analysis.actions.ActionSpawn→com.google.devtools.build.lib.actions.Artifactcom.google.devtools.build.lib.analysis.actions.ActionSpawn→com.google.devtools.build.lib.actions.BaseSpawncom.google.devtools.build.lib.analysis.actions.ActionSpawn→com.google.devtools.build.lib.actions.PathMappercom.google.devtools.build.lib.analysis.actions.ActionSpawn→com.google.devtools.build.lib.actions.SpawnInputscom.google.devtools.build.lib.analysis.actions.ArgvFragment→com.google.devtools.build.lib.actions.ActionKeyContextcom.google.devtools.build.lib.analysis.actions.ArgvFragment→com.google.devtools.build.lib.actions.PathMappercom.google.devtools.build.lib.analysis.actions.ArtifactTemplate→com.google.devtools.build.lib.actions.Artifactcom.google.devtools.build.lib.analysis.actions.ArtifactTemplate→com.google.devtools.build.lib.actions.ArtifactPathResolvercom.google.devtools.build.lib.analysis.actions.BinaryFileWriteAction→com.google.devtools.build.lib.actions.ActionExecutionContextcom.google.devtools.build.lib.analysis.actions.BinaryFileWriteAction→com.google.devtools.build.lib.actions.ActionKeyContextcom.google.devtools.build.lib.analysis.actions.BinaryFileWriteAction→com.google.devtools.build.lib.actions.ActionOwnercom.google.devtools.build.lib.analysis.actions.BinaryFileWriteAction→com.google.devtools.build.lib.actions.Artifactcom.google.devtools.build.lib.analysis.actions.BinaryFileWriteAction→com.google.devtools.build.lib.actions.InputMetadataProvidercom.google.devtools.build.lib.analysis.actions.BuildInfoFileWriteAction→com.google.devtools.build.lib.actions.AbstractAction
- Direction
- com.google.devtools.build.lib.analysis.actions uses com.google.devtools.build.lib.actions, so a change to com.google.devtools.build.lib.actions can break com.google.devtools.build.lib.analysis.actions, while a change to com.google.devtools.build.lib.analysis.actions can't break com.google.devtools.build.lib.actions.
- 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 com.google.devtools.build.lib.analysis uses net.starlark.java.syntax✕
- Connections
- 8 pairs of types, where a type in com.google.devtools.build.lib.analysis uses a type in net.starlark.java.syntax.
- The types involved
com.google.devtools.build.lib.analysis.AspectResolutionHelpers→net.starlark.java.syntax.Locationcom.google.devtools.build.lib.analysis.DefaultDefaultInfo→net.starlark.java.syntax.Locationcom.google.devtools.build.lib.analysis.DefaultInfo→net.starlark.java.syntax.Locationcom.google.devtools.build.lib.analysis.ErrorReporter→net.starlark.java.syntax.Locationcom.google.devtools.build.lib.analysis.EventHandlingErrorReporter→net.starlark.java.syntax.Locationcom.google.devtools.build.lib.analysis.Failure→net.starlark.java.syntax.Locationcom.google.devtools.build.lib.analysis.InconsistentAspectOrderException→net.starlark.java.syntax.Locationcom.google.devtools.build.lib.analysis.LabelAndLocation→net.starlark.java.syntax.Location
- Direction
- com.google.devtools.build.lib.analysis uses net.starlark.java.syntax, so a change to net.starlark.java.syntax can break com.google.devtools.build.lib.analysis, while a change to com.google.devtools.build.lib.analysis can't break net.starlark.java.syntax.
- Position
- Below the diagonal: com.google.devtools.build.lib.analysis uses a module listed above it, which is the healthy direction.
35→2 com.google.devtools.build.lib.analysis uses com.google.devtools.build.lib.events✕
- Connections
- 11 pairs of types, where a type in com.google.devtools.build.lib.analysis uses a type in com.google.devtools.build.lib.events.
- The types involved
com.google.devtools.build.lib.analysis.AnalysisEnvironment→com.google.devtools.build.lib.events.ExtendedEventHandlercom.google.devtools.build.lib.analysis.AspectResolutionHelpers→com.google.devtools.build.lib.events.ExtendedEventHandlercom.google.devtools.build.lib.analysis.BuildInfoEvent→com.google.devtools.build.lib.events.Postablecom.google.devtools.build.lib.analysis.BuildView→com.google.devtools.build.lib.events.EventHandlercom.google.devtools.build.lib.analysis.BuildView→com.google.devtools.build.lib.events.ExtendedEventHandlercom.google.devtools.build.lib.analysis.CachingAnalysisEnvironment→com.google.devtools.build.lib.events.ExtendedEventHandlercom.google.devtools.build.lib.analysis.ConfiguredTargetFactory→com.google.devtools.build.lib.events.EventHandlercom.google.devtools.build.lib.analysis.PlatformConfiguration→com.google.devtools.build.lib.events.EventHandlercom.google.devtools.build.lib.analysis.Project→com.google.devtools.build.lib.events.ExtendedEventHandlercom.google.devtools.build.lib.analysis.RepoMappingManifestAction→com.google.devtools.build.lib.events.EventHandlercom.google.devtools.build.lib.analysis.SourceManifestAction→com.google.devtools.build.lib.events.EventHandler
- Direction
- com.google.devtools.build.lib.analysis uses com.google.devtools.build.lib.events, so a change to com.google.devtools.build.lib.events can break com.google.devtools.build.lib.analysis, while a change to com.google.devtools.build.lib.analysis can't break com.google.devtools.build.lib.events.
- Position
- Below the diagonal: com.google.devtools.build.lib.analysis uses a module listed above it, which is the healthy direction.
35→3 com.google.devtools.build.lib.analysis uses com.google.devtools.common.options✕
- Connections
- 6 pairs of types, where a type in com.google.devtools.build.lib.analysis uses a type in com.google.devtools.common.options.
- The types involved
com.google.devtools.build.lib.analysis.AnalysisOptions→com.google.devtools.common.options.OptionsBasecom.google.devtools.build.lib.analysis.ConfiguredRuleClassProvider→com.google.devtools.common.options.OptionDefinitioncom.google.devtools.build.lib.analysis.OneLineStringConverter→com.google.devtools.common.options.Contextlesscom.google.devtools.build.lib.analysis.Options→com.google.devtools.common.options.OptionsBasecom.google.devtools.build.lib.analysis.OptionsDiffPredicate→com.google.devtools.common.options.OptionDefinitioncom.google.devtools.build.lib.analysis.PlatformMappingKeyConverter→com.google.devtools.common.options.Converter
- Direction
- com.google.devtools.build.lib.analysis uses com.google.devtools.common.options, so a change to com.google.devtools.common.options can break com.google.devtools.build.lib.analysis, while a change to com.google.devtools.build.lib.analysis can't break com.google.devtools.common.options.
- Position
- Below the diagonal: com.google.devtools.build.lib.analysis uses a module listed above it, which is the healthy direction.
35→4 com.google.devtools.build.lib.analysis uses net.starlark.java.eval✕
- Connections
- 38 pairs of types, where a type in com.google.devtools.build.lib.analysis uses a type in net.starlark.java.eval. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.google.devtools.build.lib.analysis.AnalysisEnvironment→net.starlark.java.eval.StarlarkSemanticscom.google.devtools.build.lib.analysis.BazelRuleAnalysisThreadContext→net.starlark.java.eval.StarlarkThreadcom.google.devtools.build.lib.analysis.CachingAnalysisEnvironment→net.starlark.java.eval.StarlarkSemanticscom.google.devtools.build.lib.analysis.ConfigurationMakeVariableContext→net.starlark.java.eval.Buildercom.google.devtools.build.lib.analysis.ConfiguredTarget→net.starlark.java.eval.Dictcom.google.devtools.build.lib.analysis.ConfiguredTarget→net.starlark.java.eval.Structurecom.google.devtools.build.lib.analysis.DefaultInfoProvider→net.starlark.java.eval.StarlarkThreadcom.google.devtools.build.lib.analysis.DormantDependency→net.starlark.java.eval.Printercom.google.devtools.build.lib.analysis.DormantDependency→net.starlark.java.eval.StarlarkSemanticscom.google.devtools.build.lib.analysis.DormantDependency→net.starlark.java.eval.StarlarkValuecom.google.devtools.build.lib.analysis.FileProvider→net.starlark.java.eval.Printercom.google.devtools.build.lib.analysis.FileProvider→net.starlark.java.eval.StarlarkThreadcom.google.devtools.build.lib.analysis.FilesToRunProvider→net.starlark.java.eval.Printercom.google.devtools.build.lib.analysis.FilesToRunProvider→net.starlark.java.eval.StarlarkThreadcom.google.devtools.build.lib.analysis.MaterializedDepsInfo→net.starlark.java.eval.Sequencecom.google.devtools.build.lib.analysis.MaterializedDepsInfo→net.starlark.java.eval.StarlarkValuecom.google.devtools.build.lib.analysis.OutputGroupInfo→net.starlark.java.eval.StarlarkIndexablecom.google.devtools.build.lib.analysis.OutputGroupInfo→net.starlark.java.eval.StarlarkIterablecom.google.devtools.build.lib.analysis.OutputGroupInfo→net.starlark.java.eval.StarlarkSemanticscom.google.devtools.build.lib.analysis.OutputGroupInfoProvider→net.starlark.java.eval.Dictcom.google.devtools.build.lib.analysis.Provider→net.starlark.java.eval.Dictcom.google.devtools.build.lib.analysis.ResolvedToolchainData→net.starlark.java.eval.StarlarkValuecom.google.devtools.build.lib.analysis.RuleContext→net.starlark.java.eval.Mutabilitycom.google.devtools.build.lib.analysis.RuleContext→net.starlark.java.eval.StarlarkThreadcom.google.devtools.build.lib.analysis.RuleContext→net.starlark.java.eval.SymbolGenerator
- Direction
- com.google.devtools.build.lib.analysis uses net.starlark.java.eval, so a change to net.starlark.java.eval can break com.google.devtools.build.lib.analysis, while a change to com.google.devtools.build.lib.analysis can't break net.starlark.java.eval.
- Position
- Below the diagonal: com.google.devtools.build.lib.analysis uses a module listed above it, which is the healthy direction.
35→6 com.google.devtools.build.lib.analysis uses com.google.devtools.build.skyframe✕
- Connections
- 5 pairs of types, where a type in com.google.devtools.build.lib.analysis uses a type in com.google.devtools.build.skyframe.
- The types involved
com.google.devtools.build.lib.analysis.AnalysisOperationWatcher→com.google.devtools.build.skyframe.SkyKeycom.google.devtools.build.lib.analysis.AspectCompleteEvent→com.google.devtools.build.skyframe.SkyValuecom.google.devtools.build.lib.analysis.CachingAnalysisEnvironment→com.google.devtools.build.skyframe.Environmentcom.google.devtools.build.lib.analysis.ConfiguredObjectValue→com.google.devtools.build.skyframe.NotComparableSkyValuecom.google.devtools.build.lib.analysis.TargetCompleteEvent→com.google.devtools.build.skyframe.SkyValue
- Direction
- com.google.devtools.build.lib.analysis uses com.google.devtools.build.skyframe, so a change to com.google.devtools.build.skyframe can break com.google.devtools.build.lib.analysis, while a change to com.google.devtools.build.lib.analysis can't break com.google.devtools.build.skyframe.
- Position
- Below the diagonal: com.google.devtools.build.lib.analysis uses a module listed above it, which is the healthy direction.
35→8 com.google.devtools.build.lib.analysis uses com.google.devtools.build.lib.vfs✕
- Connections
- 29 pairs of types, where a type in com.google.devtools.build.lib.analysis uses a type in com.google.devtools.build.lib.vfs. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.google.devtools.build.lib.analysis.AnalysisEnvironment→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.analysis.AnalysisUtils→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.analysis.BashCommandConstructor→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.analysis.BlazeDirectories→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.analysis.BlazeDirectories→com.google.devtools.build.lib.vfs.Rootcom.google.devtools.build.lib.analysis.BundledFileSystem→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.analysis.CachingAnalysisEnvironment→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.analysis.CommandHelper→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.analysis.ConfiguredRuleClassProvider→com.google.devtools.build.lib.vfs.Rootcom.google.devtools.build.lib.analysis.DummyEmptyFilesSupplier→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.analysis.EmptyFilesSupplier→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.analysis.ExecutableTargetData→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.analysis.LocationFunction→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.analysis.ManifestWriter→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.analysis.Options→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.analysis.RuleContext→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.analysis.Runfiles→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.analysis.RunfilesSupport→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.analysis.RunfilesSupport→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.analysis.RunfilesTreeImpl→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.analysis.ServerDirectories→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.analysis.ServerDirectories→com.google.devtools.build.lib.vfs.Rootcom.google.devtools.build.lib.analysis.ShToolchain→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.analysis.ShellConfiguration→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.analysis.SourceManifestAction→com.google.devtools.build.lib.vfs.PathFragment
- Direction
- com.google.devtools.build.lib.analysis uses com.google.devtools.build.lib.vfs, so a change to com.google.devtools.build.lib.vfs can break com.google.devtools.build.lib.analysis, while a change to com.google.devtools.build.lib.analysis can't break com.google.devtools.build.lib.vfs.
- Position
- Below the diagonal: com.google.devtools.build.lib.analysis uses a module listed above it, which is the healthy direction.
35→10 com.google.devtools.build.lib.analysis uses com.google.devtools.build.lib.skyframe.config✕
- Connections
- 3 pairs of types, where a type in com.google.devtools.build.lib.analysis uses a type in com.google.devtools.build.lib.skyframe.config.
- The types involved
com.google.devtools.build.lib.analysis.ConfiguredTarget→com.google.devtools.build.lib.skyframe.config.BuildConfigurationKeycom.google.devtools.build.lib.analysis.PlatformMappingKeyConverter→com.google.devtools.build.lib.skyframe.config.PlatformMappingKeycom.google.devtools.build.lib.analysis.PlatformOptions→com.google.devtools.build.lib.skyframe.config.PlatformMappingKey
- Direction
- com.google.devtools.build.lib.analysis uses com.google.devtools.build.lib.skyframe.config, so a change to com.google.devtools.build.lib.skyframe.config can break com.google.devtools.build.lib.analysis, while a change to com.google.devtools.build.lib.analysis can't break com.google.devtools.build.lib.skyframe.config.
- Position
- Below the diagonal: com.google.devtools.build.lib.analysis uses a module listed above it, which is the healthy direction.
35→11 com.google.devtools.build.lib.analysis uses com.google.devtools.build.lib.util✕
- Connections
- 30 pairs of types, where a type in com.google.devtools.build.lib.analysis uses a type in com.google.devtools.build.lib.util. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.google.devtools.build.lib.analysis.AnalysisAndExecutionResult→com.google.devtools.build.lib.util.DetailedExitCodecom.google.devtools.build.lib.analysis.AnalysisOptions→com.google.devtools.build.lib.util.RegexFiltercom.google.devtools.build.lib.analysis.AspectResolutionHelpers→com.google.devtools.build.lib.util.OrderedSetMultimapcom.google.devtools.build.lib.analysis.BuildView→com.google.devtools.build.lib.util.RegexFiltercom.google.devtools.build.lib.analysis.CommandHelper→com.google.devtools.build.lib.util.OScom.google.devtools.build.lib.analysis.CommandHelper→com.google.devtools.build.lib.util.Paircom.google.devtools.build.lib.analysis.ConfiguredTargetFactory→com.google.devtools.build.lib.util.OrderedSetMultimapcom.google.devtools.build.lib.analysis.DependencyLabels→com.google.devtools.build.lib.util.OrderedSetMultimapcom.google.devtools.build.lib.analysis.DependencyResolutionHelpers→com.google.devtools.build.lib.util.OrderedSetMultimapcom.google.devtools.build.lib.analysis.DummyEmptyFilesSupplier→com.google.devtools.build.lib.util.Fingerprintcom.google.devtools.build.lib.analysis.EmptyFilesSupplier→com.google.devtools.build.lib.util.Fingerprintcom.google.devtools.build.lib.analysis.InvalidExecGroupException→com.google.devtools.build.lib.util.DetailedExitCodecom.google.devtools.build.lib.analysis.MaterializedDepsInfo→com.google.devtools.build.lib.util.Eithercom.google.devtools.build.lib.analysis.NoBuildRequestFinishedEvent→com.google.devtools.build.lib.util.ExitCodecom.google.devtools.build.lib.analysis.PlatformConfiguration→com.google.devtools.build.lib.util.RegexFiltercom.google.devtools.build.lib.analysis.PlatformOptions→com.google.devtools.build.lib.util.RegexFiltercom.google.devtools.build.lib.analysis.PrerequisiteArtifacts→com.google.devtools.build.lib.util.FileTypecom.google.devtools.build.lib.analysis.PrerequisiteArtifacts→com.google.devtools.build.lib.util.FileTypeSetcom.google.devtools.build.lib.analysis.PseudoAction→com.google.devtools.build.lib.util.Fingerprintcom.google.devtools.build.lib.analysis.RepoMappingManifestAction→com.google.devtools.build.lib.util.DeterministicWritercom.google.devtools.build.lib.analysis.RepoMappingManifestAction→com.google.devtools.build.lib.util.Fingerprintcom.google.devtools.build.lib.analysis.RuleContext→com.google.devtools.build.lib.util.OrderedSetMultimapcom.google.devtools.build.lib.analysis.Runfiles→com.google.devtools.build.lib.util.Fingerprintcom.google.devtools.build.lib.analysis.RunfilesTreeImpl→com.google.devtools.build.lib.util.Fingerprintcom.google.devtools.build.lib.analysis.ShellConfiguration→com.google.devtools.build.lib.util.OS
- Direction
- com.google.devtools.build.lib.analysis uses com.google.devtools.build.lib.util, so a change to com.google.devtools.build.lib.util can break com.google.devtools.build.lib.analysis, while a change to com.google.devtools.build.lib.analysis can't break com.google.devtools.build.lib.util.
- Position
- Below the diagonal: com.google.devtools.build.lib.analysis uses a module listed above it, which is the healthy direction.
35→14 com.google.devtools.build.lib.analysis uses com.google.devtools.build.lib.buildeventstream✕
- Connections
- 22 pairs of types, where a type in com.google.devtools.build.lib.analysis uses a type in com.google.devtools.build.lib.buildeventstream.
- The types involved
com.google.devtools.build.lib.analysis.AnalysisFailureEvent→com.google.devtools.build.lib.buildeventstream.BuildEventcom.google.devtools.build.lib.analysis.AnalysisFailureEvent→com.google.devtools.build.lib.buildeventstream.BuildEventContextcom.google.devtools.build.lib.analysis.AnalysisRootCauseEvent→com.google.devtools.build.lib.buildeventstream.BuildEventcom.google.devtools.build.lib.analysis.AnalysisRootCauseEvent→com.google.devtools.build.lib.buildeventstream.BuildEventContextcom.google.devtools.build.lib.analysis.AnalysisRootCauseEvent→com.google.devtools.build.lib.buildeventstream.BuildEventWithConfigurationcom.google.devtools.build.lib.analysis.AspectCompleteEvent→com.google.devtools.build.lib.buildeventstream.BuildEventContextcom.google.devtools.build.lib.analysis.AspectCompleteEvent→com.google.devtools.build.lib.buildeventstream.BuildEventWithOrderConstraintcom.google.devtools.build.lib.analysis.AspectConfiguredEvent→com.google.devtools.build.lib.buildeventstream.BuildEventcom.google.devtools.build.lib.analysis.AspectConfiguredEvent→com.google.devtools.build.lib.buildeventstream.BuildEventContextcom.google.devtools.build.lib.analysis.AspectConfiguredEvent→com.google.devtools.build.lib.buildeventstream.BuildEventWithConfigurationcom.google.devtools.build.lib.analysis.BuildInfoEvent→com.google.devtools.build.lib.buildeventstream.BuildEventContextcom.google.devtools.build.lib.analysis.BuildInfoEvent→com.google.devtools.build.lib.buildeventstream.BuildEventWithOrderConstraintcom.google.devtools.build.lib.analysis.NoBuildEvent→com.google.devtools.build.lib.buildeventstream.BuildEventcom.google.devtools.build.lib.analysis.NoBuildEvent→com.google.devtools.build.lib.buildeventstream.BuildEventContextcom.google.devtools.build.lib.analysis.NoBuildRequestFinishedEvent→com.google.devtools.build.lib.buildeventstream.BuildCompletingEventcom.google.devtools.build.lib.analysis.TargetCompleteEvent→com.google.devtools.build.lib.buildeventstream.BuildEventcom.google.devtools.build.lib.analysis.TargetCompleteEvent→com.google.devtools.build.lib.buildeventstream.BuildEventContextcom.google.devtools.build.lib.analysis.TargetCompleteEvent→com.google.devtools.build.lib.buildeventstream.BuildEventWithConfigurationcom.google.devtools.build.lib.analysis.TargetCompleteEvent→com.google.devtools.build.lib.buildeventstream.BuildEventWithOrderConstraintcom.google.devtools.build.lib.analysis.TargetConfiguredEvent→com.google.devtools.build.lib.buildeventstream.BuildEventcom.google.devtools.build.lib.analysis.TargetConfiguredEvent→com.google.devtools.build.lib.buildeventstream.BuildEventContextcom.google.devtools.build.lib.analysis.TargetConfiguredEvent→com.google.devtools.build.lib.buildeventstream.BuildEventWithConfiguration
- Direction
- com.google.devtools.build.lib.analysis uses com.google.devtools.build.lib.buildeventstream, so a change to com.google.devtools.build.lib.buildeventstream can break com.google.devtools.build.lib.analysis, while a change to com.google.devtools.build.lib.analysis can't break com.google.devtools.build.lib.buildeventstream.
- Position
- Below the diagonal: com.google.devtools.build.lib.analysis uses a module listed above it, which is the healthy direction.
35→16 com.google.devtools.build.lib.analysis uses com.google.devtools.build.lib.query2.common✕
- Connections
- 2 pairs of types, where a type in com.google.devtools.build.lib.analysis uses a type in com.google.devtools.build.lib.query2.common.
- The types involved
com.google.devtools.build.lib.analysis.ConfiguredTarget→com.google.devtools.build.lib.query2.common.CqueryNodecom.google.devtools.build.lib.analysis.TopLevelArtifactHelper→com.google.devtools.build.lib.query2.common.CqueryNode
- Direction
- com.google.devtools.build.lib.analysis uses com.google.devtools.build.lib.query2.common, so a change to com.google.devtools.build.lib.query2.common can break com.google.devtools.build.lib.analysis, while a change to com.google.devtools.build.lib.analysis can't break com.google.devtools.build.lib.query2.common.
- Position
- Below the diagonal: com.google.devtools.build.lib.analysis uses a module listed above it, which is the healthy direction.
35→19 com.google.devtools.build.lib.analysis uses com.google.devtools.build.lib.skyframe.serialization.analysis✕
- Connections
- 2 pairs of types, where a type in com.google.devtools.build.lib.analysis uses a type in com.google.devtools.build.lib.skyframe.serialization.analysis.
- The types involved
com.google.devtools.build.lib.analysis.BuildView→com.google.devtools.build.lib.skyframe.serialization.analysis.RemoteAnalysisCacheReaderDepsProvidercom.google.devtools.build.lib.analysis.BuildView→com.google.devtools.build.lib.skyframe.serialization.analysis.RemoteAnalysisCachingDependenciesProvider
- Direction
- com.google.devtools.build.lib.analysis uses com.google.devtools.build.lib.skyframe.serialization.analysis, so a change to com.google.devtools.build.lib.skyframe.serialization.analysis can break com.google.devtools.build.lib.analysis, while a change to com.google.devtools.build.lib.analysis can't break com.google.devtools.build.lib.skyframe.serialization.analysis.
- Position
- Below the diagonal: com.google.devtools.build.lib.analysis uses a module listed above it, which is the healthy direction.
35→23 com.google.devtools.build.lib.analysis uses com.google.devtools.build.lib.buildtool✕
- Connections
- 1 pair of types, where a type in com.google.devtools.build.lib.analysis uses a type in com.google.devtools.build.lib.buildtool.
- The types involved
com.google.devtools.build.lib.analysis.BuildView→com.google.devtools.build.lib.buildtool.BuildRequestOptions
- Direction
- com.google.devtools.build.lib.analysis uses com.google.devtools.build.lib.buildtool, so a change to com.google.devtools.build.lib.buildtool can break com.google.devtools.build.lib.analysis, while a change to com.google.devtools.build.lib.analysis can't break com.google.devtools.build.lib.buildtool.
- Position
- Below the diagonal: com.google.devtools.build.lib.analysis uses a module listed above it, which is the healthy direction.
35→24 com.google.devtools.build.lib.analysis uses com.google.devtools.build.lib.skyframe✕
- Connections
- 35 pairs of types, where a type in com.google.devtools.build.lib.analysis uses a type in com.google.devtools.build.lib.skyframe. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.google.devtools.build.lib.analysis.AliasProvider→com.google.devtools.build.lib.skyframe.ConfiguredTargetAndDatacom.google.devtools.build.lib.analysis.AnalysisFailureEvent→com.google.devtools.build.lib.skyframe.ConfiguredTargetKeycom.google.devtools.build.lib.analysis.AspectBaseTargetResolvedToolchainContext→com.google.devtools.build.lib.skyframe.ConfiguredTargetAndDatacom.google.devtools.build.lib.analysis.AspectCollection→com.google.devtools.build.lib.skyframe.ConfiguredTargetKeycom.google.devtools.build.lib.analysis.AspectContext→com.google.devtools.build.lib.skyframe.ConfiguredTargetAndDatacom.google.devtools.build.lib.analysis.BuildView→com.google.devtools.build.lib.skyframe.BuildResultListenercom.google.devtools.build.lib.analysis.BuildView→com.google.devtools.build.lib.skyframe.SkyframeAnalysisResultcom.google.devtools.build.lib.analysis.BuildView→com.google.devtools.build.lib.skyframe.SkyframeBuildViewcom.google.devtools.build.lib.analysis.BuildView→com.google.devtools.build.lib.skyframe.SkyframeExecutorcom.google.devtools.build.lib.analysis.BuildView→com.google.devtools.build.lib.skyframe.TargetPatternPhaseValuecom.google.devtools.build.lib.analysis.CachingAnalysisEnvironment→com.google.devtools.build.lib.skyframe.StarlarkBuiltinsValuecom.google.devtools.build.lib.analysis.CachingAnalysisEnvironment→com.google.devtools.build.lib.skyframe.WorkspaceStatusValuecom.google.devtools.build.lib.analysis.CommonPrerequisiteValidator→com.google.devtools.build.lib.skyframe.ConfiguredTargetAndDatacom.google.devtools.build.lib.analysis.ConfiguredTargetFactory→com.google.devtools.build.lib.skyframe.AspectKeycom.google.devtools.build.lib.analysis.ConfiguredTargetFactory→com.google.devtools.build.lib.skyframe.ConfiguredTargetAndDatacom.google.devtools.build.lib.analysis.ConfiguredTargetFactory→com.google.devtools.build.lib.skyframe.ConfiguredTargetKeycom.google.devtools.build.lib.analysis.ConfiguredTargetFactory→com.google.devtools.build.lib.skyframe.IncrementalArtifactConflictFindercom.google.devtools.build.lib.analysis.ExecutableTargetData→com.google.devtools.build.lib.skyframe.ConfiguredTargetAndDatacom.google.devtools.build.lib.analysis.Factory→com.google.devtools.build.lib.skyframe.WorkspaceInfoFromDiffcom.google.devtools.build.lib.analysis.InvalidExecGroupException→com.google.devtools.build.lib.skyframe.AbstractSaneAnalysisExceptioncom.google.devtools.build.lib.analysis.PackageCollector→com.google.devtools.build.lib.skyframe.ConfiguredTargetKeycom.google.devtools.build.lib.analysis.PrerequisiteValidator→com.google.devtools.build.lib.skyframe.ConfiguredTargetAndDatacom.google.devtools.build.lib.analysis.PrerequisitesCollection→com.google.devtools.build.lib.skyframe.ConfiguredTargetAndDatacom.google.devtools.build.lib.analysis.Project→com.google.devtools.build.lib.skyframe.SkyframeExecutorcom.google.devtools.build.lib.analysis.ResolvedToolchainContext→com.google.devtools.build.lib.skyframe.ConfiguredTargetAndData
- Direction
- com.google.devtools.build.lib.analysis uses com.google.devtools.build.lib.skyframe, so a change to com.google.devtools.build.lib.skyframe can break com.google.devtools.build.lib.analysis, while a change to com.google.devtools.build.lib.analysis can't break com.google.devtools.build.lib.skyframe.
- Position
- Below the diagonal: com.google.devtools.build.lib.analysis uses a module listed above it, which is the healthy direction.
35→25 com.google.devtools.build.lib.analysis uses com.google.devtools.build.lib.packages✕
- Connections
- 154 pairs of types, where a type in com.google.devtools.build.lib.analysis uses a type in com.google.devtools.build.lib.packages. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.google.devtools.build.lib.analysis.1852→com.google.devtools.build.lib.packages.BuiltinProvidercom.google.devtools.build.lib.analysis.3→com.google.devtools.build.lib.packages.AttributeMapcom.google.devtools.build.lib.analysis.3→com.google.devtools.build.lib.packages.ComputedDefaultcom.google.devtools.build.lib.analysis.4→com.google.devtools.build.lib.packages.AttributeMapcom.google.devtools.build.lib.analysis.4→com.google.devtools.build.lib.packages.ComputedDefaultcom.google.devtools.build.lib.analysis.ActionsProvider→com.google.devtools.build.lib.packages.BuiltinProvidercom.google.devtools.build.lib.analysis.ActionsProvider→com.google.devtools.build.lib.packages.StructImplcom.google.devtools.build.lib.analysis.AliasProvider→com.google.devtools.build.lib.packages.Rulecom.google.devtools.build.lib.analysis.AliasProvider→com.google.devtools.build.lib.packages.Targetcom.google.devtools.build.lib.analysis.Allowlist→com.google.devtools.build.lib.packages.Buildercom.google.devtools.build.lib.analysis.AnalysisPhaseStartedEvent→com.google.devtools.build.lib.packages.Targetcom.google.devtools.build.lib.analysis.AnalysisUtils→com.google.devtools.build.lib.packages.BuiltinProvidercom.google.devtools.build.lib.analysis.AnalysisUtils→com.google.devtools.build.lib.packages.StarlarkProviderWrappercom.google.devtools.build.lib.analysis.AnalysisUtils→com.google.devtools.build.lib.packages.TriStatecom.google.devtools.build.lib.analysis.AspectAwareAttributeMapper→com.google.devtools.build.lib.packages.Attributecom.google.devtools.build.lib.analysis.AspectAwareAttributeMapper→com.google.devtools.build.lib.packages.AttributeMapcom.google.devtools.build.lib.analysis.AspectAwareAttributeMapper→com.google.devtools.build.lib.packages.DependencyFiltercom.google.devtools.build.lib.analysis.AspectAwareAttributeMapper→com.google.devtools.build.lib.packages.PackageArgscom.google.devtools.build.lib.analysis.AspectAwareAttributeMapper→com.google.devtools.build.lib.packages.Typecom.google.devtools.build.lib.analysis.AspectCollection→com.google.devtools.build.lib.packages.Aspectcom.google.devtools.build.lib.analysis.AspectCollection→com.google.devtools.build.lib.packages.AspectDescriptorcom.google.devtools.build.lib.analysis.AspectContext→com.google.devtools.build.lib.packages.Aspectcom.google.devtools.build.lib.analysis.AspectContext→com.google.devtools.build.lib.packages.AspectDescriptorcom.google.devtools.build.lib.analysis.AspectContext→com.google.devtools.build.lib.packages.Attributecom.google.devtools.build.lib.analysis.AspectContext→com.google.devtools.build.lib.packages.AttributeMap
- Direction
- com.google.devtools.build.lib.analysis uses com.google.devtools.build.lib.packages, so a change to com.google.devtools.build.lib.packages can break com.google.devtools.build.lib.analysis, while a change to com.google.devtools.build.lib.analysis can't break com.google.devtools.build.lib.packages.
- Position
- Below the diagonal: com.google.devtools.build.lib.analysis uses a module listed above it, which is the healthy direction.
35→26 com.google.devtools.build.lib.analysis uses com.google.devtools.build.lib.analysis.starlark✕
- Connections
- 4 pairs of types, where a type in com.google.devtools.build.lib.analysis uses a type in com.google.devtools.build.lib.analysis.starlark.
- The types involved
com.google.devtools.build.lib.analysis.CommonPrerequisiteValidator→com.google.devtools.build.lib.analysis.starlark.StarlarkSubrulecom.google.devtools.build.lib.analysis.ConfiguredTargetFactory→com.google.devtools.build.lib.analysis.starlark.StarlarkAttributeTransitionProvidercom.google.devtools.build.lib.analysis.RequiredFragmentsUtil→com.google.devtools.build.lib.analysis.starlark.StarlarkAttributeTransitionProvidercom.google.devtools.build.lib.analysis.RuleContext→com.google.devtools.build.lib.analysis.starlark.StarlarkRuleContext
- Direction
- com.google.devtools.build.lib.analysis uses com.google.devtools.build.lib.analysis.starlark, so a change to com.google.devtools.build.lib.analysis.starlark can break com.google.devtools.build.lib.analysis, while a change to com.google.devtools.build.lib.analysis can't break com.google.devtools.build.lib.analysis.starlark.
- Position
- Below the diagonal: com.google.devtools.build.lib.analysis uses a module listed above it, which is the healthy direction.
35→27 com.google.devtools.build.lib.analysis uses com.google.devtools.build.lib.analysis.test✕
- Connections
- 5 pairs of types, where a type in com.google.devtools.build.lib.analysis uses a type in com.google.devtools.build.lib.analysis.test.
- The types involved
com.google.devtools.build.lib.analysis.BaseRuleClasses→com.google.devtools.build.lib.analysis.test.CoverageConfigurationcom.google.devtools.build.lib.analysis.BaseRuleClasses→com.google.devtools.build.lib.analysis.test.TestConfigurationcom.google.devtools.build.lib.analysis.BuildView→com.google.devtools.build.lib.analysis.test.CoverageReportActionFactorycom.google.devtools.build.lib.analysis.ConfiguredTargetFactory→com.google.devtools.build.lib.analysis.test.AnalysisFailurecom.google.devtools.build.lib.analysis.RuleConfiguredTargetBuilder→com.google.devtools.build.lib.analysis.test.TestProvider
- Direction
- com.google.devtools.build.lib.analysis uses com.google.devtools.build.lib.analysis.test, so a change to com.google.devtools.build.lib.analysis.test can break com.google.devtools.build.lib.analysis, while a change to com.google.devtools.build.lib.analysis can't break com.google.devtools.build.lib.analysis.test.
- Position
- Below the diagonal: com.google.devtools.build.lib.analysis uses a module listed above it, which is the healthy direction.
35→28 com.google.devtools.build.lib.analysis uses com.google.devtools.build.lib.runtime✕
- Connections
- 1 pair of types, where a type in com.google.devtools.build.lib.analysis uses a type in com.google.devtools.build.lib.runtime.
- The types involved
com.google.devtools.build.lib.analysis.Project→com.google.devtools.build.lib.runtime.ConfigFlagDefinitions
- Direction
- com.google.devtools.build.lib.analysis uses com.google.devtools.build.lib.runtime, so a change to com.google.devtools.build.lib.runtime can break com.google.devtools.build.lib.analysis, while a change to com.google.devtools.build.lib.analysis can't break com.google.devtools.build.lib.runtime.
- Position
- Below the diagonal: com.google.devtools.build.lib.analysis uses a module listed above it, which is the healthy direction.
35→29 com.google.devtools.build.lib.analysis uses com.google.devtools.build.lib.skyframe.serialization✕
- Connections
- 11 pairs of types, where a type in com.google.devtools.build.lib.analysis uses a type in com.google.devtools.build.lib.skyframe.serialization.
- The types involved
com.google.devtools.build.lib.analysis.ArrayFieldSetter→com.google.devtools.build.lib.skyframe.serialization.FieldSettercom.google.devtools.build.lib.analysis.Codec→com.google.devtools.build.lib.skyframe.serialization.AsyncDeserializationContextcom.google.devtools.build.lib.analysis.Codec→com.google.devtools.build.lib.skyframe.serialization.DeferredObjectCodeccom.google.devtools.build.lib.analysis.Codec→com.google.devtools.build.lib.skyframe.serialization.SerializationContextcom.google.devtools.build.lib.analysis.DeferredKeysCodec→com.google.devtools.build.lib.skyframe.serialization.AsyncDeserializationContextcom.google.devtools.build.lib.analysis.DeferredKeysCodec→com.google.devtools.build.lib.skyframe.serialization.DeferredObjectCodeccom.google.devtools.build.lib.analysis.DeferredKeysCodec→com.google.devtools.build.lib.skyframe.serialization.SerializationContextcom.google.devtools.build.lib.analysis.DeserializationBuilder→com.google.devtools.build.lib.skyframe.serialization.DeferredValuecom.google.devtools.build.lib.analysis.ValueSharingCodec→com.google.devtools.build.lib.skyframe.serialization.AsyncDeserializationContextcom.google.devtools.build.lib.analysis.ValueSharingCodec→com.google.devtools.build.lib.skyframe.serialization.DeferredObjectCodeccom.google.devtools.build.lib.analysis.ValueSharingCodec→com.google.devtools.build.lib.skyframe.serialization.SerializationContext
- Direction
- com.google.devtools.build.lib.analysis uses com.google.devtools.build.lib.skyframe.serialization, so a change to com.google.devtools.build.lib.skyframe.serialization can break com.google.devtools.build.lib.analysis, while a change to com.google.devtools.build.lib.analysis can't break com.google.devtools.build.lib.skyframe.serialization.
- Position
- Below the diagonal: com.google.devtools.build.lib.analysis uses a module listed above it, which is the healthy direction.
35→30 com.google.devtools.build.lib.analysis uses com.google.devtools.build.lib.collect.nestedset✕
- Connections
- 54 pairs of types, where a type in com.google.devtools.build.lib.analysis uses a type in com.google.devtools.build.lib.collect.nestedset. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.google.devtools.build.lib.analysis.Allowlist→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.analysis.AnalysisFailureEvent→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.analysis.ArbitraryGroups→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.analysis.ArtifactsInOutputGroup→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.analysis.ArtifactsToBuild→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.analysis.AspectCompleteEvent→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.analysis.AspectValue→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.analysis.AspectValueWithTransitivePackages→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.analysis.AspectValueWithTransitivePackagesForAlias→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.analysis.CommandHelper→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.analysis.CommandHelper→com.google.devtools.build.lib.collect.nestedset.NestedSetBuildercom.google.devtools.build.lib.analysis.ConfiguredObjectValue→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.analysis.ConfiguredTargetFactory→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.analysis.DefaultDefaultInfo→com.google.devtools.build.lib.collect.nestedset.Depsetcom.google.devtools.build.lib.analysis.DefaultOnly→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.analysis.DelegatingDefaultInfo→com.google.devtools.build.lib.collect.nestedset.Depsetcom.google.devtools.build.lib.analysis.EmptyFiles→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.analysis.ExtraActionArtifactsProvider→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.analysis.FileProvider→com.google.devtools.build.lib.collect.nestedset.Depsetcom.google.devtools.build.lib.analysis.FileProvider→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.analysis.FilesToRunProvider→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.analysis.FullFilesToRunProvider→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.analysis.HiddenTopLevelAndOneOther→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.analysis.HiddenTopLevelOnly→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.analysis.OtherGroupOnly→com.google.devtools.build.lib.collect.nestedset.NestedSet
- Direction
- com.google.devtools.build.lib.analysis uses com.google.devtools.build.lib.collect.nestedset, so a change to com.google.devtools.build.lib.collect.nestedset can break com.google.devtools.build.lib.analysis, while a change to com.google.devtools.build.lib.analysis can't break com.google.devtools.build.lib.collect.nestedset.
- Position
- Below the diagonal: com.google.devtools.build.lib.analysis uses a module listed above it, which is the healthy direction.
35→31 com.google.devtools.build.lib.analysis uses com.google.devtools.build.lib.cmdline✕
- Connections
- 81 pairs of types, where a type in com.google.devtools.build.lib.analysis uses a type in com.google.devtools.build.lib.cmdline. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.google.devtools.build.lib.analysis.ActiveProjects→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.analysis.AliasProvider→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.analysis.Allowlist→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.analysis.AnalysisEnvironment→com.google.devtools.build.lib.cmdline.RepositoryMappingcom.google.devtools.build.lib.analysis.AnalysisFailureEvent→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.analysis.AnalysisPhaseStartedEvent→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.analysis.AnalysisRootCauseEvent→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.analysis.AnalysisUtils→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.analysis.AspectAwareAttributeMapper→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.analysis.AspectBaseTargetResolvedToolchainContext→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.analysis.AspectCompleteEvent→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.analysis.AspectConfiguredEvent→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.analysis.AspectContext→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.analysis.AspectResolutionHelpers→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.analysis.BaseRuleClasses→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.analysis.BaseTargetToolchainDependencyKind→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.analysis.BazelRuleAnalysisThreadContext→com.google.devtools.build.lib.cmdline.StarlarkThreadContextcom.google.devtools.build.lib.analysis.BuildSettingProvider→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.analysis.BuildView→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.analysis.CachingAnalysisEnvironment→com.google.devtools.build.lib.cmdline.RepositoryMappingcom.google.devtools.build.lib.analysis.CommandHelper→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.analysis.CommonPrerequisiteValidator→com.google.devtools.build.lib.cmdline.PackageIdentifiercom.google.devtools.build.lib.analysis.ConfiguredAspectFactory→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.analysis.ConfiguredAspectFactory→com.google.devtools.build.lib.cmdline.RepositoryNamecom.google.devtools.build.lib.analysis.ConfiguredRuleClassProvider→com.google.devtools.build.lib.cmdline.Label
- Direction
- com.google.devtools.build.lib.analysis uses com.google.devtools.build.lib.cmdline, so a change to com.google.devtools.build.lib.cmdline can break com.google.devtools.build.lib.analysis, while a change to com.google.devtools.build.lib.analysis can't break com.google.devtools.build.lib.cmdline.
- Position
- Below the diagonal: com.google.devtools.build.lib.analysis uses a module listed above it, which is the healthy direction.
35→32 com.google.devtools.build.lib.analysis uses com.google.devtools.build.lib.analysis.platform✕
- Connections
- 12 pairs of types, where a type in com.google.devtools.build.lib.analysis uses a type in com.google.devtools.build.lib.analysis.platform.
- The types involved
com.google.devtools.build.lib.analysis.AspectBaseTargetResolvedToolchainContext→com.google.devtools.build.lib.analysis.platform.ToolchainTypeInfocom.google.devtools.build.lib.analysis.IncompatiblePlatformProvider→com.google.devtools.build.lib.analysis.platform.ConstraintValueInfocom.google.devtools.build.lib.analysis.ResolvedToolchainContext→com.google.devtools.build.lib.analysis.platform.ToolchainInfocom.google.devtools.build.lib.analysis.ResolvedToolchainContext→com.google.devtools.build.lib.analysis.platform.ToolchainTypeInfocom.google.devtools.build.lib.analysis.ResolvedToolchainsDataInterface→com.google.devtools.build.lib.analysis.platform.ToolchainTypeInfocom.google.devtools.build.lib.analysis.RuleContext→com.google.devtools.build.lib.analysis.platform.ConstraintValueInfocom.google.devtools.build.lib.analysis.RuleContext→com.google.devtools.build.lib.analysis.platform.PlatformInfocom.google.devtools.build.lib.analysis.RuleContext→com.google.devtools.build.lib.analysis.platform.ToolchainInfocom.google.devtools.build.lib.analysis.ShToolchain→com.google.devtools.build.lib.analysis.platform.PlatformInfocom.google.devtools.build.lib.analysis.TargetNotToolchainException→com.google.devtools.build.lib.analysis.platform.ToolchainTypeInfocom.google.devtools.build.lib.analysis.ToolchainCollection→com.google.devtools.build.lib.analysis.platform.PlatformInfocom.google.devtools.build.lib.analysis.ToolchainContext→com.google.devtools.build.lib.analysis.platform.PlatformInfo
- Direction
- com.google.devtools.build.lib.analysis uses com.google.devtools.build.lib.analysis.platform, so a change to com.google.devtools.build.lib.analysis.platform can break com.google.devtools.build.lib.analysis, while a change to com.google.devtools.build.lib.analysis can't break com.google.devtools.build.lib.analysis.platform.
- Position
- Below the diagonal: com.google.devtools.build.lib.analysis uses a module listed above it, which is the healthy direction.
35→33 com.google.devtools.build.lib.analysis uses com.google.devtools.build.lib.analysis.config✕
- Connections
- 46 pairs of types, where a type in com.google.devtools.build.lib.analysis uses a type in com.google.devtools.build.lib.analysis.config. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.google.devtools.build.lib.analysis.AnalysisAndExecutionResult→com.google.devtools.build.lib.analysis.config.BuildConfigurationValuecom.google.devtools.build.lib.analysis.AnalysisResult→com.google.devtools.build.lib.analysis.config.BuildConfigurationValuecom.google.devtools.build.lib.analysis.AnalysisRootCauseEvent→com.google.devtools.build.lib.analysis.config.BuildConfigurationValuecom.google.devtools.build.lib.analysis.AnalysisUtils→com.google.devtools.build.lib.analysis.config.BuildConfigurationValuecom.google.devtools.build.lib.analysis.AspectConfiguredEvent→com.google.devtools.build.lib.analysis.config.BuildConfigurationValuecom.google.devtools.build.lib.analysis.BuildConfigurationsCreated→com.google.devtools.build.lib.analysis.config.BuildConfigurationValuecom.google.devtools.build.lib.analysis.BuildView→com.google.devtools.build.lib.analysis.config.AdditionalConfigurationChangeEventcom.google.devtools.build.lib.analysis.BuildView→com.google.devtools.build.lib.analysis.config.BuildConfigurationValuecom.google.devtools.build.lib.analysis.BuildView→com.google.devtools.build.lib.analysis.config.BuildOptionscom.google.devtools.build.lib.analysis.ConfigurationMakeVariableContext→com.google.devtools.build.lib.analysis.config.BuildConfigurationValuecom.google.devtools.build.lib.analysis.ConfiguredRuleClassProvider→com.google.devtools.build.lib.analysis.config.BuildOptionscom.google.devtools.build.lib.analysis.ConfiguredRuleClassProvider→com.google.devtools.build.lib.analysis.config.FragmentClassSetcom.google.devtools.build.lib.analysis.ConfiguredRuleClassProvider→com.google.devtools.build.lib.analysis.config.FragmentRegistrycom.google.devtools.build.lib.analysis.ConfiguredRuleClassProvider→com.google.devtools.build.lib.analysis.config.GlobalStateProvidercom.google.devtools.build.lib.analysis.ConfiguredTarget→com.google.devtools.build.lib.analysis.config.ConfigMatchingProvidercom.google.devtools.build.lib.analysis.ConfiguredTargetFactory→com.google.devtools.build.lib.analysis.config.BuildConfigurationValuecom.google.devtools.build.lib.analysis.ConfiguredTargetFactory→com.google.devtools.build.lib.analysis.config.ConfigConditionscom.google.devtools.build.lib.analysis.DependencyResolutionHelpers→com.google.devtools.build.lib.analysis.config.BuildConfigurationValuecom.google.devtools.build.lib.analysis.DependencyResolutionHelpers→com.google.devtools.build.lib.analysis.config.ConfigMatchingProvidercom.google.devtools.build.lib.analysis.DependencyResolutionHelpers→com.google.devtools.build.lib.analysis.config.ExecutionTransitionFactorycom.google.devtools.build.lib.analysis.ErrorReporter→com.google.devtools.build.lib.analysis.config.BuildConfigurationValuecom.google.devtools.build.lib.analysis.EventHandlingErrorReporter→com.google.devtools.build.lib.analysis.config.BuildConfigurationValuecom.google.devtools.build.lib.analysis.MissingToolchainTypeRequirementException→com.google.devtools.build.lib.analysis.config.ToolchainTypeRequirementcom.google.devtools.build.lib.analysis.OptionsDiffPredicate→com.google.devtools.build.lib.analysis.config.BuildOptionscom.google.devtools.build.lib.analysis.PlatformConfiguration→com.google.devtools.build.lib.analysis.config.BuildOptions
- Direction
- com.google.devtools.build.lib.analysis uses com.google.devtools.build.lib.analysis.config, so a change to com.google.devtools.build.lib.analysis.config can break com.google.devtools.build.lib.analysis, while a change to com.google.devtools.build.lib.analysis can't break com.google.devtools.build.lib.analysis.config.
- Position
- Below the diagonal: com.google.devtools.build.lib.analysis uses a module listed above it, which is the healthy direction.
35→34 com.google.devtools.build.lib.analysis uses com.google.devtools.build.lib.analysis.actions✕
- Connections
- 11 pairs of types, where a type in com.google.devtools.build.lib.analysis uses a type in com.google.devtools.build.lib.analysis.actions.
- The types involved
com.google.devtools.build.lib.analysis.BashCommandConstructor→com.google.devtools.build.lib.analysis.actions.ActionConstructionContextcom.google.devtools.build.lib.analysis.CommandConstructor→com.google.devtools.build.lib.analysis.actions.ActionConstructionContextcom.google.devtools.build.lib.analysis.PseudoAction→com.google.devtools.build.lib.analysis.actions.ActionConstructionContextcom.google.devtools.build.lib.analysis.RepoMappingManifestAction→com.google.devtools.build.lib.analysis.actions.AbstractFileWriteActioncom.google.devtools.build.lib.analysis.RepoMappingManifestAction→com.google.devtools.build.lib.analysis.actions.FileContentsProvidercom.google.devtools.build.lib.analysis.RuleContext→com.google.devtools.build.lib.analysis.actions.ActionConstructionContextcom.google.devtools.build.lib.analysis.RunfilesSupport→com.google.devtools.build.lib.analysis.actions.ActionConstructionContextcom.google.devtools.build.lib.analysis.SourceManifestAction→com.google.devtools.build.lib.analysis.actions.AbstractFileWriteActioncom.google.devtools.build.lib.analysis.SourceManifestAction→com.google.devtools.build.lib.analysis.actions.FileContentsProvidercom.google.devtools.build.lib.analysis.WindowsBatchCommandConstructor→com.google.devtools.build.lib.analysis.actions.ActionConstructionContextcom.google.devtools.build.lib.analysis.WindowsPowershellCommandConstructor→com.google.devtools.build.lib.analysis.actions.ActionConstructionContext
- Direction
- com.google.devtools.build.lib.analysis uses com.google.devtools.build.lib.analysis.actions, so a change to com.google.devtools.build.lib.analysis.actions can break com.google.devtools.build.lib.analysis, while a change to com.google.devtools.build.lib.analysis can't break com.google.devtools.build.lib.analysis.actions.
- Position
- Below the diagonal: com.google.devtools.build.lib.analysis uses a module listed above it, which is the healthy direction.
35→37 com.google.devtools.build.lib.analysis uses com.google.devtools.build.lib.actions part of a loop✕
- Connections
- 140 pairs of types, where a type in com.google.devtools.build.lib.analysis uses a type in com.google.devtools.build.lib.actions. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.google.devtools.build.lib.analysis.1→com.google.devtools.build.lib.actions.Artifactcom.google.devtools.build.lib.analysis.1→com.google.devtools.build.lib.actions.FileArtifactValuecom.google.devtools.build.lib.analysis.1→com.google.devtools.build.lib.actions.FilesetOutputSymlinkcom.google.devtools.build.lib.analysis.2→com.google.devtools.build.lib.actions.Artifactcom.google.devtools.build.lib.analysis.2→com.google.devtools.build.lib.actions.FileArtifactValuecom.google.devtools.build.lib.analysis.2→com.google.devtools.build.lib.actions.FilesetOutputSymlinkcom.google.devtools.build.lib.analysis.ActionsProvider→com.google.devtools.build.lib.actions.ActionAnalysisMetadatacom.google.devtools.build.lib.analysis.AnalysisAndExecutionResult→com.google.devtools.build.lib.actions.Artifactcom.google.devtools.build.lib.analysis.AnalysisEnvironment→com.google.devtools.build.lib.actions.ActionAnalysisMetadatacom.google.devtools.build.lib.analysis.AnalysisEnvironment→com.google.devtools.build.lib.actions.ActionKeyContextcom.google.devtools.build.lib.analysis.AnalysisEnvironment→com.google.devtools.build.lib.actions.ActionRegistrycom.google.devtools.build.lib.analysis.AnalysisEnvironment→com.google.devtools.build.lib.actions.Artifactcom.google.devtools.build.lib.analysis.AnalysisEnvironment→com.google.devtools.build.lib.actions.ArtifactRootcom.google.devtools.build.lib.analysis.AnalysisFailureEvent→com.google.devtools.build.lib.actions.ActionLookupKeycom.google.devtools.build.lib.analysis.AnalysisPhaseCompleteEvent→com.google.devtools.build.lib.actions.TotalAndConfiguredTargetOnlyMetriccom.google.devtools.build.lib.analysis.AnalysisResult→com.google.devtools.build.lib.actions.ActionGraphcom.google.devtools.build.lib.analysis.AnalysisResult→com.google.devtools.build.lib.actions.Artifactcom.google.devtools.build.lib.analysis.AnalysisResult→com.google.devtools.build.lib.actions.PackageRootscom.google.devtools.build.lib.analysis.ArbitraryGroups→com.google.devtools.build.lib.actions.Artifactcom.google.devtools.build.lib.analysis.ArtifactsInOutputGroup→com.google.devtools.build.lib.actions.Artifactcom.google.devtools.build.lib.analysis.ArtifactsToBuild→com.google.devtools.build.lib.actions.Artifactcom.google.devtools.build.lib.analysis.AspectCompleteEvent→com.google.devtools.build.lib.actions.Artifactcom.google.devtools.build.lib.analysis.AspectCompleteEvent→com.google.devtools.build.lib.actions.CompletionContextcom.google.devtools.build.lib.analysis.AspectCompleteEvent→com.google.devtools.build.lib.actions.EventReportingArtifactscom.google.devtools.build.lib.analysis.AspectValue→com.google.devtools.build.lib.actions.ActionAnalysisMetadata
- Direction
- com.google.devtools.build.lib.analysis uses com.google.devtools.build.lib.actions, so a change to com.google.devtools.build.lib.actions can break com.google.devtools.build.lib.analysis, while a change to com.google.devtools.build.lib.analysis can't break com.google.devtools.build.lib.actions.
- 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.
36→2 com.google.devtools.build.lib.remote uses com.google.devtools.build.lib.events✕
- Connections
- 17 pairs of types, where a type in com.google.devtools.build.lib.remote uses a type in com.google.devtools.build.lib.events.
- The types involved
com.google.devtools.build.lib.remote.AbstractActionInputPrefetcher→com.google.devtools.build.lib.events.Reportercom.google.devtools.build.lib.remote.BazelOutputService→com.google.devtools.build.lib.events.EventHandlercom.google.devtools.build.lib.remote.ByteStreamBuildEventArtifactUploader→com.google.devtools.build.lib.events.ExtendedEventHandlercom.google.devtools.build.lib.remote.ByteStreamBuildEventArtifactUploaderFactory→com.google.devtools.build.lib.events.ExtendedEventHandlercom.google.devtools.build.lib.remote.GoogleChannelConnectionFactory→com.google.devtools.build.lib.events.Reportercom.google.devtools.build.lib.remote.LazyMaterializer→com.google.devtools.build.lib.events.ExtendedEventHandlercom.google.devtools.build.lib.remote.RemoteActionInputFetcher→com.google.devtools.build.lib.events.Reportercom.google.devtools.build.lib.remote.RemoteExecutionService→com.google.devtools.build.lib.events.Eventcom.google.devtools.build.lib.remote.RemoteExecutionService→com.google.devtools.build.lib.events.Reportercom.google.devtools.build.lib.remote.RemoteExternalOverlayFileSystem→com.google.devtools.build.lib.events.ExtendedEventHandlercom.google.devtools.build.lib.remote.RemoteExternalOverlayFileSystem→com.google.devtools.build.lib.events.Reportercom.google.devtools.build.lib.remote.RemoteModule→com.google.devtools.build.lib.events.Reportercom.google.devtools.build.lib.remote.RemoteOutputService→com.google.devtools.build.lib.events.EventHandlercom.google.devtools.build.lib.remote.RemoteRepoContentsCacheImpl→com.google.devtools.build.lib.events.ExtendedEventHandlercom.google.devtools.build.lib.remote.RemoteSpawnRunner→com.google.devtools.build.lib.events.Eventcom.google.devtools.build.lib.remote.RemoteSpawnRunner→com.google.devtools.build.lib.events.Reportercom.google.devtools.build.lib.remote.UploadManifest→com.google.devtools.build.lib.events.ExtendedEventHandler
- Direction
- com.google.devtools.build.lib.remote uses com.google.devtools.build.lib.events, so a change to com.google.devtools.build.lib.events can break com.google.devtools.build.lib.remote, while a change to com.google.devtools.build.lib.remote can't break com.google.devtools.build.lib.events.
- Position
- Below the diagonal: com.google.devtools.build.lib.remote uses a module listed above it, which is the healthy direction.
36→3 com.google.devtools.build.lib.remote uses com.google.devtools.common.options✕
- Connections
- 3 pairs of types, where a type in com.google.devtools.build.lib.remote uses a type in com.google.devtools.common.options.
- The types involved
com.google.devtools.build.lib.remote.RemoteModule→com.google.devtools.common.options.OptionsBasecom.google.devtools.build.lib.remote.RemoteModule→com.google.devtools.common.options.OptionsParsingResultcom.google.devtools.build.lib.remote.RemoteOutputChecker→com.google.devtools.common.options.RegexPatternOption
- Direction
- com.google.devtools.build.lib.remote uses com.google.devtools.common.options, so a change to com.google.devtools.common.options can break com.google.devtools.build.lib.remote, while a change to com.google.devtools.build.lib.remote can't break com.google.devtools.common.options.
- Position
- Below the diagonal: com.google.devtools.build.lib.remote uses a module listed above it, which is the healthy direction.
36→6 com.google.devtools.build.lib.remote uses com.google.devtools.build.skyframe✕
- Connections
- 9 pairs of types, where a type in com.google.devtools.build.lib.remote uses a type in com.google.devtools.build.skyframe.
- The types involved
com.google.devtools.build.lib.remote.LeaseService→com.google.devtools.build.skyframe.MemoizingEvaluatorcom.google.devtools.build.lib.remote.RemoteExternalOverlayFileSystem→com.google.devtools.build.skyframe.MemoizingEvaluatorcom.google.devtools.build.lib.remote.RemoteImportantOutputHandler→com.google.devtools.build.skyframe.WalkableGraphcom.google.devtools.build.lib.remote.RemoteLeaseExtension→com.google.devtools.build.skyframe.MemoizingEvaluatorcom.google.devtools.build.lib.remote.RemoteLeaseExtension→com.google.devtools.build.skyframe.SkyKeycom.google.devtools.build.lib.remote.RemoteOutputChecker→com.google.devtools.build.skyframe.MemoizingEvaluatorcom.google.devtools.build.lib.remote.RemoteOutputService→com.google.devtools.build.skyframe.WalkableGraphcom.google.devtools.build.lib.remote.RemoteRepoContentsCacheImpl→com.google.devtools.build.skyframe.Environmentcom.google.devtools.build.lib.remote.RemoteRewoundActionSynchronizer→com.google.devtools.build.skyframe.WalkableGraph
- Direction
- com.google.devtools.build.lib.remote uses com.google.devtools.build.skyframe, so a change to com.google.devtools.build.skyframe can break com.google.devtools.build.lib.remote, while a change to com.google.devtools.build.lib.remote can't break com.google.devtools.build.skyframe.
- Position
- Below the diagonal: com.google.devtools.build.lib.remote uses a module listed above it, which is the healthy direction.
36→8 com.google.devtools.build.lib.remote uses com.google.devtools.build.lib.vfs✕
- Connections
- 100 pairs of types, where a type in com.google.devtools.build.lib.remote uses a type in com.google.devtools.build.lib.vfs. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.google.devtools.build.lib.remote.AbstractActionInputPrefetcher→com.google.devtools.build.lib.vfs.OutputPermissionscom.google.devtools.build.lib.remote.AbstractActionInputPrefetcher→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.remote.AbstractActionInputPrefetcher→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.remote.ActionResultMetadata→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.remote.BazelOutputService→com.google.devtools.build.lib.vfs.BatchStatcom.google.devtools.build.lib.remote.BazelOutputService→com.google.devtools.build.lib.vfs.ModifiedFileSetcom.google.devtools.build.lib.remote.BazelOutputService→com.google.devtools.build.lib.vfs.OutputServicecom.google.devtools.build.lib.remote.BazelOutputService→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.remote.BazelOutputService→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.remote.BazelOutputService→com.google.devtools.build.lib.vfs.XattrProvidercom.google.devtools.build.lib.remote.BazelOutputServiceDirectory→com.google.devtools.build.lib.vfs.FileStatusWithDigestcom.google.devtools.build.lib.remote.BazelOutputServiceFile→com.google.devtools.build.lib.vfs.FileStatusWithDigestcom.google.devtools.build.lib.remote.BazelOutputServiceSymlink→com.google.devtools.build.lib.vfs.FileStatusWithDigestcom.google.devtools.build.lib.remote.ByteStreamBuildEventArtifactUploader→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.remote.ByteStreamBuildEventArtifactUploader→com.google.devtools.build.lib.vfs.XattrProvidercom.google.devtools.build.lib.remote.ChunkBlob→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.remote.ChunkLocation→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.remote.ChunkLocationMap→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.remote.ChunkedBlobUploader→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.remote.CombinedCache→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.remote.CombinedCache→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.remote.CombinedCacheClientFactory→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.remote.CombinedCacheClientFactory→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.remote.ConcurrentArtifactPathTrie→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.remote.DirectoryBuilder→com.google.devtools.build.lib.vfs.Path
- Direction
- com.google.devtools.build.lib.remote uses com.google.devtools.build.lib.vfs, so a change to com.google.devtools.build.lib.vfs can break com.google.devtools.build.lib.remote, while a change to com.google.devtools.build.lib.remote can't break com.google.devtools.build.lib.vfs.
- Position
- Below the diagonal: com.google.devtools.build.lib.remote uses a module listed above it, which is the healthy direction.
36→11 com.google.devtools.build.lib.remote uses com.google.devtools.build.lib.util✕
- Connections
- 9 pairs of types, where a type in com.google.devtools.build.lib.remote uses a type in com.google.devtools.build.lib.util.
- The types involved
com.google.devtools.build.lib.remote.AbstractActionInputPrefetcher→com.google.devtools.build.lib.util.TempPathGeneratorcom.google.devtools.build.lib.remote.DeterministicWriterBlob→com.google.devtools.build.lib.util.DeterministicWritercom.google.devtools.build.lib.remote.RemoteActionContextProvider→com.google.devtools.build.lib.util.TempPathGeneratorcom.google.devtools.build.lib.remote.RemoteActionInputFetcher→com.google.devtools.build.lib.util.TempPathGeneratorcom.google.devtools.build.lib.remote.RemoteExecutionCache→com.google.devtools.build.lib.util.DeterministicWritercom.google.devtools.build.lib.remote.RemoteExecutionService→com.google.devtools.build.lib.util.TempPathGeneratorcom.google.devtools.build.lib.remote.RemoteModule→com.google.devtools.build.lib.util.AbruptExitExceptioncom.google.devtools.build.lib.remote.RemoteModule→com.google.devtools.build.lib.util.ExitCodecom.google.devtools.build.lib.remote.RemoteModule→com.google.devtools.build.lib.util.TempPathGenerator
- Direction
- com.google.devtools.build.lib.remote uses com.google.devtools.build.lib.util, so a change to com.google.devtools.build.lib.util can break com.google.devtools.build.lib.remote, while a change to com.google.devtools.build.lib.remote can't break com.google.devtools.build.lib.util.
- Position
- Below the diagonal: com.google.devtools.build.lib.remote uses a module listed above it, which is the healthy direction.
36→14 com.google.devtools.build.lib.remote uses com.google.devtools.build.lib.buildeventstream✕
- Connections
- 5 pairs of types, where a type in com.google.devtools.build.lib.remote uses a type in com.google.devtools.build.lib.buildeventstream.
- The types involved
com.google.devtools.build.lib.remote.BuildEventArtifactUploaderFactoryDelegate→com.google.devtools.build.lib.buildeventstream.BuildEventArtifactUploadercom.google.devtools.build.lib.remote.ByteStreamBuildEventArtifactUploader→com.google.devtools.build.lib.buildeventstream.BuildEventArtifactUploadercom.google.devtools.build.lib.remote.ByteStreamBuildEventArtifactUploader→com.google.devtools.build.lib.buildeventstream.PathConvertercom.google.devtools.build.lib.remote.ByteStreamBuildEventArtifactUploaderFactory→com.google.devtools.build.lib.buildeventstream.BuildEventArtifactUploadercom.google.devtools.build.lib.remote.PathConverterImpl→com.google.devtools.build.lib.buildeventstream.PathConverter
- Direction
- com.google.devtools.build.lib.remote uses com.google.devtools.build.lib.buildeventstream, so a change to com.google.devtools.build.lib.buildeventstream can break com.google.devtools.build.lib.remote, while a change to com.google.devtools.build.lib.remote can't break com.google.devtools.build.lib.buildeventstream.
- Position
- Below the diagonal: com.google.devtools.build.lib.remote uses a module listed above it, which is the healthy direction.
36→15 com.google.devtools.build.lib.remote uses com.google.devtools.build.lib.exec✕
- Connections
- 14 pairs of types, where a type in com.google.devtools.build.lib.remote uses a type in com.google.devtools.build.lib.exec.
- The types involved
com.google.devtools.build.lib.remote.CombinedCache→com.google.devtools.build.lib.exec.SpawnCheckingCacheEventcom.google.devtools.build.lib.remote.RemoteActionContextProvider→com.google.devtools.build.lib.exec.Buildercom.google.devtools.build.lib.remote.RemoteExecutionService→com.google.devtools.build.lib.exec.ExecutionOptionscom.google.devtools.build.lib.remote.RemoteModule→com.google.devtools.build.lib.exec.Buildercom.google.devtools.build.lib.remote.RemoteModule→com.google.devtools.build.lib.exec.ExecutorBuildercom.google.devtools.build.lib.remote.RemoteSpawnCache→com.google.devtools.build.lib.exec.SpawnCachecom.google.devtools.build.lib.remote.RemoteSpawnRunner→com.google.devtools.build.lib.exec.SpawnCheckingCacheEventcom.google.devtools.build.lib.remote.RemoteSpawnRunner→com.google.devtools.build.lib.exec.SpawnExecutingEventcom.google.devtools.build.lib.remote.RemoteSpawnRunner→com.google.devtools.build.lib.exec.SpawnRunnercom.google.devtools.build.lib.remote.RemoteSpawnRunner→com.google.devtools.build.lib.exec.SpawnSchedulingEventcom.google.devtools.build.lib.remote.RemoteSpawnRunner→com.google.devtools.build.lib.exec.SpawnUploadingEventcom.google.devtools.build.lib.remote.RemoteSpawnStrategy→com.google.devtools.build.lib.exec.AbstractSpawnStrategycom.google.devtools.build.lib.remote.RemoteSpawnStrategy→com.google.devtools.build.lib.exec.ExecutionOptionscom.google.devtools.build.lib.remote.RemoteSpawnStrategy→com.google.devtools.build.lib.exec.SpawnRunner
- Direction
- com.google.devtools.build.lib.remote uses com.google.devtools.build.lib.exec, so a change to com.google.devtools.build.lib.exec can break com.google.devtools.build.lib.remote, while a change to com.google.devtools.build.lib.remote can't break com.google.devtools.build.lib.exec.
- Position
- Below the diagonal: com.google.devtools.build.lib.remote uses a module listed above it, which is the healthy direction.
36→23 com.google.devtools.build.lib.remote uses com.google.devtools.build.lib.buildtool✕
- Connections
- 1 pair of types, where a type in com.google.devtools.build.lib.remote uses a type in com.google.devtools.build.lib.buildtool.
- The types involved
com.google.devtools.build.lib.remote.RemoteModule→com.google.devtools.build.lib.buildtool.BuildRequest
- Direction
- com.google.devtools.build.lib.remote uses com.google.devtools.build.lib.buildtool, so a change to com.google.devtools.build.lib.buildtool can break com.google.devtools.build.lib.remote, while a change to com.google.devtools.build.lib.remote can't break com.google.devtools.build.lib.buildtool.
- Position
- Below the diagonal: com.google.devtools.build.lib.remote uses a module listed above it, which is the healthy direction.
36→24 com.google.devtools.build.lib.remote uses com.google.devtools.build.lib.skyframe✕
- Connections
- 4 pairs of types, where a type in com.google.devtools.build.lib.remote uses a type in com.google.devtools.build.lib.skyframe.
- The types involved
com.google.devtools.build.lib.remote.LeaseService→com.google.devtools.build.lib.skyframe.ActionExecutionValuecom.google.devtools.build.lib.remote.LeaseService→com.google.devtools.build.lib.skyframe.TreeArtifactValuecom.google.devtools.build.lib.remote.RemoteLeaseExtension→com.google.devtools.build.lib.skyframe.ActionExecutionValuecom.google.devtools.build.lib.remote.TreeArtifactDirectoryCache→com.google.devtools.build.lib.skyframe.TreeArtifactValue
- Direction
- com.google.devtools.build.lib.remote uses com.google.devtools.build.lib.skyframe, so a change to com.google.devtools.build.lib.skyframe can break com.google.devtools.build.lib.remote, while a change to com.google.devtools.build.lib.remote can't break com.google.devtools.build.lib.skyframe.
- Position
- Below the diagonal: com.google.devtools.build.lib.remote uses a module listed above it, which is the healthy direction.
36→28 com.google.devtools.build.lib.remote uses com.google.devtools.build.lib.runtime✕
- Connections
- 22 pairs of types, where a type in com.google.devtools.build.lib.remote uses a type in com.google.devtools.build.lib.runtime.
- The types involved
com.google.devtools.build.lib.remote.BuildEventArtifactUploaderFactoryDelegate→com.google.devtools.build.lib.runtime.BuildEventArtifactUploaderFactorycom.google.devtools.build.lib.remote.BuildEventArtifactUploaderFactoryDelegate→com.google.devtools.build.lib.runtime.CommandEnvironmentcom.google.devtools.build.lib.remote.ByteStreamBuildEventArtifactUploaderFactory→com.google.devtools.build.lib.runtime.BuildEventArtifactUploaderFactorycom.google.devtools.build.lib.remote.ByteStreamBuildEventArtifactUploaderFactory→com.google.devtools.build.lib.runtime.CommandEnvironmentcom.google.devtools.build.lib.remote.RemoteActionContextProvider→com.google.devtools.build.lib.runtime.CommandEnvironmentcom.google.devtools.build.lib.remote.RemoteModule→com.google.devtools.build.lib.runtime.BlazeModulecom.google.devtools.build.lib.remote.RemoteModule→com.google.devtools.build.lib.runtime.BlazeRuntimecom.google.devtools.build.lib.remote.RemoteModule→com.google.devtools.build.lib.runtime.BlazeServicecom.google.devtools.build.lib.remote.RemoteModule→com.google.devtools.build.lib.runtime.BlockWaitingModulecom.google.devtools.build.lib.remote.RemoteModule→com.google.devtools.build.lib.runtime.CommandEnvironmentcom.google.devtools.build.lib.remote.RemoteModule→com.google.devtools.build.lib.runtime.CommandLinePathFactorycom.google.devtools.build.lib.remote.RemoteModule→com.google.devtools.build.lib.runtime.RepositoryRemoteHelpersFactorycom.google.devtools.build.lib.remote.RemoteModule→com.google.devtools.build.lib.runtime.ServerBuildercom.google.devtools.build.lib.remote.RemoteModule→com.google.devtools.build.lib.runtime.WorkspaceBuildercom.google.devtools.build.lib.remote.RemoteRepoContentsCacheImpl→com.google.devtools.build.lib.runtime.RemoteRepoContentsCachecom.google.devtools.build.lib.remote.RemoteRepositoryRemoteExecutor→com.google.devtools.build.lib.runtime.RepositoryRemoteExecutorcom.google.devtools.build.lib.remote.RepositoryRemoteHelpersFactoryDelegate→com.google.devtools.build.lib.runtime.RemoteRepoContentsCachecom.google.devtools.build.lib.remote.RepositoryRemoteHelpersFactoryDelegate→com.google.devtools.build.lib.runtime.RepositoryRemoteExecutorcom.google.devtools.build.lib.remote.RepositoryRemoteHelpersFactoryDelegate→com.google.devtools.build.lib.runtime.RepositoryRemoteHelpersFactorycom.google.devtools.build.lib.remote.RepositoryRemoteHelpersFactoryImpl→com.google.devtools.build.lib.runtime.RemoteRepoContentsCachecom.google.devtools.build.lib.remote.RepositoryRemoteHelpersFactoryImpl→com.google.devtools.build.lib.runtime.RepositoryRemoteExecutorcom.google.devtools.build.lib.remote.RepositoryRemoteHelpersFactoryImpl→com.google.devtools.build.lib.runtime.RepositoryRemoteHelpersFactory
- Direction
- com.google.devtools.build.lib.remote uses com.google.devtools.build.lib.runtime, so a change to com.google.devtools.build.lib.runtime can break com.google.devtools.build.lib.remote, while a change to com.google.devtools.build.lib.remote can't break com.google.devtools.build.lib.runtime.
- Position
- Below the diagonal: com.google.devtools.build.lib.remote uses a module listed above it, which is the healthy direction.
36→31 com.google.devtools.build.lib.remote uses com.google.devtools.build.lib.cmdline✕
- Connections
- 3 pairs of types, where a type in com.google.devtools.build.lib.remote uses a type in com.google.devtools.build.lib.cmdline.
- The types involved
com.google.devtools.build.lib.remote.LazyMaterializer→com.google.devtools.build.lib.cmdline.RepositoryNamecom.google.devtools.build.lib.remote.RemoteExternalOverlayFileSystem→com.google.devtools.build.lib.cmdline.RepositoryNamecom.google.devtools.build.lib.remote.RemoteRepoContentsCacheImpl→com.google.devtools.build.lib.cmdline.RepositoryName
- Direction
- com.google.devtools.build.lib.remote uses com.google.devtools.build.lib.cmdline, so a change to com.google.devtools.build.lib.cmdline can break com.google.devtools.build.lib.remote, while a change to com.google.devtools.build.lib.remote can't break com.google.devtools.build.lib.cmdline.
- Position
- Below the diagonal: com.google.devtools.build.lib.remote uses a module listed above it, which is the healthy direction.
36→32 com.google.devtools.build.lib.remote uses com.google.devtools.build.lib.analysis.platform✕
- Connections
- 1 pair of types, where a type in com.google.devtools.build.lib.remote uses a type in com.google.devtools.build.lib.analysis.platform.
- The types involved
com.google.devtools.build.lib.remote.RemoteExecutionService→com.google.devtools.build.lib.analysis.platform.PlatformInfo
- Direction
- com.google.devtools.build.lib.remote uses com.google.devtools.build.lib.analysis.platform, so a change to com.google.devtools.build.lib.analysis.platform can break com.google.devtools.build.lib.remote, while a change to com.google.devtools.build.lib.remote can't break com.google.devtools.build.lib.analysis.platform.
- Position
- Below the diagonal: com.google.devtools.build.lib.remote uses a module listed above it, which is the healthy direction.
36→33 com.google.devtools.build.lib.remote uses com.google.devtools.build.lib.analysis.config✕
- Connections
- 1 pair of types, where a type in com.google.devtools.build.lib.remote uses a type in com.google.devtools.build.lib.analysis.config.
- The types involved
com.google.devtools.build.lib.remote.RemoteModule→com.google.devtools.build.lib.analysis.config.BuildOptions
- Direction
- com.google.devtools.build.lib.remote uses com.google.devtools.build.lib.analysis.config, so a change to com.google.devtools.build.lib.analysis.config can break com.google.devtools.build.lib.remote, while a change to com.google.devtools.build.lib.remote can't break com.google.devtools.build.lib.analysis.config.
- Position
- Below the diagonal: com.google.devtools.build.lib.remote uses a module listed above it, which is the healthy direction.
36→35 com.google.devtools.build.lib.remote uses com.google.devtools.build.lib.analysis✕
- Connections
- 12 pairs of types, where a type in com.google.devtools.build.lib.remote uses a type in com.google.devtools.build.lib.analysis.
- The types involved
com.google.devtools.build.lib.remote.RemoteModule→com.google.devtools.build.lib.analysis.AnalysisResultcom.google.devtools.build.lib.remote.RemoteModule→com.google.devtools.build.lib.analysis.BlazeDirectoriescom.google.devtools.build.lib.remote.RemoteModule→com.google.devtools.build.lib.analysis.ConfiguredAspectcom.google.devtools.build.lib.remote.RemoteModule→com.google.devtools.build.lib.analysis.ConfiguredTargetcom.google.devtools.build.lib.remote.RemoteOutputChecker→com.google.devtools.build.lib.analysis.AnalysisResultcom.google.devtools.build.lib.remote.RemoteOutputChecker→com.google.devtools.build.lib.analysis.ConfiguredAspectcom.google.devtools.build.lib.remote.RemoteOutputChecker→com.google.devtools.build.lib.analysis.ConfiguredTargetcom.google.devtools.build.lib.remote.RemoteOutputChecker→com.google.devtools.build.lib.analysis.ProviderCollectioncom.google.devtools.build.lib.remote.RemoteOutputChecker→com.google.devtools.build.lib.analysis.TopLevelArtifactContextcom.google.devtools.build.lib.remote.RemoteOutputService→com.google.devtools.build.lib.analysis.BlazeDirectoriescom.google.devtools.build.lib.remote.RemoteRepoContentsCacheImpl→com.google.devtools.build.lib.analysis.BlazeDirectoriescom.google.devtools.build.lib.remote.RepositoryRemoteHelpersFactoryImpl→com.google.devtools.build.lib.analysis.BlazeDirectories
- Direction
- com.google.devtools.build.lib.remote uses com.google.devtools.build.lib.analysis, so a change to com.google.devtools.build.lib.analysis can break com.google.devtools.build.lib.remote, while a change to com.google.devtools.build.lib.remote can't break com.google.devtools.build.lib.analysis.
- Position
- Below the diagonal: com.google.devtools.build.lib.remote uses a module listed above it, which is the healthy direction.
36→37 com.google.devtools.build.lib.remote uses com.google.devtools.build.lib.actions part of a loop✕
- Connections
- 78 pairs of types, where a type in com.google.devtools.build.lib.remote uses a type in com.google.devtools.build.lib.actions. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.google.devtools.build.lib.remote.1RequestSizeLimitingActionFinalizer→com.google.devtools.build.lib.actions.Artifactcom.google.devtools.build.lib.remote.3→com.google.devtools.build.lib.actions.FileArtifactValuecom.google.devtools.build.lib.remote.3→com.google.devtools.build.lib.actions.FileStatusWithMetadatacom.google.devtools.build.lib.remote.AbstractActionInputPrefetcher→com.google.devtools.build.lib.actions.Actioncom.google.devtools.build.lib.remote.AbstractActionInputPrefetcher→com.google.devtools.build.lib.actions.ActionExecutionMetadatacom.google.devtools.build.lib.remote.AbstractActionInputPrefetcher→com.google.devtools.build.lib.actions.ActionInputcom.google.devtools.build.lib.remote.AbstractActionInputPrefetcher→com.google.devtools.build.lib.actions.ActionInputPrefetchercom.google.devtools.build.lib.remote.AbstractActionInputPrefetcher→com.google.devtools.build.lib.actions.ActionOutputDirectoryHelpercom.google.devtools.build.lib.remote.AbstractActionInputPrefetcher→com.google.devtools.build.lib.actions.Artifactcom.google.devtools.build.lib.remote.AbstractActionInputPrefetcher→com.google.devtools.build.lib.actions.FileArtifactValuecom.google.devtools.build.lib.remote.AbstractActionInputPrefetcher→com.google.devtools.build.lib.actions.InputMetadataProvidercom.google.devtools.build.lib.remote.AbstractActionInputPrefetcher→com.google.devtools.build.lib.actions.OutputMetadataStorecom.google.devtools.build.lib.remote.AbstractActionInputPrefetcher→com.google.devtools.build.lib.actions.Spawncom.google.devtools.build.lib.remote.AbstractActionInputPrefetcher→com.google.devtools.build.lib.actions.VirtualActionInputcom.google.devtools.build.lib.remote.ActionCacheToken→com.google.devtools.build.lib.actions.Artifactcom.google.devtools.build.lib.remote.BazelOutputService→com.google.devtools.build.lib.actions.Actioncom.google.devtools.build.lib.remote.BazelOutputService→com.google.devtools.build.lib.actions.OutputMetadataStorecom.google.devtools.build.lib.remote.ConcurrentArtifactPathTrie→com.google.devtools.build.lib.actions.ActionInputcom.google.devtools.build.lib.remote.LocalExecution→com.google.devtools.build.lib.actions.SpawnResultcom.google.devtools.build.lib.remote.MetadataSupplier→com.google.devtools.build.lib.actions.ActionInputcom.google.devtools.build.lib.remote.MetadataSupplier→com.google.devtools.build.lib.actions.FileArtifactValuecom.google.devtools.build.lib.remote.OutputUploadTask→com.google.devtools.build.lib.actions.ActionExecutionMetadatacom.google.devtools.build.lib.remote.OutputUploadTask→com.google.devtools.build.lib.actions.SpawnResultcom.google.devtools.build.lib.remote.RemoteAction→com.google.devtools.build.lib.actions.ActionInputcom.google.devtools.build.lib.remote.RemoteAction→com.google.devtools.build.lib.actions.Spawn
- Direction
- com.google.devtools.build.lib.remote uses com.google.devtools.build.lib.actions, so a change to com.google.devtools.build.lib.actions can break com.google.devtools.build.lib.remote, while a change to com.google.devtools.build.lib.remote can't break com.google.devtools.build.lib.actions.
- 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 com.google.devtools.build.lib.actions uses net.starlark.java.syntax✕
- Connections
- 5 pairs of types, where a type in com.google.devtools.build.lib.actions uses a type in net.starlark.java.syntax.
- The types involved
com.google.devtools.build.lib.actions.ActionExecutionException→net.starlark.java.syntax.Locationcom.google.devtools.build.lib.actions.ActionOwner→net.starlark.java.syntax.Locationcom.google.devtools.build.lib.actions.FullActionOwner→net.starlark.java.syntax.Locationcom.google.devtools.build.lib.actions.LiteActionOwner→net.starlark.java.syntax.Locationcom.google.devtools.build.lib.actions.MissingInputFileException→net.starlark.java.syntax.Location
- Direction
- com.google.devtools.build.lib.actions uses net.starlark.java.syntax, so a change to net.starlark.java.syntax can break com.google.devtools.build.lib.actions, while a change to com.google.devtools.build.lib.actions can't break net.starlark.java.syntax.
- Position
- Below the diagonal: com.google.devtools.build.lib.actions uses a module listed above it, which is the healthy direction.
37→2 com.google.devtools.build.lib.actions uses com.google.devtools.build.lib.events✕
- Connections
- 11 pairs of types, where a type in com.google.devtools.build.lib.actions uses a type in com.google.devtools.build.lib.events.
- The types involved
com.google.devtools.build.lib.actions.ActionCacheChecker→com.google.devtools.build.lib.events.EventHandlercom.google.devtools.build.lib.actions.ActionCachedContext→com.google.devtools.build.lib.events.ExtendedEventHandlercom.google.devtools.build.lib.actions.ActionConflictException→com.google.devtools.build.lib.events.EventHandlercom.google.devtools.build.lib.actions.ActionExecutionContext→com.google.devtools.build.lib.events.ExtendedEventHandlercom.google.devtools.build.lib.actions.ActionExecutionStatusReporter→com.google.devtools.build.lib.events.EventHandlercom.google.devtools.build.lib.actions.ActionTemplate→com.google.devtools.build.lib.events.EventHandlercom.google.devtools.build.lib.actions.ChangePhase→com.google.devtools.build.lib.events.Postablecom.google.devtools.build.lib.actions.DiscoveredInputsEvent→com.google.devtools.build.lib.events.Postablecom.google.devtools.build.lib.actions.InjectedActionExecutionEvent→com.google.devtools.build.lib.events.Postablecom.google.devtools.build.lib.actions.SpawnExecutedEvent→com.google.devtools.build.lib.events.Postablecom.google.devtools.build.lib.actions.StoppedScanningActionEvent→com.google.devtools.build.lib.events.Postable
- Direction
- com.google.devtools.build.lib.actions uses com.google.devtools.build.lib.events, so a change to com.google.devtools.build.lib.events can break com.google.devtools.build.lib.actions, while a change to com.google.devtools.build.lib.actions can't break com.google.devtools.build.lib.events.
- Position
- Below the diagonal: com.google.devtools.build.lib.actions uses a module listed above it, which is the healthy direction.
37→3 com.google.devtools.build.lib.actions uses com.google.devtools.common.options✕
- Connections
- 3 pairs of types, where a type in com.google.devtools.build.lib.actions uses a type in com.google.devtools.common.options.
- The types involved
com.google.devtools.build.lib.actions.ActionExecutionContext→com.google.devtools.common.options.OptionsProvidercom.google.devtools.build.lib.actions.Executor→com.google.devtools.common.options.OptionsProvidercom.google.devtools.build.lib.actions.ResourceSetConverter→com.google.devtools.common.options.Contextless
- Direction
- com.google.devtools.build.lib.actions uses com.google.devtools.common.options, so a change to com.google.devtools.common.options can break com.google.devtools.build.lib.actions, while a change to com.google.devtools.build.lib.actions can't break com.google.devtools.common.options.
- Position
- Below the diagonal: com.google.devtools.build.lib.actions uses a module listed above it, which is the healthy direction.
37→4 com.google.devtools.build.lib.actions uses net.starlark.java.eval✕
- Connections
- 17 pairs of types, where a type in com.google.devtools.build.lib.actions uses a type in net.starlark.java.eval.
- The types involved
com.google.devtools.build.lib.actions.2→net.starlark.java.eval.StarlarkSemanticscom.google.devtools.build.lib.actions.AbstractAction→net.starlark.java.eval.Dictcom.google.devtools.build.lib.actions.AbstractAction→net.starlark.java.eval.Printercom.google.devtools.build.lib.actions.AbstractAction→net.starlark.java.eval.Sequencecom.google.devtools.build.lib.actions.AbstractAction→net.starlark.java.eval.StarlarkSemanticscom.google.devtools.build.lib.actions.ActionTemplate→net.starlark.java.eval.Printercom.google.devtools.build.lib.actions.ActionTemplate→net.starlark.java.eval.StarlarkSemanticscom.google.devtools.build.lib.actions.ActionTemplate→net.starlark.java.eval.StarlarkValuecom.google.devtools.build.lib.actions.Artifact→net.starlark.java.eval.Printercom.google.devtools.build.lib.actions.Artifact→net.starlark.java.eval.StarlarkSemanticscom.google.devtools.build.lib.actions.Artifact→net.starlark.java.eval.Structurecom.google.devtools.build.lib.actions.ArtifactRoot→net.starlark.java.eval.Printercom.google.devtools.build.lib.actions.ArtifactRoot→net.starlark.java.eval.StarlarkSemanticscom.google.devtools.build.lib.actions.MappedArtifactRoot→net.starlark.java.eval.Printercom.google.devtools.build.lib.actions.MappedArtifactRoot→net.starlark.java.eval.StarlarkSemanticscom.google.devtools.build.lib.actions.PathMapper→net.starlark.java.eval.StarlarkSemanticscom.google.devtools.build.lib.actions.PathMapperConstants→net.starlark.java.eval.Key
- Direction
- com.google.devtools.build.lib.actions uses net.starlark.java.eval, so a change to net.starlark.java.eval can break com.google.devtools.build.lib.actions, while a change to com.google.devtools.build.lib.actions can't break net.starlark.java.eval.
- Position
- Below the diagonal: com.google.devtools.build.lib.actions uses a module listed above it, which is the healthy direction.
37→6 com.google.devtools.build.lib.actions uses com.google.devtools.build.skyframe✕
- Connections
- 11 pairs of types, where a type in com.google.devtools.build.lib.actions uses a type in com.google.devtools.build.skyframe.
- The types involved
com.google.devtools.build.lib.actions.ActionLookupData→com.google.devtools.build.skyframe.ExecutionPhaseSkyKeycom.google.devtools.build.lib.actions.ActionLookupData→com.google.devtools.build.skyframe.SkyFunctionNamecom.google.devtools.build.lib.actions.ActionLookupKey→com.google.devtools.build.skyframe.CPUHeavySkyKeycom.google.devtools.build.lib.actions.ActionLookupSummaryKey→com.google.devtools.build.skyframe.SkyKeycom.google.devtools.build.lib.actions.ActionLookupValue→com.google.devtools.build.skyframe.SkyValuecom.google.devtools.build.lib.actions.Actions→com.google.devtools.build.skyframe.WalkableGraphcom.google.devtools.build.lib.actions.Artifact→com.google.devtools.build.skyframe.ExecutionPhaseSkyKeycom.google.devtools.build.lib.actions.Artifact→com.google.devtools.build.skyframe.SkyFunctionNamecom.google.devtools.build.lib.actions.Artifact→com.google.devtools.build.skyframe.SkyKeycom.google.devtools.build.lib.actions.FileArtifactValue→com.google.devtools.build.skyframe.SkyValuecom.google.devtools.build.lib.actions.FileValue→com.google.devtools.build.skyframe.SkyValue
- Direction
- com.google.devtools.build.lib.actions uses com.google.devtools.build.skyframe, so a change to com.google.devtools.build.skyframe can break com.google.devtools.build.lib.actions, while a change to com.google.devtools.build.lib.actions can't break com.google.devtools.build.skyframe.
- Position
- Below the diagonal: com.google.devtools.build.lib.actions uses a module listed above it, which is the healthy direction.
37→8 com.google.devtools.build.lib.actions uses com.google.devtools.build.lib.vfs✕
- Connections
- 132 pairs of types, where a type in com.google.devtools.build.lib.actions uses a type in com.google.devtools.build.lib.vfs. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.google.devtools.build.lib.actions.AbstractAction→com.google.devtools.build.lib.vfs.BulkDeletercom.google.devtools.build.lib.actions.AbstractAction→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.actions.AbstractAction→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.actions.AbstractAction→com.google.devtools.build.lib.vfs.Rootcom.google.devtools.build.lib.actions.Action→com.google.devtools.build.lib.vfs.BulkDeletercom.google.devtools.build.lib.actions.Action→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.actions.ActionCacheChecker→com.google.devtools.build.lib.vfs.OutputPermissionscom.google.devtools.build.lib.actions.ActionCachedContext→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.actions.ActionExecutedEvent→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.actions.ActionExecutedEvent→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.actions.ActionExecutionContext→com.google.devtools.build.lib.vfs.FileSystemcom.google.devtools.build.lib.actions.ActionExecutionContext→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.actions.ActionExecutionContext→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.actions.ActionExecutionContext→com.google.devtools.build.lib.vfs.Rootcom.google.devtools.build.lib.actions.ActionExecutionContext→com.google.devtools.build.lib.vfs.SyscallCachecom.google.devtools.build.lib.actions.ActionInput→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.actions.ActionInputHelper→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.actions.ActionInputHelper→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.actions.ActionInputMap→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.actions.ActionLogBufferPathGenerator→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.actions.ActionOutputDirectoryHelper→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.actions.ActionOutputDirectoryHelper→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.actions.ArchivedTreeArtifact→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.actions.ArchivedTreeArtifact→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.actions.Artifact→com.google.devtools.build.lib.vfs.Path
- Direction
- com.google.devtools.build.lib.actions uses com.google.devtools.build.lib.vfs, so a change to com.google.devtools.build.lib.vfs can break com.google.devtools.build.lib.actions, while a change to com.google.devtools.build.lib.actions can't break com.google.devtools.build.lib.vfs.
- Position
- Below the diagonal: com.google.devtools.build.lib.actions uses a module listed above it, which is the healthy direction.
37→10 com.google.devtools.build.lib.actions uses com.google.devtools.build.lib.skyframe.config✕
- Connections
- 1 pair of types, where a type in com.google.devtools.build.lib.actions uses a type in com.google.devtools.build.lib.skyframe.config.
- The types involved
com.google.devtools.build.lib.actions.ActionLookupKey→com.google.devtools.build.lib.skyframe.config.BuildConfigurationKey
- Direction
- com.google.devtools.build.lib.actions uses com.google.devtools.build.lib.skyframe.config, so a change to com.google.devtools.build.lib.skyframe.config can break com.google.devtools.build.lib.actions, while a change to com.google.devtools.build.lib.actions can't break com.google.devtools.build.lib.skyframe.config.
- Position
- Below the diagonal: com.google.devtools.build.lib.actions uses a module listed above it, which is the healthy direction.
37→11 com.google.devtools.build.lib.actions uses com.google.devtools.build.lib.util✕
- Connections
- 36 pairs of types, where a type in com.google.devtools.build.lib.actions uses a type in com.google.devtools.build.lib.util. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.google.devtools.build.lib.actions.1→com.google.devtools.build.lib.util.OScom.google.devtools.build.lib.actions.AbstractCommandLine→com.google.devtools.build.lib.util.Fingerprintcom.google.devtools.build.lib.actions.ActionConflictException→com.google.devtools.build.lib.util.DetailedExitCodecom.google.devtools.build.lib.actions.ActionEnvironment→com.google.devtools.build.lib.util.Fingerprintcom.google.devtools.build.lib.actions.ActionExecutionException→com.google.devtools.build.lib.util.DetailedExitCodecom.google.devtools.build.lib.actions.ActionExecutionException→com.google.devtools.build.lib.util.ExitCodecom.google.devtools.build.lib.actions.ActionExecutionStatusReporter→com.google.devtools.build.lib.util.Paircom.google.devtools.build.lib.actions.ActionKeyComputer→com.google.devtools.build.lib.util.Fingerprintcom.google.devtools.build.lib.actions.ActionKeyContext→com.google.devtools.build.lib.util.Fingerprintcom.google.devtools.build.lib.actions.Artifact→com.google.devtools.build.lib.util.FileTypecom.google.devtools.build.lib.actions.Artifact→com.google.devtools.build.lib.util.FileTypeSetcom.google.devtools.build.lib.actions.Artifact→com.google.devtools.build.lib.util.HasFileTypecom.google.devtools.build.lib.actions.Artifacts→com.google.devtools.build.lib.util.Fingerprintcom.google.devtools.build.lib.actions.BuildFailedException→com.google.devtools.build.lib.util.DetailedExitCodecom.google.devtools.build.lib.actions.CommandLine→com.google.devtools.build.lib.util.Fingerprintcom.google.devtools.build.lib.actions.CommandLines→com.google.devtools.build.lib.util.Fingerprintcom.google.devtools.build.lib.actions.FailAction→com.google.devtools.build.lib.util.Fingerprintcom.google.devtools.build.lib.actions.FileArtifactValue→com.google.devtools.build.lib.util.Fingerprintcom.google.devtools.build.lib.actions.FileContentsProxy→com.google.devtools.build.lib.util.Fingerprintcom.google.devtools.build.lib.actions.FilesetOutputTree→com.google.devtools.build.lib.util.Fingerprintcom.google.devtools.build.lib.actions.ImportantOutputException→com.google.devtools.build.lib.util.DetailedExitCodecom.google.devtools.build.lib.actions.InputFileErrorException→com.google.devtools.build.lib.util.DetailedExitCodecom.google.devtools.build.lib.actions.LostInputsActionExecutionException→com.google.devtools.build.lib.util.DetailedExitCodecom.google.devtools.build.lib.actions.LostInputsExecException→com.google.devtools.build.lib.util.DetailedExitCodecom.google.devtools.build.lib.actions.MetadataDigestUtils→com.google.devtools.build.lib.util.Fingerprint
- Direction
- com.google.devtools.build.lib.actions uses com.google.devtools.build.lib.util, so a change to com.google.devtools.build.lib.util can break com.google.devtools.build.lib.actions, while a change to com.google.devtools.build.lib.actions can't break com.google.devtools.build.lib.util.
- Position
- Below the diagonal: com.google.devtools.build.lib.actions uses a module listed above it, which is the healthy direction.
37→14 com.google.devtools.build.lib.actions uses com.google.devtools.build.lib.buildeventstream✕
- Connections
- 6 pairs of types, where a type in com.google.devtools.build.lib.actions uses a type in com.google.devtools.build.lib.buildeventstream.
- The types involved
com.google.devtools.build.lib.actions.ActionExecutedEvent→com.google.devtools.build.lib.buildeventstream.BuildEventcom.google.devtools.build.lib.actions.ActionExecutedEvent→com.google.devtools.build.lib.buildeventstream.BuildEventContextcom.google.devtools.build.lib.actions.ActionExecutedEvent→com.google.devtools.build.lib.buildeventstream.BuildEventWithConfigurationcom.google.devtools.build.lib.actions.BuildConfigurationEvent→com.google.devtools.build.lib.buildeventstream.BuildEventcom.google.devtools.build.lib.actions.BuildConfigurationEvent→com.google.devtools.build.lib.buildeventstream.BuildEventContextcom.google.devtools.build.lib.actions.EventReportingArtifacts→com.google.devtools.build.lib.buildeventstream.BuildEvent
- Direction
- com.google.devtools.build.lib.actions uses com.google.devtools.build.lib.buildeventstream, so a change to com.google.devtools.build.lib.buildeventstream can break com.google.devtools.build.lib.actions, while a change to com.google.devtools.build.lib.actions can't break com.google.devtools.build.lib.buildeventstream.
- Position
- Below the diagonal: com.google.devtools.build.lib.actions uses a module listed above it, which is the healthy direction.
37→24 com.google.devtools.build.lib.actions uses com.google.devtools.build.lib.skyframe✕
- Connections
- 20 pairs of types, where a type in com.google.devtools.build.lib.actions uses a type in com.google.devtools.build.lib.skyframe.
- The types involved
com.google.devtools.build.lib.actions.ActionCacheChecker→com.google.devtools.build.lib.skyframe.TreeArtifactValuecom.google.devtools.build.lib.actions.ActionConflictException→com.google.devtools.build.lib.skyframe.AbstractSaneAnalysisExceptioncom.google.devtools.build.lib.actions.ActionExecutionException→com.google.devtools.build.lib.skyframe.DetailedExceptioncom.google.devtools.build.lib.actions.ActionInputMap→com.google.devtools.build.lib.skyframe.TreeArtifactValuecom.google.devtools.build.lib.actions.ActionSuccessEvent→com.google.devtools.build.lib.skyframe.ActionExecutionValuecom.google.devtools.build.lib.actions.ActionTemplateOutputEvent→com.google.devtools.build.lib.skyframe.TreeArtifactValuecom.google.devtools.build.lib.actions.BuildFailedException→com.google.devtools.build.lib.skyframe.DetailedExceptioncom.google.devtools.build.lib.actions.CachedOutputMetadata→com.google.devtools.build.lib.skyframe.TreeArtifactValuecom.google.devtools.build.lib.actions.DelegatingPairInputMetadataProvider→com.google.devtools.build.lib.skyframe.TreeArtifactValuecom.google.devtools.build.lib.actions.FileValue→com.google.devtools.build.lib.skyframe.FileKeycom.google.devtools.build.lib.actions.FilesetOutputTree→com.google.devtools.build.lib.skyframe.TreeArtifactValuecom.google.devtools.build.lib.actions.ImportantOutputException→com.google.devtools.build.lib.skyframe.DetailedExceptioncom.google.devtools.build.lib.actions.InputMetadataProvider→com.google.devtools.build.lib.skyframe.TreeArtifactValuecom.google.devtools.build.lib.actions.MissingInputFileException→com.google.devtools.build.lib.skyframe.DetailedExceptioncom.google.devtools.build.lib.actions.OutputMetadataStore→com.google.devtools.build.lib.skyframe.TreeArtifactValuecom.google.devtools.build.lib.actions.OverriddenRunfilesPathInputMetadataProvider→com.google.devtools.build.lib.skyframe.TreeArtifactValuecom.google.devtools.build.lib.actions.RunfilesArtifactValue→com.google.devtools.build.lib.skyframe.TreeArtifactValuecom.google.devtools.build.lib.actions.SharedActionEvent→com.google.devtools.build.lib.skyframe.ActionExecutionValuecom.google.devtools.build.lib.actions.StaticInputMetadataProvider→com.google.devtools.build.lib.skyframe.TreeArtifactValuecom.google.devtools.build.lib.actions.TrieArtifact→com.google.devtools.build.lib.skyframe.TreeArtifactValue
- Direction
- com.google.devtools.build.lib.actions uses com.google.devtools.build.lib.skyframe, so a change to com.google.devtools.build.lib.skyframe can break com.google.devtools.build.lib.actions, while a change to com.google.devtools.build.lib.actions can't break com.google.devtools.build.lib.skyframe.
- Position
- Below the diagonal: com.google.devtools.build.lib.actions uses a module listed above it, which is the healthy direction.
37→25 com.google.devtools.build.lib.actions uses com.google.devtools.build.lib.packages✕
- Connections
- 4 pairs of types, where a type in com.google.devtools.build.lib.actions uses a type in com.google.devtools.build.lib.packages.
- The types involved
com.google.devtools.build.lib.actions.ActionOwner→com.google.devtools.build.lib.packages.AspectDescriptorcom.google.devtools.build.lib.actions.FullActionOwner→com.google.devtools.build.lib.packages.AspectDescriptorcom.google.devtools.build.lib.actions.LiteActionOwner→com.google.devtools.build.lib.packages.AspectDescriptorcom.google.devtools.build.lib.actions.PackageRootException→com.google.devtools.build.lib.packages.BuildFileNotFoundException
- Direction
- com.google.devtools.build.lib.actions uses com.google.devtools.build.lib.packages, so a change to com.google.devtools.build.lib.packages can break com.google.devtools.build.lib.actions, while a change to com.google.devtools.build.lib.actions can't break com.google.devtools.build.lib.packages.
- Position
- Below the diagonal: com.google.devtools.build.lib.actions uses a module listed above it, which is the healthy direction.
37→29 com.google.devtools.build.lib.actions uses com.google.devtools.build.lib.skyframe.serialization✕
- Connections
- 24 pairs of types, where a type in com.google.devtools.build.lib.actions uses a type in com.google.devtools.build.lib.skyframe.serialization.
- The types involved
com.google.devtools.build.lib.actions.ArchivedTreeArtifactCodec→com.google.devtools.build.lib.skyframe.serialization.AsyncDeserializationContextcom.google.devtools.build.lib.actions.ArchivedTreeArtifactCodec→com.google.devtools.build.lib.skyframe.serialization.DeferredObjectCodeccom.google.devtools.build.lib.actions.ArchivedTreeArtifactCodec→com.google.devtools.build.lib.skyframe.serialization.SerializationContextcom.google.devtools.build.lib.actions.ArtifactCodecs→com.google.devtools.build.lib.skyframe.serialization.AsyncDeserializationContextcom.google.devtools.build.lib.actions.ArtifactCodecs→com.google.devtools.build.lib.skyframe.serialization.ObjectCodeccom.google.devtools.build.lib.actions.ArtifactCodecs→com.google.devtools.build.lib.skyframe.serialization.SerializationContextcom.google.devtools.build.lib.actions.ArtifactSerializationContext→com.google.devtools.build.lib.skyframe.serialization.SerializationDependencyProvidercom.google.devtools.build.lib.actions.DerivedArtifactCodec→com.google.devtools.build.lib.skyframe.serialization.AsyncDeserializationContextcom.google.devtools.build.lib.actions.DerivedArtifactCodec→com.google.devtools.build.lib.skyframe.serialization.DeferredObjectCodeccom.google.devtools.build.lib.actions.DerivedArtifactCodec→com.google.devtools.build.lib.skyframe.serialization.SerializationContextcom.google.devtools.build.lib.actions.DeserializedDerivedArtifactBuilder→com.google.devtools.build.lib.skyframe.serialization.AsyncDeserializationContextcom.google.devtools.build.lib.actions.DeserializedSpecialArtifactBuilder→com.google.devtools.build.lib.skyframe.serialization.AsyncDeserializationContextcom.google.devtools.build.lib.actions.ResolvedSymlinkArtifactValueCodec→com.google.devtools.build.lib.skyframe.serialization.AsyncDeserializationContextcom.google.devtools.build.lib.actions.ResolvedSymlinkArtifactValueCodec→com.google.devtools.build.lib.skyframe.serialization.DeferredObjectCodeccom.google.devtools.build.lib.actions.ResolvedSymlinkArtifactValueCodec→com.google.devtools.build.lib.skyframe.serialization.SerializationContextcom.google.devtools.build.lib.actions.SourceArtifactCodec→com.google.devtools.build.lib.skyframe.serialization.AsyncDeserializationContextcom.google.devtools.build.lib.actions.SourceArtifactCodec→com.google.devtools.build.lib.skyframe.serialization.DeferredObjectCodeccom.google.devtools.build.lib.actions.SourceArtifactCodec→com.google.devtools.build.lib.skyframe.serialization.SerializationContextcom.google.devtools.build.lib.actions.SpecialArtifactCodec→com.google.devtools.build.lib.skyframe.serialization.AsyncDeserializationContextcom.google.devtools.build.lib.actions.SpecialArtifactCodec→com.google.devtools.build.lib.skyframe.serialization.DeferredObjectCodeccom.google.devtools.build.lib.actions.SpecialArtifactCodec→com.google.devtools.build.lib.skyframe.serialization.SerializationContextcom.google.devtools.build.lib.actions.TreeFileArtifactCodec→com.google.devtools.build.lib.skyframe.serialization.AsyncDeserializationContextcom.google.devtools.build.lib.actions.TreeFileArtifactCodec→com.google.devtools.build.lib.skyframe.serialization.DeferredObjectCodeccom.google.devtools.build.lib.actions.TreeFileArtifactCodec→com.google.devtools.build.lib.skyframe.serialization.SerializationContext
- Direction
- com.google.devtools.build.lib.actions uses com.google.devtools.build.lib.skyframe.serialization, so a change to com.google.devtools.build.lib.skyframe.serialization can break com.google.devtools.build.lib.actions, while a change to com.google.devtools.build.lib.actions can't break com.google.devtools.build.lib.skyframe.serialization.
- Position
- Below the diagonal: com.google.devtools.build.lib.actions uses a module listed above it, which is the healthy direction.
37→30 com.google.devtools.build.lib.actions uses com.google.devtools.build.lib.collect.nestedset✕
- Connections
- 21 pairs of types, where a type in com.google.devtools.build.lib.actions uses a type in com.google.devtools.build.lib.collect.nestedset.
- The types involved
com.google.devtools.build.lib.actions.AbstractAction→com.google.devtools.build.lib.collect.nestedset.Depsetcom.google.devtools.build.lib.actions.AbstractAction→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.actions.Action→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.actions.ActionAnalysisMetadata→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.actions.ActionCacheChecker→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.actions.ActionExecutionException→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.actions.ActionKeyContext→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.actions.ActionKeyContext→com.google.devtools.build.lib.collect.nestedset.NestedSetFingerprintCachecom.google.devtools.build.lib.actions.ActionWithDiscoveredInputsState→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.actions.Artifact→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.actions.BaseSpawn→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.actions.CommandAction→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.actions.DiscoveredModulesPruner→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.actions.OverriddenPathRunfilesTree→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.actions.ReportedArtifacts→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.actions.RunfilesTree→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.actions.RunfilesTreeAction→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.actions.SimpleSpawn→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.actions.Spawn→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.actions.SpawnInputs→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.actions.ToolProvider→com.google.devtools.build.lib.collect.nestedset.NestedSet
- Direction
- com.google.devtools.build.lib.actions uses com.google.devtools.build.lib.collect.nestedset, so a change to com.google.devtools.build.lib.collect.nestedset can break com.google.devtools.build.lib.actions, while a change to com.google.devtools.build.lib.actions can't break com.google.devtools.build.lib.collect.nestedset.
- Position
- Below the diagonal: com.google.devtools.build.lib.actions uses a module listed above it, which is the healthy direction.
37→31 com.google.devtools.build.lib.actions uses com.google.devtools.build.lib.cmdline✕
- Connections
- 17 pairs of types, where a type in com.google.devtools.build.lib.actions uses a type in com.google.devtools.build.lib.cmdline.
- The types involved
com.google.devtools.build.lib.actions.AbstractAction→com.google.devtools.build.lib.cmdline.RepositoryMappingcom.google.devtools.build.lib.actions.ActionConflictException→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.actions.ActionExecutionMetadata→com.google.devtools.build.lib.cmdline.RepositoryMappingcom.google.devtools.build.lib.actions.ActionLookupData→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.actions.ActionOwner→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.actions.Artifact→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.actions.ArtifactFactory→com.google.devtools.build.lib.cmdline.RepositoryNamecom.google.devtools.build.lib.actions.ArtifactOwner→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.actions.ArtifactResolver→com.google.devtools.build.lib.cmdline.RepositoryNamecom.google.devtools.build.lib.actions.CacheConfig→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.actions.DerivedArtifact→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.actions.FullActionOwner→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.actions.LiteActionOwner→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.actions.PackageRootLookup→com.google.devtools.build.lib.cmdline.PackageIdentifiercom.google.devtools.build.lib.actions.PackageRoots→com.google.devtools.build.lib.cmdline.PackageIdentifiercom.google.devtools.build.lib.actions.SourceArtifact→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.actions.Spawn→com.google.devtools.build.lib.cmdline.Label
- Direction
- com.google.devtools.build.lib.actions uses com.google.devtools.build.lib.cmdline, so a change to com.google.devtools.build.lib.cmdline can break com.google.devtools.build.lib.actions, while a change to com.google.devtools.build.lib.actions can't break com.google.devtools.build.lib.cmdline.
- Position
- Below the diagonal: com.google.devtools.build.lib.actions uses a module listed above it, which is the healthy direction.
37→32 com.google.devtools.build.lib.actions uses com.google.devtools.build.lib.analysis.platform✕
- Connections
- 10 pairs of types, where a type in com.google.devtools.build.lib.actions uses a type in com.google.devtools.build.lib.analysis.platform.
- The types involved
com.google.devtools.build.lib.actions.AbstractAction→com.google.devtools.build.lib.analysis.platform.PlatformInfocom.google.devtools.build.lib.actions.ActionAnalysisMetadata→com.google.devtools.build.lib.analysis.platform.PlatformInfocom.google.devtools.build.lib.actions.ActionOwner→com.google.devtools.build.lib.analysis.platform.PlatformInfocom.google.devtools.build.lib.actions.ActionTemplate→com.google.devtools.build.lib.analysis.platform.PlatformInfocom.google.devtools.build.lib.actions.BaseSpawn→com.google.devtools.build.lib.analysis.platform.PlatformInfocom.google.devtools.build.lib.actions.FullActionOwner→com.google.devtools.build.lib.analysis.platform.PlatformInfocom.google.devtools.build.lib.actions.LiteActionOwner→com.google.devtools.build.lib.analysis.platform.PlatformInfocom.google.devtools.build.lib.actions.RunfilesTreeAction→com.google.devtools.build.lib.analysis.platform.PlatformInfocom.google.devtools.build.lib.actions.SimpleSpawn→com.google.devtools.build.lib.analysis.platform.PlatformInfocom.google.devtools.build.lib.actions.Spawn→com.google.devtools.build.lib.analysis.platform.PlatformInfo
- Direction
- com.google.devtools.build.lib.actions uses com.google.devtools.build.lib.analysis.platform, so a change to com.google.devtools.build.lib.analysis.platform can break com.google.devtools.build.lib.actions, while a change to com.google.devtools.build.lib.actions can't break com.google.devtools.build.lib.analysis.platform.
- Position
- Below the diagonal: com.google.devtools.build.lib.actions uses a module listed above it, which is the healthy direction.
37→33 com.google.devtools.build.lib.actions uses com.google.devtools.build.lib.analysis.config✕
- Connections
- 7 pairs of types, where a type in com.google.devtools.build.lib.actions uses a type in com.google.devtools.build.lib.analysis.config.
- The types involved
com.google.devtools.build.lib.actions.AbstractCommandLine→com.google.devtools.build.lib.analysis.config.OutputPathsModecom.google.devtools.build.lib.actions.ActionOwner→com.google.devtools.build.lib.analysis.config.BuildConfigurationInfocom.google.devtools.build.lib.actions.CommandLine→com.google.devtools.build.lib.analysis.config.OutputPathsModecom.google.devtools.build.lib.actions.CommandLines→com.google.devtools.build.lib.analysis.config.OutputPathsModecom.google.devtools.build.lib.actions.FullActionOwner→com.google.devtools.build.lib.analysis.config.BuildConfigurationInfocom.google.devtools.build.lib.actions.LiteActionOwner→com.google.devtools.build.lib.analysis.config.BuildConfigurationInfocom.google.devtools.build.lib.actions.PathMapper→com.google.devtools.build.lib.analysis.config.OutputPathsMode
- Direction
- com.google.devtools.build.lib.actions uses com.google.devtools.build.lib.analysis.config, so a change to com.google.devtools.build.lib.analysis.config can break com.google.devtools.build.lib.actions, while a change to com.google.devtools.build.lib.actions can't break com.google.devtools.build.lib.analysis.config.
- Position
- Below the diagonal: com.google.devtools.build.lib.actions uses a module listed above it, which is the healthy direction.
37→35 com.google.devtools.build.lib.actions uses com.google.devtools.build.lib.analysis✕
- Connections
- 2 pairs of types, where a type in com.google.devtools.build.lib.actions uses a type in com.google.devtools.build.lib.analysis.
- The types involved
com.google.devtools.build.lib.actions.OverriddenPathRunfilesTree→com.google.devtools.build.lib.analysis.SymlinkEntrycom.google.devtools.build.lib.actions.RunfilesTree→com.google.devtools.build.lib.analysis.SymlinkEntry
- Direction
- com.google.devtools.build.lib.actions uses com.google.devtools.build.lib.analysis, so a change to com.google.devtools.build.lib.analysis can break com.google.devtools.build.lib.actions, while a change to com.google.devtools.build.lib.actions can't break com.google.devtools.build.lib.analysis.
- Position
- Below the diagonal: com.google.devtools.build.lib.actions uses a module listed above it, which is the healthy direction.
37→36 com.google.devtools.build.lib.actions uses com.google.devtools.build.lib.remote✕
- Connections
- 2 pairs of types, where a type in com.google.devtools.build.lib.actions uses a type in com.google.devtools.build.lib.remote.
- The types involved
com.google.devtools.build.lib.actions.ActionUploadFinishedEvent→com.google.devtools.build.lib.remote.Storecom.google.devtools.build.lib.actions.ActionUploadStartedEvent→com.google.devtools.build.lib.remote.Store
- Direction
- com.google.devtools.build.lib.actions uses com.google.devtools.build.lib.remote, so a change to com.google.devtools.build.lib.remote can break com.google.devtools.build.lib.actions, while a change to com.google.devtools.build.lib.actions can't break com.google.devtools.build.lib.remote.
- Position
- Below the diagonal: com.google.devtools.build.lib.actions uses a module listed above it, which is the healthy direction.
38→1 com.google.devtools.build.lib.rules.cpp uses net.starlark.java.syntax✕
- Connections
- 1 pair of types, where a type in com.google.devtools.build.lib.rules.cpp uses a type in net.starlark.java.syntax.
- The types involved
com.google.devtools.build.lib.rules.cpp.CcToolchainInfoProvider→net.starlark.java.syntax.Location
- Direction
- com.google.devtools.build.lib.rules.cpp uses net.starlark.java.syntax, so a change to net.starlark.java.syntax can break com.google.devtools.build.lib.rules.cpp, while a change to com.google.devtools.build.lib.rules.cpp can't break net.starlark.java.syntax.
- Position
- Below the diagonal: com.google.devtools.build.lib.rules.cpp uses a module listed above it, which is the healthy direction.
38→2 com.google.devtools.build.lib.rules.cpp uses com.google.devtools.build.lib.events✕
- Connections
- 3 pairs of types, where a type in com.google.devtools.build.lib.rules.cpp uses a type in com.google.devtools.build.lib.events.
- The types involved
com.google.devtools.build.lib.rules.cpp.CppCompileActionTemplate→com.google.devtools.build.lib.events.EventHandlercom.google.devtools.build.lib.rules.cpp.CppConfiguration→com.google.devtools.build.lib.events.EventHandlercom.google.devtools.build.lib.rules.cpp.LtoBackendActionTemplate→com.google.devtools.build.lib.events.EventHandler
- Direction
- com.google.devtools.build.lib.rules.cpp uses com.google.devtools.build.lib.events, so a change to com.google.devtools.build.lib.events can break com.google.devtools.build.lib.rules.cpp, while a change to com.google.devtools.build.lib.rules.cpp can't break com.google.devtools.build.lib.events.
- Position
- Below the diagonal: com.google.devtools.build.lib.rules.cpp uses a module listed above it, which is the healthy direction.
38→3 com.google.devtools.build.lib.rules.cpp uses com.google.devtools.common.options✕
- Connections
- 5 pairs of types, where a type in com.google.devtools.build.lib.rules.cpp uses a type in com.google.devtools.common.options.
- The types involved
com.google.devtools.build.lib.rules.cpp.DynamicModeConverter→com.google.devtools.common.options.EnumConvertercom.google.devtools.build.lib.rules.cpp.FissionOptionConverter→com.google.devtools.common.options.Contextlesscom.google.devtools.build.lib.rules.cpp.FissionOptionConverter→com.google.devtools.common.options.Convertercom.google.devtools.build.lib.rules.cpp.LibcTopLabelConverter→com.google.devtools.common.options.Convertercom.google.devtools.build.lib.rules.cpp.StripModeConverter→com.google.devtools.common.options.EnumConverter
- Direction
- com.google.devtools.build.lib.rules.cpp uses com.google.devtools.common.options, so a change to com.google.devtools.common.options can break com.google.devtools.build.lib.rules.cpp, while a change to com.google.devtools.build.lib.rules.cpp can't break com.google.devtools.common.options.
- Position
- Below the diagonal: com.google.devtools.build.lib.rules.cpp uses a module listed above it, which is the healthy direction.
38→4 com.google.devtools.build.lib.rules.cpp uses net.starlark.java.eval✕
- Connections
- 31 pairs of types, where a type in com.google.devtools.build.lib.rules.cpp uses a type in net.starlark.java.eval. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.google.devtools.build.lib.rules.cpp.CcCompilationContext→net.starlark.java.eval.Tuplecom.google.devtools.build.lib.rules.cpp.CcModule→net.starlark.java.eval.Dictcom.google.devtools.build.lib.rules.cpp.CcModule→net.starlark.java.eval.Sequencecom.google.devtools.build.lib.rules.cpp.CcModule→net.starlark.java.eval.StarlarkThreadcom.google.devtools.build.lib.rules.cpp.CcStarlarkInternal→net.starlark.java.eval.Dictcom.google.devtools.build.lib.rules.cpp.CcStarlarkInternal→net.starlark.java.eval.Sequencecom.google.devtools.build.lib.rules.cpp.CcStarlarkInternal→net.starlark.java.eval.StarlarkFunctioncom.google.devtools.build.lib.rules.cpp.CcStarlarkInternal→net.starlark.java.eval.StarlarkThreadcom.google.devtools.build.lib.rules.cpp.CcStarlarkInternal→net.starlark.java.eval.StarlarkValuecom.google.devtools.build.lib.rules.cpp.CcStarlarkInternal→net.starlark.java.eval.Tuplecom.google.devtools.build.lib.rules.cpp.CcToolchainFeatures→net.starlark.java.eval.StarlarkListcom.google.devtools.build.lib.rules.cpp.CcToolchainFeatures→net.starlark.java.eval.StarlarkThreadcom.google.devtools.build.lib.rules.cpp.CcToolchainFeatures→net.starlark.java.eval.StarlarkValuecom.google.devtools.build.lib.rules.cpp.CcToolchainFeaturesLib→net.starlark.java.eval.EvalExceptioncom.google.devtools.build.lib.rules.cpp.CcToolchainFeaturesLib→net.starlark.java.eval.Structurecom.google.devtools.build.lib.rules.cpp.CcToolchainProvider→net.starlark.java.eval.Sequencecom.google.devtools.build.lib.rules.cpp.CppCompileAction→net.starlark.java.eval.Sequencecom.google.devtools.build.lib.rules.cpp.CppCompileActionBuilder→net.starlark.java.eval.StarlarkValuecom.google.devtools.build.lib.rules.cpp.CppConfiguration→net.starlark.java.eval.Sequencecom.google.devtools.build.lib.rules.cpp.CppConfiguration→net.starlark.java.eval.StarlarkThreadcom.google.devtools.build.lib.rules.cpp.CppSemantics→net.starlark.java.eval.Sequencecom.google.devtools.build.lib.rules.cpp.CppSemantics→net.starlark.java.eval.StarlarkValuecom.google.devtools.build.lib.rules.cpp.ExpansionException→net.starlark.java.eval.EvalExceptioncom.google.devtools.build.lib.rules.cpp.FeatureConfigurationForStarlark→net.starlark.java.eval.Printercom.google.devtools.build.lib.rules.cpp.FeatureConfigurationForStarlark→net.starlark.java.eval.StarlarkSemantics
- Direction
- com.google.devtools.build.lib.rules.cpp uses net.starlark.java.eval, so a change to net.starlark.java.eval can break com.google.devtools.build.lib.rules.cpp, while a change to com.google.devtools.build.lib.rules.cpp can't break net.starlark.java.eval.
- Position
- Below the diagonal: com.google.devtools.build.lib.rules.cpp uses a module listed above it, which is the healthy direction.
38→6 com.google.devtools.build.lib.rules.cpp uses com.google.devtools.build.skyframe✕
- Connections
- 1 pair of types, where a type in com.google.devtools.build.lib.rules.cpp uses a type in com.google.devtools.build.skyframe.
- The types involved
com.google.devtools.build.lib.rules.cpp.CppCompileAction→com.google.devtools.build.skyframe.Environment
- Direction
- com.google.devtools.build.lib.rules.cpp uses com.google.devtools.build.skyframe, so a change to com.google.devtools.build.skyframe can break com.google.devtools.build.lib.rules.cpp, while a change to com.google.devtools.build.lib.rules.cpp can't break com.google.devtools.build.skyframe.
- Position
- Below the diagonal: com.google.devtools.build.lib.rules.cpp uses a module listed above it, which is the healthy direction.
38→8 com.google.devtools.build.lib.rules.cpp uses com.google.devtools.build.lib.vfs✕
- Connections
- 25 pairs of types, where a type in com.google.devtools.build.lib.rules.cpp uses a type in com.google.devtools.build.lib.vfs.
- The types involved
com.google.devtools.build.lib.rules.cpp.BitcodeFiles→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.rules.cpp.CcCompilationContext→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.rules.cpp.CcToolchainFeatures→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.rules.cpp.CcToolchainProvider→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.rules.cpp.CompileCommandLine→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.rules.cpp.CppCompileAction→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.rules.cpp.CppCompileAction→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.rules.cpp.CppCompileActionBuilder→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.rules.cpp.CppHelper→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.rules.cpp.FdoPathData→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.rules.cpp.FeatureConfiguration→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.rules.cpp.FeatureSelection→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.rules.cpp.HeaderDiscovery→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.rules.cpp.HeaderDiscovery→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.rules.cpp.IncludeScannable→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.rules.cpp.IncludeScanningHeaderData→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.rules.cpp.IncludeScanningHeaderDataHelper→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.rules.cpp.LinkActionConstruction→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.rules.cpp.LtoBackendAction→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.rules.cpp.LtoBackendActionTemplate→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.rules.cpp.PathFragmentValue→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.rules.cpp.RelativePathChunk→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.rules.cpp.ShowIncludesFilter→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.rules.cpp.SolibSymlinkAction→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.rules.cpp.SwigIncludeScanningContext→com.google.devtools.build.lib.vfs.PathFragment
- Direction
- com.google.devtools.build.lib.rules.cpp uses com.google.devtools.build.lib.vfs, so a change to com.google.devtools.build.lib.vfs can break com.google.devtools.build.lib.rules.cpp, while a change to com.google.devtools.build.lib.rules.cpp can't break com.google.devtools.build.lib.vfs.
- Position
- Below the diagonal: com.google.devtools.build.lib.rules.cpp uses a module listed above it, which is the healthy direction.
38→11 com.google.devtools.build.lib.rules.cpp uses com.google.devtools.build.lib.util✕
- Connections
- 30 pairs of types, where a type in com.google.devtools.build.lib.rules.cpp uses a type in com.google.devtools.build.lib.util. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.google.devtools.build.lib.rules.cpp.10→com.google.devtools.build.lib.util.FileTypecom.google.devtools.build.lib.rules.cpp.11→com.google.devtools.build.lib.util.FileTypecom.google.devtools.build.lib.rules.cpp.2→com.google.devtools.build.lib.util.FileTypecom.google.devtools.build.lib.rules.cpp.3→com.google.devtools.build.lib.util.FileTypecom.google.devtools.build.lib.rules.cpp.4→com.google.devtools.build.lib.util.FileTypecom.google.devtools.build.lib.rules.cpp.5→com.google.devtools.build.lib.util.FileTypecom.google.devtools.build.lib.rules.cpp.6→com.google.devtools.build.lib.util.FileTypecom.google.devtools.build.lib.rules.cpp.7→com.google.devtools.build.lib.util.FileTypecom.google.devtools.build.lib.rules.cpp.8→com.google.devtools.build.lib.util.FileTypecom.google.devtools.build.lib.rules.cpp.9→com.google.devtools.build.lib.util.FileTypecom.google.devtools.build.lib.rules.cpp.BitcodeFiles→com.google.devtools.build.lib.util.Fingerprintcom.google.devtools.build.lib.rules.cpp.CcToolchainFeaturesLib→com.google.devtools.build.lib.util.OScom.google.devtools.build.lib.rules.cpp.CcToolchainFeaturesLib→com.google.devtools.build.lib.util.Paircom.google.devtools.build.lib.rules.cpp.CompileCommandLine→com.google.devtools.build.lib.util.Paircom.google.devtools.build.lib.rules.cpp.CppCompileAction→com.google.devtools.build.lib.util.DependencySetcom.google.devtools.build.lib.rules.cpp.CppCompileAction→com.google.devtools.build.lib.util.DetailedExitCodecom.google.devtools.build.lib.rules.cpp.CppCompileAction→com.google.devtools.build.lib.util.Fingerprintcom.google.devtools.build.lib.rules.cpp.CppCompileAction→com.google.devtools.build.lib.util.OScom.google.devtools.build.lib.rules.cpp.CppCompileActionTemplate→com.google.devtools.build.lib.util.DetailedExitCodecom.google.devtools.build.lib.rules.cpp.CppCompileActionTemplate→com.google.devtools.build.lib.util.FileTypeSetcom.google.devtools.build.lib.rules.cpp.CppCompileActionTemplate→com.google.devtools.build.lib.util.Fingerprintcom.google.devtools.build.lib.rules.cpp.CppFileTypes→com.google.devtools.build.lib.util.FileTypecom.google.devtools.build.lib.rules.cpp.CppFileTypes→com.google.devtools.build.lib.util.FileTypeSetcom.google.devtools.build.lib.rules.cpp.FeatureConfiguration→com.google.devtools.build.lib.util.Paircom.google.devtools.build.lib.rules.cpp.Link→com.google.devtools.build.lib.util.FileTypeSet
- Direction
- com.google.devtools.build.lib.rules.cpp uses com.google.devtools.build.lib.util, so a change to com.google.devtools.build.lib.util can break com.google.devtools.build.lib.rules.cpp, while a change to com.google.devtools.build.lib.rules.cpp can't break com.google.devtools.build.lib.util.
- Position
- Below the diagonal: com.google.devtools.build.lib.rules.cpp uses a module listed above it, which is the healthy direction.
38→24 com.google.devtools.build.lib.rules.cpp uses com.google.devtools.build.lib.skyframe✕
- Connections
- 1 pair of types, where a type in com.google.devtools.build.lib.rules.cpp uses a type in com.google.devtools.build.lib.skyframe.
- The types involved
com.google.devtools.build.lib.rules.cpp.CcToolchainInfoProvider→com.google.devtools.build.lib.skyframe.Key
- Direction
- com.google.devtools.build.lib.rules.cpp uses com.google.devtools.build.lib.skyframe, so a change to com.google.devtools.build.lib.skyframe can break com.google.devtools.build.lib.rules.cpp, while a change to com.google.devtools.build.lib.rules.cpp can't break com.google.devtools.build.lib.skyframe.
- Position
- Below the diagonal: com.google.devtools.build.lib.rules.cpp uses a module listed above it, which is the healthy direction.
38→25 com.google.devtools.build.lib.rules.cpp uses com.google.devtools.build.lib.packages✕
- Connections
- 28 pairs of types, where a type in com.google.devtools.build.lib.rules.cpp uses a type in com.google.devtools.build.lib.packages. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.google.devtools.build.lib.rules.cpp.BranchFdoProfile→com.google.devtools.build.lib.packages.StructImplcom.google.devtools.build.lib.rules.cpp.CcCompilationContext→com.google.devtools.build.lib.packages.StarlarkInfocom.google.devtools.build.lib.rules.cpp.CcModule→com.google.devtools.build.lib.packages.Infocom.google.devtools.build.lib.rules.cpp.CcModule→com.google.devtools.build.lib.packages.Providercom.google.devtools.build.lib.rules.cpp.CcStarlarkInternal→com.google.devtools.build.lib.packages.Allowlistcom.google.devtools.build.lib.rules.cpp.CcStarlarkInternal→com.google.devtools.build.lib.packages.Infocom.google.devtools.build.lib.rules.cpp.CcStarlarkInternal→com.google.devtools.build.lib.packages.StarlarkInfocom.google.devtools.build.lib.rules.cpp.CcToolchainAliasRule→com.google.devtools.build.lib.packages.Buildercom.google.devtools.build.lib.rules.cpp.CcToolchainAliasRule→com.google.devtools.build.lib.packages.RuleClasscom.google.devtools.build.lib.rules.cpp.CcToolchainConfigInfo→com.google.devtools.build.lib.packages.StarlarkInfocom.google.devtools.build.lib.rules.cpp.CcToolchainFeaturesLib→com.google.devtools.build.lib.packages.Infocom.google.devtools.build.lib.rules.cpp.CcToolchainFeaturesLib→com.google.devtools.build.lib.packages.StarlarkInfocom.google.devtools.build.lib.rules.cpp.CcToolchainInfoProvider→com.google.devtools.build.lib.packages.Infocom.google.devtools.build.lib.rules.cpp.CcToolchainInfoProvider→com.google.devtools.build.lib.packages.Providercom.google.devtools.build.lib.rules.cpp.CcToolchainInfoProvider→com.google.devtools.build.lib.packages.StarlarkProviderWrappercom.google.devtools.build.lib.rules.cpp.CcToolchainProvider→com.google.devtools.build.lib.packages.Infocom.google.devtools.build.lib.rules.cpp.CcToolchainProvider→com.google.devtools.build.lib.packages.StarlarkInfocom.google.devtools.build.lib.rules.cpp.CppModuleMap→com.google.devtools.build.lib.packages.StarlarkInfocom.google.devtools.build.lib.rules.cpp.CppSemantics→com.google.devtools.build.lib.packages.AspectDescriptorcom.google.devtools.build.lib.rules.cpp.CppSemantics→com.google.devtools.build.lib.packages.Infocom.google.devtools.build.lib.rules.cpp.DebugPackageProvider→com.google.devtools.build.lib.packages.StarlarkInfocom.google.devtools.build.lib.rules.cpp.FdoContext→com.google.devtools.build.lib.packages.StructImplcom.google.devtools.build.lib.rules.cpp.PropellerOptimizeInputFile→com.google.devtools.build.lib.packages.StructImplcom.google.devtools.build.lib.rules.cpp.Provider→com.google.devtools.build.lib.packages.Infocom.google.devtools.build.lib.rules.cpp.Provider→com.google.devtools.build.lib.packages.StarlarkProviderWrapper
- Direction
- com.google.devtools.build.lib.rules.cpp uses com.google.devtools.build.lib.packages, so a change to com.google.devtools.build.lib.packages can break com.google.devtools.build.lib.rules.cpp, while a change to com.google.devtools.build.lib.rules.cpp can't break com.google.devtools.build.lib.packages.
- Position
- Below the diagonal: com.google.devtools.build.lib.rules.cpp uses a module listed above it, which is the healthy direction.
38→26 com.google.devtools.build.lib.rules.cpp uses com.google.devtools.build.lib.analysis.starlark✕
- Connections
- 6 pairs of types, where a type in com.google.devtools.build.lib.rules.cpp uses a type in com.google.devtools.build.lib.analysis.starlark.
- The types involved
com.google.devtools.build.lib.rules.cpp.CcStarlarkInternal→com.google.devtools.build.lib.analysis.starlark.Argscom.google.devtools.build.lib.rules.cpp.CcStarlarkInternal→com.google.devtools.build.lib.analysis.starlark.StarlarkActionFactorycom.google.devtools.build.lib.rules.cpp.CcStarlarkInternal→com.google.devtools.build.lib.analysis.starlark.StarlarkRuleContextcom.google.devtools.build.lib.rules.cpp.CcTemplateContext→com.google.devtools.build.lib.analysis.starlark.StarlarkTemplateContextcom.google.devtools.build.lib.rules.cpp.CppSemantics→com.google.devtools.build.lib.analysis.starlark.StarlarkRuleContextcom.google.devtools.build.lib.rules.cpp.WrappedStarlarkActionFactory→com.google.devtools.build.lib.analysis.starlark.StarlarkActionFactory
- Direction
- com.google.devtools.build.lib.rules.cpp uses com.google.devtools.build.lib.analysis.starlark, so a change to com.google.devtools.build.lib.analysis.starlark can break com.google.devtools.build.lib.rules.cpp, while a change to com.google.devtools.build.lib.rules.cpp can't break com.google.devtools.build.lib.analysis.starlark.
- Position
- Below the diagonal: com.google.devtools.build.lib.rules.cpp uses a module listed above it, which is the healthy direction.
38→29 com.google.devtools.build.lib.rules.cpp uses com.google.devtools.build.lib.skyframe.serialization✕
- Connections
- 3 pairs of types, where a type in com.google.devtools.build.lib.rules.cpp uses a type in com.google.devtools.build.lib.skyframe.serialization.
- The types involved
com.google.devtools.build.lib.rules.cpp.HeaderInfoCodec→com.google.devtools.build.lib.skyframe.serialization.AsyncDeserializationContextcom.google.devtools.build.lib.rules.cpp.HeaderInfoCodec→com.google.devtools.build.lib.skyframe.serialization.DeferredObjectCodeccom.google.devtools.build.lib.rules.cpp.HeaderInfoCodec→com.google.devtools.build.lib.skyframe.serialization.SerializationContext
- Direction
- com.google.devtools.build.lib.rules.cpp uses com.google.devtools.build.lib.skyframe.serialization, so a change to com.google.devtools.build.lib.skyframe.serialization can break com.google.devtools.build.lib.rules.cpp, while a change to com.google.devtools.build.lib.rules.cpp can't break com.google.devtools.build.lib.skyframe.serialization.
- Position
- Below the diagonal: com.google.devtools.build.lib.rules.cpp uses a module listed above it, which is the healthy direction.
38→30 com.google.devtools.build.lib.rules.cpp uses com.google.devtools.build.lib.collect.nestedset✕
- Connections
- 16 pairs of types, where a type in com.google.devtools.build.lib.rules.cpp uses a type in com.google.devtools.build.lib.collect.nestedset.
- The types involved
com.google.devtools.build.lib.rules.cpp.BitcodeFiles→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.rules.cpp.CcCompilationContext→com.google.devtools.build.lib.collect.nestedset.Depsetcom.google.devtools.build.lib.rules.cpp.CcCompilationContext→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.rules.cpp.CcCompilationContext→com.google.devtools.build.lib.collect.nestedset.NestedSetBuildercom.google.devtools.build.lib.rules.cpp.CcStarlarkInternal→com.google.devtools.build.lib.collect.nestedset.Depsetcom.google.devtools.build.lib.rules.cpp.CcToolchainProvider→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.rules.cpp.CppCompileAction→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.rules.cpp.CppCompileActionBuilder→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.rules.cpp.CppCompileActionBuilder→com.google.devtools.build.lib.collect.nestedset.NestedSetBuildercom.google.devtools.build.lib.rules.cpp.CppCompileActionTemplate→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.rules.cpp.CppDiscoveredModules→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.rules.cpp.HeaderDiscovery→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.rules.cpp.IncludeScannable→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.rules.cpp.LtoBackendAction→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.rules.cpp.LtoBackendActionTemplate→com.google.devtools.build.lib.collect.nestedset.NestedSetcom.google.devtools.build.lib.rules.cpp.LtoBackendArtifacts→com.google.devtools.build.lib.collect.nestedset.NestedSet
- Direction
- com.google.devtools.build.lib.rules.cpp uses com.google.devtools.build.lib.collect.nestedset, so a change to com.google.devtools.build.lib.collect.nestedset can break com.google.devtools.build.lib.rules.cpp, while a change to com.google.devtools.build.lib.rules.cpp can't break com.google.devtools.build.lib.collect.nestedset.
- Position
- Below the diagonal: com.google.devtools.build.lib.rules.cpp uses a module listed above it, which is the healthy direction.
38→31 com.google.devtools.build.lib.rules.cpp uses com.google.devtools.build.lib.cmdline✕
- Connections
- 9 pairs of types, where a type in com.google.devtools.build.lib.rules.cpp uses a type in com.google.devtools.build.lib.cmdline.
- The types involved
com.google.devtools.build.lib.rules.cpp.CcStarlarkInternal→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.rules.cpp.CcToolchainProvider→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.rules.cpp.CppConfiguration→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.rules.cpp.CppHelper→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.rules.cpp.CppOptions→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.rules.cpp.DebugPackageProvider→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.rules.cpp.FdoPathData→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.rules.cpp.LibcTopLabelConverter→com.google.devtools.build.lib.cmdline.Labelcom.google.devtools.build.lib.rules.cpp.SolibSymlinkAction→com.google.devtools.build.lib.cmdline.Label
- Direction
- com.google.devtools.build.lib.rules.cpp uses com.google.devtools.build.lib.cmdline, so a change to com.google.devtools.build.lib.cmdline can break com.google.devtools.build.lib.rules.cpp, while a change to com.google.devtools.build.lib.rules.cpp can't break com.google.devtools.build.lib.cmdline.
- Position
- Below the diagonal: com.google.devtools.build.lib.rules.cpp uses a module listed above it, which is the healthy direction.
38→32 com.google.devtools.build.lib.rules.cpp uses com.google.devtools.build.lib.analysis.platform✕
- Connections
- 6 pairs of types, where a type in com.google.devtools.build.lib.rules.cpp uses a type in com.google.devtools.build.lib.analysis.platform.
- The types involved
com.google.devtools.build.lib.rules.cpp.CcStarlarkInternal→com.google.devtools.build.lib.analysis.platform.PlatformInfocom.google.devtools.build.lib.rules.cpp.CcToolchainProvider→com.google.devtools.build.lib.analysis.platform.PlatformInfocom.google.devtools.build.lib.rules.cpp.CppCompileAction→com.google.devtools.build.lib.analysis.platform.PlatformInfocom.google.devtools.build.lib.rules.cpp.IncludeScanner→com.google.devtools.build.lib.analysis.platform.PlatformInfocom.google.devtools.build.lib.rules.cpp.SolibSymlinkAction→com.google.devtools.build.lib.analysis.platform.PlatformInfocom.google.devtools.build.lib.rules.cpp.SwigIncludeScanningContext→com.google.devtools.build.lib.analysis.platform.PlatformInfo
- Direction
- com.google.devtools.build.lib.rules.cpp uses com.google.devtools.build.lib.analysis.platform, so a change to com.google.devtools.build.lib.analysis.platform can break com.google.devtools.build.lib.rules.cpp, while a change to com.google.devtools.build.lib.rules.cpp can't break com.google.devtools.build.lib.analysis.platform.
- Position
- Below the diagonal: com.google.devtools.build.lib.rules.cpp uses a module listed above it, which is the healthy direction.
38→33 com.google.devtools.build.lib.rules.cpp uses com.google.devtools.build.lib.analysis.config✕
- Connections
- 16 pairs of types, where a type in com.google.devtools.build.lib.rules.cpp uses a type in com.google.devtools.build.lib.analysis.config.
- The types involved
com.google.devtools.build.lib.rules.cpp.CcStarlarkInternal→com.google.devtools.build.lib.analysis.config.BuildConfigurationValuecom.google.devtools.build.lib.rules.cpp.CppCompileAction→com.google.devtools.build.lib.analysis.config.BuildConfigurationValuecom.google.devtools.build.lib.rules.cpp.CppCompileActionBuilder→com.google.devtools.build.lib.analysis.config.BuildConfigurationValuecom.google.devtools.build.lib.rules.cpp.CppConfiguration→com.google.devtools.build.lib.analysis.config.BuildOptionscom.google.devtools.build.lib.rules.cpp.CppConfiguration→com.google.devtools.build.lib.analysis.config.CompilationModecom.google.devtools.build.lib.rules.cpp.CppConfiguration→com.google.devtools.build.lib.analysis.config.Fragmentcom.google.devtools.build.lib.rules.cpp.CppConfiguration→com.google.devtools.build.lib.analysis.config.PerLabelOptionscom.google.devtools.build.lib.rules.cpp.CppHelper→com.google.devtools.build.lib.analysis.config.BuildConfigurationValuecom.google.devtools.build.lib.rules.cpp.CppLinkActionBuilder→com.google.devtools.build.lib.analysis.config.BuildConfigurationValuecom.google.devtools.build.lib.rules.cpp.CppOptions→com.google.devtools.build.lib.analysis.config.CompilationModecom.google.devtools.build.lib.rules.cpp.CppOptions→com.google.devtools.build.lib.analysis.config.FragmentOptionscom.google.devtools.build.lib.rules.cpp.CppOptions→com.google.devtools.build.lib.analysis.config.PerLabelOptionscom.google.devtools.build.lib.rules.cpp.FissionOptionConverter→com.google.devtools.build.lib.analysis.config.CompilationModecom.google.devtools.build.lib.rules.cpp.LinkActionConstruction→com.google.devtools.build.lib.analysis.config.BuildConfigurationValuecom.google.devtools.build.lib.rules.cpp.LtoBackendAction→com.google.devtools.build.lib.analysis.config.BuildConfigurationValuecom.google.devtools.build.lib.rules.cpp.LtoBackendArtifacts→com.google.devtools.build.lib.analysis.config.BuildConfigurationValue
- Direction
- com.google.devtools.build.lib.rules.cpp uses com.google.devtools.build.lib.analysis.config, so a change to com.google.devtools.build.lib.analysis.config can break com.google.devtools.build.lib.rules.cpp, while a change to com.google.devtools.build.lib.rules.cpp can't break com.google.devtools.build.lib.analysis.config.
- Position
- Below the diagonal: com.google.devtools.build.lib.rules.cpp uses a module listed above it, which is the healthy direction.
38→34 com.google.devtools.build.lib.rules.cpp uses com.google.devtools.build.lib.analysis.actions✕
- Connections
- 6 pairs of types, where a type in com.google.devtools.build.lib.rules.cpp uses a type in com.google.devtools.build.lib.analysis.actions.
- The types involved
com.google.devtools.build.lib.rules.cpp.CppCompileActionBuilder→com.google.devtools.build.lib.analysis.actions.ActionConstructionContextcom.google.devtools.build.lib.rules.cpp.CppHelper→com.google.devtools.build.lib.analysis.actions.ActionConstructionContextcom.google.devtools.build.lib.rules.cpp.CppLinkActionBuilder→com.google.devtools.build.lib.analysis.actions.ActionConstructionContextcom.google.devtools.build.lib.rules.cpp.LinkActionConstruction→com.google.devtools.build.lib.analysis.actions.ActionConstructionContextcom.google.devtools.build.lib.rules.cpp.LtoBackendAction→com.google.devtools.build.lib.analysis.actions.SpawnActioncom.google.devtools.build.lib.rules.cpp.SolibSymlinkAction→com.google.devtools.build.lib.analysis.actions.ActionConstructionContext
- Direction
- com.google.devtools.build.lib.rules.cpp uses com.google.devtools.build.lib.analysis.actions, so a change to com.google.devtools.build.lib.analysis.actions can break com.google.devtools.build.lib.rules.cpp, while a change to com.google.devtools.build.lib.rules.cpp can't break com.google.devtools.build.lib.analysis.actions.
- Position
- Below the diagonal: com.google.devtools.build.lib.rules.cpp uses a module listed above it, which is the healthy direction.
38→35 com.google.devtools.build.lib.rules.cpp uses com.google.devtools.build.lib.analysis✕
- Connections
- 11 pairs of types, where a type in com.google.devtools.build.lib.rules.cpp uses a type in com.google.devtools.build.lib.analysis.
- The types involved
com.google.devtools.build.lib.rules.cpp.CcRuleContext→com.google.devtools.build.lib.analysis.RuleContextcom.google.devtools.build.lib.rules.cpp.CcToolchainAliasRule→com.google.devtools.build.lib.analysis.RuleDefinitioncom.google.devtools.build.lib.rules.cpp.CcToolchainAliasRule→com.google.devtools.build.lib.analysis.RuleDefinitionEnvironmentcom.google.devtools.build.lib.rules.cpp.CcToolchainConfigInfo→com.google.devtools.build.lib.analysis.ConfiguredTargetcom.google.devtools.build.lib.rules.cpp.CcToolchainProvider→com.google.devtools.build.lib.analysis.ConfiguredTargetcom.google.devtools.build.lib.rules.cpp.CcToolchainProvider→com.google.devtools.build.lib.analysis.OutputGroupInfocom.google.devtools.build.lib.rules.cpp.CcToolchainProvider→com.google.devtools.build.lib.analysis.PackageSpecificationProvidercom.google.devtools.build.lib.rules.cpp.CppHelper→com.google.devtools.build.lib.analysis.RuleContextcom.google.devtools.build.lib.rules.cpp.CppSemantics→com.google.devtools.build.lib.analysis.RuleContextcom.google.devtools.build.lib.rules.cpp.DebugPackageProvider→com.google.devtools.build.lib.analysis.TransitiveInfoCollectioncom.google.devtools.build.lib.rules.cpp.SolibSymlinkAction→com.google.devtools.build.lib.analysis.RuleContext
- Direction
- com.google.devtools.build.lib.rules.cpp uses com.google.devtools.build.lib.analysis, so a change to com.google.devtools.build.lib.analysis can break com.google.devtools.build.lib.rules.cpp, while a change to com.google.devtools.build.lib.rules.cpp can't break com.google.devtools.build.lib.analysis.
- Position
- Below the diagonal: com.google.devtools.build.lib.rules.cpp uses a module listed above it, which is the healthy direction.
38→37 com.google.devtools.build.lib.rules.cpp uses com.google.devtools.build.lib.actions✕
- Connections
- 141 pairs of types, where a type in com.google.devtools.build.lib.rules.cpp uses a type in com.google.devtools.build.lib.actions. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.google.devtools.build.lib.rules.cpp.1→com.google.devtools.build.lib.actions.AbstractCommandLinecom.google.devtools.build.lib.rules.cpp.1→com.google.devtools.build.lib.actions.InputMetadataProvidercom.google.devtools.build.lib.rules.cpp.1→com.google.devtools.build.lib.actions.PathMappercom.google.devtools.build.lib.rules.cpp.ActionConfig→com.google.devtools.build.lib.actions.InputMetadataProvidercom.google.devtools.build.lib.rules.cpp.ActionConfig→com.google.devtools.build.lib.actions.PathMappercom.google.devtools.build.lib.rules.cpp.ArgumentsAndParamFileActionInput→com.google.devtools.build.lib.actions.ParamFileActionInputcom.google.devtools.build.lib.rules.cpp.ArtifactValue→com.google.devtools.build.lib.actions.Artifactcom.google.devtools.build.lib.rules.cpp.ArtifactValue→com.google.devtools.build.lib.actions.PathMappercom.google.devtools.build.lib.rules.cpp.BitcodeFiles→com.google.devtools.build.lib.actions.Artifactcom.google.devtools.build.lib.rules.cpp.BooleanValue→com.google.devtools.build.lib.actions.PathMappercom.google.devtools.build.lib.rules.cpp.BranchFdoProfile→com.google.devtools.build.lib.actions.Artifactcom.google.devtools.build.lib.rules.cpp.CcActionContext→com.google.devtools.build.lib.actions.ActionOwnercom.google.devtools.build.lib.rules.cpp.CcCompilationContext→com.google.devtools.build.lib.actions.Artifactcom.google.devtools.build.lib.rules.cpp.CcRuleContext→com.google.devtools.build.lib.actions.ActionOwnercom.google.devtools.build.lib.rules.cpp.CcStarlarkInternal→com.google.devtools.build.lib.actions.ActionOwnercom.google.devtools.build.lib.rules.cpp.CcStarlarkInternal→com.google.devtools.build.lib.actions.Artifactcom.google.devtools.build.lib.rules.cpp.CcTemplateContext→com.google.devtools.build.lib.actions.ActionOwnercom.google.devtools.build.lib.rules.cpp.CcToolchainProvider→com.google.devtools.build.lib.actions.Artifactcom.google.devtools.build.lib.rules.cpp.CcToolchainVariables→com.google.devtools.build.lib.actions.InputMetadataProvidercom.google.devtools.build.lib.rules.cpp.CcToolchainVariables→com.google.devtools.build.lib.actions.PathMappercom.google.devtools.build.lib.rules.cpp.CompileCommandLine→com.google.devtools.build.lib.actions.CommandLinecom.google.devtools.build.lib.rules.cpp.CompileCommandLine→com.google.devtools.build.lib.actions.PathMappercom.google.devtools.build.lib.rules.cpp.CppCompileAction→com.google.devtools.build.lib.actions.AbstractActioncom.google.devtools.build.lib.rules.cpp.CppCompileAction→com.google.devtools.build.lib.actions.ActionEnvironmentcom.google.devtools.build.lib.rules.cpp.CppCompileAction→com.google.devtools.build.lib.actions.ActionExecutionContext
- Direction
- com.google.devtools.build.lib.rules.cpp uses com.google.devtools.build.lib.actions, so a change to com.google.devtools.build.lib.actions can break com.google.devtools.build.lib.rules.cpp, while a change to com.google.devtools.build.lib.rules.cpp can't break com.google.devtools.build.lib.actions.
- Position
- Below the diagonal: com.google.devtools.build.lib.rules.cpp uses a module listed above it, which is the healthy direction.
39→2 com.google.devtools.build.lib.runtime.commands uses com.google.devtools.build.lib.events✕
- Connections
- 3 pairs of types, where a type in com.google.devtools.build.lib.runtime.commands uses a type in com.google.devtools.build.lib.events.
- The types involved
com.google.devtools.build.lib.runtime.commands.CleanCommand→com.google.devtools.build.lib.events.Reportercom.google.devtools.build.lib.runtime.commands.HelpCommand→com.google.devtools.build.lib.events.Reportercom.google.devtools.build.lib.runtime.commands.RunCommand→com.google.devtools.build.lib.events.Reporter
- Direction
- com.google.devtools.build.lib.runtime.commands uses com.google.devtools.build.lib.events, so a change to com.google.devtools.build.lib.events can break com.google.devtools.build.lib.runtime.commands, while a change to com.google.devtools.build.lib.runtime.commands can't break com.google.devtools.build.lib.events.
- Position
- Below the diagonal: com.google.devtools.build.lib.runtime.commands uses a module listed above it, which is the healthy direction.
39→3 com.google.devtools.build.lib.runtime.commands uses com.google.devtools.common.options✕
- Connections
- 44 pairs of types, where a type in com.google.devtools.build.lib.runtime.commands uses a type in com.google.devtools.common.options. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.google.devtools.build.lib.runtime.commands.AqueryCommand→com.google.devtools.common.options.OptionsParsercom.google.devtools.build.lib.runtime.commands.AqueryCommand→com.google.devtools.common.options.OptionsParsingResultcom.google.devtools.build.lib.runtime.commands.BuildCommand→com.google.devtools.common.options.OptionsParsingResultcom.google.devtools.build.lib.runtime.commands.BuiltinCommandModule→com.google.devtools.common.options.OptionsParsingResultcom.google.devtools.build.lib.runtime.commands.CanonicalizeCommand→com.google.devtools.common.options.OptionsParsingResultcom.google.devtools.build.lib.runtime.commands.CleanCommand→com.google.devtools.common.options.OptionsParsingResultcom.google.devtools.build.lib.runtime.commands.CommandOptionVisitor→com.google.devtools.common.options.OptionsParsercom.google.devtools.build.lib.runtime.commands.ConfigCommand→com.google.devtools.common.options.OptionsParsingResultcom.google.devtools.build.lib.runtime.commands.ConfigOptions→com.google.devtools.common.options.OptionsBasecom.google.devtools.build.lib.runtime.commands.CoverageCommand→com.google.devtools.common.options.OptionsParsercom.google.devtools.build.lib.runtime.commands.CqueryCommand→com.google.devtools.common.options.OptionsParsercom.google.devtools.build.lib.runtime.commands.CqueryCommand→com.google.devtools.common.options.OptionsParsingResultcom.google.devtools.build.lib.runtime.commands.DumpCommand→com.google.devtools.common.options.OptionsParsingResultcom.google.devtools.build.lib.runtime.commands.DumpOptions→com.google.devtools.common.options.OptionsBasecom.google.devtools.build.lib.runtime.commands.FlagClashCanaryOptions→com.google.devtools.common.options.OptionsBasecom.google.devtools.build.lib.runtime.commands.HelpCommand→com.google.devtools.common.options.HelpVerbositycom.google.devtools.build.lib.runtime.commands.HelpCommand→com.google.devtools.common.options.OptionDefinitioncom.google.devtools.build.lib.runtime.commands.HelpCommand→com.google.devtools.common.options.OptionsParsercom.google.devtools.build.lib.runtime.commands.HelpCommand→com.google.devtools.common.options.OptionsParsingResultcom.google.devtools.build.lib.runtime.commands.HtmlEmitter→com.google.devtools.common.options.OptionsBasecom.google.devtools.build.lib.runtime.commands.InfoCommand→com.google.devtools.common.options.OptionsParsingResultcom.google.devtools.build.lib.runtime.commands.InfoCommand→com.google.devtools.common.options.OptionsProvidercom.google.devtools.build.lib.runtime.commands.InfoItemOutputTypeConverter→com.google.devtools.common.options.EnumConvertercom.google.devtools.build.lib.runtime.commands.LicenseCommand→com.google.devtools.common.options.OptionsParsingResultcom.google.devtools.build.lib.runtime.commands.MemoryModeConverter→com.google.devtools.common.options.Contextless
- Direction
- com.google.devtools.build.lib.runtime.commands uses com.google.devtools.common.options, so a change to com.google.devtools.common.options can break com.google.devtools.build.lib.runtime.commands, while a change to com.google.devtools.build.lib.runtime.commands can't break com.google.devtools.common.options.
- Position
- Below the diagonal: com.google.devtools.build.lib.runtime.commands uses a module listed above it, which is the healthy direction.
39→6 com.google.devtools.build.lib.runtime.commands uses com.google.devtools.build.skyframe✕
- Connections
- 3 pairs of types, where a type in com.google.devtools.build.lib.runtime.commands uses a type in com.google.devtools.build.skyframe.
- The types involved
com.google.devtools.build.lib.runtime.commands.DumpCommand→com.google.devtools.build.skyframe.InMemoryGraphcom.google.devtools.build.lib.runtime.commands.DumpCommand→com.google.devtools.build.skyframe.SkyFunctionNamecom.google.devtools.build.lib.runtime.commands.DumpCommand→com.google.devtools.build.skyframe.SkyKey
- Direction
- com.google.devtools.build.lib.runtime.commands uses com.google.devtools.build.skyframe, so a change to com.google.devtools.build.skyframe can break com.google.devtools.build.lib.runtime.commands, while a change to com.google.devtools.build.lib.runtime.commands can't break com.google.devtools.build.skyframe.
- Position
- Below the diagonal: com.google.devtools.build.lib.runtime.commands uses a module listed above it, which is the healthy direction.
39→8 com.google.devtools.build.lib.runtime.commands uses com.google.devtools.build.lib.vfs✕
- Connections
- 9 pairs of types, where a type in com.google.devtools.build.lib.runtime.commands uses a type in com.google.devtools.build.lib.vfs.
- The types involved
com.google.devtools.build.lib.runtime.commands.Builder→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.runtime.commands.BuiltTargets→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.runtime.commands.BuiltTargets→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.runtime.commands.CleanCommand→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.runtime.commands.RunCommand→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.runtime.commands.RunCommand→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.runtime.commands.RunCommandLine→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.runtime.commands.RunOptions→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.runtime.commands.TestCommand→com.google.devtools.build.lib.vfs.PathFragment
- Direction
- com.google.devtools.build.lib.runtime.commands uses com.google.devtools.build.lib.vfs, so a change to com.google.devtools.build.lib.vfs can break com.google.devtools.build.lib.runtime.commands, while a change to com.google.devtools.build.lib.runtime.commands can't break com.google.devtools.build.lib.vfs.
- Position
- Below the diagonal: com.google.devtools.build.lib.runtime.commands uses a module listed above it, which is the healthy direction.
39→10 com.google.devtools.build.lib.runtime.commands uses com.google.devtools.build.lib.skyframe.config✕
- Connections
- 2 pairs of types, where a type in com.google.devtools.build.lib.runtime.commands uses a type in com.google.devtools.build.lib.skyframe.config.
- The types involved
com.google.devtools.build.lib.runtime.commands.ConfigCommand→com.google.devtools.build.lib.skyframe.config.BuildConfigurationKeycom.google.devtools.build.lib.runtime.commands.DumpCommand→com.google.devtools.build.lib.skyframe.config.BuildConfigurationKey
- Direction
- com.google.devtools.build.lib.runtime.commands uses com.google.devtools.build.lib.skyframe.config, so a change to com.google.devtools.build.lib.skyframe.config can break com.google.devtools.build.lib.runtime.commands, while a change to com.google.devtools.build.lib.runtime.commands can't break com.google.devtools.build.lib.skyframe.config.
- Position
- Below the diagonal: com.google.devtools.build.lib.runtime.commands uses a module listed above it, which is the healthy direction.
39→11 com.google.devtools.build.lib.runtime.commands uses com.google.devtools.build.lib.util✕
- Connections
- 13 pairs of types, where a type in com.google.devtools.build.lib.runtime.commands uses a type in com.google.devtools.build.lib.util.
- The types involved
com.google.devtools.build.lib.runtime.commands.AbruptExitRuntimeException→com.google.devtools.build.lib.util.DetailedExitCodecom.google.devtools.build.lib.runtime.commands.CleanCommand→com.google.devtools.build.lib.util.OScom.google.devtools.build.lib.runtime.commands.ConfigCommand→com.google.devtools.build.lib.util.Paircom.google.devtools.build.lib.runtime.commands.DumpOptions→com.google.devtools.build.lib.util.RegexFiltercom.google.devtools.build.lib.runtime.commands.FragmentDiffForOutput→com.google.devtools.build.lib.util.Paircom.google.devtools.build.lib.runtime.commands.InfoCommand→com.google.devtools.build.lib.util.ExitCodecom.google.devtools.build.lib.runtime.commands.NoTestsFound→com.google.devtools.build.lib.util.ExitCodecom.google.devtools.build.lib.runtime.commands.PrintActionRunner→com.google.devtools.build.lib.util.DetailedExitCodecom.google.devtools.build.lib.runtime.commands.QueryCommand→com.google.devtools.build.lib.util.Eithercom.google.devtools.build.lib.runtime.commands.QueryCommand→com.google.devtools.build.lib.util.ExitCodecom.google.devtools.build.lib.runtime.commands.QueryEnvironmentBasedCommand→com.google.devtools.build.lib.util.Eithercom.google.devtools.build.lib.runtime.commands.RunOptions→com.google.devtools.build.lib.util.EnvVarcom.google.devtools.build.lib.runtime.commands.TestCommand→com.google.devtools.build.lib.util.DetailedExitCode
- Direction
- com.google.devtools.build.lib.runtime.commands uses com.google.devtools.build.lib.util, so a change to com.google.devtools.build.lib.util can break com.google.devtools.build.lib.runtime.commands, while a change to com.google.devtools.build.lib.runtime.commands can't break com.google.devtools.build.lib.util.
- Position
- Below the diagonal: com.google.devtools.build.lib.runtime.commands uses a module listed above it, which is the healthy direction.
39→14 com.google.devtools.build.lib.runtime.commands uses com.google.devtools.build.lib.buildeventstream✕
- Connections
- 1 pair of types, where a type in com.google.devtools.build.lib.runtime.commands uses a type in com.google.devtools.build.lib.buildeventstream.
- The types involved
com.google.devtools.build.lib.runtime.commands.NoTestsFound→com.google.devtools.build.lib.buildeventstream.BuildCompletingEvent
- Direction
- com.google.devtools.build.lib.runtime.commands uses com.google.devtools.build.lib.buildeventstream, so a change to com.google.devtools.build.lib.buildeventstream can break com.google.devtools.build.lib.runtime.commands, while a change to com.google.devtools.build.lib.runtime.commands can't break com.google.devtools.build.lib.buildeventstream.
- Position
- Below the diagonal: com.google.devtools.build.lib.runtime.commands uses a module listed above it, which is the healthy direction.
39→15 com.google.devtools.build.lib.runtime.commands uses com.google.devtools.build.lib.exec✕
- Connections
- 2 pairs of types, where a type in com.google.devtools.build.lib.runtime.commands uses a type in com.google.devtools.build.lib.exec.
- The types involved
com.google.devtools.build.lib.runtime.commands.RunCommand→com.google.devtools.build.lib.exec.RunfilesTreeUpdatercom.google.devtools.build.lib.runtime.commands.RunCommand→com.google.devtools.build.lib.exec.TestPolicy
- Direction
- com.google.devtools.build.lib.runtime.commands uses com.google.devtools.build.lib.exec, so a change to com.google.devtools.build.lib.exec can break com.google.devtools.build.lib.runtime.commands, while a change to com.google.devtools.build.lib.runtime.commands can't break com.google.devtools.build.lib.exec.
- Position
- Below the diagonal: com.google.devtools.build.lib.runtime.commands uses a module listed above it, which is the healthy direction.
39→16 com.google.devtools.build.lib.runtime.commands uses com.google.devtools.build.lib.query2.common✕
- Connections
- 4 pairs of types, where a type in com.google.devtools.build.lib.runtime.commands uses a type in com.google.devtools.build.lib.query2.common.
- The types involved
com.google.devtools.build.lib.runtime.commands.QueryCommand→com.google.devtools.build.lib.query2.common.AbstractBlazeQueryEnvironmentcom.google.devtools.build.lib.runtime.commands.QueryEnvironmentBasedCommand→com.google.devtools.build.lib.query2.common.AbstractBlazeQueryEnvironmentcom.google.devtools.build.lib.runtime.commands.QueryEnvironmentBasedCommand→com.google.devtools.build.lib.query2.common.UniverseScopecom.google.devtools.build.lib.runtime.commands.QueryOptionHelper→com.google.devtools.build.lib.query2.common.CommonQueryOptions
- Direction
- com.google.devtools.build.lib.runtime.commands uses com.google.devtools.build.lib.query2.common, so a change to com.google.devtools.build.lib.query2.common can break com.google.devtools.build.lib.runtime.commands, while a change to com.google.devtools.build.lib.runtime.commands can't break com.google.devtools.build.lib.query2.common.
- Position
- Below the diagonal: com.google.devtools.build.lib.runtime.commands uses a module listed above it, which is the healthy direction.
39→19 com.google.devtools.build.lib.runtime.commands uses com.google.devtools.build.lib.skyframe.serialization.analysis✕
- Connections
- 1 pair of types, where a type in com.google.devtools.build.lib.runtime.commands uses a type in com.google.devtools.build.lib.skyframe.serialization.analysis.
- The types involved
com.google.devtools.build.lib.runtime.commands.DumpCommand→com.google.devtools.build.lib.skyframe.serialization.analysis.RemoteAnalysisCachingServicesSupplier
- Direction
- com.google.devtools.build.lib.runtime.commands uses com.google.devtools.build.lib.skyframe.serialization.analysis, so a change to com.google.devtools.build.lib.skyframe.serialization.analysis can break com.google.devtools.build.lib.runtime.commands, while a change to com.google.devtools.build.lib.runtime.commands can't break com.google.devtools.build.lib.skyframe.serialization.analysis.
- Position
- Below the diagonal: com.google.devtools.build.lib.runtime.commands uses a module listed above it, which is the healthy direction.
39→23 com.google.devtools.build.lib.runtime.commands uses com.google.devtools.build.lib.buildtool✕
- Connections
- 5 pairs of types, where a type in com.google.devtools.build.lib.runtime.commands uses a type in com.google.devtools.build.lib.buildtool.
- The types involved
com.google.devtools.build.lib.runtime.commands.Builder→com.google.devtools.build.lib.buildtool.PathPrettyPrintercom.google.devtools.build.lib.runtime.commands.PrintActionRunner→com.google.devtools.build.lib.buildtool.BuildResultcom.google.devtools.build.lib.runtime.commands.RunCommand→com.google.devtools.build.lib.buildtool.BuildResultcom.google.devtools.build.lib.runtime.commands.TestCommand→com.google.devtools.build.lib.buildtool.BuildRequestcom.google.devtools.build.lib.runtime.commands.TestCommand→com.google.devtools.build.lib.buildtool.BuildResult
- Direction
- com.google.devtools.build.lib.runtime.commands uses com.google.devtools.build.lib.buildtool, so a change to com.google.devtools.build.lib.buildtool can break com.google.devtools.build.lib.runtime.commands, while a change to com.google.devtools.build.lib.runtime.commands can't break com.google.devtools.build.lib.buildtool.
- Position
- Below the diagonal: com.google.devtools.build.lib.runtime.commands uses a module listed above it, which is the healthy direction.
39→24 com.google.devtools.build.lib.runtime.commands uses com.google.devtools.build.lib.skyframe✕
- Connections
- 2 pairs of types, where a type in com.google.devtools.build.lib.runtime.commands uses a type in com.google.devtools.build.lib.skyframe.
- The types involved
com.google.devtools.build.lib.runtime.commands.DumpCommand→com.google.devtools.build.lib.skyframe.SkyKeyStatscom.google.devtools.build.lib.runtime.commands.DumpCommand→com.google.devtools.build.lib.skyframe.SkyframeExecutor
- Direction
- com.google.devtools.build.lib.runtime.commands uses com.google.devtools.build.lib.skyframe, so a change to com.google.devtools.build.lib.skyframe can break com.google.devtools.build.lib.runtime.commands, while a change to com.google.devtools.build.lib.runtime.commands can't break com.google.devtools.build.lib.skyframe.
- Position
- Below the diagonal: com.google.devtools.build.lib.runtime.commands uses a module listed above it, which is the healthy direction.
39→25 com.google.devtools.build.lib.runtime.commands uses com.google.devtools.build.lib.packages✕
- Connections
- 5 pairs of types, where a type in com.google.devtools.build.lib.runtime.commands uses a type in com.google.devtools.build.lib.packages.
- The types involved
com.google.devtools.build.lib.runtime.commands.PrintActionRunner→com.google.devtools.build.lib.packages.Targetcom.google.devtools.build.lib.runtime.commands.QueryCommand→com.google.devtools.build.lib.packages.Targetcom.google.devtools.build.lib.runtime.commands.QueryEnvironmentBasedCommand→com.google.devtools.build.lib.packages.LabelPrintercom.google.devtools.build.lib.runtime.commands.QueryEnvironmentBasedCommand→com.google.devtools.build.lib.packages.Targetcom.google.devtools.build.lib.runtime.commands.RunCommand→com.google.devtools.build.lib.packages.Target
- Direction
- com.google.devtools.build.lib.runtime.commands uses com.google.devtools.build.lib.packages, so a change to com.google.devtools.build.lib.packages can break com.google.devtools.build.lib.runtime.commands, while a change to com.google.devtools.build.lib.runtime.commands can't break com.google.devtools.build.lib.packages.
- Position
- Below the diagonal: com.google.devtools.build.lib.runtime.commands uses a module listed above it, which is the healthy direction.
39→28 com.google.devtools.build.lib.runtime.commands uses com.google.devtools.build.lib.runtime✕
- Connections
- 69 pairs of types, where a type in com.google.devtools.build.lib.runtime.commands uses a type in com.google.devtools.build.lib.runtime. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.google.devtools.build.lib.runtime.commands.ActionFilter→com.google.devtools.build.lib.runtime.CommandEnvironmentcom.google.devtools.build.lib.runtime.commands.AqueryCommand→com.google.devtools.build.lib.runtime.BlazeCommandcom.google.devtools.build.lib.runtime.commands.AqueryCommand→com.google.devtools.build.lib.runtime.BlazeCommandResultcom.google.devtools.build.lib.runtime.commands.AqueryCommand→com.google.devtools.build.lib.runtime.CommandEnvironmentcom.google.devtools.build.lib.runtime.commands.BuildCommand→com.google.devtools.build.lib.runtime.BlazeCommandcom.google.devtools.build.lib.runtime.commands.BuildCommand→com.google.devtools.build.lib.runtime.BlazeCommandResultcom.google.devtools.build.lib.runtime.commands.BuildCommand→com.google.devtools.build.lib.runtime.CommandEnvironmentcom.google.devtools.build.lib.runtime.commands.BuiltinCommandModule→com.google.devtools.build.lib.runtime.BlazeModulecom.google.devtools.build.lib.runtime.commands.BuiltinCommandModule→com.google.devtools.build.lib.runtime.ServerBuildercom.google.devtools.build.lib.runtime.commands.CanonicalizeCommand→com.google.devtools.build.lib.runtime.BlazeCommandcom.google.devtools.build.lib.runtime.commands.CanonicalizeCommand→com.google.devtools.build.lib.runtime.BlazeCommandResultcom.google.devtools.build.lib.runtime.commands.CanonicalizeCommand→com.google.devtools.build.lib.runtime.CommandEnvironmentcom.google.devtools.build.lib.runtime.commands.CleanCommand→com.google.devtools.build.lib.runtime.BlazeCommandcom.google.devtools.build.lib.runtime.commands.CleanCommand→com.google.devtools.build.lib.runtime.BlazeCommandResultcom.google.devtools.build.lib.runtime.commands.CleanCommand→com.google.devtools.build.lib.runtime.CommandEnvironmentcom.google.devtools.build.lib.runtime.commands.CommandOptionVisitor→com.google.devtools.build.lib.runtime.Commandcom.google.devtools.build.lib.runtime.commands.ConfigCommand→com.google.devtools.build.lib.runtime.BlazeCommandcom.google.devtools.build.lib.runtime.commands.ConfigCommand→com.google.devtools.build.lib.runtime.BlazeCommandResultcom.google.devtools.build.lib.runtime.commands.ConfigCommand→com.google.devtools.build.lib.runtime.CommandEnvironmentcom.google.devtools.build.lib.runtime.commands.CqueryCommand→com.google.devtools.build.lib.runtime.BlazeCommandcom.google.devtools.build.lib.runtime.commands.CqueryCommand→com.google.devtools.build.lib.runtime.BlazeCommandResultcom.google.devtools.build.lib.runtime.commands.CqueryCommand→com.google.devtools.build.lib.runtime.CommandEnvironmentcom.google.devtools.build.lib.runtime.commands.DumpCommand→com.google.devtools.build.lib.runtime.BlazeCommandcom.google.devtools.build.lib.runtime.commands.DumpCommand→com.google.devtools.build.lib.runtime.BlazeCommandResultcom.google.devtools.build.lib.runtime.commands.DumpCommand→com.google.devtools.build.lib.runtime.BlazeRuntime
- Direction
- com.google.devtools.build.lib.runtime.commands uses com.google.devtools.build.lib.runtime, so a change to com.google.devtools.build.lib.runtime can break com.google.devtools.build.lib.runtime.commands, while a change to com.google.devtools.build.lib.runtime.commands can't break com.google.devtools.build.lib.runtime.
- Position
- Below the diagonal: com.google.devtools.build.lib.runtime.commands uses a module listed above it, which is the healthy direction.
39→29 com.google.devtools.build.lib.runtime.commands uses com.google.devtools.build.lib.skyframe.serialization✕
- Connections
- 1 pair of types, where a type in com.google.devtools.build.lib.runtime.commands uses a type in com.google.devtools.build.lib.skyframe.serialization.
- The types involved
com.google.devtools.build.lib.runtime.commands.DumpCommand→com.google.devtools.build.lib.skyframe.serialization.ObjectCodecs
- Direction
- com.google.devtools.build.lib.runtime.commands uses com.google.devtools.build.lib.skyframe.serialization, so a change to com.google.devtools.build.lib.skyframe.serialization can break com.google.devtools.build.lib.runtime.commands, while a change to com.google.devtools.build.lib.runtime.commands can't break com.google.devtools.build.lib.skyframe.serialization.
- Position
- Below the diagonal: com.google.devtools.build.lib.runtime.commands uses a module listed above it, which is the healthy direction.
39→31 com.google.devtools.build.lib.runtime.commands uses com.google.devtools.build.lib.cmdline✕
- Connections
- 2 pairs of types, where a type in com.google.devtools.build.lib.runtime.commands uses a type in com.google.devtools.build.lib.cmdline.
- The types involved
com.google.devtools.build.lib.runtime.commands.QueryEnvironmentBasedCommand→com.google.devtools.build.lib.cmdline.Parsercom.google.devtools.build.lib.runtime.commands.TestCommand→com.google.devtools.build.lib.cmdline.RepositoryMapping
- Direction
- com.google.devtools.build.lib.runtime.commands uses com.google.devtools.build.lib.cmdline, so a change to com.google.devtools.build.lib.cmdline can break com.google.devtools.build.lib.runtime.commands, while a change to com.google.devtools.build.lib.runtime.commands can't break com.google.devtools.build.lib.cmdline.
- Position
- Below the diagonal: com.google.devtools.build.lib.runtime.commands uses a module listed above it, which is the healthy direction.
39→33 com.google.devtools.build.lib.runtime.commands uses com.google.devtools.build.lib.analysis.config✕
- Connections
- 8 pairs of types, where a type in com.google.devtools.build.lib.runtime.commands uses a type in com.google.devtools.build.lib.analysis.config.
- The types involved
com.google.devtools.build.lib.runtime.commands.BuiltTargets→com.google.devtools.build.lib.analysis.config.BuildConfigurationValuecom.google.devtools.build.lib.runtime.commands.ConfigCommand→com.google.devtools.build.lib.analysis.config.BuildConfigurationValuecom.google.devtools.build.lib.runtime.commands.ConfigCommand→com.google.devtools.build.lib.analysis.config.Fragmentcom.google.devtools.build.lib.runtime.commands.ConfigCommand→com.google.devtools.build.lib.analysis.config.FragmentOptionscom.google.devtools.build.lib.runtime.commands.ConfigCommand→com.google.devtools.build.lib.analysis.config.FragmentRegistrycom.google.devtools.build.lib.runtime.commands.InfoCommand→com.google.devtools.build.lib.analysis.config.BuildConfigurationValuecom.google.devtools.build.lib.runtime.commands.RunCommand→com.google.devtools.build.lib.analysis.config.BuildConfigurationValuecom.google.devtools.build.lib.runtime.commands.RunCommand→com.google.devtools.build.lib.analysis.config.RunUnder
- Direction
- com.google.devtools.build.lib.runtime.commands uses com.google.devtools.build.lib.analysis.config, so a change to com.google.devtools.build.lib.analysis.config can break com.google.devtools.build.lib.runtime.commands, while a change to com.google.devtools.build.lib.runtime.commands can't break com.google.devtools.build.lib.analysis.config.
- Position
- Below the diagonal: com.google.devtools.build.lib.runtime.commands uses a module listed above it, which is the healthy direction.
39→35 com.google.devtools.build.lib.runtime.commands uses com.google.devtools.build.lib.analysis✕
- Connections
- 7 pairs of types, where a type in com.google.devtools.build.lib.runtime.commands uses a type in com.google.devtools.build.lib.analysis.
- The types involved
com.google.devtools.build.lib.runtime.commands.ActionFilter→com.google.devtools.build.lib.analysis.ConfiguredTargetcom.google.devtools.build.lib.runtime.commands.BuiltTargets→com.google.devtools.build.lib.analysis.ConfiguredTargetcom.google.devtools.build.lib.runtime.commands.BuiltTargets→com.google.devtools.build.lib.analysis.RunfilesSupportcom.google.devtools.build.lib.runtime.commands.PrintActionRunner→com.google.devtools.build.lib.analysis.ConfiguredTargetcom.google.devtools.build.lib.runtime.commands.RunCommand→com.google.devtools.build.lib.analysis.ConfiguredTargetcom.google.devtools.build.lib.runtime.commands.RunCommand→com.google.devtools.build.lib.analysis.RunfilesSupportcom.google.devtools.build.lib.runtime.commands.VersionCommand→com.google.devtools.build.lib.analysis.BlazeVersionInfo
- Direction
- com.google.devtools.build.lib.runtime.commands uses com.google.devtools.build.lib.analysis, so a change to com.google.devtools.build.lib.analysis can break com.google.devtools.build.lib.runtime.commands, while a change to com.google.devtools.build.lib.runtime.commands can't break com.google.devtools.build.lib.analysis.
- Position
- Below the diagonal: com.google.devtools.build.lib.runtime.commands uses a module listed above it, which is the healthy direction.
39→37 com.google.devtools.build.lib.runtime.commands uses com.google.devtools.build.lib.actions✕
- Connections
- 5 pairs of types, where a type in com.google.devtools.build.lib.runtime.commands uses a type in com.google.devtools.build.lib.actions.
- The types involved
com.google.devtools.build.lib.runtime.commands.1→com.google.devtools.build.lib.actions.ActionAnalysisMetadatacom.google.devtools.build.lib.runtime.commands.ActionFilter→com.google.devtools.build.lib.actions.ActionAnalysisMetadatacom.google.devtools.build.lib.runtime.commands.PrintActionRunner→com.google.devtools.build.lib.actions.ActionAnalysisMetadatacom.google.devtools.build.lib.runtime.commands.PrintActionRunner→com.google.devtools.build.lib.actions.ActionGraphcom.google.devtools.build.lib.runtime.commands.PrintActionRunner→com.google.devtools.build.lib.actions.ActionKeyContext
- Direction
- com.google.devtools.build.lib.runtime.commands uses com.google.devtools.build.lib.actions, so a change to com.google.devtools.build.lib.actions can break com.google.devtools.build.lib.runtime.commands, while a change to com.google.devtools.build.lib.runtime.commands can't break com.google.devtools.build.lib.actions.
- Position
- Below the diagonal: com.google.devtools.build.lib.runtime.commands uses a module listed above it, which is the healthy direction.
40→2 com.google.devtools.build.lib.bazel uses com.google.devtools.build.lib.events✕
- Connections
- 1 pair of types, where a type in com.google.devtools.build.lib.bazel uses a type in com.google.devtools.build.lib.events.
- The types involved
com.google.devtools.build.lib.bazel.CacheHitReportingModule→com.google.devtools.build.lib.events.Reporter
- Direction
- com.google.devtools.build.lib.bazel uses com.google.devtools.build.lib.events, so a change to com.google.devtools.build.lib.events can break com.google.devtools.build.lib.bazel, while a change to com.google.devtools.build.lib.bazel can't break com.google.devtools.build.lib.events.
- Position
- Below the diagonal: com.google.devtools.build.lib.bazel uses a module listed above it, which is the healthy direction.
40→3 com.google.devtools.build.lib.bazel uses com.google.devtools.common.options✕
- Connections
- 7 pairs of types, where a type in com.google.devtools.build.lib.bazel uses a type in com.google.devtools.common.options.
- The types involved
com.google.devtools.build.lib.bazel.BazelDiffAwarenessModule→com.google.devtools.common.options.OptionsBasecom.google.devtools.build.lib.bazel.BazelFileSystemModule→com.google.devtools.common.options.OptionsParsingResultcom.google.devtools.build.lib.bazel.BazelRepositoryModule→com.google.devtools.common.options.OptionsBasecom.google.devtools.build.lib.bazel.BazelRepositoryModule→com.google.devtools.common.options.OptionsParsingResultcom.google.devtools.build.lib.bazel.BazelStartupOptionsModule→com.google.devtools.common.options.OptionsBasecom.google.devtools.build.lib.bazel.BazelWorkspaceStatusModule→com.google.devtools.common.options.OptionsBasecom.google.devtools.build.lib.bazel.Options→com.google.devtools.common.options.OptionsBase
- Direction
- com.google.devtools.build.lib.bazel uses com.google.devtools.common.options, so a change to com.google.devtools.common.options can break com.google.devtools.build.lib.bazel, while a change to com.google.devtools.build.lib.bazel can't break com.google.devtools.common.options.
- Position
- Below the diagonal: com.google.devtools.build.lib.bazel uses a module listed above it, which is the healthy direction.
40→8 com.google.devtools.build.lib.bazel uses com.google.devtools.build.lib.vfs✕
- Connections
- 8 pairs of types, where a type in com.google.devtools.build.lib.bazel uses a type in com.google.devtools.build.lib.vfs.
- The types involved
com.google.devtools.build.lib.bazel.BazelRepositoryModule→com.google.devtools.build.lib.vfs.FileSystemcom.google.devtools.build.lib.bazel.BazelRepositoryModule→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.bazel.BazelRepositoryModule→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.bazel.BazelWorkspaceStatusAction→com.google.devtools.build.lib.vfs.BulkDeletercom.google.devtools.build.lib.bazel.BazelWorkspaceStatusAction→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.bazel.SpawnLogModule→com.google.devtools.build.lib.vfs.Pathcom.google.devtools.build.lib.bazel.SpawnLogModule→com.google.devtools.build.lib.vfs.PathFragmentcom.google.devtools.build.lib.bazel.SpawnLogModule→com.google.devtools.build.lib.vfs.XattrProvider
- Direction
- com.google.devtools.build.lib.bazel uses com.google.devtools.build.lib.vfs, so a change to com.google.devtools.build.lib.vfs can break com.google.devtools.build.lib.bazel, while a change to com.google.devtools.build.lib.bazel can't break com.google.devtools.build.lib.vfs.
- Position
- Below the diagonal: com.google.devtools.build.lib.bazel uses a module listed above it, which is the healthy direction.
40→11 com.google.devtools.build.lib.bazel uses com.google.devtools.build.lib.util✕
- Connections
- 6 pairs of types, where a type in com.google.devtools.build.lib.bazel uses a type in com.google.devtools.build.lib.util.
- The types involved
com.google.devtools.build.lib.bazel.BazelRepositoryModule→com.google.devtools.build.lib.util.AbruptExitExceptioncom.google.devtools.build.lib.bazel.BazelRepositoryModule→com.google.devtools.build.lib.util.DetailedExitCodecom.google.devtools.build.lib.bazel.BazelWorkspaceStatusModule→com.google.devtools.build.lib.util.DetailedExitCodecom.google.devtools.build.lib.bazel.CacheHitReportingModule→com.google.devtools.build.lib.util.Paircom.google.devtools.build.lib.bazel.SpawnLogModule→com.google.devtools.build.lib.util.AbruptExitExceptioncom.google.devtools.build.lib.bazel.SpawnLogModule→com.google.devtools.build.lib.util.DetailedExitCode
- Direction
- com.google.devtools.build.lib.bazel uses com.google.devtools.build.lib.util, so a change to com.google.devtools.build.lib.util can break com.google.devtools.build.lib.bazel, while a change to com.google.devtools.build.lib.bazel can't break com.google.devtools.build.lib.util.
- Position
- Below the diagonal: com.google.devtools.build.lib.bazel uses a module listed above it, which is the healthy direction.
40→13 com.google.devtools.build.lib.bazel uses com.google.devtools.build.lib.bazel.bzlmod✕
- Connections
- 7 pairs of types, where a type in com.google.devtools.build.lib.bazel uses a type in com.google.devtools.build.lib.bazel.bzlmod.
- The types involved
com.google.devtools.build.lib.bazel.BazelRepositoryModule→com.google.devtools.build.lib.bazel.bzlmod.ModuleFileFunctioncom.google.devtools.build.lib.bazel.BazelRepositoryModule→com.google.devtools.build.lib.bazel.bzlmod.ModuleOverridecom.google.devtools.build.lib.bazel.BazelRepositoryModule→com.google.devtools.build.lib.bazel.bzlmod.NonRegistryOverridecom.google.devtools.build.lib.bazel.BazelRepositoryModule→com.google.devtools.build.lib.bazel.bzlmod.RegistryFactoryImplcom.google.devtools.build.lib.bazel.BazelRepositoryModule→com.google.devtools.build.lib.bazel.bzlmod.RepoSpecFunctioncom.google.devtools.build.lib.bazel.BazelRepositoryModule→com.google.devtools.build.lib.bazel.bzlmod.SingleExtensionEvalFunctioncom.google.devtools.build.lib.bazel.BazelRepositoryModule→com.google.devtools.build.lib.bazel.bzlmod.YankedVersionsFunction
- Direction
- com.google.devtools.build.lib.bazel uses com.google.devtools.build.lib.bazel.bzlmod, so a change to com.google.devtools.build.lib.bazel.bzlmod can break com.google.devtools.build.lib.bazel, while a change to com.google.devtools.build.lib.bazel can't break com.google.devtools.build.lib.bazel.bzlmod.
- Position
- Below the diagonal: com.google.devtools.build.lib.bazel uses a module listed above it, which is the healthy direction.
40→15 com.google.devtools.build.lib.bazel uses com.google.devtools.build.lib.exec✕
- Connections
- 4 pairs of types, where a type in com.google.devtools.build.lib.bazel uses a type in com.google.devtools.build.lib.exec.
- The types involved
com.google.devtools.build.lib.bazel.BazelWorkspaceStatusModule→com.google.devtools.build.lib.exec.Buildercom.google.devtools.build.lib.bazel.SpawnLogModule→com.google.devtools.build.lib.exec.Buildercom.google.devtools.build.lib.bazel.SpawnLogModule→com.google.devtools.build.lib.exec.ExecutorBuildercom.google.devtools.build.lib.bazel.SpawnLogModule→com.google.devtools.build.lib.exec.SpawnLogContext
- Direction
- com.google.devtools.build.lib.bazel uses com.google.devtools.build.lib.exec, so a change to com.google.devtools.build.lib.exec can break com.google.devtools.build.lib.bazel, while a change to com.google.devtools.build.lib.bazel can't break com.google.devtools.build.lib.exec.
- Position
- Below the diagonal: com.google.devtools.build.lib.bazel uses a module listed above it, which is the healthy direction.
40→23 com.google.devtools.build.lib.bazel uses com.google.devtools.build.lib.buildtool✕
- Connections
- 2 pairs of types, where a type in com.google.devtools.build.lib.bazel uses a type in com.google.devtools.build.lib.buildtool.
- The types involved
com.google.devtools.build.lib.bazel.BazelWorkspaceStatusModule→com.google.devtools.build.lib.buildtool.BuildRequestcom.google.devtools.build.lib.bazel.SpawnLogModule→com.google.devtools.build.lib.buildtool.BuildRequest
- Direction
- com.google.devtools.build.lib.bazel uses com.google.devtools.build.lib.buildtool, so a change to com.google.devtools.build.lib.buildtool can break com.google.devtools.build.lib.bazel, while a change to com.google.devtools.build.lib.bazel can't break com.google.devtools.build.lib.buildtool.
- Position
- Below the diagonal: com.google.devtools.build.lib.bazel uses a module listed above it, which is the healthy direction.
40→24 com.google.devtools.build.lib.bazel uses com.google.devtools.build.lib.skyframe✕
- Connections
- 2 pairs of types, where a type in com.google.devtools.build.lib.bazel uses a type in com.google.devtools.build.lib.skyframe.
- The types involved
com.google.devtools.build.lib.bazel.BazelRepositoryModule→com.google.devtools.build.lib.skyframe.MutableSuppliercom.google.devtools.build.lib.bazel.BazelStatusActionFactory→com.google.devtools.build.lib.skyframe.WorkspaceInfoFromDiff
- Direction
- com.google.devtools.build.lib.bazel uses com.google.devtools.build.lib.skyframe, so a change to com.google.devtools.build.lib.skyframe can break com.google.devtools.build.lib.bazel, while a change to com.google.devtools.build.lib.bazel can't break com.google.devtools.build.lib.skyframe.
- Position
- Below the diagonal: com.google.devtools.build.lib.bazel uses a module listed above it, which is the healthy direction.
40→28 com.google.devtools.build.lib.bazel uses com.google.devtools.build.lib.runtime✕
- Connections
- 24 pairs of types, where a type in com.google.devtools.build.lib.bazel uses a type in com.google.devtools.build.lib.runtime.
- The types involved
com.google.devtools.build.lib.bazel.Bazel→com.google.devtools.build.lib.runtime.BlazeModulecom.google.devtools.build.lib.bazel.BazelDiffAwarenessModule→com.google.devtools.build.lib.runtime.BlazeModulecom.google.devtools.build.lib.bazel.BazelDiffAwarenessModule→com.google.devtools.build.lib.runtime.BlazeRuntimecom.google.devtools.build.lib.bazel.BazelDiffAwarenessModule→com.google.devtools.build.lib.runtime.WorkspaceBuildercom.google.devtools.build.lib.bazel.BazelFileSystemModule→com.google.devtools.build.lib.runtime.BlazeModulecom.google.devtools.build.lib.bazel.BazelFileSystemModule→com.google.devtools.build.lib.runtime.BlazeServicecom.google.devtools.build.lib.bazel.BazelRepositoryModule→com.google.devtools.build.lib.runtime.BlazeModulecom.google.devtools.build.lib.bazel.BazelRepositoryModule→com.google.devtools.build.lib.runtime.BlazeRuntimecom.google.devtools.build.lib.bazel.BazelRepositoryModule→com.google.devtools.build.lib.runtime.CommandEnvironmentcom.google.devtools.build.lib.bazel.BazelRepositoryModule→com.google.devtools.build.lib.runtime.ServerBuildercom.google.devtools.build.lib.bazel.BazelRepositoryModule→com.google.devtools.build.lib.runtime.WorkspaceBuildercom.google.devtools.build.lib.bazel.BazelServices→com.google.devtools.build.lib.runtime.BlazeServicecom.google.devtools.build.lib.bazel.BazelStartupOptionsModule→com.google.devtools.build.lib.runtime.BlazeModulecom.google.devtools.build.lib.bazel.BazelWorkspaceStatusActionContext→com.google.devtools.build.lib.runtime.CommandEnvironmentcom.google.devtools.build.lib.bazel.BazelWorkspaceStatusModule→com.google.devtools.build.lib.runtime.BlazeModulecom.google.devtools.build.lib.bazel.BazelWorkspaceStatusModule→com.google.devtools.build.lib.runtime.BlazeRuntimecom.google.devtools.build.lib.bazel.BazelWorkspaceStatusModule→com.google.devtools.build.lib.runtime.CommandEnvironmentcom.google.devtools.build.lib.bazel.BazelWorkspaceStatusModule→com.google.devtools.build.lib.runtime.WorkspaceBuildercom.google.devtools.build.lib.bazel.CacheHitReportingModule→com.google.devtools.build.lib.runtime.BlazeModulecom.google.devtools.build.lib.bazel.CacheHitReportingModule→com.google.devtools.build.lib.runtime.CommandEnvironmentcom.google.devtools.build.lib.bazel.RepositoryCacheInfoItem→com.google.devtools.build.lib.runtime.CommandEnvironmentcom.google.devtools.build.lib.bazel.RepositoryCacheInfoItem→com.google.devtools.build.lib.runtime.InfoItemcom.google.devtools.build.lib.bazel.SpawnLogModule→com.google.devtools.build.lib.runtime.BlazeModulecom.google.devtools.build.lib.bazel.SpawnLogModule→com.google.devtools.build.lib.runtime.CommandEnvironment
- Direction
- com.google.devtools.build.lib.bazel uses com.google.devtools.build.lib.runtime, so a change to com.google.devtools.build.lib.runtime can break com.google.devtools.build.lib.bazel, while a change to com.google.devtools.build.lib.bazel can't break com.google.devtools.build.lib.runtime.
- Position
- Below the diagonal: com.google.devtools.build.lib.bazel uses a module listed above it, which is the healthy direction.
40→33 com.google.devtools.build.lib.bazel uses com.google.devtools.build.lib.analysis.config✕
- Connections
- 1 pair of types, where a type in com.google.devtools.build.lib.bazel uses a type in com.google.devtools.build.lib.analysis.config.
- The types involved
com.google.devtools.build.lib.bazel.RepositoryCacheInfoItem→com.google.devtools.build.lib.analysis.config.BuildConfigurationValue
- Direction
- com.google.devtools.build.lib.bazel uses com.google.devtools.build.lib.analysis.config, so a change to com.google.devtools.build.lib.analysis.config can break com.google.devtools.build.lib.bazel, while a change to com.google.devtools.build.lib.bazel can't break com.google.devtools.build.lib.analysis.config.
- Position
- Below the diagonal: com.google.devtools.build.lib.bazel uses a module listed above it, which is the healthy direction.
40→35 com.google.devtools.build.lib.bazel uses com.google.devtools.build.lib.analysis✕
- Connections
- 9 pairs of types, where a type in com.google.devtools.build.lib.bazel uses a type in com.google.devtools.build.lib.analysis.
- The types involved
com.google.devtools.build.lib.bazel.BazelDiffAwarenessModule→com.google.devtools.build.lib.analysis.BlazeDirectoriescom.google.devtools.build.lib.bazel.BazelRepositoryModule→com.google.devtools.build.lib.analysis.BlazeDirectoriescom.google.devtools.build.lib.bazel.BazelRepositoryModule→com.google.devtools.build.lib.analysis.Buildercom.google.devtools.build.lib.bazel.BazelStatusActionFactory→com.google.devtools.build.lib.analysis.Environmentcom.google.devtools.build.lib.bazel.BazelStatusActionFactory→com.google.devtools.build.lib.analysis.Factorycom.google.devtools.build.lib.bazel.BazelStatusActionFactory→com.google.devtools.build.lib.analysis.WorkspaceStatusActioncom.google.devtools.build.lib.bazel.BazelWorkspaceStatusAction→com.google.devtools.build.lib.analysis.WorkspaceStatusActioncom.google.devtools.build.lib.bazel.BazelWorkspaceStatusActionContext→com.google.devtools.build.lib.analysis.Contextcom.google.devtools.build.lib.bazel.BazelWorkspaceStatusModule→com.google.devtools.build.lib.analysis.BlazeDirectories
- Direction
- com.google.devtools.build.lib.bazel uses com.google.devtools.build.lib.analysis, so a change to com.google.devtools.build.lib.analysis can break com.google.devtools.build.lib.bazel, while a change to com.google.devtools.build.lib.bazel can't break com.google.devtools.build.lib.analysis.
- Position
- Below the diagonal: com.google.devtools.build.lib.bazel uses a module listed above it, which is the healthy direction.
40→37 com.google.devtools.build.lib.bazel uses com.google.devtools.build.lib.actions✕
- Connections
- 4 pairs of types, where a type in com.google.devtools.build.lib.bazel uses a type in com.google.devtools.build.lib.actions.
- The types involved
com.google.devtools.build.lib.bazel.BazelWorkspaceStatusAction→com.google.devtools.build.lib.actions.ActionExecutionContextcom.google.devtools.build.lib.bazel.BazelWorkspaceStatusAction→com.google.devtools.build.lib.actions.ActionResultcom.google.devtools.build.lib.bazel.BazelWorkspaceStatusAction→com.google.devtools.build.lib.actions.Artifactcom.google.devtools.build.lib.bazel.BazelWorkspaceStatusAction→com.google.devtools.build.lib.actions.ArtifactPathResolver
- Direction
- com.google.devtools.build.lib.bazel uses com.google.devtools.build.lib.actions, so a change to com.google.devtools.build.lib.actions can break com.google.devtools.build.lib.bazel, while a change to com.google.devtools.build.lib.bazel can't break com.google.devtools.build.lib.actions.
- Position
- Below the diagonal: com.google.devtools.build.lib.bazel uses a module listed above it, which is the healthy direction.
40→39 com.google.devtools.build.lib.bazel uses com.google.devtools.build.lib.runtime.commands✕
- Connections
- 1 pair of types, where a type in com.google.devtools.build.lib.bazel uses a type in com.google.devtools.build.lib.runtime.commands.
- The types involved
com.google.devtools.build.lib.bazel.BazelBuiltinCommandModule→com.google.devtools.build.lib.runtime.commands.BuiltinCommandModule
- Direction
- com.google.devtools.build.lib.bazel uses com.google.devtools.build.lib.runtime.commands, so a change to com.google.devtools.build.lib.runtime.commands can break com.google.devtools.build.lib.bazel, while a change to com.google.devtools.build.lib.bazel can't break com.google.devtools.build.lib.runtime.commands.
- Position
- Below the diagonal: com.google.devtools.build.lib.bazel 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 |
|---|---|---|
| A07:2025 — Authentication Failures | 12 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 7 | High / Critical |
| A05:2025 — Injection | 5 | High / Critical |
Roadmap
Begin by documenting significant design decisions in the docs/adr folder and updating the README with clear instructions for running tests. Next, address the specific documentation quality issue in the command-line reference and resolve the orphaned knowledge finding for InvalidatingNodeVisitor.java. Finally, immediately remediate the three leaked secrets found in REDACTED to secure the codebase.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 Documentation finding(s) in Documentation Quality — start with command-line-reference-suffix.html. | +3.2 pts | Low | Documentation Quality |
| Resolve the 1 Orphaned knowledge finding(s) in Knowledge Freshness — start with InvalidatingNodeVisitor.java. | +2.7 pts | Low | Knowledge Freshness |
| Resolve the 3 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (3). | +2.4 pts | Low | REDACTED Scanning |
| 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. | +4.6 pts | Medium | Architecture documentation |
| Resolve the 1 Banned license finding(s) in License Compliance. | +1.7 pts | Low | License Compliance |
| Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite. | +2.8 pts | Medium | Documentation (README) |
| Automate the release in CI — a deploy stage for a service (Helm/Kubernetes manifests or an equivalent rollout), or a tag-triggered publish job for an artifact — so releases are repeatable and reversible. | +1.9 pts | Medium | Deployment & Rollback |
| Resolve the 17 No assertions (empty test) finding(s) in Test Quality — start with PostAnalysisQueryTest.java (9), NonconfigurableAttributeMapperTest.java (2), StarlarkAttrTransitionProviderTest.java (2). | +1.7 pts | Medium | Test Quality |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| src/test/java/com/google/devtools/build/lib/analysis/starlark/StarlarkAttrTransitionProviderTest.java | 1.0 | Slop | Test Quality: No assertions (empty test): testOptionConversionCrosstoolTop |
| src/main/java/com/google/devtools/build/lib/remote/RemoteModule.java | 1.5 | Slop | Change Coupling: Boundary-crossing change coupling: RemoteModule.java ↔ OnDiskBlobStoreCache.java |
| src/test/java/com/google/devtools/build/lib/query2/testutil/PostAnalysisQueryTest.java | 3.2 | Slop | Test Quality: No assertions (empty test): boundedDepsWithError |
| REDACTED | 5.1 | Mixed | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 5.1 | Mixed | Dependency Vulnerabilities: Critical vulnerability: REDACTED |
| src/test/java/com/google/devtools/build/lib/testutil/TestInterruptingBugReporterTest.java | 5.4 | Mixed | Test Quality: No assertions (empty test): passing |
| src/test/java/com/google/devtools/build/lib/analysis/select/NonconfigurableAttributeMapperTest.java | 5.5 | Mixed | Test Quality: No assertions (empty test): testAttributeTypeChecking |
| src/main/java/com/google/devtools/build/lib/analysis/RunfilesSupport.java | 5.7 | Mixed | God Classes: ClassTooLong: RunfilesSupport |
| REDACTED | 5.8 | Mixed | Secrets (history): REDACTED: REDACTED |
| src/main/java/com/google/devtools/build/lib/remote/RemoteSpawnCache.java | 5.9 | Mixed | Cyclomatic Complexity: RemoteSpawnCache.lookup (cyclomatic 29) |
| src/main/java/com/google/devtools/build/lib/skyframe/CompletionFunction.java | 5.9 | Mixed | Cyclomatic Complexity: CompletionFunction.compute (cyclomatic 23) |
| src/main/java/com/google/devtools/build/lib/skyframe/serialization/ObjectCodecRegistry.java | 5.9 | Mixed | Cognitive Complexity: ObjectCodecRegistry.<init> (cognitive 26) |
| src/main/java/net/starlark/java/eval/EvalUtils.java | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/main/java/com/google/devtools/build/lib/analysis/starlark/StarlarkRuleClassFunctions.java | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/main/java/net/starlark/java/syntax/Lexer.java | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/main/java/com/google/devtools/build/lib/runtime/BlazeCommandDispatcher.java | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/main/java/com/google/devtools/build/lib/bazel/BazelRepositoryModule.java | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/main/java/com/google/devtools/build/lib/analysis/starlark/StarlarkAttrModule.java | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/main/java/com/google/devtools/build/lib/skyframe/GlobFunctionWithMultipleRecursiveFunctions.java | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/main/java/com/google/devtools/build/lib/rules/cpp/CcCommon.java | 6.0 | Mixed | Explicit Debt: TodoComment |
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
Watchdog 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. 62 of 65 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 3 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
What we checked — 65 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, 6106 of 6134 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, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — 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 |
| Watchdog 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 | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
| LLM (sampled · advisory) | Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement | Local LLM | ◐ LLM · sampled · advisory |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.java, .py) 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 (JaCoCo XML — `mvn jacoco:report` or the Gradle `jacocoTestReport` task, or `coverage run -m pytest` then `coverage xml`) 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 (JaCoCo XML — `mvn jacoco:report` or the Gradle `jacocoTestReport` task, or `coverage run -m pytest` then `coverage xml`) 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.
- D10 Test Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 15,327 test(s) behind this row are the ones the code-model census could read, and this repository also carries at least 56 test source file(s) (.py) that it cannot: it reads the test types the .java frontend declared, so a suite in any other language is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
- D11 Test Reliability — not measured this run — Watchdog 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 repository declares 3 of its own test(s) unreliable. The built-in reliability runner does not support this repository's ecosystem (.java, .py), so the suite was not re-run and no reliability score is given — these are the repository's own declarations, not our measurement.
- D12 Dependency Hygiene — not measured this run — Watchdog 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 — 4 Maven/Gradle manifest(s) were read, stating a version for 0 dependency(ies) and leaving 0 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
- D20 ADR Quality — not measured this run — Watchdog 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.
- D22 Internal API Consistency — not measured this run — Watchdog 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 a COLLECTOR gap, not an environment fault: no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
- D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- D32 Data Compliance (PII/GDPR) — not measured this run — Watchdog 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. `src/main/java/net/starlark/java/eval/Printer.java`, `src/main/java/net/starlark/java/eval/Starlark.java`, `src/main/java/net/starlark/java/eval/StarlarkFunction.java`, `src/main/java/net/starlark/java/syntax/Parser.java`, `src/main/java/net/starlark/java/syntax/Resolver.java`, … (+1 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- AX1 Captive dependencies — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository defines its own container in src/main/java/com/google/devtools/build/lib/skyframe/ActionExecutionFunction.java, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- C1 Data Protection — not measured this run — Watchdog 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- C3 Audit Trail — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
- C4 Data Retention — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
- C5 Data-Subject Rights — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
- ED5 Idempotency — not measured this run — Watchdog 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 decides whether a handler's mutation is safe to re-run by recognising its persistence writes (a database save, a repository write, an event publish) and its guards. Those markers are .NET member names, so in this repository's language a write such as `repository.save(order)` is not recognised and a same-named call on an unrelated library type could be. The handlers were found; their idempotency was neither confirmed nor ruled out.
- GD1 Unfinished & placeholder code — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Java, Python, c, cpp, objectivec is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- M4 Documentation accuracy — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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. 702 further occurrence(s) are not listed individually; the score already reflects all 742.
- P1 CI/CD gates — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Which of the two it is cannot be settled from this dimension's evidence; the coverage dimensions report whether a suite exists at all. You can widen what we reach: name the test runner explicitly in the pipeline step (your stack's test command, or a job named for the suite) so the gate is unambiguous to a reader and to this pass.
- 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.
- S1 Web-Security Posture — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does 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.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
- D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned REDACTED, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
- 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.
The LLM boundary
Dimensions
D1 · Cyclomatic Complexity
245 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was EvalUtils.binaryOp at 111. A further 6 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being Lexer.scanIdentifier at 65 — they are counted neither in the figure above nor in this dimension's score. 3 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: src/main/java/com/google/devtools/build/lib/profiler/memory/AllocationTracker.java (AllocationTracker.isValueClass at 32), src/main/java/com/google/devtools/build/lib/analysis/config/AutoCpuConverter.java (AutoCpuConverter.convert at 20), src/main/java/com/google/devtools/build/docgen/RuleDocumentationAttribute.java (RuleDocumentationAttribute.getAttributeInfoType at 16). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 4 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with EvalUtils.binaryOp (cyclomatic 111), StarlarkRuleClassFunctions.createRule (cyclomatic 83), Lexer.scanWord (cyclomatic 79). — 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 5.9 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
- 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
553 method(s) exceeded the cognitive complexity threshold of 15; the worst was EvalUtils.binaryOp at 174.
What to do
- Bring the 3 bodies over 120 down to 120 or less in Cognitive Complexity — start with EvalUtils.binaryOp (cognitive 174), BazelRepositoryModule.beforeCommand (cognitive 143), StarlarkRuleClassFunctions.createRule (cognitive 134). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 3 together lifts Cognitive Complexity from 5.4 to about 5.8/10, projected with the scoring formula itself and assuming each lands exactly at 120; 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
462 god class(es) detected.
What to do
- Resolve the 128 ClassTooLong finding(s) in God Classes — start with SkyframeExecutor.java, CcModuleApi.java, StarlarkBaseExternalContext.java. — One of this dimension's main actionable groups (128 warning-level).
- Resolve the 126 FileTooLong finding(s) in God Classes — start with SkyframeExecutor.java, CcModuleApi.java, StarlarkBaseExternalContext.java. — One of this dimension's main actionable groups (126 warning-level).
- Resolve the 123 TooManyMethods finding(s) in God Classes — start with RuleContext.java (2), Attribute.java (2), RuleClass.java (2). — One of this dimension's main actionable groups (123 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
245 duplicated block group(s) detected. A further 6 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted. 1 of the 251 are in trees this repository does not ship — vendored, example/demo, 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 25 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with BazelModTidyFunction.java, ModuleFileGlobals.java, VendorCommand.java. — One of this dimension's main actionable groups (25 warning-level).
- Resolve the 23 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with SkyQueryEnvironment.java (3), CompactPersistentActionCache.java, PostAnalysisQueryEnvironment.java. — One of this dimension's main actionable groups (23 warning-level).
- Resolve the 20 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with CppCompileAction.java (2), StarlarkActionFactory.java, ModuleFileFunction.java. — One of this dimension's main actionable groups (20 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
119 production modules (Gradle+Bazel), 0 dependency cycle(s), 1 unstable depended-on module(s). Read from the build's own module declarations; edges a convention plugin adds from buildSrc or build-logic are not visible there, and main-sequence distance (abstractness) is not computed for these modules yet.
What to do
- Resolve the 1 Unstable project //src/main/cpp finding(s) in Coupling. — One of this dimension's main actionable groups (1 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)
31 of 1636 classes have LCOM4 above 3.
What to do
- Resolve the 31 Low cohesion finding(s) in Cohesion (LCOM4) — start with SpawnResult.java, StarlarkCustomCommandLine.java, AbstractPackageLoader.java. — One of this dimension's main actionable groups (31 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
15879 test methods: 15879 unit, 0 integration, 0 BDD, 0 e2e. The Python suite contributes 552 test function(s) across 50 file(s) declaring at least one — every `def test…` in a file pytest or unittest would collect, which is those frameworks' own definition of a case; a parametrize table counts once, so this is a floor. Its tier split is read from file names and paths only.
D10 · Test Quality
90 skipped (90 with a documented reason), 2306 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 15327 tests. Measured on the .java suite only — at least 56 test source file(s) (.py) went unread, so its test quality is unmeasured and is not in these counts.
What to do
- Resolve the 2289 No assertions finding(s) in Test Quality — start with StarlarkRuleClassFunctionsTest.java (113), StarlarkEvaluationTest.java (103), StarlarkIntegrationTest.java (76). — One of this dimension's main actionable groups (2289 warning-level).
- Resolve the 17 No assertions (empty test) finding(s) in Test Quality — start with PostAnalysisQueryTest.java (9), NonconfigurableAttributeMapperTest.java (2), StarlarkAttrTransitionProviderTest.java (2). — One of this dimension's main actionable groups (17 issue-level).
- Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D13 · REDACTED Scanning
1 secret(s) detected.
What to do
- Resolve the 3 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
- Enforce REDACTED Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D14 · License Compliance
1 of 13 shipped Python distribution(s) use a banned license. Licences were resolved from PyPI over the distributions a consumer installs — this repository's 13 declared runtime requirement(s) closed transitively over each distribution's published `requires_dist` (0 reached that way). Requirements it states ONLY under an extra, a PEP 735 dependency group, a Poetry dev group or a dev-named requirements file are excluded: pip does not install any of them for a consumer. ★ This repository commits no dependency lockfile that this pass reads, so each licence is the one PyPI publishes for the distribution's CURRENT release rather than for a pinned version.
What to do
- Resolve the 1 Banned license finding(s) in License Compliance. — One of this dimension's main actionable groups (1 issue-level).
- Enforce License Compliance in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D15 · Churn × Complexity Hotspots
Top hotspots: src/main/java/com/google/devtools/build/lib/remote/RemoteModule.java (24×50=1200); src/main/java/com/google/devtools/build/lib/runtime/BlazeCommandDispatcher.java (9×60=540); src/main/java/com/google/devtools/build/lib/analysis/starlark/StarlarkActionFactory.java (12×39=468)
What to do
- Resolve the 56 Hotspot finding(s) in Churn × Complexity Hotspots — start with RemoteModule.java, BlazeCommandDispatcher.java, StarlarkActionFactory.java. — One of this dimension's main actionable groups (56 warning-level).
D16 · Bus Factor
188 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/main/java/com/google/devtools/build/lib/worker/WorkRequestHandler.java. Counted over 2176 of the 3282 production source files in this repository: 1098 are under the ~2,400-byte size floor this dimension measures over, and the remaining 8 have no attributable history left to measure.
D17 · Explicit Debt
1799 deducted task-comment markers across 595527 LoC (0.3/KLoC) → score 9.4. 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 1757 TodoComment finding(s) in Explicit Debt — start with TypeCheckerTest.java (49), Package.java (18), StarlarkRuleClassFunctions.java (16). — One of this dimension's main actionable groups (1757 warning-level).
- Resolve the 8 HackComment finding(s) in Explicit Debt — start with FileHandlerQuerier.java (2), docs2mdx.py, NestedSet.java. — One of this dimension's main actionable groups (8 warning-level).
- Resolve the 1 TodoComment repeated across 10 files finding(s) in Explicit Debt — start with SharedValueDeserializationContext.java. — 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.
D19 · Documentation Quality
The repository has an excellent root README that describes itself as 'Fast, Correct - Choose two' and documents the project's speed, multi-language support, scalability, extensibility, and security-vulnerability-reporting process. It also links to a comprehensive architecture/Docs directory (34 markdown files) covering Bazel's command-line reference, rule reference, query, extension, test-encyclopedia, community-users pages, plus the specific release-documentation scripts, Chocolatey package creation docs, Windows installer generator, remote-worker guide, workspace-log parser, and Jacoco upgrade steps. The READMEs for each subdirectory (examples/cpp/, examples/java-native/) are focused on their own directories rather than the repository root, which is consistent with the project's structure. The repository's READMEs are mostly test-data directories (22 of 56 total documents), with a few scattered architecture/CLI-reference HTML docs and one Bazel shell script README. The visible content is thin: the only non-test-README document is an HTML CLI reference covering options syntax, boolean flags, short forms, tristate defaults, and tags for each option (e.g. --connect_timeout_secs=30), but it does not explain what the project is or how to use its test-data directories.
What to do
- Resolve the 1 Documentation finding(s) in Documentation Quality — start with command-line-reference-suffix.html. — One of this dimension's main actionable groups (1 recommendation-level).
D21 · Naming Consistency
0 naming inconsistencies across 0 sampled symbols.
D26 · Project Cohesion
1 of 1 build units (Python) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
24 finding(s): 0 critical, 24 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 5 REDACTED finding(s) in Secrets (history) — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (5 issue-level).
- Resolve the 3 High secret finding(s) in Secrets (history) — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
5 finding(s): 0 critical, 5 high, 0 medium, 0 low. semgrep hit a parse error in 28 file(s) — `docs/command-line-reference-prefix.html` (lines 1–67), `examples/shell/bin.sh` (line 34), `examples/shell/lib.sh` (line 34), `examples/shell/test.sh` (line 34), `scripts/bash_completion_test.sh` (line 27), … (+23 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D30 · Dependency Vulnerabilities
3 finding(s): 1 critical, 2 high, 0 medium, 0 low.
What to do
- Resolve the 2 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 Critical vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D34 · Knowledge Freshness
175 of 2184 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/main/java/com/google/devtools/build/skyframe/InvalidatingNodeVisitor.java. Counted over 2184 of the 3282 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 1 Orphaned knowledge finding(s) in Knowledge Freshness — start with InvalidatingNodeVisitor.java. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 174 Orphaned file finding(s) in Knowledge Freshness — start with PackageFunctionWithMultipleGlobDeps.java, ModuleArg.java, RecursivePackageProviderBackedTargetPatternResolver.java. — One of this dimension's main actionable groups (174 recommendation-level).
- Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
Strongest change-coupling: AnalysisPhaseRunner.java↔FlagSetValue.java 76%; BuildTool.java↔FlagSetValue.java 71%; BuildTool.java↔RemoteAnalysisCachingEventListener.java 67%
What to do
- Resolve the 1 Boundary-crossing change coupling finding(s) in Change Coupling — start with RemoteModule.java. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 11 Change coupling finding(s) in Change Coupling — start with AnalysisPhaseRunner.java, Project.java, RemoteSpawnCache.java. — One of this dimension's main actionable groups (11 warning-level).
- Resolve the 1 Change-coupling hub finding(s) in Change Coupling — start with BuildTool.java. — One of this dimension's main actionable groups (1 warning-level).
D36 · Supply-chain Provenance & Signing
2/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 0 platform declaration(s) and 13 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
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
AX5 · Architecture & structure
AX6 · Interface segregation
- `VerificationTypeVisitor` declares 27 abstract methods: `visitDoubleType`, `visitFloatType`, `visitIntegerType`, `visitLongType`, `visitNullType`, `visitObjectType`, `visitStackDoubleType`, `visitStackFloatType`, `visitStackIntegerType`, `visitStackLongType`, `visitStackNullType`, `visitStackObjectType`, `visitStackTopType`, `visitStackUninitializedThisType`, `visitStackUninitializedType`, `visitTopType`, `visitUninitializedThisType`, `visitUninitializedType`, `visitVariablesDoubleType`, `visitVariablesFloatType`, `visitVariablesIntegerType`, `visitVariablesLongType`, `visitVariablesNullType`, `visitVariablesObjectType`, `visitVariablesTopType`, `visitVariablesUninitializedThisType`, `visitVariablesUninitializedType`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — third_party/java/proguard/proguard6.2.2/src/proguard/classfile/attribute/preverification/visitor/VerificationTypeVisitor.java:34
- `AttributeVisitor` declares 46 abstract methods: `visitAnnotationDefaultAttribute`, `visitBootstrapMethodsAttribute`, `visitCodeAttribute`, `visitConstantValueAttribute`, `visitDeprecatedAttribute`, `visitDeprecatedAttribute`, `visitDeprecatedAttribute`, `visitEnclosingMethodAttribute`, `visitExceptionsAttribute`, `visitInnerClassesAttribute`, `visitLineNumberTableAttribute`, `visitLocalVariableTableAttribute`, `visitLocalVariableTypeTableAttribute`, `visitMethodParametersAttribute`, `visitModuleAttribute`, `visitModuleMainClassAttribute`, `visitModulePackagesAttribute`, `visitNestHostAttribute`, `visitNestMembersAttribute`, `visitRuntimeInvisibleAnnotationsAttribute`, `visitRuntimeInvisibleAnnotationsAttribute`, `visitRuntimeInvisibleAnnotationsAttribute`, `visitRuntimeInvisibleParameterAnnotationsAttribute`, `visitRuntimeInvisibleTypeAnnotationsAttribute`, `visitRuntimeInvisibleTypeAnnotationsAttribute`, `visitRuntimeInvisibleTypeAnnotationsAttribute`, `visitRuntimeInvisibleTypeAnnotationsAttribute`, `visitRuntimeVisibleAnnotationsAttribute`, `visitRuntimeVisibleAnnotationsAttribute`, `visitRuntimeVisibleAnnotationsAttribute`, `visitRuntimeVisibleParameterAnnotationsAttribute`, `visitRuntimeVisibleTypeAnnotationsAttribute`, `visitRuntimeVisibleTypeAnnotationsAttribute`, `visitRuntimeVisibleTypeAnnotationsAttribute`, `visitRuntimeVisibleTypeAnnotationsAttribute`, `visitSignatureAttribute`, `visitSignatureAttribute`, `visitSignatureAttribute`, `visitSourceDirAttribute`, `visitSourceFileAttribute`, and 6 more. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. Those 46 declarations carry 30 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 30 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — third_party/java/proguard/proguard6.2.2/src/proguard/classfile/attribute/visitor/AttributeVisitor.java:35
- `ConstantVisitor` declares 18 abstract methods: `visitClassConstant`, `visitDoubleConstant`, `visitDynamicConstant`, `visitFieldrefConstant`, `visitFloatConstant`, `visitIntegerConstant`, `visitInterfaceMethodrefConstant`, `visitInvokeDynamicConstant`, `visitLongConstant`, `visitMethodHandleConstant`, `visitMethodTypeConstant`, `visitMethodrefConstant`, `visitModuleConstant`, `visitNameAndTypeConstant`, `visitPackageConstant`, `visitPrimitiveArrayConstant`, `visitStringConstant`, `visitUtf8Constant`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — third_party/java/proguard/proguard6.2.2/src/proguard/classfile/constant/visitor/ConstantVisitor.java:33
- `Clazz` declares 38 abstract methods: `accept`, `addSubClass`, `attributeAccept`, `attributesAccept`, `constantPoolEntriesAccept`, `constantPoolEntryAccept`, `extendsOrImplements`, `extendsOrImplements`, `extends_`, `extends_`, `fieldAccept`, `fieldsAccept`, `findField`, `findMethod`, `getAccessFlags`, `getClassName`, `getInterface`, `getInterfaceCount`, `getInterfaceName`, `getName`, `getName`, `getRefClassName`, `getRefName`, `getRefType`, `getString`, `getStringString`, `getSuperClass`, `getSuperName`, `getTag`, `getType`, `hierarchyAccept`, `interfaceConstantsAccept`, `mayHaveImplementations`, `methodAccept`, `methodsAccept`, `subclassesAccept`, `superClassConstantAccept`, `thisClassConstantAccept`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. Those 38 declarations carry 35 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 35 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — third_party/java/proguard/proguard6.2.2/src/proguard/classfile/Clazz.java:33
- `NodeEntry` declares 38 abstract methods: `addExternalDep`, `addReverseDepAndCheckIfDone`, `addSingletonTemporaryDirectDep`, `addTemporaryDirectDepGroup`, `addTemporaryDirectDepsInGroups`, `checkIfDoneForDirtyReverseDep`, `forceRebuild`, `getAllDirectDepsForIncompleteNode`, `getAllRemainingDirtyDirectDeps`, `getAllReverseDepsForNodeBeingDeleted`, `getDirectDeps`, `getErrorInfo`, `getInProgressReverseDeps`, `getLifecycleState`, `getNextDirtyDirectDeps`, `getResetDirectDeps`, `getReverseDepsForDoneEntry`, `getTemporaryDirectDeps`, `getValue`, `getValueMaybeWithMetadata`, `getVersion`, `hasAtLeastOneDep`, `hasUnsignaledDeps`, `isChanged`, `isDirty`, `isDone`, `isReadyToEvaluate`, `markClean`, `markDirty`, `markRebuilding`, `noDepsLastBuild`, `removeReverseDep`, `removeReverseDepsFromDoneEntryDueToDeletion`, `removeUnfinishedDeps`, `resetEvaluationFromScratch`, `setValue`, `signalDep`, `toValue`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/main/java/com/google/devtools/build/skyframe/NodeEntry.java:34
- `MemoizingEvaluator` declares 19 abstract methods: `cleanupInterningPools`, `delete`, `deleteDirty`, `dumpCount`, `dumpDeps`, `dumpFunctionGraph`, `dumpKeys`, `dumpRdeps`, `dumpSummary`, `dumpValues`, `evaluate`, `getDoneValues`, `getExistingEntryAtCurrentlyEvaluatingVersion`, `getExistingErrorForTesting`, `getExistingValue`, `getInMemoryGraph`, `getValues`, `injectGraphTransformerForTesting`, `isRewinding`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/main/java/com/google/devtools/build/skyframe/MemoizingEvaluator.java:37
- `JavaInfoApi<FileT, JavaOutputT, JavaPluginDataT>` declares 17 abstract methods: `getCompilationInfoProvider`, `getCompileTimeJars`, `getCompileTimeJavaDependencies`, `getFullCompileTimeJars`, `getGenJarsProvider`, `getJavaConstraintsStarlark`, `getJavaModuleFlagsInfo`, `getOutputJars`, `getRuntimeOutputJars`, `getSourceJars`, `getTransitiveCompileTimeJars`, `getTransitiveFullCompileJars`, `getTransitiveNativeLibrariesForStarlark`, `getTransitiveRuntimeJars`, `getTransitiveSourceJars`, `headerCompilationDirectDeps`, `isNeverlink`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/main/java/com/google/devtools/build/lib/starlarkbuildapi/java/JavaInfoApi.java:34
- `JavaConfigurationApi` declares 21 abstract methods: `autoCreateJavaTestDeployJars`, `bytecodeOptimizationPassActions`, `enforceOneVersionOnJavaTests`, `enforceProguardFileExtension`, `explicitJavaTestDepsStarlark`, `getBytecodeOptimizerMnemonic`, `getDefaultJavacFlagsForStarlarkAsList`, `getDefaultJavacFlagsStarlark`, `getDefaultJvmFlags`, `getDisallowJavaImportExportsInStarlark`, `getGenerateJavaDepsStarlark`, `getPlugins`, `getReduceJavaClasspathStarlark`, `getStrictJavaDepsName`, `getUseHeaderCompilationDirectDepsInStarlark`, `getUseIjarsInStarlark`, `multiReleaseDeployJars`, `runAndroidLint`, `splitBytecodeOptimizationPass`, `starlarkOneVersionEnforcementLevel`, `useHeaderCompilationStarlark`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/main/java/com/google/devtools/build/lib/starlarkbuildapi/java/JavaConfigurationApi.java:32
- `CppConfigurationApi<InvalidConfigurationExceptionT>` declares 24 abstract methods: `appleGenerateDsym`, `buildTestDwpIsActivatedStarlark`, `csFdoInstrumentStarlark`, `customMalloc`, `disableNocoptsStarlark`, `fdoInstrumentStarlark`, `fissionActiveForCurrentCompilationModeStarlark`, `forcePicStarlark`, `generateLlvmLcovStarlark`, `getConlyopts`, `getCopts`, `getCxxopts`, `getExperimentalLinkStaticLibrariesOnce`, `getLibcTopLabelStarlark`, `getLinkopts`, `getObjcopts`, `getSaveTempsForStarlark`, `getStripOptsStarlark`, `objcGenerateLinkmap`, `objcShouldStripBinary`, `processHeadersInDependenciesStarlark`, `saveFeatureStateStarlark`, `shareNativeDepsStarlark`, `shouldStripBinariesForStarlark`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/main/java/com/google/devtools/build/lib/starlarkbuildapi/cpp/CppConfigurationApi.java:33
- `CcCompilationContextApi<FileT>` declares 25 abstract methods: `getDirectModuleMapsForStarlark`, `getHeaderInfo`, `getNonCodeInputsForStarlark`, `getStarlarkDefines`, `getStarlarkDirectModularHeaders`, `getStarlarkDirectPrivateHeaders`, `getStarlarkDirectPublicHeaders`, `getStarlarkDirectTextualHeaders`, `getStarlarkExportingModuleMaps`, `getStarlarkExternalIncludeDirs`, `getStarlarkFrameworkIncludeDirs`, `getStarlarkHeaders`, `getStarlarkIncludeDirs`, `getStarlarkModuleFiles`, `getStarlarkModuleMap`, `getStarlarkModulesInfoFiles`, `getStarlarkNonTransitiveDefines`, `getStarlarkPicModuleFiles`, `getStarlarkPicModulesInfoFiles`, `getStarlarkQuoteIncludeDirs`, `getStarlarkSystemIncludeDirs`, `getStarlarkTransitiveModules`, `getStarlarkTransitivePicModules`, `getStarlarkValidationArtifacts`, `getStarlarkVirtualToOriginalHeaders`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/main/java/com/google/devtools/build/lib/starlarkbuildapi/cpp/CcCompilationContextApi.java:35
- `AndroidConfigurationApi` declares 20 abstract methods: `apkSigningMethodV1`, `apkSigningMethodV2`, `apkSigningMethodV4`, `compressJavaResources`, `desugarJava8`, `desugarJava8Libs`, `fixedResourceNeverlinking`, `getDexoptsSupportedInDexSharder`, `getExportsManifestDefault`, `getJavaResourcesFromOptimizedJar`, `getOutputDirectoryName`, `incrementalDexingShardsAfterProguard`, `persistentBusyboxTools`, `persistentDexDesugar`, `persistentMultiplexBusyboxTools`, `persistentMultiplexDexDesugar`, `useAndroidResourceCycleShrinking`, `useAndroidResourceNameObfuscation`, `useAndroidResourcePathShortening`, `useAndroidResourceShrinking`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/main/java/com/google/devtools/build/lib/starlarkbuildapi/android/AndroidConfigurationApi.java:32
- `StarlarkRuleContextApi<ConstraintValueT>` declares 36 abstract methods: `actions`, `aspectIds`, `callParent`, `checkPlaceholders`, `createdActions`, `execGroups`, `expandLocation`, `expandMakeVariables`, `getAttr`, `getBinDirectory`, `getBuildFileRelativePath`, `getBuildSettingValue`, `getConfiguration`, `getDisabledFeatures`, `getExecutable`, `getFeatures`, `getFile`, `getFiles`, `getFragments`, `getGenfilesDirectory`, `getLabel`, `getSplitAttr`, `getStableWorkspaceStatus`, `getVolatileWorkspaceStatus`, `getWorkspaceName`, `instrumentCoverage`, `outputs`, `packageRelativeLabel`, `resolveCommand`, `resolveTools`, `rule`, `runfiles`, `targetPlatformHasConstraint`, `tokenize`, `toolchains`, `var`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/main/java/com/google/devtools/build/lib/starlarkbuildapi/StarlarkRuleContextApi.java:58
- `StarlarkAttrModuleApi` declares 17 abstract methods: `boolAttribute`, `dormantLabelAttribute`, `dormantLabelListAttribute`, `intAttribute`, `intListAttribute`, `labelAttribute`, `labelKeyedStringDictAttribute`, `labelListAttribute`, `labelListDictAttribute`, `licenseAttribute`, `outputAttribute`, `outputListAttribute`, `stringAttribute`, `stringDictAttribute`, `stringKeyedLabelDictAttribute`, `stringListAttribute`, `stringListDictAttribute`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/main/java/com/google/devtools/build/lib/starlarkbuildapi/StarlarkAttrModuleApi.java:57
- `QueryEnvironment<T>` declares 30 abstract methods: `buildTransitiveClosure`, `createEvaluateExpression`, `createMinDepthUniquifier`, `createThreadSafeMutableSet`, `createUniquifier`, `eval`, `execute`, `executeAsync`, `getAccessor`, `getFunctions`, `getFwdDeps`, `getLabelPrinter`, `getNodesOnPath`, `getOrCreate`, `getReverseDeps`, `getSiblingTargetsInPackage`, `getTargetsMatchingPattern`, `getTransitiveClosure`, `getTransitiveLoadFilesHelper`, `handleError`, `immediateCancelledFuture`, `immediateFailedFuture`, `immediateSuccessfulFuture`, `isSettingEnabled`, `transformAsync`, `transitiveLoadFiles`, `whenAllSucceed`, `whenAllSucceedCall`, `whenSucceedsCall`, `whenSucceedsOrIsCancelledCall`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/main/java/com/google/devtools/build/lib/query2/engine/QueryEnvironment.java:47
- `TraceProfilerService` declares 28 abstract methods: `clear`, `completeTask`, `createTimeSeries`, `getProfileElapsedTime`, `getServerProcessCpuTime`, `getSlowestTasks`, `getTasksHistograms`, `isActive`, `isProfiling`, `logCounters`, `logEvent`, `logEventAtTime`, `logSimpleTask`, `logSimpleTask`, `logSimpleTaskDuration`, `markPhase`, `nanoTimeMaybe`, `profile`, `profile`, `profile`, `profileAction`, `profileAsync`, `profileFuture`, `registerCounterSeriesCollector`, `setVfsTypeHeuristics`, `start`, `stop`, `unregisterCounterSeriesCollector`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. Those 28 declarations carry 25 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 25 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/main/java/com/google/devtools/build/lib/profiler/TraceProfilerService.java:51
- `SpawnExecutionContext` declares 16 abstract methods: `checkForLostInputs`, `getActionFileSystem`, `getClientEnv`, `getContext`, `getDigest`, `getFileOutErr`, `getId`, `getInputMapping`, `getInputMetadataProvider`, `getTimeout`, `isRewindingEnabled`, `lockOutputFiles`, `prefetchInputs`, `report`, `setDigest`, `speculating`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/main/java/com/google/devtools/build/lib/exec/SpawnRunner.java:141
- `ActionConstructionContext` declares 22 abstract methods: `getActionKeyContext`, `getActionOwner`, `getActionOwner`, `getAnalysisEnvironment`, `getBinDirectory`, `getBinOrGenfilesDirectory`, `getConfiguration`, `getDerivedArtifact`, `getExecutionPlatform`, `getExecutionPlatform`, `getGenfilesDirectory`, `getImplicitOutputArtifact`, `getPackageDirectory`, `getPackageRelativeArtifact`, `getRelatedArtifact`, `getRuleErrorConsumer`, `getShareableArtifact`, `getTreeArtifact`, `getUniqueDirectory`, `getUniqueDirectoryArtifact`, `getUniqueDirectoryArtifact`, `getUniqueDirectoryArtifact`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. Those 22 declarations carry 18 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 18 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/main/java/com/google/devtools/build/lib/analysis/actions/ActionConstructionContext.java:37
- `AnalysisEnvironment` declares 20 abstract methods: `declareStampSettingDep`, `getActionKeyContext`, `getConstantMetadataArtifact`, `getDerivedArtifact`, `getEventHandler`, `getFilesetArtifact`, `getLocalGeneratingAction`, `getMainRepoMapping`, `getOrphanArtifacts`, `getRegisteredActions`, `getRunfilesArtifact`, `getSkyframeEnv`, `getStableWorkspaceStatusArtifact`, `getStarlarkDefinedBuiltins`, `getStarlarkSemantics`, `getSymlinkArtifact`, `getTreeArtifact`, `getTreeArtifactsConflictingWithFiles`, `getVolatileWorkspaceStatusArtifact`, `hasErrors`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/main/java/com/google/devtools/build/lib/analysis/AnalysisEnvironment.java:40
- `SpawnResult` declares 18 abstract methods: `exitCode`, `failureDetail`, `getDetailMessage`, `getExecutorHostName`, `getMemoryInKb`, `getMetrics`, `getNumBlockInputOperations`, `getNumBlockOutputOperations`, `getNumInvoluntaryContextSwitches`, `getRunnerName`, `getRunnerSubtype`, `getStartTime`, `getSystemTimeInMs`, `getUserTimeInMs`, `getWallTimeInMs`, `isCacheHit`, `status`, `wasRemote`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/main/java/com/google/devtools/build/lib/actions/SpawnResult.java:38
- `ActionAnalysisMetadata` declares 19 abstract methods: `describe`, `getClientEnvironmentVariables`, `getExecProperties`, `getExecutionPlatform`, `getInputFilesForExtraAction`, `getInputs`, `getKey`, `getMandatoryInputs`, `getMandatoryOutputs`, `getMnemonic`, `getOriginalInputs`, `getOutputs`, `getOwner`, `getPrimaryInput`, `getPrimaryOutput`, `getSchedulingDependencies`, `getTools`, `isShareable`, `prettyPrint`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/main/java/com/google/devtools/build/lib/actions/ActionAnalysisMetadata.java:27
What to do
- Split fat interfaces into focused role-interfaces so clients depend only on what they use.
AX8 · Test isolation
AX9 · CQS / query purity
IC1 · Incompleteness & stubs
- A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. (×36) — src/java_tools/import_deps_checker/javatests/com/google/devtools/build/importdeps/MainTest.java:33, src/java_tools/junitrunner/javatests/com/google/testing/junit/runner/internal/junit4/JUnit4TestXmlListenerTest.java:268, src/java_tools/junitrunner/javatests/com/google/testing/junit/runner/junit4/JUnit4TestModelBuilderTest.java:172, …
- `testPass` has an empty body — confirm it's an intentional no-op and not an unfinished method. (×2) — src/java_tools/junitrunner/javatests/com/google/testing/junit/runner/testbed/JUnit4TestbridgeExercises.java:29, src/java_tools/junitrunner/javatests/com/google/testing/junit/runner/testbed/JUnit4TestbridgeOomExercises.java:27
- `ensureRegistered` has an empty body — confirm it's an intentional no-op and not an unfinished method. — src/main/java/com/google/devtools/build/lib/vfs/bazel/BazelHashFunctions.java:44
What to do
- Clear the softer debt: re-enable or delete @Disabled/@Ignore tests, decide whether each empty method or UnsupportedOperationException is deliberate (and say so in a comment), and replace @SuppressWarnings("all") with targeted, justified suppressions.
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
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.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
M4 · Documentation accuracy
- docs/help.mdx links to `/community/experts`, but `community/experts` 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. — docs/help.mdx:45
- docs/help.mdx links to `/release`, but `release` 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. — docs/help.mdx:49
- docs/about/faq.mdx links to `/help`, but `help` 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. — docs/about/faq.mdx:7
- docs/about/faq.mdx links to `/reference/be/overview`, but `reference/be/overview` 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. — docs/about/faq.mdx:17
- docs/about/faq.mdx links to `/remote/rbe`, but `remote/rbe` 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. — docs/about/faq.mdx:45
- docs/about/faq.mdx links to `/remote/caching`, but `remote/caching` 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. — docs/about/faq.mdx:45
- docs/about/faq.mdx links to `/start/`, but `start` 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. — docs/about/faq.mdx:111
- docs/about/faq.mdx links to `/release/`, but `release` 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. — docs/about/faq.mdx:142
- docs/about/faq.mdx links to `/run/scripts#exit-codes`, but `run/scripts` 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. — docs/about/faq.mdx:158
- docs/about/faq.mdx links to `/extending/concepts`, but `extending/concepts` 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. — docs/about/faq.mdx:164
- docs/about/faq.mdx links to `/contribute/`, but `contribute` 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. — docs/about/faq.mdx:168
- docs/about/intro.mdx links to `/rules`, but `rules` 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. — docs/about/intro.mdx:37
- docs/about/intro.mdx links to `/install`, but `install` 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. — docs/about/intro.mdx:45
- docs/about/intro.mdx links to `/concepts/build-ref#workspaces`, but `concepts/build-ref` 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. — docs/about/intro.mdx:47
- docs/about/intro.mdx links to `/reference/command-line-reference`, but `reference/command-line-reference` 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. — docs/about/intro.mdx:67
- docs/about/intro.mdx links to `/reference/test-encyclopedia`, but `reference/test-encyclopedia` 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. — docs/about/intro.mdx:71
- docs/about/intro.mdx links to `/query/guide`, but `query/guide` 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. — docs/about/intro.mdx:71
- docs/about/intro.mdx links to `/concepts/dependencies`, but `concepts/dependencies` 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. — docs/about/intro.mdx:81
- docs/about/intro.mdx links to `/extending/concepts#evaluation-model`, but `extending/concepts` 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. — docs/about/intro.mdx:82
- docs/about/intro.mdx links to `/basics/hermeticity`, but `basics/hermeticity` 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. — docs/about/intro.mdx:91
- docs/about/intro.mdx links to `/start/`, but `start` 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. — docs/about/intro.mdx:105
- docs/about/intro.mdx links to `/start/cpp`, but `start/cpp` 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. — docs/about/intro.mdx:108
- docs/about/intro.mdx links to `/start/java`, but `start/java` 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. — docs/about/intro.mdx:109
- docs/about/intro.mdx links to `/start/android-app`, but `start/android-app` 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. — docs/about/intro.mdx:110
- docs/about/intro.mdx links to `/start/ios-app`, but `start/ios-app` 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. — docs/about/intro.mdx:111
- docs/about/vision.mdx links to `/extending/toolchains`, but `extending/toolchains` 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. — docs/about/vision.mdx:87
- docs/about/why.mdx links to `/remote/rbe`, but `remote/rbe` 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. — docs/about/why.mdx:18
- docs/about/why.mdx links to `/basics/hermeticity`, but `basics/hermeticity` 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. — docs/about/why.mdx:31
- docs/about/why.mdx links to `/rules/language`, but `rules/language` 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. — docs/about/why.mdx:42
- docs/about/why.mdx links to `/docs/user-manual#running-tests`, but `docs/user-manual` 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. — docs/about/why.mdx:49
- docs/about/why.mdx links to `/remote/bep`, but `remote/bep` 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. — docs/about/why.mdx:54
- docs/about/why.mdx links to `/external/overview`, but `external/overview` 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. — docs/about/why.mdx:67
- docs/about/why.mdx links to `/extending/platforms`, but `extending/platforms` 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. — docs/about/why.mdx:76
- docs/about/why.mdx links to `/community/users`, but `community/users` 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. — docs/about/why.mdx:81
- docs/about/why.mdx links to `/community/experts`, but `community/experts` 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. — docs/about/why.mdx:83
- docs/about/why.mdx links to `/rules`, but `rules` 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. — docs/about/why.mdx:85
- docs/basics/artifact-based-builds.mdx links to `/extending/rules`, but `extending/rules` 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. — docs/basics/artifact-based-builds.mdx:187
- docs/basics/artifact-based-builds.mdx links to `/docs/sandboxing`, but `docs/sandboxing` 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. — docs/basics/artifact-based-builds.mdx:214
- docs/basics/dependencies.mdx links to `/images/transitive-dependencies.png`, but `images/transitive-dependencies.png` 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. — docs/basics/dependencies.mdx:110
- docs/basics/dependencies.mdx links to `/external/overview`, but `external/overview` 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. — docs/basics/dependencies.mdx:232
What to do
- Reconcile the README with reality: docs/help.mdx links to `/community/experts`, but `community/experts` does not exist; docs/help.mdx links to `/release`, but `release` does not exist; docs/about/faq.mdx links to `/help`, but `help` does not exist; docs/about/faq.mdx links to `/reference/be/overview`, but `reference/be/overview` does not exist; docs/about/faq.mdx links to `/remote/rbe`, but `remote/rbe` does not exist.
P1 · CI/CD gates
What to do
- Run the test suite in CI via an explicit runner step (`pytest` for the toolchain this pipeline already uses) and gate merges on it.
P2 · Observability
- Only 1/2 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
P3 · Security & performance tooling
- `scorecard.yml` run(s) a static-analysis scan, but no workflow that runs one is triggered by a pull request (or a merge queue, or an unfiltered push) — the scan fires on a schedule or a manual dispatch only. A vulnerable change therefore merges clean and is reported on the next scheduled run, by which time it is on the default branch and the only remedy is a follow-up fix. Add the pull-request trigger to the workflow that runs the scan so the finding arrives before the merge rather than after it.
What to do
- Trigger your SAST workflow on pull requests — a scan that only runs on a cron reports history, it does not gate.
- Dependabot is configured but does not watch `pip`, `maven`, `gradle` — add those `package-ecosystem` entries to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- No release automation was found in CI — neither a deploy stage (Helm/Kubernetes/compose manifests, an orchestrated rollout) nor a publish job that ships the built artifact. Releases appear to be run by hand, which is slower, less repeatable and harder to reverse.
What to do
- Automate the release in CI — a deploy stage for a service (Helm/Kubernetes manifests or an equivalent rollout), or a tag-triggered publish job for an artifact — so releases are repeatable and reversible.
P6 · Release Hygiene
PF1 · Benchmark discipline
- A JMH/Jetpack Benchmark suite exists but nothing turns on its allocation measurement — allocations (the main way hot code pressures a garbage collector or allocator) aren't being measured. — src/test/java/com/google/devtools/build/lib/remote/ChunkedTransferBenchmark.java
What to do
- Run JMH with the GC profiler (`-prof gc`, or addProfiler(GCProfiler.class)) so allocation rate regressions are visible, not just time.
PF2 · Allocation hygiene
What to do
- Raise allocation-aware density on the hot paths — currently 84 use(s) across 653,384 production line(s) (~0.1/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).
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
- `length` is read from the bytes being parsed at line 189 (`readInt`), then used to size a `new byte[]` at line 193 — and nowhere in its scope is `length` bounded from above — compared to a limit, clamped, or checked against the input that remains (a zero or sign test, or the loop that counts up to it, bounds nothing). Whoever wrote those bytes therefore chooses the allocation directly: a 32-bit length asks for up to 2 GiB before a single byte of the payload is known to exist, which either exhausts the heap with an `OutOfMemoryError` or, negative, throws `NegativeArraySizeException` out of a parser whose failure path was written for malformed input, not for hostile input. Bound `length` against the bytes actually remaining and a maximum the format allows before allocating. — src/main/java/com/google/devtools/build/lib/actions/cache/PersistentStringIndexer.java:193
- `size` is read from the bytes being parsed at line 210 (`readInt`), then used to size a `new byte[]` at line 214 — and nowhere in its scope is `size` bounded from above — compared to a limit, clamped, or checked against the input that remains (a zero or sign test, or the loop that counts up to it, bounds nothing). Whoever wrote those bytes therefore chooses the allocation directly: a 32-bit length asks for up to 2 GiB before a single byte of the payload is known to exist, which either exhausts the heap with an `OutOfMemoryError` or, negative, throws `NegativeArraySizeException` out of a parser whose failure path was written for malformed input, not for hostile input. Bound `size` against the bytes actually remaining and a maximum the format allows before allocating. — src/main/java/com/google/devtools/build/lib/actions/cache/CompactPersistentActionCache.java:214
What to do
- Each finding names the read that takes the length from the input and the site that spends it, and states that the value is never compared in between. Confirm from the two, then bound the length against the remaining stream before using it.
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
- `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — src/main/java/com/google/devtools/build/lib/collect/nestedset/NestedSet.java:500
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×3) — src/main/java/com/google/devtools/build/lib/runtime/BlazeRuntime.java:2158, src/main/java/com/google/devtools/build/lib/runtime/BlazeRuntime.java:2177, src/main/java/com/google/devtools/build/lib/runtime/BlazeRuntime.java:2182
What to do
- Swallowed exception (caught, then discarded)
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
- 0/224 of this repository's Java package directories are under a non-null default: a `REDACTED` declaring `@NullMarked` (JSpecify) or `@NonNullApi`, `@ParametersAreNonnullByDefault`, `@NonNullByDefault`, `@DefaultQualifier(NonNull.class)`; a `module-info.java` declaring `@NullMarked`; every type in it `@NullMarked`; or a build that runs NullAway with the package in `AnnotatedPackages`, or the Checker Framework's `NullnessChecker`. Elsewhere every reference admits null and no checker warns on the dereference that throws a `NullPointerException`.
What to do
- Declare the default where Java declares it: `@NullMarked` (org.jspecify.annotations) in each package's `REDACTED`, or once in `module-info.java`, and run NullAway (Error Prone) or the Checker Framework so the declaration is enforced. Then annotate the real exceptions `@Nullable` and resolve the suppressions rather than adding to them: a `@SuppressWarnings("NullAway")` or `castToNonNull(x)` on a value the checker could show to be null is a `NullPointerException` waiting for the path that makes it true — where the value genuinely cannot be null, say something the checker can see instead (a null check, `Objects.requireNonNull`, a non-null field initialised in the constructor).
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 65% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 91% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 55% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 60% | Adequate — gated by P4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 67% | Adequate — gated by D28 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 71% | Strong | Strongest area. |
Unscored — 4 check(s) recorded observations but carry no score
- D11 Test Reliability — 3 observation(s) recorded · This repository declares 3 of its own test(s) unreliable. The built-in reliability runner does not support this repository's ecosystem (.java, .py), so the suite was not re-run and no reliability score is given — these are the repository's own declarations, not our measurement.
- X10 Duplicated predicate — 25 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X6 Hand-rolled structured-format parsing — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 45 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 analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No Go request handler (a net/http, Gin, Echo, Fiber or fasthttp handler, or a gRPC service method) is declared as a method or function, and no handler function literal writes a value captured from outside it, so no state is shared between request goroutines. No class in this Java code is a Spring, JSR-330 or CDI singleton bean. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads.
- AX4 Dependency direction — not applicable to a CQRS architecture (the inward-dependency rule is for layered/clean styles)
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- 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.
- D12 Dependency Hygiene — Not scored — 4 Maven/Gradle manifest(s) were read, stating a version for 0 dependency(ies) and leaving 0 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
- 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.
- D20 ADR Quality — Repository kind not determined
- 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+ projects each declaring an entity of their own. 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 — No inline comments to assess — comment value is not applicable here.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.java), 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.
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — 6 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- 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.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — applicable but not scored (2 signals for this style, 2 needed — the count is met but a required primary signal is absent): 830 value object(s); 56 domain event(s); its domain events are published by services or handlers — no domain entity raises one
- ED1 Event-Driven — not scored — this repository shows only 1 of the 3 signals this lens looks for (11 CQRS handler(s))
- ED5 Idempotency — Not assessed, and this one is on us: 6 command handler(s) or message consumer(s) were found here, but this check does not yet recognise persistence writes in this repository's language. Idempotency was neither confirmed nor ruled out — this is a limit of the analyzer, not a finding about your code.
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- 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, Python 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 (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, or wire coverage collection into CI, to enable this cross-layer check
- PF3 Async & latency hygiene — Not applicable: Go has no async/await function colour, so there is no asynchronous code for a blocking call to stall.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- X2 Cancellation propagation — no C# was loaded; this repository's Java and Python were read, and no request in it can be cancelled by a caller — a Java request off Android takes no token: it is cancelled through the handle it returns (Future.cancel, Call.cancel, a Disposable), ambiently (io.grpc.Context) or by interrupting its thread, not through a parameter; a Python request takes no token: asyncio cancels the task and trio or anyio the scope that made it, from outside the call, and requests, httpx, aiohttp and gRPC take a timeout, not a cancellation
- 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.
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Java was read, and it logs through none that an assembled message defeats: java.util.logging's level methods, log4j 1, commons-logging, JBoss Logging and Flogger take one finished message (as log4net does in C#), or it makes no call through a named logger at all. Calls made through SLF4J or log4j 2 (`org.slf4j.Logger`, `org.apache.logging.log4j.Logger`, Lombok's `@Slf4j`) would be judged.
- 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 — 42 finding(s)
- No assertions (empty test): testAttributeTypeChecking src/test/java/com/google/devtools/build/lib/analysis/select/NonconfigurableAttributeMapperTest.java:82
- No assertions (empty test): testVisitation src/test/java/com/google/devtools/build/lib/analysis/select/NonconfigurableAttributeMapperTest.java:88
- No assertions (empty test): testOptionConversionCrosstoolTop src/test/java/com/google/devtools/build/lib/analysis/starlark/StarlarkAttrTransitionProviderTest.java:3089
- No assertions (empty test): testOptionConversionDynamicMode src/test/java/com/google/devtools/build/lib/analysis/starlark/StarlarkAttrTransitionProviderTest.java:3084
- No assertions (empty test): passing src/test/java/com/google/devtools/build/lib/testutil/TestInterruptingBugReporterTest.java:55
- No assertions (empty test): globMissingFile src/test/java/com/google/devtools/build/lib/buildtool/DanglingSymlinkTest.java:137
- No assertions (empty test): testGraphOrderOfWildcards src/test/java/com/google/devtools/build/lib/query2/engine/GraphlessQueryTest.java:85
- No assertions (empty test): boundedDepsWithError src/test/java/com/google/devtools/build/lib/query2/testutil/PostAnalysisQueryTest.java:1307
- No assertions (empty test): labelPointsToMultipleConfiguredTargets src/test/java/com/google/devtools/build/lib/query2/testutil/PostAnalysisQueryTest.java:1030
- No assertions (empty test): testDefaultVisibilityReturnedInDeps_nonEmptyDependencyFilter src/test/java/com/google/devtools/build/lib/query2/testutil/PostAnalysisQueryTest.java:1334
- No assertions (empty test): testEqualityOfOrderedThreadSafeImmutableSet src/test/java/com/google/devtools/build/lib/query2/testutil/PostAnalysisQueryTest.java:1101
- No assertions (empty test): testGraphOrderOfWildcards src/test/java/com/google/devtools/build/lib/query2/testutil/PostAnalysisQueryTest.java:1312
- No assertions (empty test): testNodepDeps_false src/test/java/com/google/devtools/build/lib/query2/testutil/PostAnalysisQueryTest.java:1329
- No assertions (empty test): testVisibleWithNonPackageGroupVisibility src/test/java/com/google/devtools/build/lib/query2/testutil/PostAnalysisQueryTest.java:1318
- No assertions (empty test): testVisibleWithPackageGroupWithNonPackageGroupIncludes src/test/java/com/google/devtools/build/lib/query2/testutil/PostAnalysisQueryTest.java:1324
- No assertions (empty test): testWildcardsDontLoadUnnecessaryPackages src/test/java/com/google/devtools/build/lib/query2/testutil/PostAnalysisQueryTest.java:1303
- No assertions (empty test): testBadPermissionsThrowsExceptionOnStatIfFound src/test/java/com/google/devtools/build/lib/vfs/JavaIoFileSystemTest.java:57
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Test declared unreliable: testSimple src/test/java/com/google/devtools/build/lib/skyframe/MacOSXFsEventsDiffAwarenessTest.java:170
- Test declared unreliable: testRenameDirectory src/test/java/com/google/devtools/build/lib/skyframe/MacOSXFsEventsDiffAwarenessTest.java:186
- Test declared unreliable: testStress src/test/java/com/google/devtools/build/lib/skyframe/MacOSXFsEventsDiffAwarenessTest.java:201
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Banned license: frozendict
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Orphaned knowledge src/main/java/com/google/devtools/build/skyframe/InvalidatingNodeVisitor.java:1
- Boundary-crossing change coupling: RemoteModule.java ↔ OnDiskBlobStoreCache.java src/main/java/com/google/devtools/build/lib/remote/RemoteModule.java:1
Serious — 5676 finding(s)
- No assertions: testSleep examples/java-native/src/test/java/com/example/myproject/TestSleep.java:8
- No assertions: testInheritedAttributeGeneratesSignature src/test/java/com/google/devtools/build/docgen/RuleDocumentationTest.java:92
- No assertions: testSignatureContainsCommonAttribute src/test/java/com/google/devtools/build/docgen/RuleDocumentationTest.java:84
- No assertions: equals_returnsTrueForIdenticalRootAndDetectsDifferencesOnEachField src/test/java/com/google/devtools/build/lib/actions/ArtifactRootTest.java:199
- No assertions: equalsAndHashCode src/test/java/com/google/devtools/build/lib/actions/FileContentsProxyTest.java:92
- No assertions: testNoActionConflictWhenUnregisteringSharedAction src/test/java/com/google/devtools/build/lib/actions/MapBasedActionGraphTest.java:78
- No assertions: testSharedActionStressTest src/test/java/com/google/devtools/build/lib/actions/MapBasedActionGraphTest.java:170
- No assertions: testSmoke src/test/java/com/google/devtools/build/lib/actions/MapBasedActionGraphTest.java:49
- No assertions: testCPULoadScheduling_allowsExplicitZeroCpuWithNoCpuCapacity src/test/java/com/google/devtools/build/lib/actions/ResourceManagerTest.java:968
- No assertions: testCPULoadScheduling_success src/test/java/com/google/devtools/build/lib/actions/ResourceManagerTest.java:789
- No assertions: testMemoryLoadScheduling_success src/test/java/com/google/devtools/build/lib/actions/ResourceManagerTest.java:813
- No assertions: testScaledCpuRequestSucceeds src/test/java/com/google/devtools/build/lib/actions/ResourceManagerTest.java:862
- No assertions: testEquals src/test/java/com/google/devtools/build/lib/actions/ResourceSetTest.java:63
- No assertions: testComputesConsistentKeys src/test/java/com/google/devtools/build/lib/analysis/actions/BinaryFileWriteActionTest.java:57
- No assertions: actionInputsVary_checkComputeKeyResults src/test/java/com/google/devtools/build/lib/analysis/actions/BuildInfoFileWriteActionTest.java:201
- No assertions: testComputesConsistentKeys src/test/java/com/google/devtools/build/lib/analysis/actions/FileWriteActionTest.java:58
- No assertions: testComputeKey src/test/java/com/google/devtools/build/lib/analysis/actions/ParamFileWriteActionTest.java:219
- No assertions: starlarkRule_heuristicPathMappingNotAllowedViaExecutionRequirements src/test/java/com/google/devtools/build/lib/analysis/actions/PathMappersTest.java:242
- No assertions: testComputeKey src/test/java/com/google/devtools/build/lib/analysis/actions/SpawnActionTest.java:379
- No assertions: testComputeKey src/test/java/com/google/devtools/build/lib/analysis/actions/SymlinkTreeActionTest.java:48
- No assertions: testAbsentPackage src/test/java/com/google/devtools/build/lib/analysis/allowlisting/AllowlistTest.java:70
- No assertions: testCatchAll src/test/java/com/google/devtools/build/lib/analysis/allowlisting/AllowlistTest.java:85
- No assertions: testDirectPackage src/test/java/com/google/devtools/build/lib/analysis/allowlisting/AllowlistTest.java:36
- No assertions: testEmptyPackageGroup src/test/java/com/google/devtools/build/lib/analysis/allowlisting/AllowlistTest.java:102
- No assertions: testIncludes src/test/java/com/google/devtools/build/lib/analysis/allowlisting/AllowlistTest.java:119
- TodoComment scripts/ctexplain/lib_test.py:66
- TodoComment scripts/ctexplain/bazel_api.py:137
- TodoComment scripts/docs/mdx_fixes.py:38
- TodoComment src/java_tools/buildjar/java/com/google/devtools/build/buildjar/VanillaJavaBuilder.java:205
- TodoComment src/java_tools/buildjar/java/com/google/devtools/build/buildjar/ReducedClasspathJavaLibraryBuilder.java:99
- TodoComment src/java_tools/buildjar/java/com/google/devtools/build/buildjar/OptionsParser.java:188
- TodoComment src/java_tools/buildjar/java/com/google/devtools/build/buildjar/JavaLibraryBuildRequest.java:298
- TodoComment src/java_tools/buildjar/java/com/google/devtools/build/buildjar/JavaLibraryBuildRequest.java:323
- TodoComment src/java_tools/buildjar/java/com/google/devtools/build/buildjar/instrumentation/JacocoInstrumentationProcessor.java:102
- TodoComment src/java_tools/buildjar/java/com/google/devtools/build/buildjar/javac/BlazeJavacMain.java:118
- TodoComment src/java_tools/buildjar/java/com/google/devtools/build/buildjar/javac/BlazeJavacMain.java:225
- TodoComment src/java_tools/buildjar/java/com/google/devtools/build/buildjar/javac/BlazeJavacMain.java:228
- TodoComment src/java_tools/buildjar/java/com/google/devtools/build/buildjar/javac/plugins/dependency/StrictJavaDepsPlugin.java:299
- TodoComment src/java_tools/buildjar/java/com/google/devtools/build/buildjar/javac/plugins/dependency/DependencyModule.java:318
- TodoComment src/java_tools/buildjar/java/com/google/devtools/build/buildjar/javac/statistics/BlazeJavacStatistics.java:85
- TodoComment src/java_tools/import_deps_checker/java/com/google/devtools/build/importdeps/Main.java:182
- TodoComment src/java_tools/import_deps_checker/java/com/google/devtools/build/importdeps/DepsCheckerClassVisitor.java:112
- TodoComment src/java_tools/import_deps_checker/javatests/com/google/devtools/build/importdeps/MainTest.java:33
- TodoComment src/java_tools/junitrunner/java/com/google/testing/junit/runner/BazelTestRunner.java:181
- TodoComment src/java_tools/junitrunner/java/com/google/testing/junit/runner/internal/junit4/JUnit4TestXmlListener.java:83
- TodoComment src/java_tools/junitrunner/java/com/google/testing/junit/runner/junit4/JUnit4RunnerModule.java:53
- TodoComment src/java_tools/junitrunner/java/com/google/testing/junit/runner/model/TestCaseNode.java:178
- TodoComment src/java_tools/junitrunner/java/com/google/testing/junit/runner/model/AntXmlResultWriter.java:126
- TodoComment src/java_tools/junitrunner/java/com/google/testing/junit/runner/model/AntXmlResultWriter.java:129
- TodoComment src/java_tools/junitrunner/java/com/google/testing/junit/runner/model/AntXmlResultWriter.java:145
- ClassTooLong: SkyframeExecutor src/main/java/com/google/devtools/build/lib/skyframe/SkyframeExecutor.java:329
- ClassTooLong: CcModuleApi src/main/java/com/google/devtools/build/lib/starlarkbuildapi/cpp/CcModuleApi.java:47
- ClassTooLong: StarlarkBaseExternalContext src/main/java/com/google/devtools/build/lib/bazel/repository/starlark/StarlarkBaseExternalContext.java:116
- ClassTooLong: BazelRulesModule src/main/java/com/google/devtools/build/lib/bazel/rules/BazelRulesModule.java:38
- ClassTooLong: BlazeRuntime src/main/java/com/google/devtools/build/lib/runtime/BlazeRuntime.java:173
- ClassTooLong: RemoteExecutionService src/main/java/com/google/devtools/build/lib/remote/RemoteExecutionService.java:171
- ClassTooLong: SkyframeActionExecutor src/main/java/com/google/devtools/build/lib/skyframe/SkyframeActionExecutor.java:144
- ClassTooLong: StarlarkCustomCommandLine src/main/java/com/google/devtools/build/lib/analysis/starlark/StarlarkCustomCommandLine.java:132
- ClassTooLong: PackageFunction src/main/java/com/google/devtools/build/lib/skyframe/PackageFunction.java:120
- ClassTooLong: RuleContext src/main/java/com/google/devtools/build/lib/analysis/RuleContext.java:129
- ClassTooLong: CcStarlarkInternal src/main/java/com/google/devtools/build/lib/rules/cpp/CcStarlarkInternal.java:89
- ClassTooLong: StarlarkActionFactoryApi src/main/java/com/google/devtools/build/lib/starlarkbuildapi/StarlarkActionFactoryApi.java:40
- ClassTooLong: StarlarkRuleFunctionsApi src/main/java/com/google/devtools/build/lib/starlarkbuildapi/StarlarkRuleFunctionsApi.java:41
- ClassTooLong: RemoteModule src/main/java/com/google/devtools/build/lib/remote/RemoteModule.java:132
- ClassTooLong: BuildLanguageOptions src/main/java/com/google/devtools/build/lib/packages/semantics/BuildLanguageOptions.java:77
- ClassTooLong: ModuleFileGlobals src/main/java/com/google/devtools/build/lib/bazel/bzlmod/ModuleFileGlobals.java:62
- ClassTooLong: ActionExecutionFunction src/main/java/com/google/devtools/build/lib/skyframe/ActionExecutionFunction.java:138
- ClassTooLong: SkyframeBuildView src/main/java/com/google/devtools/build/lib/skyframe/SkyframeBuildView.java:139
- ClassTooLong: StarlarkActionFactory src/main/java/com/google/devtools/build/lib/analysis/starlark/StarlarkActionFactory.java:109
- ClassTooLong: TypeChecker src/main/java/net/starlark/java/syntax/TypeChecker.java:48
- ClassTooLong: Package src/main/java/com/google/devtools/build/lib/packages/Package.java:98
- ClassTooLong: RemoteOptions src/main/java/com/google/devtools/build/lib/remote/options/RemoteOptions.java:48
- ClassTooLong: StarlarkAttrModule src/main/java/com/google/devtools/build/lib/analysis/starlark/StarlarkAttrModule.java:92
- ClassTooLong: CoreOptions src/main/java/com/google/devtools/build/lib/analysis/config/CoreOptions.java:66
- ClassTooLong: RunCommand src/main/java/com/google/devtools/build/lib/runtime/commands/RunCommand.java:120
- FileTooLong: skyframe/SkyframeExecutor.java src/main/java/com/google/devtools/build/lib/skyframe/SkyframeExecutor.java
- FileTooLong: cpp/CcModuleApi.java src/main/java/com/google/devtools/build/lib/starlarkbuildapi/cpp/CcModuleApi.java
- FileTooLong: starlark/StarlarkBaseExternalContext.java src/main/java/com/google/devtools/build/lib/bazel/repository/starlark/StarlarkBaseExternalContext.java
- FileTooLong: starlark/StarlarkRuleClassFunctions.java src/main/java/com/google/devtools/build/lib/analysis/starlark/StarlarkRuleClassFunctions.java
- FileTooLong: rules/BazelRulesModule.java src/main/java/com/google/devtools/build/lib/bazel/rules/BazelRulesModule.java
- FileTooLong: runtime/BlazeRuntime.java src/main/java/com/google/devtools/build/lib/runtime/BlazeRuntime.java
- FileTooLong: remote/RemoteExecutionService.java src/main/java/com/google/devtools/build/lib/remote/RemoteExecutionService.java
- FileTooLong: cpp/CppCompileAction.java src/main/java/com/google/devtools/build/lib/rules/cpp/CppCompileAction.java
- FileTooLong: skyframe/SkyframeActionExecutor.java src/main/java/com/google/devtools/build/lib/skyframe/SkyframeActionExecutor.java
- FileTooLong: starlark/StarlarkCustomCommandLine.java src/main/java/com/google/devtools/build/lib/analysis/starlark/StarlarkCustomCommandLine.java
- FileTooLong: skyframe/PackageFunction.java src/main/java/com/google/devtools/build/lib/skyframe/PackageFunction.java
- FileTooLong: starlarkbuildapi/StarlarkAttrModuleApi.java src/main/java/com/google/devtools/build/lib/starlarkbuildapi/StarlarkAttrModuleApi.java
- FileTooLong: analysis/RuleContext.java src/main/java/com/google/devtools/build/lib/analysis/RuleContext.java
- FileTooLong: packages/RuleClass.java src/main/java/com/google/devtools/build/lib/packages/RuleClass.java
- FileTooLong: cpp/CcStarlarkInternal.java src/main/java/com/google/devtools/build/lib/rules/cpp/CcStarlarkInternal.java
- FileTooLong: syntax/Types.java src/main/java/net/starlark/java/syntax/Types.java
- FileTooLong: packages/Attribute.java src/main/java/com/google/devtools/build/lib/packages/Attribute.java
- FileTooLong: query2/SkyQueryEnvironment.java src/main/java/com/google/devtools/build/lib/query2/SkyQueryEnvironment.java
- FileTooLong: starlarkbuildapi/StarlarkActionFactoryApi.java src/main/java/com/google/devtools/build/lib/starlarkbuildapi/StarlarkActionFactoryApi.java
- FileTooLong: remote/RemoteModule.java src/main/java/com/google/devtools/build/lib/remote/RemoteModule.java
- FileTooLong: starlarkbuildapi/StarlarkRuleFunctionsApi.java src/main/java/com/google/devtools/build/lib/starlarkbuildapi/StarlarkRuleFunctionsApi.java
- FileTooLong: skyframe/SkyframeBuildView.java src/main/java/com/google/devtools/build/lib/skyframe/SkyframeBuildView.java
- FileTooLong: skyframe/ActionExecutionFunction.java src/main/java/com/google/devtools/build/lib/skyframe/ActionExecutionFunction.java
- FileTooLong: semantics/BuildLanguageOptions.java src/main/java/com/google/devtools/build/lib/packages/semantics/BuildLanguageOptions.java
- FileTooLong: starlark/StarlarkActionFactory.java src/main/java/com/google/devtools/build/lib/analysis/starlark/StarlarkActionFactory.java
- TooManyMethods: SkyframeExecutor src/main/java/com/google/devtools/build/lib/skyframe/SkyframeExecutor.java:329
- TooManyMethods: RuleContext src/main/java/com/google/devtools/build/lib/analysis/RuleContext.java:129
- TooManyMethods: RemoteOptions src/main/java/com/google/devtools/build/lib/remote/options/RemoteOptions.java:48
- TooManyMethods: CppCompileAction src/main/java/com/google/devtools/build/lib/rules/cpp/CppCompileAction.java:121
- TooManyMethods: BuildConfigurationValue src/main/java/com/google/devtools/build/lib/analysis/config/BuildConfigurationValue.java:89
- TooManyMethods: CppConfiguration src/main/java/com/google/devtools/build/lib/rules/cpp/CppConfiguration.java:52
- TooManyMethods: CoreOptions src/main/java/com/google/devtools/build/lib/analysis/config/CoreOptions.java:66
- TooManyMethods: SkyQueryEnvironment src/main/java/com/google/devtools/build/lib/query2/SkyQueryEnvironment.java:152
- TooManyMethods: CommandEnvironment src/main/java/com/google/devtools/build/lib/runtime/CommandEnvironment.java:102
- TooManyMethods: Path src/main/java/com/google/devtools/build/lib/vfs/Path.java:56
- TooManyMethods: BuildLanguageOptions src/main/java/com/google/devtools/build/lib/packages/semantics/BuildLanguageOptions.java:77
- TooManyMethods: CppOptions src/main/java/com/google/devtools/build/lib/rules/cpp/CppOptions.java:42
- TooManyMethods: Parser src/main/java/net/starlark/java/syntax/Parser.java:33
- TooManyMethods: SkyframeActionExecutor src/main/java/com/google/devtools/build/lib/skyframe/SkyframeActionExecutor.java:144
- TooManyMethods: StarlarkRuleContext src/main/java/com/google/devtools/build/lib/analysis/starlark/StarlarkRuleContext.java:129
- TooManyMethods: RemoteExternalOverlayFileSystem src/main/java/com/google/devtools/build/lib/remote/RemoteExternalOverlayFileSystem.java:91
- TooManyMethods: Artifact src/main/java/com/google/devtools/build/lib/actions/Artifact.java:122
- TooManyMethods: Attribute src/main/java/com/google/devtools/build/lib/packages/Attribute.java:81
- TooManyMethods: Builder src/main/java/com/google/devtools/build/lib/packages/RuleClass.java:336
- TooManyMethods: BuildGraveyardOptions src/main/java/com/google/devtools/build/lib/bazel/rules/BazelRulesModule.java:50
- TooManyMethods: AbstractAction src/main/java/com/google/devtools/build/lib/actions/AbstractAction.java:69
- TooManyMethods: Rule src/main/java/com/google/devtools/build/lib/packages/Rule.java:76
- TooManyMethods: BlazeRuntime src/main/java/com/google/devtools/build/lib/runtime/BlazeRuntime.java:173
- TooManyMethods: CommonCommandOptions src/main/java/com/google/devtools/build/lib/runtime/CommonCommandOptions.java:48
- TooManyMethods: UiEventHandler src/main/java/com/google/devtools/build/lib/runtime/UiEventHandler.java:93
- MethodTooLong: RemoteModule.setup src/main/java/com/google/devtools/build/lib/remote/RemoteModule.java:414
- MethodTooLong: BlazeCommandDispatcher.execExclusively src/main/java/com/google/devtools/build/lib/runtime/BlazeCommandDispatcher.java:376
- MethodTooLong: ModCommand.execInternal src/main/java/com/google/devtools/build/lib/bazel/commands/ModCommand.java:217
- MethodTooLong: BazelRepositoryModule.beforeCommand src/main/java/com/google/devtools/build/lib/bazel/BazelRepositoryModule.java:279
- MethodTooLong: SkyframeBuildView.analyzeAndExecuteTargets src/main/java/com/google/devtools/build/lib/skyframe/SkyframeBuildView.java:620
- MethodTooLong: Evaluate.runCore src/main/java/com/google/devtools/build/skyframe/AbstractParallelEvaluator.java:418
- MethodTooLong: BuildView.update src/main/java/com/google/devtools/build/lib/analysis/BuildView.java:224
- MethodTooLong: EvalUtils.binaryOp src/main/java/net/starlark/java/eval/EvalUtils.java:59
- MethodTooLong: PackageFunction.compute src/main/java/com/google/devtools/build/lib/skyframe/PackageFunction.java:368
- MethodTooLong: PackageFunction.loadPackage src/main/java/com/google/devtools/build/lib/skyframe/PackageFunction.java:994
- MethodTooLong: StandaloneTestStrategy.runTestAttempt src/main/java/com/google/devtools/build/lib/exec/StandaloneTestStrategy.java:651
- MethodTooLong: SkyframeExecutor.skyFunctions src/main/java/com/google/devtools/build/lib/skyframe/SkyframeExecutor.java:778
- MethodTooLong: ActionGraphTextOutputFormatterCallback.writeText src/main/java/com/google/devtools/build/lib/query2/aquery/ActionGraphTextOutputFormatterCallback.java:167
- MethodTooLong: SingleExtensionEvalFunction.compute src/main/java/com/google/devtools/build/lib/bazel/bzlmod/SingleExtensionEvalFunction.java:99
- MethodTooLong: ParallelEvaluator.bubbleErrorUp src/main/java/com/google/devtools/build/skyframe/ParallelEvaluator.java:293
- MethodTooLong: PatchUtil.applyInternal src/main/java/com/google/devtools/build/lib/bazel/repository/decompressor/PatchUtil.java:448
- MethodTooLong: NodePrinter.printExpr src/main/java/net/starlark/java/syntax/NodePrinter.java:313
- MethodTooLong: BlazeRuntime.newRuntime src/main/java/com/google/devtools/build/lib/runtime/BlazeRuntime.java:1408
- MethodTooLong: SourceFileReader.readDocsFromComments src/main/java/com/google/devtools/build/docgen/SourceFileReader.java:85
- MethodTooLong: BuildEventServiceUploader.publishBuildEvents src/main/java/com/google/devtools/build/lib/buildeventservice/BuildEventServiceUploader.java:458
- MethodTooLong: JavaCompilationHelper.createCompileAction src/main/java/com/google/devtools/build/lib/rules/java/JavaCompilationHelper.java:140
- MethodTooLong: BuildDriverFunction.compute src/main/java/com/google/devtools/build/lib/skyframe/BuildDriverFunction.java:157
- MethodTooLong: SkyframeBuildView.configureTargets src/main/java/com/google/devtools/build/lib/skyframe/SkyframeBuildView.java:402
- MethodTooLong: RemoteSpawnCache.lookup src/main/java/com/google/devtools/build/lib/remote/RemoteSpawnCache.java:84
- MethodTooLong: RemoteAnalysisCacheFactory.create src/main/java/com/google/devtools/build/lib/skyframe/serialization/analysis/RemoteAnalysisCacheFactory.java:80
- Hotspot: src/main/java/com/google/devtools/build/lib/remote/RemoteModule.java src/main/java/com/google/devtools/build/lib/remote/RemoteModule.java:414
- Hotspot: src/main/java/com/google/devtools/build/lib/runtime/BlazeCommandDispatcher.java src/main/java/com/google/devtools/build/lib/runtime/BlazeCommandDispatcher.java:376
- Hotspot: src/main/java/com/google/devtools/build/lib/analysis/starlark/StarlarkActionFactory.java src/main/java/com/google/devtools/build/lib/analysis/starlark/StarlarkActionFactory.java:724
- Hotspot: src/main/java/net/starlark/java/syntax/TypeChecker.java src/main/java/net/starlark/java/syntax/TypeChecker.java:156
- Hotspot: src/main/java/com/google/devtools/build/lib/bazel/BazelRepositoryModule.java src/main/java/com/google/devtools/build/lib/bazel/BazelRepositoryModule.java:279
- Hotspot: src/main/java/net/starlark/java/syntax/Types.java src/main/java/net/starlark/java/syntax/Types.java:613
- Hotspot: src/main/java/com/google/devtools/build/lib/remote/RemoteExternalOverlayFileSystem.java src/main/java/com/google/devtools/build/lib/remote/RemoteExternalOverlayFileSystem.java:288
- Hotspot: src/main/java/com/google/devtools/build/lib/bazel/repository/RepositoryFetchFunction.java src/main/java/com/google/devtools/build/lib/bazel/repository/RepositoryFetchFunction.java:222
- Hotspot: src/main/java/com/google/devtools/build/lib/analysis/RuleContext.java src/main/java/com/google/devtools/build/lib/analysis/RuleContext.java:1750
- Hotspot: src/main/java/com/google/devtools/build/lib/bazel/repository/decompressor/PatchUtil.java src/main/java/com/google/devtools/build/lib/bazel/repository/decompressor/PatchUtil.java:448
- Hotspot: src/main/java/com/google/devtools/build/lib/sandbox/SandboxModule.java src/main/java/com/google/devtools/build/lib/sandbox/SandboxModule.java:198
- Hotspot: src/main/java/com/google/devtools/build/lib/analysis/RuleConfiguredTargetBuilder.java src/main/java/com/google/devtools/build/lib/analysis/RuleConfiguredTargetBuilder.java:101
- Hotspot: src/main/java/com/google/devtools/build/lib/analysis/starlark/StarlarkCustomCommandLine.java src/main/java/com/google/devtools/build/lib/analysis/starlark/StarlarkCustomCommandLine.java:333
- Hotspot: src/main/java/com/google/devtools/build/lib/buildtool/BuildTool.java src/main/java/com/google/devtools/build/lib/buildtool/BuildTool.java:1005
- Hotspot: src/main/java/com/google/devtools/build/lib/collect/nestedset/NestedSet.java src/main/java/com/google/devtools/build/lib/collect/nestedset/NestedSet.java:224
- Hotspot: src/main/java/com/google/devtools/build/lib/remote/RemoteExecutionService.java src/main/java/com/google/devtools/build/lib/remote/RemoteExecutionService.java:1671
- Hotspot: src/main/java/com/google/devtools/build/lib/skyframe/serialization/analysis/FileDependencySerializer.java src/main/java/com/google/devtools/build/lib/skyframe/serialization/analysis/FileDependencySerializer.java:955
- Hotspot: src/main/java/com/google/devtools/build/lib/sandbox/SandboxStash.java src/main/java/com/google/devtools/build/lib/sandbox/SandboxStash.java:116
- Hotspot: src/main/java/com/google/devtools/build/lib/skyframe/BzlLoadFunction.java src/main/java/com/google/devtools/build/lib/skyframe/BzlLoadFunction.java:757
- Hotspot: src/main/java/com/google/devtools/build/lib/skyframe/BzlCompileFunction.java src/main/java/com/google/devtools/build/lib/skyframe/BzlCompileFunction.java:108
- Hotspot: src/main/java/com/google/devtools/build/lib/skyframe/SkyframeActionExecutor.java src/main/java/com/google/devtools/build/lib/skyframe/SkyframeActionExecutor.java:1752
- Hotspot: src/main/java/com/google/devtools/build/lib/bazel/commands/ModCommand.java src/main/java/com/google/devtools/build/lib/bazel/commands/ModCommand.java:217
- Hotspot: src/main/java/com/google/devtools/build/lib/skyframe/ActionExecutionFunction.java src/main/java/com/google/devtools/build/lib/skyframe/ActionExecutionFunction.java:669
- Hotspot: src/main/java/com/google/devtools/build/skyframe/AbstractParallelEvaluator.java src/main/java/com/google/devtools/build/skyframe/AbstractParallelEvaluator.java:418
- Hotspot: src/main/java/com/google/devtools/build/lib/analysis/BuildView.java src/main/java/com/google/devtools/build/lib/analysis/BuildView.java:224
- Low cohesion: Builder (LCOM4 16) src/main/java/com/google/devtools/build/lib/actions/SpawnResult.java:620
- Low cohesion: Builder (LCOM4 11) src/main/java/com/google/devtools/build/lib/analysis/starlark/StarlarkCustomCommandLine.java:729
- Low cohesion: Builder (LCOM4 9) src/main/java/com/google/devtools/build/lib/skyframe/packages/AbstractPackageLoader.java:163
- Low cohesion: CppConfiguration (LCOM4 9) src/main/java/com/google/devtools/build/lib/rules/cpp/CppConfiguration.java:52
- Low cohesion: ArchiveRepoSpecBuilder (LCOM4 9) src/main/java/com/google/devtools/build/lib/bazel/bzlmod/ArchiveRepoSpecBuilder.java:33
- Low cohesion: ServerBuilder (LCOM4 8) src/main/java/com/google/devtools/build/lib/runtime/ServerBuilder.java:30
- Low cohesion: JavaStarlarkCommon (LCOM4 8) src/main/java/com/google/devtools/build/lib/rules/java/JavaStarlarkCommon.java:63
- Low cohesion: ModuleAttribute (LCOM4 7) third_party/java/proguard/proguard6.2.2/src/proguard/classfile/attribute/module/ModuleAttribute.java:34
- Low cohesion: SubprocessBuilder (LCOM4 7) src/main/java/com/google/devtools/build/lib/shell/SubprocessBuilder.java:30
- Low cohesion: PyBuiltins (LCOM4 7) src/main/java/com/google/devtools/build/lib/rules/python/PyBuiltins.java:57
- Low cohesion: AbstractHttpHandler (LCOM4 6) src/main/java/com/google/devtools/build/lib/remote/http/AbstractHttpHandler.java:38
- Low cohesion: AbstractInMemoryMemoizingEvaluator (LCOM4 5) src/main/java/com/google/devtools/build/skyframe/AbstractInMemoryMemoizingEvaluator.java:64
- Low cohesion: Builder (LCOM4 5) src/main/java/com/google/devtools/build/lib/skyframe/serialization/ObjectCodecRegistry.java:418
- Low cohesion: RemoteExecutionCache (LCOM4 5) src/main/java/com/google/devtools/build/lib/remote/RemoteExecutionCache.java:75
- Low cohesion: AbstractBuilder (LCOM4 5) src/main/java/com/google/devtools/build/lib/packages/Package.java:770
- Low cohesion: TestStrategy (LCOM4 5) src/main/java/com/google/devtools/build/lib/analysis/test/TestStrategy.java:73
- Low cohesion: Builder (LCOM4 5) src/main/java/com/google/devtools/build/lib/analysis/RuleContext.java:1458
- Low cohesion: Builder (LCOM4 5) src/main/java/com/google/devtools/build/lib/analysis/ConfiguredRuleClassProvider.java:140
- Low cohesion: ProgramClass (LCOM4 4) third_party/java/proguard/proguard6.2.2/src/proguard/classfile/ProgramClass.java:35
- Low cohesion: TypeTable (LCOM4 4) src/main/java/net/starlark/java/syntax/TypeTable.java:37
- Low cohesion: CcToolchainFeatures (LCOM4 4) src/main/java/com/google/devtools/build/lib/rules/cpp/CcToolchainFeatures.java:84
- Low cohesion: ByteStreamBuildEventArtifactUploader (LCOM4 4) src/main/java/com/google/devtools/build/lib/remote/ByteStreamBuildEventArtifactUploader.java:66
- Low cohesion: PathLabelVisitor (LCOM4 4) src/main/java/com/google/devtools/build/lib/query2/query/PathLabelVisitor.java:50
- Low cohesion: GraphlessBlazeQueryEnvironment (LCOM4 4) src/main/java/com/google/devtools/build/lib/query2/query/GraphlessBlazeQueryEnvironment.java:80
- Low cohesion: AbstractBlazeQueryEnvironment (LCOM4 4) src/main/java/com/google/devtools/build/lib/query2/common/AbstractBlazeQueryEnvironment.java:81
- Duplicated block (9 lines × 2) src/main/java/com/google/devtools/build/lib/bazel/bzlmod/BazelModTidyFunction.java:97
- Duplicated block (9 lines × 2) src/main/java/com/google/devtools/build/lib/bazel/bzlmod/ModuleFileGlobals.java:730
- Duplicated block (9 lines × 2) src/main/java/com/google/devtools/build/lib/bazel/commands/VendorCommand.java:243
- Duplicated block (9 lines × 2) src/main/java/com/google/devtools/build/lib/collect/compacthashmap/CompactHashMap.java:291
- Duplicated block (9 lines × 2) src/main/java/com/google/devtools/build/lib/rules/java/JavaStarlarkCommon.java:163
- Duplicated block (9 lines × 2) src/main/java/com/google/devtools/build/lib/sandbox/DarwinSandboxedSpawnRunner.java:206
- Duplicated block (9 lines × 2) src/main/java/com/google/devtools/build/lib/sandbox/SandboxHelpers.java:347
- Duplicated block (9 lines × 2) src/main/java/com/google/devtools/build/lib/skyframe/DependencyResolver.java:598
- Duplicated block (9 lines × 2) src/main/java/com/google/devtools/build/lib/skyframe/serialization/analysis/FileDependencyDeserializer.java:630
- Duplicated block (9 lines × 2) src/main/java/com/google/devtools/build/lib/util/VarInt.java:66
- Duplicated block (9 lines × 2) src/main/java/com/google/devtools/build/lib/vfs/PathFragment.java:592
- Duplicated block (9 lines × 2) src/main/java/com/google/devtools/build/lib/vfs/UnixOsPathPolicy.java:76
- Duplicated block (9 lines × 2) src/main/java/com/google/devtools/build/skyframe/SkyFunctionException.java:117
- Duplicated block (9 lines × 2) src/main/java/com/google/devtools/build/lib/skyframe/BzlLoadCycleReporter.java:54
- Duplicated block (9 lines × 2) src/main/java/com/google/devtools/build/lib/skyframe/serialization/autocodec/AutoCodecProcessor.java:85
- Duplicated block (9 lines × 2) src/main/java/com/google/devtools/build/lib/skyframe/serialization/autocodec/DeferredObjectCodecFieldGenerators.java:259
- Duplicated block (9 lines × 2) src/main/java/com/google/devtools/build/lib/unix/UnixFileSystem.java:405
- Duplicated block (9 lines × 2) src/main/java/net/starlark/java/eval/ImmutableSingletonStarlarkList.java:74
- Duplicated block (9 lines × 2) src/main/java/com/google/devtools/build/lib/analysis/starlark/StarlarkAttributeTransitionProvider.java:178
- Duplicated block (9 lines × 2) src/main/java/com/google/devtools/build/lib/bazel/BazelFileSystemModule.java:56
- Duplicated block (9 lines × 2) src/main/java/com/google/devtools/build/lib/exec/CompactSpawnLogContext.java:103
- Duplicated block (9 lines × 2) src/main/java/com/google/devtools/build/lib/exec/SpawnStrategyRegistry.java:752
- Duplicated block (9 lines × 2) src/main/java/com/google/devtools/build/lib/rules/cpp/CcToolchainProvider.java:144
- Duplicated block (9 lines × 2) src/main/java/com/google/devtools/build/lib/runtime/commands/info/GcCountInfoItem.java:32
- Duplicated block (9 lines × 2) src/main/java/net/starlark/java/syntax/CastExpression.java:70
- Duplicated block (7 lines × 2) src/main/java/com/google/devtools/build/lib/actions/cache/CompactPersistentActionCache.java:1020
- Duplicated block (7 lines × 2) src/main/java/com/google/devtools/build/lib/query2/PostAnalysisQueryEnvironment.java:437
- Duplicated block (7 lines × 2) src/main/java/com/google/devtools/build/lib/runtime/BlazeOptionHandler.java:784
- Duplicated block (7 lines × 2) src/main/java/com/google/devtools/build/lib/runtime/commands/AqueryCommand.java:125
- Duplicated block (7 lines × 2) src/main/java/com/google/devtools/build/lib/server/CommandServer.java:610
- Duplicated block (7 lines × 2) src/main/java/com/google/devtools/build/lib/skyframe/toolchains/RegisteredExecutionPlatformsFunction.java:168
- Duplicated block (7 lines × 2) src/main/java/com/google/devtools/build/docgen/BuildEncyclopediaGenerator.java:42
- Duplicated block (7 lines × 2) src/main/java/com/google/devtools/build/lib/analysis/BuildView.java:869
- Duplicated block (7 lines × 2) src/main/java/com/google/devtools/build/lib/analysis/WorkspaceStatusAction.java:218
- Duplicated block (7 lines × 2) src/main/java/com/google/devtools/build/lib/analysis/actions/SymlinkAction.java:475
- Duplicated block (7 lines × 2) src/main/java/com/google/devtools/build/lib/bazel/SpawnLogModule.java:318
- Duplicated block (7 lines × 2) src/main/java/com/google/devtools/build/lib/buildtool/AqueryProcessor.java:266
- Duplicated block (7 lines × 2) src/main/java/com/google/devtools/build/lib/query2/SkyQueryEnvironment.java:844
- Duplicated block (7 lines × 2) src/main/java/com/google/devtools/build/lib/query2/query/BlazeQueryEnvironment.java:463
- Duplicated block (7 lines × 2) src/main/java/com/google/devtools/build/lib/skyframe/ConfiguredTargetFunction.java:617
- Duplicated block (7 lines × 2) src/main/java/com/google/devtools/build/lib/skyframe/serialization/ImmutableSetCodec.java:78
- Duplicated block (7 lines × 2) src/main/java/com/google/devtools/build/lib/skyframe/toolchains/RegisteredExecutionPlatformsValue.java:93
- Duplicated block (7 lines × 2) src/main/java/com/google/devtools/build/lib/worker/WorkerMultiplexerManager.java:128
- Duplicated block (7 lines × 2) src/main/java/com/google/devtools/build/lib/actions/Artifact.java:1334
- Duplicated block (7 lines × 2) src/main/java/com/google/devtools/build/lib/query2/SkyQueryEnvironment.java:1026
- Duplicated block (7 lines × 2) src/main/java/com/google/devtools/build/lib/skyframe/serialization/ImmutableBiMapCodec.java:91
- Duplicated block (7 lines × 2) src/main/java/net/starlark/java/eval/StarlarkList.java:258
- Duplicated block (7 lines × 2) src/main/java/com/google/devtools/build/lib/query2/SkyQueryEnvironment.java:1226
- Duplicated block (8 lines × 2) src/main/java/com/google/devtools/build/lib/analysis/starlark/StarlarkActionFactory.java:977
- Duplicated block (8 lines × 2) src/main/java/com/google/devtools/build/lib/bazel/bzlmod/ModuleFileFunction.java:491
- Duplicated block (8 lines × 2) src/main/java/com/google/devtools/build/lib/bazel/bzlmod/modcommand/ModExecutor.java:462
- Duplicated block (8 lines × 2) src/main/java/com/google/devtools/build/lib/bazel/repository/RepositoryOptions.java:560
- Duplicated block (8 lines × 2) src/main/java/com/google/devtools/build/lib/buildtool/BuildResultPrinter.java:449
- Duplicated block (8 lines × 2) src/main/java/com/google/devtools/build/lib/platform/SystemLoadAdvisoryModule.java:89
- Duplicated block (8 lines × 2) src/main/java/com/google/devtools/build/lib/query2/SkyQueryEnvironment.java:786
- Duplicated block (8 lines × 2) src/main/java/com/google/devtools/build/lib/remote/RemoteGrpcServiceConfig.java:100
- Duplicated block (8 lines × 2) src/main/java/com/google/devtools/build/lib/rules/config/ConfigGlobalLibrary.java:54
- Duplicated block (8 lines × 2) src/main/java/com/google/devtools/build/lib/rules/cpp/CppCompileAction.java:681
- Duplicated block (8 lines × 2) src/main/java/com/google/devtools/build/lib/rules/cpp/CppCompileAction.java:1625
- Duplicated block (8 lines × 2) src/main/java/com/google/devtools/build/lib/rules/java/JavaRuntimeInfo.java:106
- Duplicated block (8 lines × 2) src/main/java/com/google/devtools/build/lib/runtime/commands/RunCommandLine.java:257
- Duplicated block (8 lines × 2) src/main/java/com/google/devtools/build/lib/skyframe/SkyframeExecutor.java:2935
- Duplicated block (8 lines × 2) src/main/java/com/google/devtools/build/lib/skyframe/serialization/analysis/FileDependencyDeserializer.java:292
- Duplicated block (8 lines × 2) src/main/java/com/google/devtools/common/options/InvocationPolicyEnforcer.java:839
- Duplicated block (8 lines × 2) src/main/java/net/starlark/java/lib/json/Json.java:629
- Duplicated block (8 lines × 2) src/main/java/com/google/devtools/build/lib/analysis/producers/TargetAndConfigurationProducer.java:345
- Duplicated block (8 lines × 2) src/main/java/com/google/devtools/build/lib/packages/NoSuchPackageException.java:82
- Duplicated block (8 lines × 2) src/main/java/net/starlark/java/syntax/CallExpression.java:97
- Duplicated block (11 lines × 2) src/main/java/com/google/devtools/build/lib/bazel/bzlmod/VendorFileFunction.java:162
- Duplicated block (11 lines × 2) src/main/java/com/google/devtools/build/lib/bazel/bzlmod/modcommand/ModExecutor.java:131
- Duplicated block (11 lines × 2) src/main/java/com/google/devtools/build/lib/bazel/commands/ModCommand.java:644
- Duplicated block (11 lines × 2) src/main/java/com/google/devtools/build/lib/bazel/repository/decompressor/PatchUtil.java:641
- Duplicated block (11 lines × 2) src/main/java/com/google/devtools/build/lib/bazel/repository/downloader/HashInputStream.java:83
- Duplicated block (11 lines × 2) src/main/java/com/google/devtools/build/lib/bazel/repository/starlark/StarlarkBaseExternalContext.java:812
- Duplicated block (11 lines × 2) src/main/java/com/google/devtools/build/lib/collect/compacthashmap/CompactHashMap.java:321
- Duplicated block (11 lines × 2) src/main/java/com/google/devtools/build/lib/remote/BazelOutputService.java:144
- Duplicated block (11 lines × 2) src/main/java/com/google/devtools/build/lib/rules/cpp/SolibSymlinkAction.java:82
- Duplicated block (11 lines × 2) src/main/java/com/google/devtools/build/lib/rules/java/JavaCompileActionBuilder.java:309
- Duplicated block (11 lines × 2) src/main/java/com/google/devtools/build/lib/runtime/BlazeCommandDispatcher.java:689
- Duplicated block (11 lines × 2) src/main/java/com/google/devtools/build/lib/sandbox/AbstractContainerizingSandboxedSpawn.java:173
- Duplicated block (11 lines × 2) src/main/java/com/google/devtools/build/lib/skyframe/serialization/MapHelpers.java:71
- Duplicated block (11 lines × 2) src/tools/execlog/src/main/java/com/google/devtools/build/execlog/ExecLogParser.java:222
- Duplicated block (11 lines × 2) src/main/java/com/google/devtools/build/lib/bazel/commands/FetchCommand.java:247
- Duplicated block (11 lines × 2) src/main/java/net/starlark/java/eval/MutableStarlarkList.java:51
- Duplicated block (11 lines × 2) src/main/java/com/google/devtools/build/lib/skyframe/serialization/analysis/FileOpMatchMemoizingLookup.java:61
- Duplicated block (10 lines × 2) src/main/java/com/google/devtools/build/lib/analysis/starlark/StarlarkCustomCommandLine.java:1066
- Duplicated block (10 lines × 2) src/main/java/com/google/devtools/build/lib/bazel/repository/starlark/StarlarkBaseExternalContext.java:1526
- Duplicated block (10 lines × 2) src/main/java/com/google/devtools/build/lib/exec/local/LocalSpawnRunner.java:142
- Duplicated block (10 lines × 2) src/main/java/com/google/devtools/build/lib/exec/local/PosixLocalEnvProvider.java:49
- Duplicated block (10 lines × 2) src/main/java/com/google/devtools/build/lib/profiler/ThreadMetadata.java:148
- Duplicated block (10 lines × 2) src/main/java/com/google/devtools/build/lib/query2/aquery/ActionGraphQueryEnvironment.java:447
- Duplicated block (10 lines × 2) src/main/java/com/google/devtools/build/lib/query2/query/aspectresolvers/ConservativeAspectResolver.java:49
- Duplicated block (10 lines × 2) src/main/java/com/google/devtools/build/lib/remote/BazelOutputService.java:244
- Duplicated block (10 lines × 2) src/main/java/com/google/devtools/build/lib/remote/BazelOutputService.java:343
- Duplicated block (10 lines × 2) src/main/java/com/google/devtools/build/lib/remote/RemoteExternalOverlayFileSystem.java:305
- Duplicated block (10 lines × 2) src/main/java/com/google/devtools/build/lib/runtime/GcChurningDetector.java:138
- Duplicated block (10 lines × 2) src/main/java/com/google/devtools/build/lib/runtime/SkymeldUiStateTracker.java:217
- Duplicated block (10 lines × 2) src/main/java/com/google/devtools/build/lib/runtime/commands/HelpCommand.java:561
- Duplicated block (10 lines × 2) src/main/java/com/google/devtools/build/lib/runtime/commands/RunCommandLine.java:182
- Duplicated block (10 lines × 2) src/main/java/net/starlark/java/annot/processor/StarlarkMethodProcessor.java:554
- Duplicated block (10 lines × 2) src/main/java/net/starlark/java/eval/StarlarkInt.java:503
- Duplicated block (10 lines × 2) src/main/java/com/google/devtools/build/lib/query2/query/BlazeQueryEnvironment.java:167
- Duplicated block (6 lines × 2) src/main/java/com/google/devtools/build/lib/bazel/bzlmod/modcommand/ModExecutor.java:303
- Duplicated block (6 lines × 2) src/main/java/com/google/devtools/build/lib/packages/AbstractAttributeMapper.java:177
- Duplicated block (6 lines × 2) src/main/java/com/google/devtools/build/lib/packages/BazelStarlarkEnvironment.java:546
- Duplicated block (6 lines × 2) src/main/java/com/google/devtools/build/lib/packages/StarlarkInfoWithSchema.java:552
- Duplicated block (6 lines × 2) src/main/java/com/google/devtools/build/lib/remote/util/Utils.java:438
- Duplicated block (6 lines × 2) src/main/java/com/google/devtools/build/lib/runtime/commands/RunCommandLine.java:186
- Duplicated block (6 lines × 2) src/main/java/com/google/devtools/build/lib/skyframe/serialization/ObjectCodecRegistry.java:123
- Duplicated block (6 lines × 2) src/main/java/com/google/devtools/build/lib/util/VarInt.java:72
- Duplicated block (6 lines × 2) src/main/java/com/google/devtools/common/options/testing/OptionsTester.java:113
- Duplicated block (6 lines × 2) src/main/java/net/starlark/java/syntax/TypeChecker.java:753
- Duplicated block (6 lines × 2) src/main/java/net/starlark/java/syntax/Types.java:1985
- Duplicated block (6 lines × 2) src/main/java/com/google/devtools/build/lib/analysis/BuildView.java:808
- Duplicated block (6 lines × 2) src/main/java/com/google/devtools/build/lib/skyframe/ActionInputMetadataProvider.java:151
- Duplicated block (12 lines × 2) src/main/java/com/google/devtools/build/lib/actions/MachineLoadProvider.java:49
- Duplicated block (12 lines × 2) src/main/java/com/google/devtools/build/lib/bazel/bzlmod/ModuleFileGlobals.java:1103
- Duplicated block (12 lines × 2) src/main/java/com/google/devtools/build/lib/bazel/commands/FetchCommand.java:200
- Duplicated block (12 lines × 2) src/main/java/com/google/devtools/build/lib/bazel/repository/decompressor/SevenZDecompressor.java:112
- Duplicated block (12 lines × 2) src/main/java/com/google/devtools/build/lib/collect/compacthashmap/CompactHashMap.java:271
- Duplicated block (12 lines × 2) src/main/java/com/google/devtools/build/lib/collect/compacthashmap/CompactHashMap.java:350
- Duplicated block (12 lines × 2) src/main/java/com/google/devtools/build/lib/skyframe/GlobFunctionWithMultipleRecursiveFunctions.java:260
- Duplicated block (12 lines × 2) src/main/java/com/google/devtools/build/lib/skyframe/PackageLookupFunction.java:101
- Duplicated block (12 lines × 2) src/main/java/com/google/devtools/build/lib/skyframe/SkyframeBuildView.java:534
- Duplicated block (12 lines × 2) src/main/java/com/google/devtools/build/lib/skyframe/toolchains/RegisteredExecutionPlatformsFunction.java:176
- Duplicated block (12 lines × 2) src/main/java/com/google/devtools/build/lib/collect/compacthashmap/CompactHashMap.java:104
- Duplicated block (12 lines × 2) src/main/java/com/google/devtools/build/lib/query2/query/BlazeQueryEnvironment.java:475
- Change coupling: AnalysisPhaseRunner.java ↔ FlagSetValue.java src/main/java/com/google/devtools/build/lib/buildtool/AnalysisPhaseRunner.java:1
- Change coupling: Project.java ↔ FlagSetFunction.java src/main/java/com/google/devtools/build/lib/analysis/Project.java:1
- Change coupling: RemoteSpawnCache.java ↔ RemoteSpawnRunner.java src/main/java/com/google/devtools/build/lib/remote/RemoteSpawnCache.java:1
- Change coupling: StarlarkRepositoryModule.java ↔ BuildGlobals.java src/main/java/com/google/devtools/build/lib/bazel/repository/starlark/StarlarkRepositoryModule.java:1
- Change coupling: RemoteAnalysisCacheReaderDepsProvider.java ↔ RemoteAnalysisCachingDependenciesProvider.java src/main/java/com/google/devtools/build/lib/skyframe/serialization/analysis/RemoteAnalysisCacheReaderDepsProvider.java:1
- Change coupling: DelegatingPairInputMetadataProvider.java ↔ ActionInputMetadataProvider.java src/main/java/com/google/devtools/build/lib/actions/DelegatingPairInputMetadataProvider.java:1
- Change coupling: FingerprintValueService.java ↔ GetRecordingStore.java src/main/java/com/google/devtools/build/lib/skyframe/serialization/FingerprintValueService.java:1
- Change coupling: CompletionFunction.java ↔ LostImportantOutputHandlerModule.java src/main/java/com/google/devtools/build/lib/skyframe/CompletionFunction.java:1
- Change coupling: FrontierSerializer.java ↔ RemoteAnalysisCacheReaderDepsProvider.java src/main/java/com/google/devtools/build/lib/skyframe/serialization/analysis/FrontierSerializer.java:1
- Change coupling: BuildResultPrinter.java ↔ TestCommand.java src/main/java/com/google/devtools/build/lib/buildtool/BuildResultPrinter.java:1
- Change coupling: RunfilesSupport.java ↔ PyBuiltins.java src/main/java/com/google/devtools/build/lib/analysis/RunfilesSupport.java:1
- Duplicated block (5 lines × 2) src/main/java/com/google/devtools/build/lib/bazel/bzlmod/Facts.java:100
- Duplicated block (5 lines × 2) src/main/java/com/google/devtools/build/lib/bazel/bzlmod/RegularRunnableExtension.java:248
- Duplicated block (5 lines × 2) src/main/java/com/google/devtools/build/lib/query2/PostAnalysisQueryEnvironment.java:431
- Duplicated block (5 lines × 2) src/main/java/com/google/devtools/build/lib/runtime/commands/RunCommandLine.java:219
- Duplicated block (5 lines × 2) src/main/java/com/google/devtools/build/lib/skyframe/AspectFunction.java:388
- Duplicated block (5 lines × 2) src/main/java/com/google/devtools/build/lib/skyframe/SkyframeExecutor.java:1948
- Duplicated block (5 lines × 2) src/main/java/com/google/devtools/build/lib/skyframe/serialization/analysis/FileDependencyDeserializer.java:638
- Duplicated block (5 lines × 2) src/main/java/net/starlark/java/eval/ImmutableStarlarkList.java:101
- Duplicated block (5 lines × 2) src/main/java/com/google/devtools/build/lib/bazel/bzlmod/modcommand/JsonOutputFormatter.java:136
- Duplicated block (5 lines × 2) src/main/java/com/google/devtools/build/lib/bazel/repository/starlark/StarlarkRepositoryModule.java:82
- Duplicated block (5 lines × 2) examples/java-native/src/main/java/com/example/myproject/Greeter.java:43
- HackComment scripts/docs/docs2mdx.py:369
- HackComment src/main/java/com/google/devtools/build/lib/collect/nestedset/NestedSet.java:741
- HackComment src/main/java/com/google/devtools/build/lib/remote/ExecutionStatusException.java:46
- HackComment src/main/java/com/google/devtools/build/lib/rules/cpp/CppCompileAction.java:1794
- HackComment src/main/java/com/google/devtools/build/lib/util/FileHandlerQuerier.java:65
- HackComment src/main/java/com/google/devtools/build/lib/util/FileHandlerQuerier.java:79
- HackComment src/test/java/com/google/devtools/build/lib/buildtool/TargetSummaryEventTest.java:233
- HackComment src/test/java/com/google/devtools/build/lib/view/cpp/CppTemplateTest.java:114
- Duplicated block (14 lines × 2) src/main/java/com/google/devtools/build/lib/analysis/ConfiguredAspect.java:183
- Duplicated block (14 lines × 2) src/main/java/com/google/devtools/build/lib/dynamic/LocalBranch.java:178
- Duplicated block (14 lines × 2) src/main/java/com/google/devtools/build/lib/packages/PackageSpecification.java:509
- Duplicated block (14 lines × 2) src/main/java/com/google/devtools/build/lib/query2/aquery/ActionGraphSummaryOutputFormatterCallback.java:67
- Duplicated block (14 lines × 2) src/main/java/com/google/devtools/build/lib/query2/query/BlazeQueryEnvironment.java:386
- Duplicated block (14 lines × 2) src/main/java/com/google/devtools/build/lib/skyframe/config/FlagSetFunction.java:325
- Duplicated block (14 lines × 2) src/main/java/com/google/devtools/build/lib/skyframe/serialization/ArrayProcessor.java:115
- Duplicated block (14 lines × 2) src/main/java/net/starlark/java/eval/BuiltinFunction.java:407
- Duplicated block (15 lines × 2) src/main/java/com/google/devtools/build/lib/analysis/starlark/Args.java:346
- Duplicated block (15 lines × 2) src/main/java/com/google/devtools/build/lib/analysis/starlark/StarlarkRuleClassFunctions.java:286
- Duplicated block (15 lines × 2) src/main/java/com/google/devtools/build/lib/bazel/bzlmod/IndexRegistry.java:522
- Duplicated block (15 lines × 2) src/main/java/com/google/devtools/build/lib/buildtool/AnalysisAndExecutionPhaseRunner.java:169
- Duplicated block (15 lines × 2) src/main/java/com/google/devtools/build/lib/includescanning/LegacyIncludeScanner.java:210
- Duplicated block (15 lines × 2) src/main/java/com/google/devtools/build/lib/query2/engine/BuildFilesFunction.java:51
- Duplicated block (14–15 lines × 2) src/main/java/com/google/devtools/build/lib/buildtool/AnalysisAndExecutionPhaseRunner.java:124
- Duplicated block (14–15 lines × 2) src/main/java/com/google/devtools/build/lib/exec/local/XcodeLocalEnvProvider.java:194
- Duplicated block (14–15 lines × 2) src/main/java/com/google/devtools/build/lib/skyframe/TargetPatternPhaseFunction.java:437
- Duplicated block (14–15 lines × 2) src/main/java/com/google/devtools/build/lib/skyframe/toolchains/RegisteredExecutionPlatformsFunction.java:81
- Duplicated block (14–15 lines × 2) src/main/java/net/starlark/java/annot/processor/StarlarkMethodProcessor.java:222
- Duplicated block (14–15 lines × 2) src/main/java/net/starlark/java/eval/FlagGuardedValue.java:27
- Duplicated block (13 lines × 2) src/main/java/com/google/devtools/build/lib/analysis/LocationExpander.java:458
- Duplicated block (13 lines × 2) src/main/java/com/google/devtools/build/lib/bazel/commands/FetchCommand.java:85
- Duplicated block (13 lines × 2) src/main/java/com/google/devtools/build/lib/buildtool/SkyframeBuilder.java:186
- Duplicated block (13 lines × 2) src/main/java/com/google/devtools/build/lib/remote/Retrier.java:359
- Duplicated block (13 lines × 2) src/main/java/com/google/devtools/build/lib/skyframe/EvalMacroFunction.java:100
- Duplicated block (13 lines × 2) src/main/java/com/google/devtools/build/lib/vfs/DiskBackedFileSystem.java:76
- Members sharing a duplicated core (4 members, 50+ identical tokens) src/main/java/com/google/devtools/build/lib/bazel/commands/FetchCommand.java:84
- Members sharing a duplicated core (4 members, 50+ identical tokens) src/main/java/com/google/devtools/build/lib/rules/cpp/CcToolchainFeaturesLib.java:158
- Members sharing a duplicated core (4 members, 50+ identical tokens) src/main/java/com/google/devtools/build/lib/runtime/commands/AqueryCommand.java:86
- Members sharing a duplicated core (4 members, 50+ identical tokens) src/main/java/com/google/devtools/build/lib/runtime/commands/RunCommandLine.java:180
- Members sharing a duplicated core (4 members, 50+ identical tokens) src/main/java/com/google/devtools/build/lib/util/HashCodes.java:90
- Duplicated block (16 lines × 2) src/main/java/com/google/devtools/build/lib/analysis/RunfilesSupport.java:724
- Duplicated block (16 lines × 2) src/main/java/com/google/devtools/build/lib/exec/SpawnLogReconstructor.java:202
- Duplicated block (16 lines × 2) src/main/java/com/google/devtools/build/lib/remote/http/HttpCacheClient.java:707
- Duplicated block (16 lines × 2) src/main/java/com/google/devtools/build/lib/skyframe/AspectFunction.java:669
- Duplicated block (16 lines × 2) src/main/java/com/google/devtools/build/lib/platform/SystemLoadAdvisoryEvent.java:34
- Duplicated block (18 lines × 2) src/main/java/com/google/devtools/build/lib/analysis/starlark/StarlarkCustomCommandLine.java:1080
- Duplicated block (18 lines × 2) src/main/java/com/google/devtools/build/lib/remote/RemoteModule.java:750
- Duplicated block (18 lines × 2) src/main/java/com/google/devtools/build/lib/sandbox/LinuxSandboxCommandLineBuilder.java:241
- Duplicated block (18 lines × 2) src/main/java/com/google/devtools/build/lib/skyframe/BuildOptionsScopeFunction.java:258
- Duplicated block (17 lines × 2) src/main/java/com/google/devtools/build/lib/analysis/starlark/StarlarkActionFactory.java:144
- Duplicated block (17 lines × 2) src/main/java/com/google/devtools/build/lib/bazel/coverage/CoverageReportActionBuilder.java:244
- Duplicated block (17 lines × 2) src/main/java/com/google/devtools/build/lib/buildtool/AnalysisAndExecutionPhaseRunner.java:186
- Duplicated block (17 lines × 2) src/main/java/com/google/devtools/build/lib/sandbox/HardlinkedSandboxedSpawn.java:117
- Duplicated block (7–8 lines × 2) src/main/java/com/google/devtools/build/lib/packages/ImplicitOutputsFunction.java:118
- Duplicated block (7–8 lines × 2) src/main/java/com/google/devtools/build/lib/skyframe/GlobFunctionWithMultipleRecursiveFunctions.java:217
- Duplicated block (7–8 lines × 2) src/main/java/com/google/devtools/build/lib/skyframe/serialization/autocodec/DeferredObjectCodecFieldGenerators.java:70
- Duplicated block (7–8 lines × 2) src/main/java/net/starlark/java/syntax/TypeChecker.java:304
- Duplicated block (9 lines × 3) src/main/java/com/google/devtools/build/lib/rules/cpp/CppCompileAction.java:1008
- Duplicated block (9 lines × 3) src/main/java/com/google/devtools/build/lib/remote/ReferenceCountedChannel.java:164
- Duplicated block (9 lines × 3) src/main/java/com/google/devtools/build/lib/runtime/ServerBuilder.java:101
- Duplicated block (7 lines × 3) src/main/java/com/google/devtools/build/lib/runtime/BuildEventStreamer.java:366
- Duplicated block (7 lines × 3) src/main/java/net/starlark/java/eval/EvalUtils.java:132
- Duplicated block (7 lines × 3) src/main/java/com/google/devtools/build/lib/analysis/BazelRuleAnalysisThreadContext.java:51
- Swallowed exception (empty catch) src/main/java/com/google/devtools/build/lib/runtime/BlazeRuntime.java:2158
- Swallowed exception (empty catch) src/main/java/com/google/devtools/build/lib/runtime/BlazeRuntime.java:2177
- Swallowed exception (empty catch) src/main/java/com/google/devtools/build/lib/runtime/BlazeRuntime.java:2182
- Duplicated block (24 lines × 2) src/main/java/com/google/devtools/build/lib/analysis/actions/StarlarkAction.java:269
- Duplicated block (24 lines × 2) src/main/java/com/google/devtools/build/lib/query2/aquery/ActionGraphQueryEnvironment.java:486
- Duplicated block (22 lines × 2) src/main/java/com/google/devtools/build/lib/packages/PackageFactory.java:232
- Duplicated block (22 lines × 2) src/main/java/com/google/devtools/build/lib/packages/Type.java:739
- Duplicated block (19 lines × 2) src/main/java/com/google/devtools/build/lib/skyframe/SkyframeBuildView.java:547
- Duplicated block (19 lines × 2) src/main/java/com/google/devtools/build/lib/skyframe/toolchains/RegisteredExecutionPlatformsCycleReporter.java:60
- Duplicated block (13–14 lines × 3) src/main/java/com/google/devtools/build/skyframe/state/Lookup.java:119
- Duplicated block (13–14 lines × 3) src/main/java/com/google/devtools/build/lib/rules/cpp/CppConfiguration.java:192
- Duplicated block (12–13 lines × 2) src/main/java/com/google/devtools/build/docgen/ApiExporter.java:322
- Duplicated block (12–13 lines × 2) src/main/java/com/google/devtools/build/skyframe/SkyFunctionEnvironment.java:250
- Duplicated block (11 lines × 3) src/main/java/com/google/devtools/build/lib/remote/http/HttpCacheClient.java:627
- Duplicated block (11 lines × 3) src/main/java/com/google/devtools/build/lib/analysis/starlark/StarlarkMapActionTemplate.java:313
- Duplicated block (8 lines × 3) src/main/java/com/google/devtools/build/lib/bazel/debug/WorkspaceRuleEvent.java:75
- Duplicated block (8 lines × 3) src/main/java/com/google/devtools/build/lib/remote/RemoteExternalOverlayFileSystem.java:304
- Duplicated block (7 lines × 4) src/main/java/com/google/devtools/build/lib/bazel/commands/FetchCommand.java:115
- Duplicated block (7 lines × 4) src/main/java/com/google/devtools/build/lib/analysis/starlark/StarlarkBuildSettingsDetailsValue.java:66
- Duplicated block (5 lines × 3) src/main/java/com/google/devtools/build/lib/runtime/commands/AqueryCommand.java:100
- Duplicated block (5 lines × 3) src/main/java/com/google/devtools/build/docgen/BuildEncyclopediaGenerator.java:52
- Duplicated block (6 lines × 3) src/main/java/com/google/devtools/build/lib/actions/ActionExecutedEvent.java:266
- Duplicated block (6 lines × 3) src/main/java/com/google/devtools/build/lib/actions/ExecutionRequirements.java:266
- Length read from the parsed input is spent without ever being bounded src/main/java/com/google/devtools/build/lib/actions/cache/PersistentStringIndexer.java:193
- Length read from the parsed input is spent without ever being bounded src/main/java/com/google/devtools/build/lib/actions/cache/CompactPersistentActionCache.java:214
- EvalUtils.binaryOp (cyclomatic 111) src/main/java/net/starlark/java/eval/EvalUtils.java:59
- StarlarkRuleClassFunctions.createRule (cyclomatic 83) src/main/java/com/google/devtools/build/lib/analysis/starlark/StarlarkRuleClassFunctions.java:709
- Lexer.scanWord (cyclomatic 79) src/main/java/com/google/devtools/build/lib/query2/engine/Lexer.java:170
- Lexer.tokenize (cyclomatic 62) src/main/java/net/starlark/java/syntax/Lexer.java:694
- BlazeCommandDispatcher.execExclusively (cyclomatic 60) src/main/java/com/google/devtools/build/lib/runtime/BlazeCommandDispatcher.java:376
- ModCommand.execInternal (cyclomatic 60) src/main/java/com/google/devtools/build/lib/bazel/commands/ModCommand.java:217
- BazelRepositoryModule.beforeCommand (cyclomatic 55) src/main/java/com/google/devtools/build/lib/bazel/BazelRepositoryModule.java:279
- PatchUtil.applyInternal (cyclomatic 54) src/main/java/com/google/devtools/build/lib/bazel/repository/decompressor/PatchUtil.java:448
- Lexer.escapedStringLiteral (cyclomatic 52) src/main/java/net/starlark/java/syntax/Lexer.java:273
- RemoteModule.setup (cyclomatic 50) src/main/java/com/google/devtools/build/lib/remote/RemoteModule.java:414
- StarlarkAttrModule.createAttribute (cyclomatic 50) src/main/java/com/google/devtools/build/lib/analysis/starlark/StarlarkAttrModule.java:312
- HttpConnector.connect (cyclomatic 48) src/main/java/com/google/devtools/build/lib/bazel/repository/downloader/HttpConnector.java:115
- GlobFunctionWithMultipleRecursiveFunctions.compute (cyclomatic 45) src/main/java/com/google/devtools/build/lib/skyframe/GlobFunctionWithMultipleRecursiveFunctions.java:51
- CcCommon.configureFeaturesOrThrowEvalException (cyclomatic 45) src/main/java/com/google/devtools/build/lib/rules/cpp/CcCommon.java:117
- NodePrinter.printExpr (cyclomatic 41) src/main/java/net/starlark/java/syntax/NodePrinter.java:313
- Evaluate.runCore (cyclomatic 41) src/main/java/com/google/devtools/build/skyframe/AbstractParallelEvaluator.java:418
- FunctionTransitionUtil.applyTransition (cyclomatic 40) src/main/java/com/google/devtools/build/lib/analysis/starlark/FunctionTransitionUtil.java:612
- Lexer.scanNumberOrDotOrEllipsis (cyclomatic 39) src/main/java/net/starlark/java/syntax/Lexer.java:900
- StarlarkActionFactory.registerStarlarkAction (cyclomatic 39) src/main/java/com/google/devtools/build/lib/analysis/starlark/StarlarkActionFactory.java:724
- AspectFunction.compute (cyclomatic 38) src/main/java/com/google/devtools/build/lib/skyframe/AspectFunction.java:265
- BuildEventServiceUploader.publishBuildEvents (cyclomatic 38) src/main/java/com/google/devtools/build/lib/buildeventservice/BuildEventServiceUploader.java:458
- _CLRParser.handle_endtag (cyclomatic 38) scripts/docs/clr_converter.py:215
- PackageFunction.compute (cyclomatic 37) src/main/java/com/google/devtools/build/lib/skyframe/PackageFunction.java:368
- ProtoOutputFormatter.toTargetProtoBuffer (cyclomatic 36) src/main/java/com/google/devtools/build/lib/query2/query/output/ProtoOutputFormatter.java:182
- RuleConfiguredTargetBuilder.build (cyclomatic 36) src/main/java/com/google/devtools/build/lib/analysis/RuleConfiguredTargetBuilder.java:101
- UiEventHandler.handleLocked (cyclomatic 35) src/main/java/com/google/devtools/build/lib/runtime/UiEventHandler.java:429
- RemoteExecutionService.downloadOutputs (cyclomatic 35) src/main/java/com/google/devtools/build/lib/remote/RemoteExecutionService.java:1307
- RepositoryFetchFunction.computeInternal (cyclomatic 34) src/main/java/com/google/devtools/build/lib/bazel/repository/RepositoryFetchFunction.java:222
- BzlCompileFunction.computeInline (cyclomatic 33) src/main/java/com/google/devtools/build/lib/skyframe/BzlCompileFunction.java:108
- ChunkingSession.nextChunkSize (cyclomatic 33) src/main/java/com/google/devtools/build/lib/remote/chunking/RepMaxCdcChunker.java:219
- StarlarkRuleClassFunctions.aspect (cyclomatic 33) src/main/java/com/google/devtools/build/lib/analysis/starlark/StarlarkRuleClassFunctions.java:1334
- BlazeRuntime.newRuntime (cyclomatic 32) src/main/java/com/google/devtools/build/lib/runtime/BlazeRuntime.java:1408
- SingleExtensionEvalFunction.compute (cyclomatic 32) src/main/java/com/google/devtools/build/lib/bazel/bzlmod/SingleExtensionEvalFunction.java:99
- DownloadManager.downloadInExecutor (cyclomatic 31) src/main/java/com/google/devtools/build/lib/bazel/repository/downloader/DownloadManager.java:185
- Printer.formatWithList (cyclomatic 30) src/main/java/net/starlark/java/eval/Printer.java:462
- MethodDescriptor.starlarkTypeFromJava (cyclomatic 30) src/main/java/net/starlark/java/eval/MethodDescriptor.java:285
- SkyValueRetriever.tryRetrieve (cyclomatic 30) src/main/java/com/google/devtools/build/lib/skyframe/serialization/SkyValueRetriever.java:288
- StarlarkNativeModule.starlarkifyValue (cyclomatic 30) src/main/java/com/google/devtools/build/lib/packages/StarlarkNativeModule.java:716
- StandaloneTestStrategy.runTestAttempt (cyclomatic 30) src/main/java/com/google/devtools/build/lib/exec/StandaloneTestStrategy.java:651
- VectorArg.preprocess (cyclomatic 30) src/main/java/com/google/devtools/build/lib/analysis/starlark/StarlarkCustomCommandLine.java:333
- _CLRParser.handle_starttag (cyclomatic 30) scripts/docs/clr_converter.py:124
- TypeChecker.infer (cyclomatic 29) src/main/java/net/starlark/java/syntax/TypeChecker.java:156
- StarlarkMethodProcessor.process (cyclomatic 29) src/main/java/net/starlark/java/annot/processor/StarlarkMethodProcessor.java:139
- ShellUtils.tokenize (cyclomatic 29) src/main/java/com/google/devtools/build/lib/shell/ShellUtils.java:90
- RemoteSpawnCache.lookup (cyclomatic 29) src/main/java/com/google/devtools/build/lib/remote/RemoteSpawnCache.java:84
- RemoteServerCapabilities.checkClientServerCompatibility (cyclomatic 29) src/main/java/com/google/devtools/build/lib/remote/RemoteServerCapabilities.java:155
- AttributeFormatter.writeAttributeValueToBuilder (cyclomatic 29) src/main/java/com/google/devtools/build/lib/packages/AttributeFormatter.java:210
- TestActionBuilder.createTestAction (cyclomatic 29) src/main/java/com/google/devtools/build/lib/analysis/test/TestActionBuilder.java:234
- MergedConfiguredTarget.of (cyclomatic 29) src/main/java/com/google/devtools/build/lib/analysis/configuredtargets/MergedConfiguredTarget.java:197
- StarlarkOptionsParser.parseGivenArgs (cyclomatic 28) src/main/java/com/google/devtools/build/lib/runtime/StarlarkOptionsParser.java:179
- CommandEnvironment.<init> (cyclomatic 28) src/main/java/com/google/devtools/build/lib/runtime/CommandEnvironment.java:228
- BuildEventStreamer.buildEvent (cyclomatic 28) src/main/java/com/google/devtools/build/lib/runtime/BuildEventStreamer.java:671
- NestedSet.create (cyclomatic 28) src/main/java/com/google/devtools/build/lib/collect/nestedset/NestedSet.java:224
- ProxyHelper.createProxyIfNeeded (cyclomatic 28) src/main/java/com/google/devtools/build/lib/bazel/repository/downloader/ProxyHelper.java:83
- TypeChecker.inferCall (cyclomatic 27) src/main/java/net/starlark/java/syntax/TypeChecker.java:586
- TypeChecker.inferSlice (cyclomatic 27) src/main/java/net/starlark/java/syntax/TypeChecker.java:420
- SimpleCycleDetector.checkForCycles (cyclomatic 27) src/main/java/com/google/devtools/build/skyframe/SimpleCycleDetector.java:92
- ActionGraphDump.dumpSingleAction (cyclomatic 27) src/main/java/com/google/devtools/build/lib/skyframe/actiongraph/v2/ActionGraphDump.java:150
- TargetPatternPhaseFunction.compute (cyclomatic 27) src/main/java/com/google/devtools/build/lib/skyframe/TargetPatternPhaseFunction.java:76
- BuildDriverFunction.compute (cyclomatic 27) src/main/java/com/google/devtools/build/lib/skyframe/BuildDriverFunction.java:157
- DumpCommand.exec (cyclomatic 27) src/main/java/com/google/devtools/build/lib/runtime/commands/DumpCommand.java:399
- UiStateTracker.describeAction (cyclomatic 27) src/main/java/com/google/devtools/build/lib/runtime/UiStateTracker.java:819
- SymlinkForest.plantSymlinkForestMultiPackagePath (cyclomatic 27) src/main/java/com/google/devtools/build/lib/buildtool/SymlinkForest.java:146
- ExecutionServer.execute (cyclomatic 26) src/tools/remote/src/main/java/com/google/devtools/build/remote/worker/ExecutionServer.java:287
- StarlarkInt.parse (cyclomatic 26) src/main/java/net/starlark/java/eval/StarlarkInt.java:104
- AqueryThreadsafeCallback.getReachableActions (cyclomatic 26) src/main/java/com/google/devtools/build/lib/query2/aquery/AqueryThreadsafeCallback.java:65
- Resolver.resolveFunction (cyclomatic 25) src/main/java/net/starlark/java/syntax/Resolver.java:1107
- Hints.getPathLevelHintedInclusions (cyclomatic 25) src/main/java/com/google/devtools/build/lib/includescanning/IncludeParser.java:263
- StarlarkRuleFunction.call (cyclomatic 25) src/main/java/com/google/devtools/build/lib/analysis/starlark/StarlarkRuleClassFunctions.java:1795
- TypeChecker.inferBinaryOperator (cyclomatic 24) src/main/java/net/starlark/java/syntax/TypeChecker.java:516
- Parser.parsePrimary (cyclomatic 24) src/main/java/net/starlark/java/syntax/Parser.java:685
- Starlark.classType (cyclomatic 24) src/main/java/net/starlark/java/eval/Starlark.java:423
- OptionsParserImpl.identifyOptionAndPossibleArgument (cyclomatic 24) src/main/java/com/google/devtools/common/options/OptionsParserImpl.java:735
- PackageFunction.loadPackage (cyclomatic 24) src/main/java/com/google/devtools/build/lib/skyframe/PackageFunction.java:994
- ConfiguredTargetFunction.compute (cyclomatic 24) src/main/java/com/google/devtools/build/lib/skyframe/ConfiguredTargetFunction.java:256
- ActionOutputMetadataStore.constructTreeArtifactValueFromFilesystem (cyclomatic 24) src/main/java/com/google/devtools/build/lib/skyframe/ActionOutputMetadataStore.java:255
- ActionExecutionFunction.computeInternal (cyclomatic 24) src/main/java/com/google/devtools/build/lib/skyframe/ActionExecutionFunction.java:223
- GenQueryPackageProviderFactory.constructPackageMapImpl (cyclomatic 24) src/main/java/com/google/devtools/build/lib/rules/genquery/GenQueryPackageProviderFactory.java:184
- SubprocessHandler.start (cyclomatic 24) src/main/java/com/google/devtools/build/lib/exec/local/LocalSpawnRunner.java:310
- ExpandedSpawnLogContext.logSpawn (cyclomatic 24) src/main/java/com/google/devtools/build/lib/exec/ExpandedSpawnLogContext.java:156
- CompressedTarFunction.decompress (cyclomatic 24) src/main/java/com/google/devtools/build/lib/bazel/repository/decompressor/CompressedTarFunction.java:68
- CallableType.assignableFromHook (cyclomatic 23) src/main/java/net/starlark/java/syntax/Types.java:613
- TypeTagger.extractTerm (cyclomatic 23) src/main/java/net/starlark/java/syntax/TypeTagger.java:184
- ParallelEvaluator.bubbleErrorUp (cyclomatic 23) src/main/java/com/google/devtools/build/skyframe/ParallelEvaluator.java:293
- Evaluate.maybeHandleDirtyNode (cyclomatic 23) src/main/java/com/google/devtools/build/skyframe/AbstractParallelEvaluator.java:236
- DependencySet.process (cyclomatic 23) src/main/java/com/google/devtools/build/lib/util/DependencySet.java:131
- WatchServiceDiffAwareness.collectChanges (cyclomatic 23) src/main/java/com/google/devtools/build/lib/skyframe/WatchServiceDiffAwareness.java:180
- SkyframeExecutor.handleDiffsWithMissingDiffInformation (cyclomatic 23) src/main/java/com/google/devtools/build/lib/skyframe/SkyframeExecutor.java:4022
- DependencyResolver.computeDependencies (cyclomatic 23) src/main/java/com/google/devtools/build/lib/skyframe/DependencyResolver.java:672
- CompletionFunction.compute (cyclomatic 23) src/main/java/com/google/devtools/build/lib/skyframe/CompletionFunction.java:152
- LinuxSandboxCommandLineBuilder.buildForCommand (cyclomatic 23) src/main/java/com/google/devtools/build/lib/sandbox/LinuxSandboxCommandLineBuilder.java:233
- BlazeRuntime.initProfiler (cyclomatic 23) src/main/java/com/google/devtools/build/lib/runtime/BlazeRuntime.java:379
- HeaderDiscovery.runDiscovery (cyclomatic 23) src/main/java/com/google/devtools/build/lib/rules/cpp/HeaderDiscovery.java:115
- UserDefinedFlagMatch.fromAttributeValueAndPrerequisites (cyclomatic 23) src/main/java/com/google/devtools/build/lib/rules/config/ConfigSetting.java:642
- PostAnalysisQueryEnvironment.targetifyValues (cyclomatic 23) src/main/java/com/google/devtools/build/lib/query2/PostAnalysisQueryEnvironment.java:668
- ActionConflictException.debugSuffix (cyclomatic 23) src/main/java/com/google/devtools/build/lib/actions/ActionConflictException.java:254
- NodePrinter.printStmt (cyclomatic 22) src/main/java/net/starlark/java/syntax/NodePrinter.java:159
- Decoder.parse (cyclomatic 22) src/main/java/net/starlark/java/lib/json/Json.java:374
- Indenter.indent (cyclomatic 22) src/main/java/net/starlark/java/lib/json/Json.java:716
- UnixGlob.makePatternFromWildcard (cyclomatic 22) src/main/java/com/google/devtools/build/lib/vfs/UnixGlob.java:262
- AttributeInfoExtractor.getAttributeType (cyclomatic 22) src/main/java/com/google/devtools/build/lib/starlarkdocextract/AttributeInfoExtractor.java:111
- RunCommand.getBuiltTargets (cyclomatic 22) src/main/java/com/google/devtools/build/lib/runtime/commands/RunCommand.java:436
- TestSummaryPrinter.print (cyclomatic 22) src/main/java/com/google/devtools/build/lib/runtime/TestSummaryPrinter.java:135
- QueryParser.parsePrimary (cyclomatic 22) src/main/java/com/google/devtools/build/lib/query2/engine/QueryParser.java:271
- ActionGraphTextOutputFormatterCallback.writeText (cyclomatic 22) src/main/java/com/google/devtools/build/lib/query2/aquery/ActionGraphTextOutputFormatterCallback.java:167
- AttributeProvider.populateDefaultRuleAttributeValues (cyclomatic 22) src/main/java/com/google/devtools/build/lib/packages/AttributeProvider.java:298
- NestedSetBuilder.buildInternal (cyclomatic 22) src/main/java/com/google/devtools/build/lib/collect/nestedset/NestedSetBuilder.java:221
- LabelValidator.validateTargetName (cyclomatic 22) src/main/java/com/google/devtools/build/lib/cmdline/LabelValidator.java:146
- RepositoryFetchFunction.fetch (cyclomatic 22) src/main/java/com/google/devtools/build/lib/bazel/repository/RepositoryFetchFunction.java:602
- CompactPersistentActionCache.decodeInternal (cyclomatic 22) src/main/java/com/google/devtools/build/lib/actions/cache/CompactPersistentActionCache.java:999
- Decoder.parseString (cyclomatic 21) src/main/java/net/starlark/java/lib/json/Json.java:485
- WorkerSpawnRunner.execInWorker (cyclomatic 21) src/main/java/com/google/devtools/build/lib/worker/WorkerSpawnRunner.java:380
- WindowsOsPathPolicy.needsToNormalize (cyclomatic 21) src/main/java/com/google/devtools/build/lib/vfs/WindowsOsPathPolicy.java:78
- NodeDependencyHandler.reduce (cyclomatic 21) src/main/java/com/google/devtools/build/lib/skyframe/serialization/analysis/FileDependencySerializer.java:955
- ArtifactFunction.createSourceValue (cyclomatic 21) src/main/java/com/google/devtools/build/lib/skyframe/ArtifactFunction.java:311
- ShellUtils.windowsEscapeArg (cyclomatic 21) src/main/java/com/google/devtools/build/lib/shell/ShellUtils.java:186
- SandboxStash.takeStashedSandboxInternal (cyclomatic 21) src/main/java/com/google/devtools/build/lib/sandbox/SandboxStash.java:116
- RemoteSpawnRunner.exec (cyclomatic 21) src/main/java/com/google/devtools/build/lib/remote/RemoteSpawnRunner.java:182
- InclusionCache.locateOnPaths (cyclomatic 21) src/main/java/com/google/devtools/build/lib/includescanning/LegacyIncludeScanner.java:124
- BuildTool.processRequestHandleCheckedExceptions (cyclomatic 21) src/main/java/com/google/devtools/build/lib/buildtool/BuildTool.java:1005
- Builder.createTargetMap (cyclomatic 21) src/main/java/com/google/devtools/build/lib/analysis/RuleContext.java:1750
- StarlarkFloat.format (cyclomatic 20) src/main/java/net/starlark/java/eval/StarlarkFloat.java:130
- ParsedFlagsFunction.compute (cyclomatic 20) src/main/java/com/google/devtools/build/lib/skyframe/config/ParsedFlagsFunction.java:64
- FilesystemValueChecker.batchStatJob (cyclomatic 20) src/main/java/com/google/devtools/build/lib/skyframe/FilesystemValueChecker.java:314
- EvalMacroFunction.compute (cyclomatic 20) src/main/java/com/google/devtools/build/lib/skyframe/EvalMacroFunction.java:71
- VirtualCgroup.createRoot (cyclomatic 20) src/main/java/com/google/devtools/build/lib/sandbox/cgroups/VirtualCgroup.java:131
- MemoryModeConverter.convert (cyclomatic 20) src/main/java/com/google/devtools/build/lib/runtime/commands/DumpCommand.java:195
- BuildEventStreamer.post (cyclomatic 20) src/main/java/com/google/devtools/build/lib/runtime/BuildEventStreamer.java:337
- Builder.build (cyclomatic 20) src/main/java/com/google/devtools/build/lib/rules/java/JavaHeaderCompileAction.java:435
- CppConfiguration.<init> (cyclomatic 20) src/main/java/com/google/devtools/build/lib/rules/cpp/CppConfiguration.java:169
- Rule.populateOutputFilesInternal (cyclomatic 20) src/main/java/com/google/devtools/build/lib/packages/Rule.java:518
- ProxyHelper.createProxyInfo (cyclomatic 20) src/main/java/com/google/devtools/build/lib/bazel/repository/downloader/ProxyHelper.java:233
- PatchUtil.getLineType (cyclomatic 20) src/main/java/com/google/devtools/build/lib/bazel/repository/decompressor/PatchUtil.java:109
- BuildView.update (cyclomatic 20) src/main/java/com/google/devtools/build/lib/analysis/BuildView.java:224
- Encoder.encode (cyclomatic 19) src/main/java/net/starlark/java/lib/json/Json.java:121
- ArgumentProcessor.call (cyclomatic 19) src/main/java/net/starlark/java/eval/StarlarkFunction.java:581
- MethodLibrary.floatForStarlark (cyclomatic 19) src/main/java/net/starlark/java/eval/MethodLibrary.java:555
- RewindableGraphInconsistencyReceiver.noteInconsistencyAndMaybeThrow (cyclomatic 19) src/main/java/com/google/devtools/build/lib/skyframe/rewinding/RewindableGraphInconsistencyReceiver.java:65
- ParsedFlagsFunction.checkPackageVisibility (cyclomatic 19) src/main/java/com/google/devtools/build/lib/skyframe/config/ParsedFlagsFunction.java:171
- SkyframeExecutor.processDiscardAndDetermineRemoval (cyclomatic 19) src/main/java/com/google/devtools/build/lib/skyframe/SkyframeExecutor.java:1441
- SkyframeBuildView.configureTargets (cyclomatic 19) src/main/java/com/google/devtools/build/lib/skyframe/SkyframeBuildView.java:402
- RecursiveFilesystemTraversalFunction.compute (cyclomatic 19) src/main/java/com/google/devtools/build/lib/skyframe/RecursiveFilesystemTraversalFunction.java:180
- CommandServer.run (cyclomatic 19) src/main/java/com/google/devtools/build/lib/server/CommandServer.java:427
- SandboxModule.setup (cyclomatic 19) src/main/java/com/google/devtools/build/lib/sandbox/SandboxModule.java:198
- TargetPatternsHelper.readFrom (cyclomatic 19) src/main/java/com/google/devtools/build/lib/runtime/commands/TargetPatternsHelper.java:68
- QueryCommand.doQuery (cyclomatic 19) src/main/java/com/google/devtools/build/lib/runtime/commands/QueryCommand.java:76
- BlazeRuntime.deleteOutputBase (cyclomatic 19) src/main/java/com/google/devtools/build/lib/runtime/BlazeRuntime.java:2069
- JavaUtil.javaSegmentIndexImpl (cyclomatic 19) src/main/java/com/google/devtools/build/lib/rules/java/JavaUtil.java:89
- CompileOneDependencyTransformer.transformCompileOneDependency (cyclomatic 19) src/main/java/com/google/devtools/build/lib/pkgcache/CompileOneDependencyTransformer.java:88
- Builder.<init> (cyclomatic 19) src/main/java/com/google/devtools/build/lib/packages/RuleClass.java:765
- ImplicitOutputsFunction.attributeValues (cyclomatic 19) src/main/java/com/google/devtools/build/lib/packages/ImplicitOutputsFunction.java:374
- TextOutputFormatter.printModule (cyclomatic 19) src/main/java/com/google/devtools/build/lib/bazel/bzlmod/modcommand/TextOutputFormatter.java:143
- ModuleFileFunction.advanceHorizon (cyclomatic 19) src/main/java/com/google/devtools/build/lib/bazel/bzlmod/ModuleFileFunction.java:413
- ModuleExtensionMetadata.create (cyclomatic 19) src/main/java/com/google/devtools/build/lib/bazel/bzlmod/ModuleExtensionMetadata.java:88
- GoogleAuthUtils.newChannel (cyclomatic 19) src/main/java/com/google/devtools/build/lib/authandtls/GoogleAuthUtils.java:74
- VectorArg.addToFingerprint (cyclomatic 19) src/main/java/com/google/devtools/build/lib/analysis/starlark/StarlarkCustomCommandLine.java:602
- Eval.inplaceBinaryOp (cyclomatic 18) src/main/java/net/starlark/java/eval/Eval.java:558
- WorkerModule.buildStarting (cyclomatic 18) src/main/java/com/google/devtools/build/lib/worker/WorkerModule.java:90
- JsonWorkerMessageProcessor.readWorkRequest (cyclomatic 18) src/main/java/com/google/devtools/build/lib/worker/JsonWorkerMessageProcessor.java:103
- InMemoryFileSystem.pathWalkErrno (cyclomatic 18) src/main/java/com/google/devtools/build/lib/vfs/inmemoryfs/InMemoryFileSystem.java:240
- GlobVisitor.reallyGlob (cyclomatic 18) src/main/java/com/google/devtools/build/lib/vfs/UnixGlob.java:776
- ObjectGraphTraverser.process (cyclomatic 18) src/main/java/com/google/devtools/build/lib/util/ObjectGraphTraverser.java:407
- SkyframeBuildView.analyzeAndExecuteTargets (cyclomatic 18) src/main/java/com/google/devtools/build/lib/skyframe/SkyframeBuildView.java:620
- DefaultSyscallCache.getType (cyclomatic 18) src/main/java/com/google/devtools/build/lib/skyframe/DefaultSyscallCache.java:191
- CleanCommand.actuallyClean (cyclomatic 18) src/main/java/com/google/devtools/build/lib/runtime/commands/CleanCommand.java:194
- UiStateTracker.writeProgressBar (cyclomatic 18) src/main/java/com/google/devtools/build/lib/runtime/UiStateTracker.java:1388
- ActionDumpWriter.maybeAddEdges (cyclomatic 18) src/main/java/com/google/devtools/build/lib/runtime/ExecutionGraphModule.java:573
- DiskCacheClient.refreshActionResult (cyclomatic 18) src/main/java/com/google/devtools/build/lib/remote/disk/DiskCacheClient.java:253
- MacroClass.instantiateMacro (cyclomatic 18) src/main/java/com/google/devtools/build/lib/packages/MacroClass.java:210
- IncludeParser.extractInclusion (cyclomatic 18) src/main/java/com/google/devtools/build/lib/includescanning/IncludeParser.java:756
- DownloadManager.downloadAndReadOneUrlForBzlmod (cyclomatic 18) src/main/java/com/google/devtools/build/lib/bazel/repository/downloader/DownloadManager.java:409
- ModCommand.validateArgs (cyclomatic 18) src/main/java/com/google/devtools/build/lib/bazel/commands/ModCommand.java:142
- IndexRegistry.createArchiveRepoSpec (cyclomatic 18) src/main/java/com/google/devtools/build/lib/bazel/bzlmod/IndexRegistry.java:472
- TestRunnerAction.getTestOutputsMapping (cyclomatic 18) src/main/java/com/google/devtools/build/lib/analysis/test/TestRunnerAction.java:418
- StarlarkRuleContext.<init> (cyclomatic 18) src/main/java/com/google/devtools/build/lib/analysis/starlark/StarlarkRuleContext.java:195
- StarlarkRuleConfiguredTargetUtil.addProviders (cyclomatic 18) src/main/java/com/google/devtools/build/lib/analysis/starlark/StarlarkRuleConfiguredTargetUtil.java:239
- StarlarkActionFactory.symlink (cyclomatic 18) src/main/java/com/google/devtools/build/lib/analysis/starlark/StarlarkActionFactory.java:259
- VectorArgFragment.eval (cyclomatic 18) src/main/java/com/google/devtools/build/lib/analysis/actions/CustomCommandLine.java:395
- mirror_external_deps.collect_candidates (cyclomatic 18) tools/mirror_external_deps.py:185
- Resolver.createBindings (cyclomatic 17) src/main/java/net/starlark/java/syntax/Resolver.java:649
- Resolver.visit (cyclomatic 17) src/main/java/net/starlark/java/syntax/Resolver.java:783
- MethodDescriptor.call (cyclomatic 17) src/main/java/net/starlark/java/eval/MethodDescriptor.java:400
- Eval.evalCall (cyclomatic 17) src/main/java/net/starlark/java/eval/Eval.java:743
- StarlarkMethodProcessor.checkParameter (cyclomatic 17) src/main/java/net/starlark/java/annot/processor/StarlarkMethodProcessor.java:400
- OptionsClassProcessor.generateWrapper (cyclomatic 17) src/main/java/com/google/devtools/common/options/processor/OptionsClassProcessor.java:151
- WaitForNestedNodeBytes.apply (cyclomatic 17) src/main/java/com/google/devtools/build/lib/skyframe/serialization/analysis/FileDependencyDeserializer.java:596
- StarlarkBuildSettingsDetailsFunction.compute (cyclomatic 17) src/main/java/com/google/devtools/build/lib/skyframe/StarlarkBuildSettingsDetailsFunction.java:59
- SkymeldModule.determineIfMergingAnalysisExecution (cyclomatic 17) src/main/java/com/google/devtools/build/lib/skyframe/SkymeldModule.java:34
- SkyValueRetrieverUtils.retrieveRemoteSkyValue (cyclomatic 17) src/main/java/com/google/devtools/build/lib/skyframe/SkyValueRetrieverUtils.java:50
- RecursiveFilesystemTraversalFunction.lookUpFileInfo (cyclomatic 17) src/main/java/com/google/devtools/build/lib/skyframe/RecursiveFilesystemTraversalFunction.java:335
- FileSystemValueCheckerInferringAncestors.visitEntry (cyclomatic 17) src/main/java/com/google/devtools/build/lib/skyframe/FileSystemValueCheckerInferringAncestors.java:287
- ActionExecutionFunction.checkCacheAndExecuteIfNeeded (cyclomatic 17) src/main/java/com/google/devtools/build/lib/skyframe/ActionExecutionFunction.java:669
- RunCommand.exec (cyclomatic 17) src/main/java/com/google/devtools/build/lib/runtime/commands/RunCommand.java:249
- TestResultAggregator.incrementalAnalyze (cyclomatic 17) src/main/java/com/google/devtools/build/lib/runtime/TestResultAggregator.java:165
- TerminalTestResultNotifier.notify (cyclomatic 17) src/main/java/com/google/devtools/build/lib/runtime/TerminalTestResultNotifier.java:176
- ConfigExpander.expandConfigOptions (cyclomatic 17) src/main/java/com/google/devtools/build/lib/runtime/ConfigExpander.java:93
- BlazeOptionHandler.structureRcOptionsAndConfigs (cyclomatic 17) src/main/java/com/google/devtools/build/lib/runtime/BlazeOptionHandler.java:730
- BlazeCommandDispatcher.exec (cyclomatic 17) src/main/java/com/google/devtools/build/lib/runtime/BlazeCommandDispatcher.java:193
- RemoteExecutionService.waitForAndReuseOutputs (cyclomatic 17) src/main/java/com/google/devtools/build/lib/remote/RemoteExecutionService.java:1671
- TaskData.writeTraceData (cyclomatic 17) src/main/java/com/google/devtools/build/lib/profiler/TaskData.java:74
- 3.extractGlobPatterns (cyclomatic 17) src/main/java/com/google/devtools/build/lib/packages/PackageFactory.java:609
- AggregatingAttributeMapper.checkForDuplicateLabels (cyclomatic 17) src/main/java/com/google/devtools/build/lib/packages/AggregatingAttributeMapper.java:241
- AggregatingAttributeMapper.visitLabels (cyclomatic 17) src/main/java/com/google/devtools/build/lib/packages/AggregatingAttributeMapper.java:107
- TestXmlOutputParser.parseContainedElements (cyclomatic 17) src/main/java/com/google/devtools/build/lib/exec/TestXmlOutputParser.java:222
- AbstractSpawnStrategy.exec (cyclomatic 17) src/main/java/com/google/devtools/build/lib/exec/AbstractSpawnStrategy.java:101
- ModuleFileFunction.getModuleFile (cyclomatic 17) src/main/java/com/google/devtools/build/lib/bazel/bzlmod/ModuleFileFunction.java:816
- FunctionTransitionUtil.applyStarlarkFlagsAliases (cyclomatic 17) src/main/java/com/google/devtools/build/lib/analysis/starlark/FunctionTransitionUtil.java:345
- OptionsDiffCodec.serialize (cyclomatic 17) src/main/java/com/google/devtools/build/lib/analysis/config/OptionsDiff.java:667
- LocationExpander.buildLocationMap (cyclomatic 17) src/main/java/com/google/devtools/build/lib/analysis/LocationExpander.java:420
- CommonPrerequisiteValidator.validateDirectPrerequisiteVisibility (cyclomatic 17) src/main/java/com/google/devtools/build/lib/analysis/CommonPrerequisiteValidator.java:187
- ActionExecutedEvent.asStreamProto (cyclomatic 17) src/main/java/com/google/devtools/build/lib/actions/ActionExecutedEvent.java:175
- BuildDocCollector.processJavaSourceRuleAttributeDocs (cyclomatic 17) src/main/java/com/google/devtools/build/docgen/BuildDocCollector.java:200
- Lexer.stringLiteral (cyclomatic 16) src/main/java/net/starlark/java/syntax/Lexer.java:436
- MethodDescriptor.buildStarlarkType (cyclomatic 16) src/main/java/net/starlark/java/eval/MethodDescriptor.java:159
- Main.main (cyclomatic 16) src/main/java/net/starlark/java/cmd/Main.java:171
- SingleOptionValueDescription.addOptionInstance (cyclomatic 16) src/main/java/com/google/devtools/common/options/OptionValueDescription.java:208
- PathFragment.isNormalizedImpl (cyclomatic 16) src/main/java/com/google/devtools/build/lib/vfs/PathFragment.java:879
- PathFragment.subFragmentImpl (cyclomatic 16) src/main/java/com/google/devtools/build/lib/vfs/PathFragment.java:652
- CommandFailureUtils.describeCommand (cyclomatic 16) src/main/java/com/google/devtools/build/lib/util/CommandFailureUtils.java:44
- AnsiStrippingOutputStream.processByte (cyclomatic 16) src/main/java/com/google/devtools/build/lib/util/AnsiStrippingOutputStream.java:90
- SkyframeProgressReceiver.evaluated (cyclomatic 16) src/main/java/com/google/devtools/build/lib/skyframe/SkyframeExecutor.java:3622
- ProcessPackageDirectory.getPackageExistenceAndSubdirDeps (cyclomatic 16) src/main/java/com/google/devtools/build/lib/skyframe/ProcessPackageDirectory.java:78
- GlobsFunction.compute (cyclomatic 16) src/main/java/com/google/devtools/build/lib/skyframe/GlobsFunction.java:108
- BzlLoadFunction.computeInternalWithCompiledBzl (cyclomatic 16) src/main/java/com/google/devtools/build/lib/skyframe/BzlLoadFunction.java:757
- BuildOptionsScopeFunction.compute (cyclomatic 16) src/main/java/com/google/devtools/build/lib/skyframe/BuildOptionsScopeFunction.java:61
- ActionExecutionFunction.addDiscoveredInputs (cyclomatic 16) src/main/java/com/google/devtools/build/lib/skyframe/ActionExecutionFunction.java:874
- TestCommand.doTest (cyclomatic 16) src/main/java/com/google/devtools/build/lib/runtime/commands/TestCommand.java:128
- ConfigSetting.optionMatches (cyclomatic 16) src/main/java/com/google/devtools/build/lib/rules/config/ConfigSetting.java:518
- RemoteExecutionService.initUseOutputPaths (cyclomatic 16) src/main/java/com/google/devtools/build/lib/remote/RemoteExecutionService.java:461
- XmlOutputFormatter.createTargetElement (cyclomatic 16) src/main/java/com/google/devtools/build/lib/query2/query/output/XmlOutputFormatter.java:147
- JsonTraceFileWriter.run (cyclomatic 16) src/main/java/com/google/devtools/build/lib/profiler/JsonTraceFileWriter.java:252
- Directory.syncTreeRecursively (cyclomatic 16) src/main/java/com/google/devtools/build/lib/exec/SymlinkTreeHelper.java:246
- DynamicSpawnStrategy.maybeExecuteNonDynamically (cyclomatic 16) src/main/java/com/google/devtools/build/lib/dynamic/DynamicSpawnStrategy.java:355
- BuildResultPrinter.outputConfiguredTargets (cyclomatic 16) src/main/java/com/google/devtools/build/lib/buildtool/BuildResultPrinter.java:408
- UrlRewriterConfig.parseConfig (cyclomatic 16) src/main/java/com/google/devtools/build/lib/bazel/repository/downloader/UrlRewriterConfig.java:125
- PatchUtil.applyPatchToFile (cyclomatic 16) src/main/java/com/google/devtools/build/lib/bazel/repository/decompressor/PatchUtil.java:200
- StarlarkRuleContext.runfiles (cyclomatic 16) src/main/java/com/google/devtools/build/lib/analysis/starlark/StarlarkRuleContext.java:1101
- StarlarkRuleClassFunctions.macro (cyclomatic 16) src/main/java/com/google/devtools/build/lib/analysis/starlark/StarlarkRuleClassFunctions.java:407
- OptionsDiff.diff (cyclomatic 16) src/main/java/com/google/devtools/build/lib/analysis/config/OptionsDiff.java:113
- ConfiguredTargetFactory.createConfiguredTarget (cyclomatic 16) src/main/java/com/google/devtools/build/lib/analysis/ConfiguredTargetFactory.java:221
- BuildView.checkUnknownOutputGroups (cyclomatic 16) src/main/java/com/google/devtools/build/lib/analysis/BuildView.java:952
- CompactPersistentActionCache.encode (cyclomatic 16) src/main/java/com/google/devtools/build/lib/actions/cache/CompactPersistentActionCache.java:868
- ActionCacheChecker.loadCachedOutputMetadata (cyclomatic 16) src/main/java/com/google/devtools/build/lib/actions/ActionCacheChecker.java:338
- StarlarkDoc.getTypeAnchor (cyclomatic 16) src/main/java/com/google/devtools/build/docgen/starlark/StarlarkDoc.java:84
- _CLRParser._parse_dt (cyclomatic 16) scripts/docs/clr_converter.py:388
- TodoComment repeated across 10 files src/main/java/com/google/devtools/build/lib/skyframe/serialization/SharedValueDeserializationContext.java:229
- EvalUtils.binaryOp (cognitive 174) src/main/java/net/starlark/java/eval/EvalUtils.java:59
- BazelRepositoryModule.beforeCommand (cognitive 143) src/main/java/com/google/devtools/build/lib/bazel/BazelRepositoryModule.java:279
- StarlarkRuleClassFunctions.createRule (cognitive 134) src/main/java/com/google/devtools/build/lib/analysis/starlark/StarlarkRuleClassFunctions.java:709
- PatchUtil.applyInternal (cognitive 101) src/main/java/com/google/devtools/build/lib/bazel/repository/decompressor/PatchUtil.java:448
- ChunkingSession.nextChunkSize (cognitive 95) src/main/java/com/google/devtools/build/lib/remote/chunking/RepMaxCdcChunker.java:219
- HttpConnector.connect (cognitive 94) src/main/java/com/google/devtools/build/lib/bazel/repository/downloader/HttpConnector.java:115
- BlazeCommandDispatcher.execExclusively (cognitive 92) src/main/java/com/google/devtools/build/lib/runtime/BlazeCommandDispatcher.java:376
- FunctionTransitionUtil.applyTransition (cognitive 88) src/main/java/com/google/devtools/build/lib/analysis/starlark/FunctionTransitionUtil.java:612
- GlobFunctionWithMultipleRecursiveFunctions.compute (cognitive 85) src/main/java/com/google/devtools/build/lib/skyframe/GlobFunctionWithMultipleRecursiveFunctions.java:51
- ModCommand.execInternal (cognitive 82) src/main/java/com/google/devtools/build/lib/bazel/commands/ModCommand.java:217
- BuildEventServiceUploader.publishBuildEvents (cognitive 81) src/main/java/com/google/devtools/build/lib/buildeventservice/BuildEventServiceUploader.java:458
- ProtoOutputFormatter.toTargetProtoBuffer (cognitive 75) src/main/java/com/google/devtools/build/lib/query2/query/output/ProtoOutputFormatter.java:182
- RepositoryFetchFunction.computeInternal (cognitive 75) src/main/java/com/google/devtools/build/lib/bazel/repository/RepositoryFetchFunction.java:222
- DownloadManager.downloadInExecutor (cognitive 73) src/main/java/com/google/devtools/build/lib/bazel/repository/downloader/DownloadManager.java:185
- HeaderDiscovery.runDiscovery (cognitive 72) src/main/java/com/google/devtools/build/lib/rules/cpp/HeaderDiscovery.java:115
- CcCommon.configureFeaturesOrThrowEvalException (cognitive 72) src/main/java/com/google/devtools/build/lib/rules/cpp/CcCommon.java:117
- Evaluate.runCore (cognitive 71) src/main/java/com/google/devtools/build/skyframe/AbstractParallelEvaluator.java:418
- RemoteModule.setup (cognitive 71) src/main/java/com/google/devtools/build/lib/remote/RemoteModule.java:414
- Lexer.escapedStringLiteral (cognitive 70) src/main/java/net/starlark/java/syntax/Lexer.java:273
- BzlCompileFunction.computeInline (cognitive 69) src/main/java/com/google/devtools/build/lib/skyframe/BzlCompileFunction.java:108
- AqueryThreadsafeCallback.getReachableActions (cognitive 69) src/main/java/com/google/devtools/build/lib/query2/aquery/AqueryThreadsafeCallback.java:65
- Lexer.scanNumberOrDotOrEllipsis (cognitive 67) src/main/java/net/starlark/java/syntax/Lexer.java:900
- StarlarkAttrModule.createAttribute (cognitive 67) src/main/java/com/google/devtools/build/lib/analysis/starlark/StarlarkAttrModule.java:312
- Lexer.tokenize (cognitive 66) src/main/java/net/starlark/java/syntax/Lexer.java:694
- RemoteExecutionService.downloadOutputs (cognitive 66) src/main/java/com/google/devtools/build/lib/remote/RemoteExecutionService.java:1307
- VectorArg.preprocess (cognitive 66) src/main/java/com/google/devtools/build/lib/analysis/starlark/StarlarkCustomCommandLine.java:333
- NestedSet.create (cognitive 65) src/main/java/com/google/devtools/build/lib/collect/nestedset/NestedSet.java:224
- StarlarkActionFactory.registerStarlarkAction (cognitive 65) src/main/java/com/google/devtools/build/lib/analysis/starlark/StarlarkActionFactory.java:724
- TypeChecker.inferSlice (cognitive 64) src/main/java/net/starlark/java/syntax/TypeChecker.java:420
- SimpleCycleDetector.checkForCycles (cognitive 64) src/main/java/com/google/devtools/build/skyframe/SimpleCycleDetector.java:92
- GenQueryPackageProviderFactory.constructPackageMapImpl (cognitive 61) src/main/java/com/google/devtools/build/lib/rules/genquery/GenQueryPackageProviderFactory.java:184
- SymlinkForest.plantSymlinkForestMultiPackagePath (cognitive 61) src/main/java/com/google/devtools/build/lib/buildtool/SymlinkForest.java:146
- ShellUtils.tokenize (cognitive 59) src/main/java/com/google/devtools/build/lib/shell/ShellUtils.java:90
- SkyValueRetriever.tryRetrieve (cognitive 58) src/main/java/com/google/devtools/build/lib/skyframe/serialization/SkyValueRetriever.java:288
- VirtualCgroup.createRoot (cognitive 58) src/main/java/com/google/devtools/build/lib/sandbox/cgroups/VirtualCgroup.java:131
- RemoteSpawnCache.lookup (cognitive 58) src/main/java/com/google/devtools/build/lib/remote/RemoteSpawnCache.java:84
- TestActionBuilder.createTestAction (cognitive 57) src/main/java/com/google/devtools/build/lib/analysis/test/TestActionBuilder.java:234
- StarlarkRuleFunction.call (cognitive 57) src/main/java/com/google/devtools/build/lib/analysis/starlark/StarlarkRuleClassFunctions.java:1795
- StarlarkOptionsParser.parseGivenArgs (cognitive 56) src/main/java/com/google/devtools/build/lib/runtime/StarlarkOptionsParser.java:179
- StarlarkRuleClassFunctions.aspect (cognitive 54) src/main/java/com/google/devtools/build/lib/analysis/starlark/StarlarkRuleClassFunctions.java:1334
- RuleConfiguredTargetBuilder.build (cognitive 54) src/main/java/com/google/devtools/build/lib/analysis/RuleConfiguredTargetBuilder.java:101
- CallableType.assignableFromHook (cognitive 53) src/main/java/net/starlark/java/syntax/Types.java:613
- StarlarkMethodProcessor.process (cognitive 53) src/main/java/net/starlark/java/annot/processor/StarlarkMethodProcessor.java:139
- _CLRParser.handle_endtag (cognitive 53) scripts/docs/clr_converter.py:215
- TypeChecker.inferCall (cognitive 52) src/main/java/net/starlark/java/syntax/TypeChecker.java:586
- BuildDriverFunction.compute (cognitive 52) src/main/java/com/google/devtools/build/lib/skyframe/BuildDriverFunction.java:157
- StandaloneTestStrategy.runTestAttempt (cognitive 52) src/main/java/com/google/devtools/build/lib/exec/StandaloneTestStrategy.java:651
- AspectFunction.compute (cognitive 50) src/main/java/com/google/devtools/build/lib/skyframe/AspectFunction.java:265
- ShellUtils.windowsEscapeArg (cognitive 50) src/main/java/com/google/devtools/build/lib/shell/ShellUtils.java:186
- MergedConfiguredTarget.of (cognitive 50) src/main/java/com/google/devtools/build/lib/analysis/configuredtargets/MergedConfiguredTarget.java:197
- RemoteServerCapabilities.checkClientServerCompatibility (cognitive 49) src/main/java/com/google/devtools/build/lib/remote/RemoteServerCapabilities.java:155
- SingleExtensionEvalFunction.compute (cognitive 49) src/main/java/com/google/devtools/build/lib/bazel/bzlmod/SingleExtensionEvalFunction.java:99
- Evaluate.maybeHandleDirtyNode (cognitive 48) src/main/java/com/google/devtools/build/skyframe/AbstractParallelEvaluator.java:236
- WatchServiceDiffAwareness.collectChanges (cognitive 48) src/main/java/com/google/devtools/build/lib/skyframe/WatchServiceDiffAwareness.java:180
- QueryParser.parsePrimary (cognitive 48) src/main/java/com/google/devtools/build/lib/query2/engine/QueryParser.java:271
- 3.extractGlobPatterns (cognitive 48) src/main/java/com/google/devtools/build/lib/packages/PackageFactory.java:609
- ProxyHelper.createProxyIfNeeded (cognitive 48) src/main/java/com/google/devtools/build/lib/bazel/repository/downloader/ProxyHelper.java:83
- FilesystemValueChecker.batchStatJob (cognitive 47) src/main/java/com/google/devtools/build/lib/skyframe/FilesystemValueChecker.java:314
- CompletionFunction.compute (cognitive 47) src/main/java/com/google/devtools/build/lib/skyframe/CompletionFunction.java:152
- ActionCacheChecker.loadCachedOutputMetadata (cognitive 47) src/main/java/com/google/devtools/build/lib/actions/ActionCacheChecker.java:338
- BuildDocCollector.processJavaSourceRuleAttributeDocs (cognitive 47) src/main/java/com/google/devtools/build/docgen/BuildDocCollector.java:200
- Decoder.parse (cognitive 46) src/main/java/net/starlark/java/lib/json/Json.java:374
- ObjectGraphTraverser.process (cognitive 46) src/main/java/com/google/devtools/build/lib/util/ObjectGraphTraverser.java:407
- UiStateTracker.describeAction (cognitive 46) src/main/java/com/google/devtools/build/lib/runtime/UiStateTracker.java:819
- TestSummaryPrinter.print (cognitive 46) src/main/java/com/google/devtools/build/lib/runtime/TestSummaryPrinter.java:135
- UserDefinedFlagMatch.fromAttributeValueAndPrerequisites (cognitive 46) src/main/java/com/google/devtools/build/lib/rules/config/ConfigSetting.java:642
- VarInt.getVarLong (cognitive 45) src/main/java/com/google/devtools/build/lib/util/VarInt.java:149
- JsonProfile.<init> (cognitive 45) src/main/java/com/google/devtools/build/lib/profiler/JsonProfile.java:48
- StarlarkRuleContext.<init> (cognitive 45) src/main/java/com/google/devtools/build/lib/analysis/starlark/StarlarkRuleContext.java:195
- ExecutionServer.execute (cognitive 44) src/tools/remote/src/main/java/com/google/devtools/build/remote/worker/ExecutionServer.java:287
- NodePrinter.printExpr (cognitive 44) src/main/java/net/starlark/java/syntax/NodePrinter.java:313
- OptionsParserImpl.identifyOptionAndPossibleArgument (cognitive 43) src/main/java/com/google/devtools/common/options/OptionsParserImpl.java:735
- SkyframeBuildView.configureTargets (cognitive 43) src/main/java/com/google/devtools/build/lib/skyframe/SkyframeBuildView.java:402
- CommandEnvironment.<init> (cognitive 43) src/main/java/com/google/devtools/build/lib/runtime/CommandEnvironment.java:228
- BlazeRuntime.initProfiler (cognitive 43) src/main/java/com/google/devtools/build/lib/runtime/BlazeRuntime.java:379
- CompressedTarFunction.decompress (cognitive 43) src/main/java/com/google/devtools/build/lib/bazel/repository/decompressor/CompressedTarFunction.java:68
- PackageFunction.loadPackage (cognitive 42) src/main/java/com/google/devtools/build/lib/skyframe/PackageFunction.java:994
- Builder.createTargetMap (cognitive 42) src/main/java/com/google/devtools/build/lib/analysis/RuleContext.java:1750
- TargetPatternPhaseFunction.compute (cognitive 41) src/main/java/com/google/devtools/build/lib/skyframe/TargetPatternPhaseFunction.java:76
- RecursiveFilesystemTraversalFunction.lookUpFileInfo (cognitive 41) src/main/java/com/google/devtools/build/lib/skyframe/RecursiveFilesystemTraversalFunction.java:335
- PatchUtil.getLineType (cognitive 41) src/main/java/com/google/devtools/build/lib/bazel/repository/decompressor/PatchUtil.java:109
- ParsedFlagsFunction.compute (cognitive 40) src/main/java/com/google/devtools/build/lib/skyframe/config/ParsedFlagsFunction.java:64
- SkyframeActionExecutor.checkOutputs (cognitive 40) src/main/java/com/google/devtools/build/lib/skyframe/SkyframeActionExecutor.java:1752
- PackageFunction.compute (cognitive 40) src/main/java/com/google/devtools/build/lib/skyframe/PackageFunction.java:368
- AttributeFormatter.writeAttributeValueToBuilder (cognitive 40) src/main/java/com/google/devtools/build/lib/packages/AttributeFormatter.java:210
- Hints.getPathLevelHintedInclusions (cognitive 40) src/main/java/com/google/devtools/build/lib/includescanning/IncludeParser.java:263
- InMemoryFileSystem.pathWalkErrno (cognitive 39) src/main/java/com/google/devtools/build/lib/vfs/inmemoryfs/InMemoryFileSystem.java:240
- WindowsOsPathPolicy.needsToNormalize (cognitive 39) src/main/java/com/google/devtools/build/lib/vfs/WindowsOsPathPolicy.java:78
- ParsedFlagsFunction.checkPackageVisibility (cognitive 39) src/main/java/com/google/devtools/build/lib/skyframe/config/ParsedFlagsFunction.java:171
- ActionGraphDump.dumpSingleAction (cognitive 39) src/main/java/com/google/devtools/build/lib/skyframe/actiongraph/v2/ActionGraphDump.java:150
- ActionOutputMetadataStore.constructTreeArtifactValueFromFilesystem (cognitive 39) src/main/java/com/google/devtools/build/lib/skyframe/ActionOutputMetadataStore.java:255
- ActionExecutionFunction.computeInternal (cognitive 39) src/main/java/com/google/devtools/build/lib/skyframe/ActionExecutionFunction.java:223
- BlazeRuntime.newRuntime (cognitive 39) src/main/java/com/google/devtools/build/lib/runtime/BlazeRuntime.java:1408
- TypeTagger.extractTerm (cognitive 38) src/main/java/net/starlark/java/syntax/TypeTagger.java:184
- Resolver.resolveFunction (cognitive 38) src/main/java/net/starlark/java/syntax/Resolver.java:1107
- ParallelEvaluator.bubbleErrorUp (cognitive 38) src/main/java/com/google/devtools/build/skyframe/ParallelEvaluator.java:293
- DefaultSyscallCache.getType (cognitive 38) src/main/java/com/google/devtools/build/lib/skyframe/DefaultSyscallCache.java:191
- GsonTypeAdapter.read (cognitive 38) src/main/java/com/google/devtools/build/lib/authandtls/credentialhelper/GetCredentialsResponse.java:120
- SandboxStash.takeStashedSandboxInternal (cognitive 37) src/main/java/com/google/devtools/build/lib/sandbox/SandboxStash.java:116
- RunCommand.getBuiltTargets (cognitive 37) src/main/java/com/google/devtools/build/lib/runtime/commands/RunCommand.java:436
- UploadManifest.addFiles (cognitive 37) src/main/java/com/google/devtools/build/lib/remote/UploadManifest.java:240
- AttributeProvider.populateDefaultRuleAttributeValues (cognitive 37) src/main/java/com/google/devtools/build/lib/packages/AttributeProvider.java:298
- InclusionCache.locateOnPaths (cognitive 37) src/main/java/com/google/devtools/build/lib/includescanning/LegacyIncludeScanner.java:124
- GraphvizOutputFormatter.output (cognitive 37) src/main/java/com/google/devtools/build/lib/bazel/bzlmod/modcommand/GraphvizOutputFormatter.java:45
- BuildDocCollector.collectModuleInfoDocs (cognitive 37) src/main/java/com/google/devtools/build/docgen/BuildDocCollector.java:363
- StarlarkBuildSettingsDetailsFunction.compute (cognitive 36) src/main/java/com/google/devtools/build/lib/skyframe/StarlarkBuildSettingsDetailsFunction.java:59
- SkyframeTargetPatternEvaluator.preloadTargetPatterns (cognitive 36) src/main/java/com/google/devtools/build/lib/skyframe/SkyframeTargetPatternEvaluator.java:68
- Rule.populateOutputFilesInternal (cognitive 36) src/main/java/com/google/devtools/build/lib/packages/Rule.java:518
- VectorArgFragment.eval (cognitive 36) src/main/java/com/google/devtools/build/lib/analysis/actions/CustomCommandLine.java:395
- ApiExporter.appendGlobals (cognitive 36) src/main/java/com/google/devtools/build/docgen/ApiExporter.java:93
- MethodDescriptor.starlarkTypeFromJava (cognitive 35) src/main/java/net/starlark/java/eval/MethodDescriptor.java:285
- SkyframeExecutor.handleDiffsWithMissingDiffInformation (cognitive 35) src/main/java/com/google/devtools/build/lib/skyframe/SkyframeExecutor.java:4022
- SkyframeExecutor.processDiscardAndDetermineRemoval (cognitive 35) src/main/java/com/google/devtools/build/lib/skyframe/SkyframeExecutor.java:1441
- UiStateTracker.writeProgressBar (cognitive 35) src/main/java/com/google/devtools/build/lib/runtime/UiStateTracker.java:1388
- UiEventHandler.handleLocked (cognitive 35) src/main/java/com/google/devtools/build/lib/runtime/UiEventHandler.java:429
- BuildEventStreamer.buildEvent (cognitive 35) src/main/java/com/google/devtools/build/lib/runtime/BuildEventStreamer.java:671
- XmlOutputFormatter.createValueElement (cognitive 35) src/main/java/com/google/devtools/build/lib/query2/query/output/XmlOutputFormatter.java:315
- BlazeQueryEnvironment.getTargetsMatchingPatternImpl (cognitive 35) src/main/java/com/google/devtools/build/lib/query2/query/BlazeQueryEnvironment.java:178
- OptionsDiff.diff (cognitive 35) src/main/java/com/google/devtools/build/lib/analysis/config/OptionsDiff.java:113
- CompactPersistentActionCache.decodeInternal (cognitive 35) src/main/java/com/google/devtools/build/lib/actions/cache/CompactPersistentActionCache.java:999
- PostAnalysisQueryEnvironment.targetifyValues (cognitive 34) src/main/java/com/google/devtools/build/lib/query2/PostAnalysisQueryEnvironment.java:668
- CompileOneDependencyTransformer.transformCompileOneDependency (cognitive 34) src/main/java/com/google/devtools/build/lib/pkgcache/CompileOneDependencyTransformer.java:88
- StarlarkBaseExternalContext.getAuthHeaders (cognitive 34) src/main/java/com/google/devtools/build/lib/bazel/repository/starlark/StarlarkBaseExternalContext.java:340
- Resolver.bind (cognitive 33) src/main/java/net/starlark/java/syntax/Resolver.java:1249
- Lexer.stringLiteral (cognitive 33) src/main/java/net/starlark/java/syntax/Lexer.java:436
- TargetPatternsHelper.readFrom (cognitive 33) src/main/java/com/google/devtools/build/lib/runtime/commands/TargetPatternsHelper.java:68
- CleanCommand.actuallyClean (cognitive 33) src/main/java/com/google/devtools/build/lib/runtime/commands/CleanCommand.java:194
- BuildResultPrinter.outputConfiguredTargets (cognitive 33) src/main/java/com/google/devtools/build/lib/buildtool/BuildResultPrinter.java:408
- Indenter.indent (cognitive 32) src/main/java/net/starlark/java/lib/json/Json.java:716
- WorkerModule.buildStarting (cognitive 32) src/main/java/com/google/devtools/build/lib/worker/WorkerModule.java:90
- TestResultAggregator.incrementalAnalyze (cognitive 32) src/main/java/com/google/devtools/build/lib/runtime/TestResultAggregator.java:165
- AggregatingAttributeMapper.checkForDuplicateLabels (cognitive 32) src/main/java/com/google/devtools/build/lib/packages/AggregatingAttributeMapper.java:241
- Directory.syncTreeRecursively (cognitive 32) src/main/java/com/google/devtools/build/lib/exec/SymlinkTreeHelper.java:246
- NestedSetBuilder.buildInternal (cognitive 32) src/main/java/com/google/devtools/build/lib/collect/nestedset/NestedSetBuilder.java:221
- ModExecutor.displayExtension (cognitive 32) src/main/java/com/google/devtools/build/lib/bazel/bzlmod/modcommand/ModExecutor.java:613
- _CLRParser.handle_starttag (cognitive 32) scripts/docs/clr_converter.py:124
- Encoder.encode (cognitive 31) src/main/java/net/starlark/java/lib/json/Json.java:121
- StarlarkInt.parse (cognitive 31) src/main/java/net/starlark/java/eval/StarlarkInt.java:104
- StarlarkFloat.format (cognitive 31) src/main/java/net/starlark/java/eval/StarlarkFloat.java:130
- StarlarkMethodProcessor.checkParameters (cognitive 31) src/main/java/net/starlark/java/annot/processor/StarlarkMethodProcessor.java:321
- WorkerSpawnRunner.execInWorker (cognitive 31) src/main/java/com/google/devtools/build/lib/worker/WorkerSpawnRunner.java:380
- TimestampGranularityMonitor.waitForTimestampGranularity (cognitive 31) src/main/java/com/google/devtools/build/lib/util/io/TimestampGranularityMonitor.java:158
- SingleToolchainResolutionFunction.computeResolutionDiagnostic (cognitive 31) src/main/java/com/google/devtools/build/lib/skyframe/toolchains/SingleToolchainResolutionFunction.java:263
- ActionRewindStrategy.getLostInputOwningDirectDeps (cognitive 31) src/main/java/com/google/devtools/build/lib/skyframe/rewinding/ActionRewindStrategy.java:719
- SandboxHelpers.updateContentMap (cognitive 31) src/main/java/com/google/devtools/build/lib/sandbox/SandboxHelpers.java:848
- ConfigExpander.getExpansion (cognitive 31) src/main/java/com/google/devtools/build/lib/runtime/ConfigExpander.java:284
- BuildEventStreamer.post (cognitive 31) src/main/java/com/google/devtools/build/lib/runtime/BuildEventStreamer.java:337
- IncludeParser.extractInclusion (cognitive 31) src/main/java/com/google/devtools/build/lib/includescanning/IncludeParser.java:756
- ModuleFileFunction.advanceHorizon (cognitive 31) src/main/java/com/google/devtools/build/lib/bazel/bzlmod/ModuleFileFunction.java:413
- VectorArg.addToFingerprint (cognitive 31) src/main/java/com/google/devtools/build/lib/analysis/starlark/StarlarkCustomCommandLine.java:602
- OptionsDiffCodec.serialize (cognitive 31) src/main/java/com/google/devtools/build/lib/analysis/config/OptionsDiff.java:667
- ArgumentProcessor.call (cognitive 30) src/main/java/net/starlark/java/eval/StarlarkFunction.java:581
- OptionsClassProcessor.generateWrapper (cognitive 30) src/main/java/com/google/devtools/common/options/processor/OptionsClassProcessor.java:151
- DependencySet.process (cognitive 30) src/main/java/com/google/devtools/build/lib/util/DependencySet.java:131
- ExecuteRetrier.resultClassifier (cognitive 30) src/main/java/com/google/devtools/build/lib/remote/ExecuteRetrier.java:92
- GraphOutputWriter.getConditionsGraphLabel (cognitive 30) src/main/java/com/google/devtools/build/lib/query2/query/output/GraphOutputWriter.java:343
- ActionGraphTextOutputFormatterCallback.writeText (cognitive 30) src/main/java/com/google/devtools/build/lib/query2/aquery/ActionGraphTextOutputFormatterCallback.java:167
- AttributeProvider.populateDefinedRuleAttributeValues (cognitive 30) src/main/java/com/google/devtools/build/lib/packages/AttributeProvider.java:186
- StarlarkActionFactory.symlink (cognitive 30) src/main/java/com/google/devtools/build/lib/analysis/starlark/StarlarkActionFactory.java:259
- CommonPrerequisiteValidator.validateDirectPrerequisiteVisibility (cognitive 30) src/main/java/com/google/devtools/build/lib/analysis/CommonPrerequisiteValidator.java:187
- BuildView.createTopLevelAspectKeys (cognitive 30) src/main/java/com/google/devtools/build/lib/analysis/BuildView.java:532
- mirror_external_deps.collect_candidates (cognitive 30) tools/mirror_external_deps.py:185
- TypeChecker.inferIndexUnfolded (cognitive 29) src/main/java/net/starlark/java/syntax/TypeChecker.java:341
- Resolver.visit (cognitive 29) src/main/java/net/starlark/java/syntax/Resolver.java:783
- Decoder.parseString (cognitive 29) src/main/java/net/starlark/java/lib/json/Json.java:485
- Printer.formatWithList (cognitive 29) src/main/java/net/starlark/java/eval/Printer.java:462
- IsolatedOptionsData.from (cognitive 29) src/main/java/com/google/devtools/common/options/IsolatedOptionsData.java:270
- DeletingNodeVisitor.visit (cognitive 29) src/main/java/com/google/devtools/build/skyframe/InvalidatingNodeVisitor.java:300
- CommandFailureUtils.describeCommand (cognitive 29) src/main/java/com/google/devtools/build/lib/util/CommandFailureUtils.java:44
- NodeDependencyHandler.reduce (cognitive 29) src/main/java/com/google/devtools/build/lib/skyframe/serialization/analysis/FileDependencySerializer.java:955
- BuildOptionsScopeFunction.compute (cognitive 29) src/main/java/com/google/devtools/build/lib/skyframe/BuildOptionsScopeFunction.java:61
- DiskCacheClient.refreshActionResult (cognitive 29) src/main/java/com/google/devtools/build/lib/remote/disk/DiskCacheClient.java:253
- RuleClass.checkAspectAllowedValues (cognitive 29) src/main/java/com/google/devtools/build/lib/packages/RuleClass.java:2165
- Builder.<init> (cognitive 29) src/main/java/com/google/devtools/build/lib/packages/RuleClass.java:765
- MacroClass.instantiateMacro (cognitive 29) src/main/java/com/google/devtools/build/lib/packages/MacroClass.java:210
- LabelValidator.validateTargetName (cognitive 29) src/main/java/com/google/devtools/build/lib/cmdline/LabelValidator.java:146
- UrlRewriterConfig.parseConfig (cognitive 29) src/main/java/com/google/devtools/build/lib/bazel/repository/downloader/UrlRewriterConfig.java:125
- StarlarkRuleConfiguredTargetUtil.addProviders (cognitive 29) src/main/java/com/google/devtools/build/lib/analysis/starlark/StarlarkRuleConfiguredTargetUtil.java:239
- FunctionTransitionUtil.applyStarlarkFlagsAliases (cognitive 29) src/main/java/com/google/devtools/build/lib/analysis/starlark/FunctionTransitionUtil.java:345
- DependencyMapProducer.attributeResolutionStep (cognitive 29) src/main/java/com/google/devtools/build/lib/analysis/producers/DependencyMapProducer.java:329
- BuildView.update (cognitive 29) src/main/java/com/google/devtools/build/lib/analysis/BuildView.java:224
- CompactPersistentActionCache.encode (cognitive 29) src/main/java/com/google/devtools/build/lib/actions/cache/CompactPersistentActionCache.java:868
- CommandLines.expand (cognitive 29) src/main/java/com/google/devtools/build/lib/actions/CommandLines.java:84
- Main.main (cognitive 28) src/main/java/net/starlark/java/cmd/Main.java:171
- PathFragment.isNormalizedImpl (cognitive 28) src/main/java/com/google/devtools/build/lib/vfs/PathFragment.java:879
- BlazeOptionHandler.structureRcOptionsAndConfigs (cognitive 28) src/main/java/com/google/devtools/build/lib/runtime/BlazeOptionHandler.java:730
- CppConfiguration.<init> (cognitive 28) src/main/java/com/google/devtools/build/lib/rules/cpp/CppConfiguration.java:169
- ConfigSetting.optionMatches (cognitive 28) src/main/java/com/google/devtools/build/lib/rules/config/ConfigSetting.java:518
- RemoteSpawnRunner.exec (cognitive 28) src/main/java/com/google/devtools/build/lib/remote/RemoteSpawnRunner.java:182
- RemoteExecutionService.waitForAndReuseOutputs (cognitive 28) src/main/java/com/google/devtools/build/lib/remote/RemoteExecutionService.java:1671
- RepositoryUtils.replantSymlinks (cognitive 28) src/main/java/com/google/devtools/build/lib/bazel/repository/RepositoryUtils.java:109
- GoogleAuthUtils.newChannel (cognitive 28) src/main/java/com/google/devtools/build/lib/authandtls/GoogleAuthUtils.java:74
- TestRunnerAction.getTestOutputsMapping (cognitive 28) src/main/java/com/google/devtools/build/lib/analysis/test/TestRunnerAction.java:418
- NodePrinter.printStmt (cognitive 27) src/main/java/net/starlark/java/syntax/NodePrinter.java:159
- Starlark.slice (cognitive 27) src/main/java/net/starlark/java/eval/Starlark.java:796
- MethodLibrary.floatForStarlark (cognitive 27) src/main/java/net/starlark/java/eval/MethodLibrary.java:555
- ObjectGraphTraverser.getFields (cognitive 27) src/main/java/com/google/devtools/build/lib/util/ObjectGraphTraverser.java:480
- RecursiveFilesystemTraversalFunction.compute (cognitive 27) src/main/java/com/google/devtools/build/lib/skyframe/RecursiveFilesystemTraversalFunction.java:180
- IgnoredSubdirectoriesFunction.computeIgnoredPrefixes (cognitive 27) src/main/java/com/google/devtools/build/lib/skyframe/IgnoredSubdirectoriesFunction.java:128
- EvalMacroFunction.compute (cognitive 27) src/main/java/com/google/devtools/build/lib/skyframe/EvalMacroFunction.java:71
- ConfiguredTargetFunction.compute (cognitive 27) src/main/java/com/google/devtools/build/lib/skyframe/ConfiguredTargetFunction.java:256
- ActionExecutionFunction.addDiscoveredInputs (cognitive 27) src/main/java/com/google/devtools/build/lib/skyframe/ActionExecutionFunction.java:874
- ActionDumpWriter.maybeAddEdges (cognitive 27) src/main/java/com/google/devtools/build/lib/runtime/ExecutionGraphModule.java:573
- JavaUtil.javaSegmentIndexImpl (cognitive 27) src/main/java/com/google/devtools/build/lib/rules/java/JavaUtil.java:89
- JsonTraceFileWriter.run (cognitive 27) src/main/java/com/google/devtools/build/lib/profiler/JsonTraceFileWriter.java:252
- SubprocessHandler.start (cognitive 27) src/main/java/com/google/devtools/build/lib/exec/local/LocalSpawnRunner.java:310
- ExpandedSpawnLogContext.logSpawn (cognitive 27) src/main/java/com/google/devtools/build/lib/exec/ExpandedSpawnLogContext.java:156
- DownloadManager.downloadAndReadOneUrlForBzlmod (cognitive 27) src/main/java/com/google/devtools/build/lib/bazel/repository/downloader/DownloadManager.java:409
- IndexRegistry.createArchiveRepoSpec (cognitive 27) src/main/java/com/google/devtools/build/lib/bazel/bzlmod/IndexRegistry.java:472
- Eval.execFor (cognitive 26) src/main/java/net/starlark/java/eval/Eval.java:155
- Driver.drive (cognitive 26) src/main/java/com/google/devtools/build/skyframe/state/Driver.java:54
- ChangePrunableNodesFinder.scanCandidates (cognitive 26) src/main/java/com/google/devtools/build/skyframe/ChangePrunableNodesFinder.java:102
- ObjectCodecRegistry.<init> (cognitive 26) src/main/java/com/google/devtools/build/lib/skyframe/serialization/ObjectCodecRegistry.java:84
- EnvironmentBackedRecursivePackageProvider.streamPackagesUnderDirectory (cognitive 26) src/main/java/com/google/devtools/build/lib/skyframe/EnvironmentBackedRecursivePackageProvider.java:176
- ActionExecutionFunction.checkCacheAndExecuteIfNeeded (cognitive 26) src/main/java/com/google/devtools/build/lib/skyframe/ActionExecutionFunction.java:669
- SandboxHelpers.cleanRecursively (cognitive 26) src/main/java/com/google/devtools/build/lib/sandbox/SandboxHelpers.java:401
- LinuxSandboxUtil.validateBindMounts (cognitive 26) src/main/java/com/google/devtools/build/lib/sandbox/LinuxSandboxUtil.java:56
- QueryCommand.doQuery (cognitive 26) src/main/java/com/google/devtools/build/lib/runtime/commands/QueryCommand.java:76
- HttpDownloadHandler.channelRead0 (cognitive 26) src/main/java/com/google/devtools/build/lib/remote/http/HttpDownloadHandler.java:71
- RemoteImportantOutputHandler.downloadArtifact (cognitive 26) src/main/java/com/google/devtools/build/lib/remote/RemoteImportantOutputHandler.java:183
- RemoteExternalOverlayFileSystem.injectRecursively (cognitive 26) src/main/java/com/google/devtools/build/lib/remote/RemoteExternalOverlayFileSystem.java:288
- ProtoOutputFormatterCallback.processOutput (cognitive 26) src/main/java/com/google/devtools/build/lib/query2/cquery/ProtoOutputFormatterCallback.java:267
- RBuildFilesVisitor.getSkyKeysForFileFragments (cognitive 26) src/main/java/com/google/devtools/build/lib/query2/RBuildFilesVisitor.java:200
- PostAnalysisQueryEnvironment.getConfiguredTargetsForConfigFunction (cognitive 26) src/main/java/com/google/devtools/build/lib/query2/PostAnalysisQueryEnvironment.java:270
- ImplicitOutputsFunction.attributeValues (cognitive 26) src/main/java/com/google/devtools/build/lib/packages/ImplicitOutputsFunction.java:374
- TestXmlOutputParser.parseContainedElements (cognitive 26) src/main/java/com/google/devtools/build/lib/exec/TestXmlOutputParser.java:222
- BuildTool.processRequestHandleCheckedExceptions (cognitive 26) src/main/java/com/google/devtools/build/lib/buildtool/BuildTool.java:1005
- ModuleFileFunction.getModuleFile (cognitive 26) src/main/java/com/google/devtools/build/lib/bazel/bzlmod/ModuleFileFunction.java:816
- RuleContextConstraintSemantics.getConstraintCheckedDependencies (cognitive 26) src/main/java/com/google/devtools/build/lib/analysis/constraints/RuleContextConstraintSemantics.java:730
- BuildView.addExtraActionsIfRequested (cognitive 26) src/main/java/com/google/devtools/build/lib/analysis/BuildView.java:815
- Starlark.classType (cognitive 25) src/main/java/net/starlark/java/eval/Starlark.java:423
- TestCompletionFunction.compute (cognitive 25) src/main/java/com/google/devtools/build/lib/skyframe/TestCompletionFunction.java:50
- RecursiveExpander.expand (cognitive 25) src/main/java/com/google/devtools/build/lib/skyframe/EvalMacroFunction.java:305
- BzlLoadFunction.getAndDigestPredeclaredEnvironment (cognitive 25) src/main/java/com/google/devtools/build/lib/skyframe/BzlLoadFunction.java:1329
- SandboxModule.cleanSandboxBaseOnFirstBuild (cognitive 25) src/main/java/com/google/devtools/build/lib/sandbox/SandboxModule.java:380
- BlazeRuntime.deleteOutputBase (cognitive 25) src/main/java/com/google/devtools/build/lib/runtime/BlazeRuntime.java:2069
- BlazeCommandDispatcher.exec (cognitive 25) src/main/java/com/google/devtools/build/lib/runtime/BlazeCommandDispatcher.java:193
- RemoteSpawnRunner.handleError (cognitive 25) src/main/java/com/google/devtools/build/lib/remote/RemoteSpawnRunner.java:600
- TaskData.writeTraceData (cognitive 25) src/main/java/com/google/devtools/build/lib/profiler/TaskData.java:74
- DynamicSpawnStrategy.stopBranch (cognitive 25) src/main/java/com/google/devtools/build/lib/dynamic/DynamicSpawnStrategy.java:680
- BuildTool.buildTargetsWithoutMergedAnalysisExecution (cognitive 25) src/main/java/com/google/devtools/build/lib/buildtool/BuildTool.java:557
- ConfiguredTargetFactory.createRule (cognitive 25) src/main/java/com/google/devtools/build/lib/analysis/ConfiguredTargetFactory.java:383
- BuildView.checkUnknownOutputGroups (cognitive 25) src/main/java/com/google/devtools/build/lib/analysis/BuildView.java:952
- TypeChecker.checkCallMissingMandatoryArgs (cognitive 24) src/main/java/net/starlark/java/syntax/TypeChecker.java:896
- TypeChecker.inferBinaryOperator (cognitive 24) src/main/java/net/starlark/java/syntax/TypeChecker.java:516
- WorkerFilesHash.getWorkerFilesWithDigests (cognitive 24) src/main/java/com/google/devtools/build/lib/worker/WorkerFilesHash.java:66
- JsonWorkerMessageProcessor.readWorkRequest (cognitive 24) src/main/java/com/google/devtools/build/lib/worker/JsonWorkerMessageProcessor.java:103
- GlobVisitor.reallyGlob (cognitive 24) src/main/java/com/google/devtools/build/lib/vfs/UnixGlob.java:776
- FlagSetFunction.expandConfigFlags (cognitive 24) src/main/java/com/google/devtools/build/lib/skyframe/config/FlagSetFunction.java:547
- ActionExecutionFunctionExceptionHandler.accumulateAndMaybeThrowExceptions (cognitive 24) src/main/java/com/google/devtools/build/lib/skyframe/ActionExecutionFunction.java:1461
- CommandServer.run (cognitive 24) src/main/java/com/google/devtools/build/lib/server/CommandServer.java:427
- RemoteRewoundActionSynchronizer.prepareOutputsForRewinding (cognitive 24) src/main/java/com/google/devtools/build/lib/remote/RemoteRewoundActionSynchronizer.java:236
- XmlOutputFormatter.createTargetElement (cognitive 24) src/main/java/com/google/devtools/build/lib/query2/query/output/XmlOutputFormatter.java:147
- SyntheticAttributeHashCalculator.compute (cognitive 24) src/main/java/com/google/devtools/build/lib/query2/query/output/SyntheticAttributeHashCalculator.java:56
- NetworkMetricsCollector.collectSystemNetworkUsages (cognitive 24) src/main/java/com/google/devtools/build/lib/profiler/NetworkMetricsCollector.java:55
- CompileOneDependencyTransformer.listContainsFile (cognitive 24) src/main/java/com/google/devtools/build/lib/pkgcache/CompileOneDependencyTransformer.java:209
- BuildType.selectableConvert (cognitive 24) src/main/java/com/google/devtools/build/lib/packages/BuildType.java:166
- RepositoryFetchFunction.fetch (cognitive 24) src/main/java/com/google/devtools/build/lib/bazel/repository/RepositoryFetchFunction.java:602
- RepoMappingManifestAction.newDeterministicWriter (cognitive 24) src/main/java/com/google/devtools/build/lib/analysis/RepoMappingManifestAction.java:191
- MethodDescriptor.buildStarlarkType (cognitive 23) src/main/java/net/starlark/java/eval/MethodDescriptor.java:159
- BuiltinFunction.applyDefaultsReportMissingArgs (cognitive 23) src/main/java/net/starlark/java/eval/BuiltinFunction.java:472
- StarlarkMethodProcessor.checkParameter (cognitive 23) src/main/java/net/starlark/java/annot/processor/StarlarkMethodProcessor.java:400
- AttributeInfoExtractor.getAttributeType (cognitive 23) src/main/java/com/google/devtools/build/lib/starlarkdocextract/AttributeInfoExtractor.java:111
- SingleToolchainResolutionFunction.resolveConstraints (cognitive 23) src/main/java/com/google/devtools/build/lib/skyframe/toolchains/SingleToolchainResolutionFunction.java:153
- FileOpNodeMemoizingLookup.accumulateTransitiveFileSystemOperations (cognitive 23) src/main/java/com/google/devtools/build/lib/skyframe/serialization/analysis/FileOpNodeMemoizingLookup.java:226
- RewindableGraphInconsistencyReceiver.noteInconsistencyAndMaybeThrow (cognitive 23) src/main/java/com/google/devtools/build/lib/skyframe/rewinding/RewindableGraphInconsistencyReceiver.java:65
- SkyframeBuildView.analyzeAndExecuteTargets (cognitive 23) src/main/java/com/google/devtools/build/lib/skyframe/SkyframeBuildView.java:620
- ActionLookupValueProgressReceiver.evaluated (cognitive 23) src/main/java/com/google/devtools/build/lib/skyframe/SkyframeBuildView.java:1511
- LinuxSandboxCommandLineBuilder.buildForCommand (cognitive 23) src/main/java/com/google/devtools/build/lib/sandbox/LinuxSandboxCommandLineBuilder.java:233
- ConfigExpander.expandConfigOptions (cognitive 23) src/main/java/com/google/devtools/build/lib/runtime/ConfigExpander.java:93
- Builder.build (cognitive 23) src/main/java/com/google/devtools/build/lib/rules/java/JavaHeaderCompileAction.java:435
- PathCanonicalizer.resolveSymbolicLinks (cognitive 23) src/main/java/com/google/devtools/build/lib/remote/PathCanonicalizer.java:119
- SkyQueryEnvironment.processRawReverseDeps (cognitive 23) src/main/java/com/google/devtools/build/lib/query2/SkyQueryEnvironment.java:819
- TargetRecorder.checkRuleAndOutputs (cognitive 23) src/main/java/com/google/devtools/build/lib/packages/TargetRecorder.java:542
- AggregatingAttributeMapper.visitLabels (cognitive 23) src/main/java/com/google/devtools/build/lib/packages/AggregatingAttributeMapper.java:107
- InclusionCache.locateOnFrameworkPaths (cognitive 23) src/main/java/com/google/devtools/build/lib/includescanning/LegacyIncludeScanner.java:243
- AbstractSpawnStrategy.exec (cognitive 23) src/main/java/com/google/devtools/build/lib/exec/AbstractSpawnStrategy.java:101
- ConcurrentIdentitySet.add (cognitive 23) src/main/java/com/google/devtools/build/lib/collect/ConcurrentIdentitySet.java:58
- Parts.parse (cognitive 23) src/main/java/com/google/devtools/build/lib/cmdline/LabelParser.java:109
- ModCommand.getReposToShow (cognitive 23) src/main/java/com/google/devtools/build/lib/bazel/commands/ModCommand.java:656
- ModuleExtensionMetadata.create (cognitive 23) src/main/java/com/google/devtools/build/lib/bazel/bzlmod/ModuleExtensionMetadata.java:88
- StarlarkRuleClassFunctions.macro (cognitive 23) src/main/java/com/google/devtools/build/lib/analysis/starlark/StarlarkRuleClassFunctions.java:407
- MutableArgs.addVectorArg (cognitive 23) src/main/java/com/google/devtools/build/lib/analysis/starlark/Args.java:438
- LocationExpander.buildLocationMap (cognitive 23) src/main/java/com/google/devtools/build/lib/analysis/LocationExpander.java:420
- ActionConflictException.debugSuffix (cognitive 23) src/main/java/com/google/devtools/build/lib/actions/ActionConflictException.java:254
- RuleLinkExpander.expandRuleLinks (cognitive 23) src/main/java/com/google/devtools/build/docgen/RuleLinkExpander.java:91
- BuildDocCollector.collectJavaSourceDocs (cognitive 23) src/main/java/com/google/devtools/build/docgen/BuildDocCollector.java:284
- Eval.evalCall (cognitive 22) src/main/java/net/starlark/java/eval/Eval.java:743
- ParallelEvaluator.constructResult (cognitive 22) src/main/java/com/google/devtools/build/skyframe/ParallelEvaluator.java:509
- PathFragment.subFragmentImpl (cognitive 22) src/main/java/com/google/devtools/build/lib/vfs/PathFragment.java:652
- FileWatcher.run (cognitive 22) src/main/java/com/google/devtools/build/lib/util/io/FileWatcher.java:75
- SkyframeBuildView.reportActionConflictErrors (cognitive 22) src/main/java/com/google/devtools/build/lib/skyframe/SkyframeBuildView.java:1046
- BlazeOptionHandler.parseRcOptions (cognitive 22) src/main/java/com/google/devtools/build/lib/runtime/BlazeOptionHandler.java:217
- JavaCompileActionContext.addDependencies (cognitive 22) src/main/java/com/google/devtools/build/lib/rules/java/JavaCompileActionContext.java:48
- HttpCacheClient.uploadAsync (cognitive 22) src/main/java/com/google/devtools/build/lib/remote/http/HttpCacheClient.java:694
- Type.inferBinaryOperator (cognitive 22) src/main/java/com/google/devtools/build/lib/packages/SelectorValue.java:191
- SpawnLogReconstructor.visitInputSet (cognitive 22) src/main/java/com/google/devtools/build/lib/exec/SpawnLogReconstructor.java:200
- EagerRequestBatcher.submit (cognitive 22) src/main/java/com/google/devtools/build/lib/concurrent/EagerRequestBatcher.java:166
- BuildTool.buildTargets (cognitive 22) src/main/java/com/google/devtools/build/lib/buildtool/BuildTool.java:222
- ProxyHelper.createProxyInfo (cognitive 22) src/main/java/com/google/devtools/build/lib/bazel/repository/downloader/ProxyHelper.java:233
- TextOutputFormatter.printModule (cognitive 22) src/main/java/com/google/devtools/build/lib/bazel/bzlmod/modcommand/TextOutputFormatter.java:143
- ModExecutor.expandPathsToTargets (cognitive 22) src/main/java/com/google/devtools/build/lib/bazel/bzlmod/modcommand/ModExecutor.java:269
- SingleExtensionFunction.compute (cognitive 22) src/main/java/com/google/devtools/build/lib/bazel/bzlmod/SingleExtensionFunction.java:37
- Builder.addAttribute (cognitive 22) src/main/java/com/google/devtools/build/lib/analysis/starlark/StarlarkAttributesCollection.java:390
- RuleContextConstraintSemantics.getUnsupportedEnvironments (cognitive 22) src/main/java/com/google/devtools/build/lib/analysis/constraints/RuleContextConstraintSemantics.java:673
- RegularTransition.evaluate (cognitive 22) src/main/java/com/google/devtools/build/lib/analysis/config/StarlarkDefinedConfigTransition.java:547
- OptionsDiff.applyDiff (cognitive 22) src/main/java/com/google/devtools/build/lib/analysis/config/OptionsDiff.java:489
- RuleContext.getRequiredConfigFragments (cognitive 22) src/main/java/com/google/devtools/build/lib/analysis/RuleContext.java:1137
- ConfiguredTargetFactory.createConfiguredTarget (cognitive 22) src/main/java/com/google/devtools/build/lib/analysis/ConfiguredTargetFactory.java:221
- ActionExecutedEvent.asStreamProto (cognitive 22) src/main/java/com/google/devtools/build/lib/actions/ActionExecutedEvent.java:175
- ActionCacheChecker.isUpToDate (cognitive 22) src/main/java/com/google/devtools/build/lib/actions/ActionCacheChecker.java:199
- SingleOptionValueDescription.addOptionInstance (cognitive 21) src/main/java/com/google/devtools/common/options/OptionValueDescription.java:208
- TargetPatternValue.computeTargetPatternKeyWithExclusions (cognitive 21) src/main/java/com/google/devtools/build/lib/skyframe/TargetPatternValue.java:133
- SequencedSkyframeExecutor.sync (cognitive 21) src/main/java/com/google/devtools/build/lib/skyframe/SequencedSkyframeExecutor.java:264
- IncrementalPackageRoots.plantSingleSymlinkForPackage (cognitive 21) src/main/java/com/google/devtools/build/lib/skyframe/IncrementalPackageRoots.java:329
- FileSystemValueCheckerInferringAncestors.visitEntry (cognitive 21) src/main/java/com/google/devtools/build/lib/skyframe/FileSystemValueCheckerInferringAncestors.java:287
- AspectFunction.createAspect (cognitive 21) src/main/java/com/google/devtools/build/lib/skyframe/AspectFunction.java:968
- SandboxModule.setup (cognitive 21) src/main/java/com/google/devtools/build/lib/sandbox/SandboxModule.java:198
- SandboxHelpers.cleanRecursivelyWithInMemoryContents (cognitive 21) src/main/java/com/google/devtools/build/lib/sandbox/SandboxHelpers.java:335
- WorkerMetricsInfoItem.get (cognitive 21) src/main/java/com/google/devtools/build/lib/runtime/commands/info/WorkerMetricsInfoItem.java:37
- DumpCommand.exec (cognitive 21) src/main/java/com/google/devtools/build/lib/runtime/commands/DumpCommand.java:399
- TerminalTestResultNotifier.printStats (cognitive 21) src/main/java/com/google/devtools/build/lib/runtime/TerminalTestResultNotifier.java:273
- HttpCacheClient.get (cognitive 21) src/main/java/com/google/devtools/build/lib/remote/http/HttpCacheClient.java:522
- RemoteActionFileSystem.getDirectoryContents (cognitive 21) src/main/java/com/google/devtools/build/lib/remote/RemoteActionFileSystem.java:836
- ActionGraphTextOutputFormatterCallback.processOutput (cognitive 21) src/main/java/com/google/devtools/build/lib/query2/aquery/ActionGraphTextOutputFormatterCallback.java:106
- SpawnLogReconstructor.visitSymlinkEntries (cognitive 21) src/main/java/com/google/devtools/build/lib/exec/SpawnLogReconstructor.java:247
- DynamicSpawnStrategy.maybeExecuteNonDynamically (cognitive 21) src/main/java/com/google/devtools/build/lib/dynamic/DynamicSpawnStrategy.java:355
- ModCommand.validateArgs (cognitive 21) src/main/java/com/google/devtools/build/lib/bazel/commands/ModCommand.java:142
- JsonOutputFormatter.printModule (cognitive 21) src/main/java/com/google/devtools/build/lib/bazel/bzlmod/modcommand/JsonOutputFormatter.java:92
- IndexRegistry.doGrabFile (cognitive 21) src/main/java/com/google/devtools/build/lib/bazel/bzlmod/IndexRegistry.java:167
- TestStrategy.processTestOutput (cognitive 21) src/main/java/com/google/devtools/build/lib/analysis/test/TestStrategy.java:375
- TemplateExpander.expand (cognitive 21) src/main/java/com/google/devtools/build/lib/analysis/stringtemplate/TemplateExpander.java:73
- StarlarkCustomCommandLine.applyMapEach (cognitive 21) src/main/java/com/google/devtools/build/lib/analysis/starlark/StarlarkCustomCommandLine.java:1293
- Util.findImplicitDeps (cognitive 21) src/main/java/com/google/devtools/build/lib/analysis/Util.java:82
- _CLRParser._parse_dt (cognitive 21) scripts/docs/clr_converter.py:388
- Parser.parseSmallStatement (cognitive 20) src/main/java/net/starlark/java/syntax/Parser.java:1562
- Eval.newFunction (cognitive 20) src/main/java/net/starlark/java/eval/Eval.java:228
- StarlarkAnnotations.getAnnotationOnClassMatchingSignature (cognitive 20) src/main/java/net/starlark/java/annot/StarlarkAnnotations.java:222
- OptionsUsage.getUsage (cognitive 20) src/main/java/com/google/devtools/common/options/OptionsUsage.java:51
- AbstractInMemoryMemoizingEvaluator.pruneInjectedValues (cognitive 20) src/main/java/com/google/devtools/build/skyframe/AbstractInMemoryMemoizingEvaluator.java:463
- UnixGlob.removeExcludes (cognitive 20) src/main/java/com/google/devtools/build/lib/vfs/UnixGlob.java:894
- AnsiStrippingOutputStream.processByte (cognitive 20) src/main/java/com/google/devtools/build/lib/util/AnsiStrippingOutputStream.java:90
- ToolchainContextUtil.getPerExecGroupExecutionPlatformConstraints (cognitive 20) src/main/java/com/google/devtools/build/lib/skyframe/toolchains/ToolchainContextUtil.java:169
- TargetPatternPhaseFunction.determineTests (cognitive 20) src/main/java/com/google/devtools/build/lib/skyframe/TargetPatternPhaseFunction.java:412
- TargetPatternPhaseFunction.getTargetsToBuild (cognitive 20) src/main/java/com/google/devtools/build/lib/skyframe/TargetPatternPhaseFunction.java:285
- SkyframeExecutor.handleDiffs (cognitive 20) src/main/java/com/google/devtools/build/lib/skyframe/SkyframeExecutor.java:3854
- IncrementalArtifactConflictFinder.checkOutputPrefix (cognitive 20) src/main/java/com/google/devtools/build/lib/skyframe/IncrementalArtifactConflictFinder.java:378
- GlobsFunction.compute (cognitive 20) src/main/java/com/google/devtools/build/lib/skyframe/GlobsFunction.java:108
- DependencyResolver.computeDependencies (cognitive 20) src/main/java/com/google/devtools/build/lib/skyframe/DependencyResolver.java:672
- ActionExecutionFunction.checkInputs (cognitive 20) src/main/java/com/google/devtools/build/lib/skyframe/ActionExecutionFunction.java:1017
- ServerWatcherRunnable.run (cognitive 20) src/main/java/com/google/devtools/build/lib/server/ServerWatcherRunnable.java:164
- SandboxModule.afterCommand (cognitive 20) src/main/java/com/google/devtools/build/lib/sandbox/SandboxModule.java:512
- TestCommand.doTest (cognitive 20) src/main/java/com/google/devtools/build/lib/runtime/commands/TestCommand.java:128
- RunCommand.exec (cognitive 20) src/main/java/com/google/devtools/build/lib/runtime/commands/RunCommand.java:249
- GetInitPyFiles.getInitPyFiles (cognitive 20) src/main/java/com/google/devtools/build/lib/rules/python/PythonUtils.java:72
- JavaHeaderCompileAction.filterJavacoptsForTurbine (cognitive 20) src/main/java/com/google/devtools/build/lib/rules/java/JavaHeaderCompileAction.java:749
- CcToolchainVariables.lookupVariable (cognitive 20) src/main/java/com/google/devtools/build/lib/rules/cpp/CcToolchainVariables.java:341
- Retrier.execute (cognitive 20) src/main/java/com/google/devtools/build/lib/remote/Retrier.java:319
- IncludeParser.skipWhitespace (cognitive 20) src/main/java/com/google/devtools/build/lib/includescanning/IncludeParser.java:580
- BuildObjectTraverser.admit (cognitive 20) src/main/java/com/google/devtools/build/lib/buildtool/BuildObjectTraverser.java:93
- BugReport.handleCrash (cognitive 20) src/main/java/com/google/devtools/build/lib/bugreport/BugReport.java:270
- PatchUtil.applyPatchToFile (cognitive 20) src/main/java/com/google/devtools/build/lib/bazel/repository/decompressor/PatchUtil.java:200
- BazelFetchAllFunction.compute (cognitive 20) src/main/java/com/google/devtools/build/lib/bazel/bzlmod/BazelFetchAllFunction.java:43
- DependencyProducer.evaluateMaterializerTargets (cognitive 20) src/main/java/com/google/devtools/build/lib/analysis/producers/DependencyProducer.java:422
- DependencyMapProducer.evaluateAspectHintsTargets (cognitive 20) src/main/java/com/google/devtools/build/lib/analysis/producers/DependencyMapProducer.java:518
- ResolvedToolchainContext.load (cognitive 20) src/main/java/com/google/devtools/build/lib/analysis/ResolvedToolchainContext.java:48
- Actions.assignOwnersAndThrowIfConflictMaybeToleratingSharedActions (cognitive 20) src/main/java/com/google/devtools/build/lib/actions/Actions.java:238
- ActionCacheChecker.getCachedInputs (cognitive 20) src/main/java/com/google/devtools/build/lib/actions/ActionCacheChecker.java:760
- 1.readLineImpl (cognitive 20) src/main/java/com/google/devtools/build/docgen/SourceFileReader.java:109
- TypeTagger.createFunctionType (cognitive 19) src/main/java/net/starlark/java/syntax/TypeTagger.java:333
- Lexer.computeIndentation (cognitive 19) src/main/java/net/starlark/java/syntax/Lexer.java:201
- ArgumentProcessor.applyDefaultsReportMissingArgs (cognitive 19) src/main/java/net/starlark/java/eval/StarlarkFunction.java:479
- MethodDescriptor.call (cognitive 19) src/main/java/net/starlark/java/eval/MethodDescriptor.java:400
- HtmlUtils.getUsageHtml (cognitive 19) src/main/java/com/google/devtools/common/options/HtmlUtils.java:78
- SkyFunctionEnvironment.commitAndGetParents (cognitive 19) src/main/java/com/google/devtools/build/skyframe/SkyFunctionEnvironment.java:945
- ReverseDepsUtility.consolidateDataAndReturnNewElements (cognitive 19) src/main/java/com/google/devtools/build/skyframe/ReverseDepsUtility.java:194
- WorkerParser.splitSpawnArgsIntoWorkerArgsAndFlagFiles (cognitive 19) src/main/java/com/google/devtools/build/lib/worker/WorkerParser.java:212
- WorkerLifecycleManager.evictWorkers (cognitive 19) src/main/java/com/google/devtools/build/lib/worker/WorkerLifecycleManager.java:152
- ObjectGraphTraverser.enqueueMaybe (cognitive 19) src/main/java/com/google/devtools/build/lib/util/ObjectGraphTraverser.java:329
- AutoCodecProcessor.determineInstantiator (cognitive 19) src/main/java/com/google/devtools/build/lib/skyframe/serialization/autocodec/AutoCodecProcessor.java:159
- FlagSetFunction.getSclConfig (cognitive 19) src/main/java/com/google/devtools/build/lib/skyframe/config/FlagSetFunction.java:120
- SkyframeProgressReceiver.evaluated (cognitive 19) src/main/java/com/google/devtools/build/lib/skyframe/SkyframeExecutor.java:3622
- SequencedSkyframeExecutor.shouldDeleteOnAnalysisInvalidatingChange (cognitive 19) src/main/java/com/google/devtools/build/lib/skyframe/SequencedSkyframeExecutor.java:737
- PackageFunction.handleLabelsCrossingSubpackagesAndPropagateInconsistentFilesystemExceptions (cognitive 19) src/main/java/com/google/devtools/build/lib/skyframe/PackageFunction.java:871
- ConfiguredTargetFunction.createConfiguredTarget (cognitive 19) src/main/java/com/google/devtools/build/lib/skyframe/ConfiguredTargetFunction.java:427
- ArtifactNestedSetFunction.compute (cognitive 19) src/main/java/com/google/devtools/build/lib/skyframe/ArtifactNestedSetFunction.java:57
- ArtifactFunction.createTreeArtifactValueFromActionKey (cognitive 19) src/main/java/com/google/devtools/build/lib/skyframe/ArtifactFunction.java:230
- HtmlEmitter.emit (cognitive 19) src/main/java/com/google/devtools/build/lib/runtime/commands/HelpCommand.java:474
- SynchronizedOutputStream.write (cognitive 19) src/main/java/com/google/devtools/build/lib/runtime/SynchronizedOutputStream.java:91
- CppCompileActionTemplate.generateActionsForInputArtifacts (cognitive 19) src/main/java/com/google/devtools/build/lib/rules/cpp/CppCompileActionTemplate.java:119
- CppCompileAction.discoverInputs (cognitive 19) src/main/java/com/google/devtools/build/lib/rules/cpp/CppCompileAction.java:671
- CcToolchainFeatures.<init> (cognitive 19) src/main/java/com/google/devtools/build/lib/rules/cpp/CcToolchainFeatures.java:1098
- CcCompilationContext.computeUsedModules (cognitive 19) src/main/java/com/google/devtools/build/lib/rules/cpp/CcCompilationContext.java:362
- DirectoryBuilder.visit (cognitive 19) src/main/java/com/google/devtools/build/lib/remote/UploadManifest.java:479
- BazelOutputService.getBatchStatter (cognitive 19) src/main/java/com/google/devtools/build/lib/remote/BazelOutputService.java:654
- MinrankOutputFormatter.output (cognitive 19) src/main/java/com/google/devtools/build/lib/query2/query/output/MinrankOutputFormatter.java:69
- MacroClass.executeMacroImplementation (cognitive 19) src/main/java/com/google/devtools/build/lib/packages/MacroClass.java:401
- AspectsList.validateRulePropagatedAspectsParameters (cognitive 19) src/main/java/com/google/devtools/build/lib/packages/AspectsList.java:87
- AggregatingAttributeMapper.getAllValues (cognitive 19) src/main/java/com/google/devtools/build/lib/packages/AggregatingAttributeMapper.java:616
- CriticalPathComputer.finalizeActionStat (cognitive 19) src/main/java/com/google/devtools/build/lib/metrics/criticalpath/CriticalPathComputer.java:357
- TestXmlOutputParser.parseXmlToTree (cognitive 19) src/main/java/com/google/devtools/build/lib/exec/TestXmlOutputParser.java:51
- StableSort.stableSort (cognitive 19) src/main/java/com/google/devtools/build/lib/exec/StableSort.java:55
- SpawnInputExpander.addSingleRunfilesTreeToInputs (cognitive 19) src/main/java/com/google/devtools/build/lib/exec/SpawnInputExpander.java:82
- CompactSpawnLogContext.logSpawn (cognitive 19) src/main/java/com/google/devtools/build/lib/exec/CompactSpawnLogContext.java:231
- LabelValidator.validatePackageName (cognitive 19) src/main/java/com/google/devtools/build/lib/cmdline/LabelValidator.java:96
- RepositoryFetchFunction.tryGettingValueUsingVendoredRepo (cognitive 19) src/main/java/com/google/devtools/build/lib/bazel/repository/RepositoryFetchFunction.java:425
- VendorManager.vendorRepos (cognitive 19) src/main/java/com/google/devtools/build/lib/bazel/bzlmod/VendorManager.java:61
- ModuleFileFunction.compute (cognitive 19) src/main/java/com/google/devtools/build/lib/bazel/bzlmod/ModuleFileFunction.java:167
- LazySubstitution.getValue (cognitive 19) src/main/java/com/google/devtools/build/lib/analysis/starlark/TemplateDict.java:121
- StarlarkRuleContext.buildSplitAttributeInfo (cognitive 19) src/main/java/com/google/devtools/build/lib/analysis/starlark/StarlarkRuleContext.java:526
- StarlarkRuleContext.runfiles (cognitive 19) src/main/java/com/google/devtools/build/lib/analysis/starlark/StarlarkRuleContext.java:1101
- StarlarkRuleConfiguredTargetUtil.addSimpleProviders (cognitive 19) src/main/java/com/google/devtools/build/lib/analysis/starlark/StarlarkRuleConfiguredTargetUtil.java:434
- StarlarkCustomCommandLineWithIndexes.expand (cognitive 19) src/main/java/com/google/devtools/build/lib/analysis/starlark/StarlarkCustomCommandLine.java:1156
- ActionOutputDirectoryHelper.createAndCheckForSymlinks (cognitive 19) src/main/java/com/google/devtools/build/lib/actions/ActionOutputDirectoryHelper.java:261
- ActionCacheChecker.updateActionCache (cognitive 19) src/main/java/com/google/devtools/build/lib/actions/ActionCacheChecker.java:678
- TypeChecker.assignSequence (cognitive 18) src/main/java/net/starlark/java/syntax/TypeChecker.java:1172
- TypeChecker.visit (cognitive 18) src/main/java/net/starlark/java/syntax/TypeChecker.java:1301
- Resolver.lookupLexical (cognitive 18) src/main/java/net/starlark/java/syntax/Resolver.java:1065
- Eval.inplaceBinaryOp (cognitive 18) src/main/java/net/starlark/java/eval/Eval.java:558
- BuiltinFunction.getPositionalOnlyArgumentVector (cognitive 18) src/main/java/net/starlark/java/eval/BuiltinFunction.java:105
- StarlarkMethodProcessor.checkSpecialParams (cognitive 18) src/main/java/net/starlark/java/annot/processor/StarlarkMethodProcessor.java:493
- WorkerMultiplexer.createProcess (cognitive 18) src/main/java/com/google/devtools/build/lib/worker/WorkerMultiplexer.java:213
- JsonWorkerProtocol.parseResponse (cognitive 18) src/main/java/com/google/devtools/build/lib/worker/JsonWorkerProtocol.java:74
- JsonWorkerMessageProcessor.readInputs (cognitive 18) src/main/java/com/google/devtools/build/lib/worker/JsonWorkerMessageProcessor.java:58
- GlobalsVisitor.maybeVisit (cognitive 18) src/main/java/com/google/devtools/build/lib/starlarkdocextract/ModuleInfoExtractor.java:224
- ActionRewindStrategy.checkActions (cognitive 18) src/main/java/com/google/devtools/build/lib/skyframe/rewinding/ActionRewindStrategy.java:825
- FlagSetFunction.validateStarlarkFlags (cognitive 18) src/main/java/com/google/devtools/build/lib/skyframe/config/FlagSetFunction.java:435
- ActionRunner.actuallyCompleteAction (cognitive 18) src/main/java/com/google/devtools/build/lib/skyframe/SkyframeActionExecutor.java:1411
- BzlLoadFunction.getLoadLabels (cognitive 18) src/main/java/com/google/devtools/build/lib/skyframe/BzlLoadFunction.java:1047
- SandboxStash.initialize (cognitive 18) src/main/java/com/google/devtools/build/lib/sandbox/SandboxStash.java:424
- PrintActionRunner.gatherActionsForTargets (cognitive 18) src/main/java/com/google/devtools/build/lib/runtime/commands/PrintActionCommand.java:178
- StarlarkOptionsParser.parseArg (cognitive 18) src/main/java/com/google/devtools/build/lib/runtime/StarlarkOptionsParser.java:363
- JavaCompileAction.createFullOutputDeps (cognitive 18) src/main/java/com/google/devtools/build/lib/rules/java/JavaCompileAction.java:716
- SkyframeEnvTargetPatternEvaluator.preloadTargetPatterns (cognitive 18) src/main/java/com/google/devtools/build/lib/rules/genquery/GenQuery.java:410
- RemoteExecutionService.buildCommand (cognitive 18) src/main/java/com/google/devtools/build/lib/remote/RemoteExecutionService.java:278
- TextEncoder.field (cognitive 18) src/main/java/com/google/devtools/build/lib/packages/Proto.java:159
- IncludeVisitor.processInternal (cognitive 18) src/main/java/com/google/devtools/build/lib/includescanning/LegacyIncludeScanner.java:696
- StarlarkBaseExternalContext.getUrls (cognitive 18) src/main/java/com/google/devtools/build/lib/bazel/repository/starlark/StarlarkBaseExternalContext.java:463
- AttributeUtils.typeCheckAttrValues (cognitive 18) src/main/java/com/google/devtools/build/lib/bazel/repository/AttributeUtils.java:51
- VendorCommand.exec (cognitive 18) src/main/java/com/google/devtools/build/lib/bazel/commands/VendorCommand.java:133
- VendorCommand.vendorTargets (cognitive 18) src/main/java/com/google/devtools/build/lib/bazel/commands/VendorCommand.java:303
- ModuleFileFunction.maybePatchModuleFile (cognitive 18) src/main/java/com/google/devtools/build/lib/bazel/bzlmod/ModuleFileFunction.java:941
- StarlarkTransition.validate (cognitive 18) src/main/java/com/google/devtools/build/lib/analysis/starlark/StarlarkTransition.java:144
- StarlarkSubrule.call (cognitive 18) src/main/java/com/google/devtools/build/lib/analysis/starlark/StarlarkSubrule.java:141
- CustomCommandLine.arguments (cognitive 18) src/main/java/com/google/devtools/build/lib/analysis/actions/CustomCommandLine.java:1303
- VectorArgFragment.addToFingerprint (cognitive 18) src/main/java/com/google/devtools/build/lib/analysis/actions/CustomCommandLine.java:471
- Project.differentProjectFilesError (cognitive 18) src/main/java/com/google/devtools/build/lib/analysis/Project.java:203
- ResourceManager.areResourcesAvailable (cognitive 18) src/main/java/com/google/devtools/build/lib/actions/ResourceManager.java:673
- InputMetadataProvider.expandArtifacts (cognitive 18) src/main/java/com/google/devtools/build/lib/actions/InputMetadataProvider.java:127
- ExecutionRequirements.parseResources (cognitive 18) src/main/java/com/google/devtools/build/lib/actions/ExecutionRequirements.java:204
- clr_converter._render_option (cognitive 18) scripts/docs/clr_converter.py:537
- relnotes.extract_relnotes (cognitive 18) scripts/release/relnotes.py:36
- FetchServer.parseQualifiers (cognitive 17) src/tools/remote/src/main/java/com/google/devtools/build/remote/worker/FetchServer.java:182
- ExecLogParser.main (cognitive 17) src/tools/execlog/src/main/java/com/google/devtools/build/execlog/ExecLogParser.java:217
- 1Lambda.execClauses (cognitive 17) src/main/java/net/starlark/java/eval/Eval.java:962
- ParallelEvaluator.eval (cognitive 17) src/main/java/com/google/devtools/build/skyframe/ParallelEvaluator.java:644
- ResourceUsage.readPressureStallIndicator (cognitive 17) src/main/java/com/google/devtools/build/lib/util/ResourceUsage.java:166
- RegisteredExecutionPlatformsFunction.compute (cognitive 17) src/main/java/com/google/devtools/build/lib/skyframe/toolchains/RegisteredExecutionPlatformsFunction.java:76
- WaitForNestedNodeBytes.apply (cognitive 17) src/main/java/com/google/devtools/build/lib/skyframe/serialization/analysis/FileDependencyDeserializer.java:596
- PackageCollectingParallelVisitor.getVisitResult (cognitive 17) src/main/java/com/google/devtools/build/lib/skyframe/TraversalInfoRootPackageExtractor.java:143
- SkymeldModule.determineIfMergingAnalysisExecution (cognitive 17) src/main/java/com/google/devtools/build/lib/skyframe/SkymeldModule.java:34
- ProjectFunction.parseLegacyProjectSchema (cognitive 17) src/main/java/com/google/devtools/build/lib/skyframe/ProjectFunction.java:214
- ProjectFilesLookupFunction.compute (cognitive 17) src/main/java/com/google/devtools/build/lib/skyframe/ProjectFilesLookupFunction.java:47
- FileSystemValueCheckerInferringAncestors.processEntries (cognitive 17) src/main/java/com/google/devtools/build/lib/skyframe/FileSystemValueCheckerInferringAncestors.java:183
- BzlLoadFunction.computeInternalWithCompiledBzl (cognitive 17) src/main/java/com/google/devtools/build/lib/skyframe/BzlLoadFunction.java:757
- AspectFunction.getInitialValues (cognitive 17) src/main/java/com/google/devtools/build/lib/skyframe/AspectFunction.java:703
- LinuxSandboxedSpawnRunner.prepareSpawn (cognitive 17) src/main/java/com/google/devtools/build/lib/sandbox/LinuxSandboxedSpawnRunner.java:250
- MobileInstallCommand.doMobileInstall (cognitive 17) src/main/java/com/google/devtools/build/lib/runtime/mobileinstall/MobileInstallCommand.java:200
- TerminalTestResultNotifier.printSummary (cognitive 17) src/main/java/com/google/devtools/build/lib/runtime/TerminalTestResultNotifier.java:112
- CommandLinePathFactory.create (cognitive 17) src/main/java/com/google/devtools/build/lib/runtime/CommandLinePathFactory.java:83
- Builder.build (cognitive 17) src/main/java/com/google/devtools/build/lib/runtime/BlazeRuntime.java:1764
- JavaCompilationHelper.createCompileAction (cognitive 17) src/main/java/com/google/devtools/build/lib/rules/java/JavaCompilationHelper.java:140
- StarlarkStructureAdapter.getFieldValue (cognitive 17) src/main/java/com/google/devtools/build/lib/rules/cpp/CcToolchainVariables.java:858
- ConfigGlobalLibrary.validateBuildSettingKeys (cognitive 17) src/main/java/com/google/devtools/build/lib/rules/config/ConfigGlobalLibrary.java:142
- BulkTransfers.mergeBulkTransfer (cognitive 17) src/main/java/com/google/devtools/build/lib/remote/util/BulkTransfers.java:73
- BulkTransfers.waitForBulkTransfer (cognitive 17) src/main/java/com/google/devtools/build/lib/remote/util/BulkTransfers.java:36
- FastCdcChunker.chunkToDigests (cognitive 17) src/main/java/com/google/devtools/build/lib/remote/chunking/FastCdcChunker.java:192
- RemoteModule.executorInit (cognitive 17) src/main/java/com/google/devtools/build/lib/remote/RemoteModule.java:1236
- RemoteExecutionService.initUseOutputPaths (cognitive 17) src/main/java/com/google/devtools/build/lib/remote/RemoteExecutionService.java:461
- ConditionalEdges.getAllConditions (cognitive 17) src/main/java/com/google/devtools/build/lib/query2/query/output/ConditionalEdges.java:117
- StarlarkNativeModule.starlarkifyValue (cognitive 17) src/main/java/com/google/devtools/build/lib/packages/StarlarkNativeModule.java:716
- PackageSpecification.fromStringPositive (cognitive 17) src/main/java/com/google/devtools/build/lib/packages/PackageSpecification.java:160
- ConfiguredAttributeMapper.resolveSelector (cognitive 17) src/main/java/com/google/devtools/build/lib/packages/ConfiguredAttributeMapper.java:279
- AspectsList.validateTopLevelAspectsParameters (cognitive 17) src/main/java/com/google/devtools/build/lib/packages/AspectsList.java:125
- IncludeParser.extractInclusions (cognitive 17) src/main/java/com/google/devtools/build/lib/includescanning/IncludeParser.java:814
- DefaultNestedSetBuilder.addTransitiveImpl (cognitive 17) src/main/java/com/google/devtools/build/lib/collect/nestedset/NestedSetBuilder.java:480
- SymlinkForest.plantSymlinkForest (cognitive 17) src/main/java/com/google/devtools/build/lib/buildtool/SymlinkForest.java:275
- OutputDirectoryLinksUtils.createOutputDirectoryLinks (cognitive 17) src/main/java/com/google/devtools/build/lib/buildtool/OutputDirectoryLinksUtils.java:75
- UrlRewriter.updateAuthHeaders (cognitive 17) src/main/java/com/google/devtools/build/lib/bazel/repository/downloader/UrlRewriter.java:191
- Factory.create (cognitive 17) src/main/java/com/google/devtools/build/lib/bazel/repository/downloader/HttpStream.java:71
- StarlarkRuleConfiguredTargetUtil.parseDefaultProviderFields (cognitive 17) src/main/java/com/google/devtools/build/lib/analysis/starlark/StarlarkRuleConfiguredTargetUtil.java:364
- BuildConfigurationKeyProducer.resetFlags (cognitive 17) src/main/java/com/google/devtools/build/lib/analysis/producers/BuildConfigurationKeyProducer.java:329
- SuccessfulArtifactFilter.filterArtifactNestedSetToBuiltArtifacts (cognitive 17) src/main/java/com/google/devtools/build/lib/analysis/TopLevelArtifactHelper.java:357
- Runfiles.filterListForObscuringSymlinks (cognitive 17) src/main/java/com/google/devtools/build/lib/analysis/Runfiles.java:266
- AnnotParamDoc.getType (cognitive 17) src/main/java/com/google/devtools/build/docgen/starlark/AnnotParamDoc.java:41
- DocCheckerUtils.getFirstUnclosedTag (cognitive 17) src/main/java/com/google/devtools/build/docgen/DocCheckerUtils.java:58
- aquery_differ._aquery_diff (cognitive 17) scripts/aquery_differ/aquery_differ.py:215
- ExecutionServer.getCommand (cognitive 16) src/tools/remote/src/main/java/com/google/devtools/build/remote/worker/ExecutionServer.java:570
- CallableType.toSignatureString (cognitive 16) src/main/java/net/starlark/java/syntax/Types.java:713
- TypeTagger.resolveTypeConstructor (cognitive 16) src/main/java/net/starlark/java/syntax/TypeTagger.java:141
- Printer.appendTripleQuoted (cognitive 16) src/main/java/net/starlark/java/eval/Printer.java:319
- EvalException.formatCallStack (cognitive 16) src/main/java/net/starlark/java/eval/EvalException.java:201
- ArgumentProcessor.addNamedArg (cognitive 16) src/main/java/net/starlark/java/eval/BuiltinFunction.java:333
- OptionsParser.describeOptionsWithDeprecatedCategories (cognitive 16) src/main/java/com/google/devtools/common/options/OptionsParser.java:495
- FilterValueOperation.checkUserValue (cognitive 16) src/main/java/com/google/devtools/common/options/InvocationPolicyEnforcer.java:864
- DirtyingNodeVisitor.visit (cognitive 16) src/main/java/com/google/devtools/build/skyframe/InvalidatingNodeVisitor.java:456
- UnixOsPathPolicy.needsToNormalize (cognitive 16) src/main/java/com/google/devtools/build/lib/vfs/UnixOsPathPolicy.java:26
- ThreadDumpAnalyzer.analyze (cognitive 16) src/main/java/com/google/devtools/build/lib/util/ThreadDumpAnalyzer.java:60
- SimpleLogHandler.openOutputIfNeeded (cognitive 16) src/main/java/com/google/devtools/build/lib/util/SimpleLogHandler.java:827
- RemoteAnalysisCacheFactory.create (cognitive 16) src/main/java/com/google/devtools/build/lib/skyframe/serialization/analysis/RemoteAnalysisCacheFactory.java:80
- ActionRewindStrategy.calculateLostInputOwners (cognitive 16) src/main/java/com/google/devtools/build/lib/skyframe/rewinding/ActionRewindStrategy.java:671
- PlatformMappingFunction.compute (cognitive 16) src/main/java/com/google/devtools/build/lib/skyframe/config/PlatformMappingFunction.java:70
- TestExpansionFunction.getPrerequisites (cognitive 16) src/main/java/com/google/devtools/build/lib/skyframe/TestExpansionFunction.java:147
- StarlarkBuildSettingsDetailsFunction.getBuildSettingPackages (cognitive 16) src/main/java/com/google/devtools/build/lib/skyframe/StarlarkBuildSettingsDetailsFunction.java:245
- SequencedSkyframeExecutor.decideKeepIncrementalState (cognitive 16) src/main/java/com/google/devtools/build/lib/skyframe/SequencedSkyframeExecutor.java:439
- RecursiveFilesystemTraversalFunction.checkIfPackage (cognitive 16) src/main/java/com/google/devtools/build/lib/skyframe/RecursiveFilesystemTraversalFunction.java:551
- RecursiveFilesystemTraversalFunction.traverseSourceChildren (cognitive 16) src/main/java/com/google/devtools/build/lib/skyframe/RecursiveFilesystemTraversalFunction.java:722
- ProjectFunction.parseConfigs (cognitive 16) src/main/java/com/google/devtools/build/lib/skyframe/ProjectFunction.java:274
- ProcessPackageDirectory.getPackageExistenceAndSubdirDeps (cognitive 16) src/main/java/com/google/devtools/build/lib/skyframe/ProcessPackageDirectory.java:78
- BzlLoadCycleReporter.maybeReportCycle (cognitive 16) src/main/java/com/google/devtools/build/lib/skyframe/BzlLoadCycleReporter.java:65
- RunCommand.validateTargets (cognitive 16) src/main/java/com/google/devtools/build/lib/runtime/commands/RunCommand.java:1066
- UiStateTracker.writeExecutionProgress (cognitive 16) src/main/java/com/google/devtools/build/lib/runtime/UiStateTracker.java:1315
- LocationPrinter.getRelativeLocationString (cognitive 16) src/main/java/com/google/devtools/build/lib/runtime/LocationPrinter.java:49
- BlazeRuntime.afterCommand (cognitive 16) src/main/java/com/google/devtools/build/lib/runtime/BlazeRuntime.java:806
- AggregatingTestListener.differentialAnalyzeAndReport (cognitive 16) src/main/java/com/google/devtools/build/lib/runtime/AggregatingTestListener.java:251
- JavaCompileAction.execute (cognitive 16) src/main/java/com/google/devtools/build/lib/rules/java/JavaCompileAction.java:356
- FilterShowIncludesOutputStream.write (cognitive 16) src/main/java/com/google/devtools/build/lib/rules/cpp/ShowIncludesFilter.java:115
- GrpcRemoteDownloader.newFetchBlobRequest (cognitive 16) src/main/java/com/google/devtools/build/lib/remote/downloader/GrpcRemoteDownloader.java:247
- ProtoOutputFormatter.getFlattenedAttributeValues (cognitive 16) src/main/java/com/google/devtools/build/lib/query2/query/output/ProtoOutputFormatter.java:505
- StarlarkOutputFormatterCallback.<init> (cognitive 16) src/main/java/com/google/devtools/build/lib/query2/cquery/StarlarkOutputFormatterCallback.java:129
- ConfiguredTargetQueryEnvironment.getConfiguredTargetsForLabel (cognitive 16) src/main/java/com/google/devtools/build/lib/query2/cquery/ConfiguredTargetQueryEnvironment.java:343
- AbstractBlazeQueryEnvironment.transitiveLoadFiles (cognitive 16) src/main/java/com/google/devtools/build/lib/query2/common/AbstractBlazeQueryEnvironment.java:510
- ActionGraphQueryEnvironment.getConfiguredTargetsForLabel (cognitive 16) src/main/java/com/google/devtools/build/lib/query2/aquery/ActionGraphQueryEnvironment.java:463
- MemoryProfiler.prepareBeanAndGetLocalMinUsage (cognitive 16) src/main/java/com/google/devtools/build/lib/profiler/MemoryProfiler.java:148
- PathPackageLocator.getPackageBuildFileNullable (cognitive 16) src/main/java/com/google/devtools/build/lib/pkgcache/PathPackageLocator.java:83
- PostGCMemoryUseRecorder.handleNotification (cognitive 16) src/main/java/com/google/devtools/build/lib/metrics/PostGCMemoryUseRecorder.java:229
- IncludeScannerHelper.createInclusionWithContext (cognitive 16) src/main/java/com/google/devtools/build/lib/includescanning/IncludeScannerHelper.java:66
- Digraph.isSubgraph (cognitive 16) src/main/java/com/google/devtools/build/lib/graph/Digraph.java:164
- RunfilesTreeUpdater.updateRunfiles (cognitive 16) src/main/java/com/google/devtools/build/lib/exec/RunfilesTreeUpdater.java:67
- BuildEventServiceModule.createBepTransports (cognitive 16) src/main/java/com/google/devtools/build/lib/buildeventservice/BuildEventServiceModule.java:866
- LocalRepoContentsCache.runGc (cognitive 16) src/main/java/com/google/devtools/build/lib/bazel/repository/cache/LocalRepoContentsCache.java:240
- BazelModuleInspectorFunction.computeAugmentedGraph (cognitive 16) src/main/java/com/google/devtools/build/lib/bazel/bzlmod/BazelModuleInspectorFunction.java:92
- BazelLockFileModule.afterCommand (cognitive 16) src/main/java/com/google/devtools/build/lib/bazel/bzlmod/BazelLockFileModule.java:62
- TestRunnerAction.executeAllAttempts (cognitive 16) src/main/java/com/google/devtools/build/lib/analysis/test/TestRunnerAction.java:1236
- Builder.validateDirectPrerequisiteFileTypes (cognitive 16) src/main/java/com/google/devtools/build/lib/analysis/RuleContext.java:1996
- DependencyResolutionHelpers.resolveAttributes (cognitive 16) src/main/java/com/google/devtools/build/lib/analysis/DependencyResolutionHelpers.java:427
- CommonPrerequisiteValidator.maybeAddMoreDelegationNeededBullet (cognitive 16) src/main/java/com/google/devtools/build/lib/analysis/CommonPrerequisiteValidator.java:629
- CommandHelper.<init> (cognitive 16) src/main/java/com/google/devtools/build/lib/analysis/CommandHelper.java:127
- BuildView.collectTests (cognitive 16) src/main/java/com/google/devtools/build/lib/analysis/BuildView.java:898
- ActionInputMap.getInputMetadataChecked (cognitive 16) src/main/java/com/google/devtools/build/lib/actions/ActionInputMap.java:209
- StarlarkDoc.getTypeAnchor (cognitive 16) src/main/java/com/google/devtools/build/docgen/starlark/StarlarkDoc.java:84
- mirror_external_deps.extract_lockfile_source_urls (cognitive 16) tools/mirror_external_deps.py:142
- mirror_external_deps.main (cognitive 16) tools/mirror_external_deps.py:377
- Change-coupling hub: BuildTool.java → Project.java, ProjectValue.java, FlagSetValue.java, RemoteAnalysisCacheDeps.java, RemoteAnalysisCachingEventListener.java, RemoteAnalysisCachingOptions.java src/main/java/com/google/devtools/build/lib/buildtool/BuildTool.java
- REDACTED
- REDACTED
- Members sharing a duplicated core (5 members, 50+ identical tokens) src/main/java/com/google/devtools/build/lib/rules/cpp/CppCompileAction.java:672
- Duplicated block (37 lines × 2) src/main/java/com/google/devtools/build/lib/buildtool/AnalysisAndExecutionPhaseRunner.java:234
- Duplicated block (31 lines × 2) src/main/java/com/google/devtools/build/lib/bazel/repository/downloader/ProxyHelper.java:141
- Duplicated block (29 lines × 2) src/main/java/com/google/devtools/build/lib/analysis/starlark/StarlarkAttrModule.java:988
- Duplicated block (28 lines × 2) src/main/java/com/google/devtools/build/lib/remote/util/RxFutures.java:88
- Duplicated block (25 lines × 2) src/main/java/com/google/devtools/build/lib/query2/aquery/ActionGraphQueryEnvironment.java:421
- Duplicated block (23–25 lines × 2) src/main/java/com/google/devtools/common/options/IsolatedOptionsData.java:320
- Duplicated block (22–24 lines × 2) src/main/java/com/google/devtools/build/lib/runtime/commands/AqueryCommand.java:92
- Duplicated block (23 lines × 2) src/main/java/com/google/devtools/build/lib/collect/compacthashmap/CompactHashMap.java:456
- Duplicated block (15–23 lines × 2) src/main/java/com/google/devtools/build/lib/rules/platform/ConstraintSettingRule.java:42
- Duplicated block (21–22 lines × 2) src/main/java/com/google/devtools/build/lib/remote/http/HttpCacheClient.java:337
- Duplicated block (20–22 lines × 2) src/main/java/com/google/devtools/build/lib/skyframe/toolchains/RegisteredExecutionPlatformsCycleReporter.java:86
- Duplicated block (18–20 lines × 2) src/main/java/com/google/devtools/build/lib/profiler/TraceProfilerServiceImpl.java:477
- Duplicated block (17–20 lines × 2) src/main/java/com/google/devtools/build/lib/skyframe/SkyframeExecutor.java:1467
- Duplicated block (19–20 lines × 2) src/main/java/com/google/devtools/build/lib/util/HashCodes.java:143
- Duplicated block (15–19 lines × 2) src/main/java/com/google/devtools/build/lib/profiler/TraceProfilerServiceImpl.java:498
- Duplicated block (18–19 lines × 2) src/main/java/com/google/devtools/build/lib/skyframe/config/PlatformMappingFunction.java:238
- Duplicated block (16–18 lines × 3) src/main/java/com/google/devtools/build/lib/util/HashCodes.java:114
- Duplicated block (12–18 lines × 2) src/main/java/com/google/devtools/build/lib/query2/aquery/ActionGraphQueryEnvironment.java:466
- Duplicated block (16–17 lines × 2) src/main/java/com/google/devtools/build/lib/remote/http/HttpCacheClient.java:373
- Duplicated block (14–16 lines × 2) src/main/java/com/google/devtools/build/lib/skyframe/BzlCompileFunction.java:525
- Duplicated block (9–15 lines × 4) src/main/java/com/google/devtools/build/lib/rules/cpp/CcToolchainFeaturesLib.java:159
- Duplicated block (12–15 lines × 4) src/main/java/com/google/devtools/build/lib/util/HashCodes.java:91
- Duplicated block (11–14 lines × 3) src/main/java/com/google/devtools/build/lib/bazel/repository/decompressor/ArFunction.java:57
- Duplicated block (14 lines × 3) src/main/java/com/google/devtools/build/lib/bazel/repository/decompressor/PatchUtil.java:590
- Duplicated block (10–14 lines × 2) src/main/java/com/google/devtools/build/lib/remote/http/HttpCacheClient.java:582
- Duplicated block (13–14 lines × 2) src/main/java/net/starlark/java/eval/Starlark.java:927
- Duplicated block (10–13 lines × 2) src/main/java/com/google/devtools/build/lib/vfs/inmemoryfs/InMemoryFileSystem.java:517
- Duplicated block (10–11 lines × 4) src/main/java/com/google/devtools/build/lib/analysis/starlark/StarlarkRuleClassFunctions.java:824
- Duplicated block (10–11 lines × 2) src/main/java/com/google/devtools/build/lib/authandtls/credentialhelper/GetCredentialsRequest.java:79
- Duplicated block (8–9 lines × 4) src/main/java/com/google/devtools/build/lib/runtime/commands/AqueryCommand.java:147
- Duplicated block (6–7 lines × 2) src/main/java/com/google/devtools/build/lib/runtime/CommandLineEvent.java:333
- Duplicated block (4–5 lines × 3) src/main/java/com/google/devtools/build/lib/runtime/UiStateTracker.java:570
- Duplicated block (82 lines × 2) src/main/java/com/google/devtools/build/lib/io/FileSymlinkCycleUniquenessFunction.java:1
- Duplicated block (54 lines × 3) src/main/java/com/google/devtools/build/lib/starlarkbuildapi/java/JavaCommonApi.java:65
- Duplicated block (54 lines × 2) src/main/java/com/google/devtools/build/lib/starlarkbuildapi/java/JavaCommonApi.java:65
- Duplicated block (6 lines × 5) src/main/java/com/google/devtools/build/lib/analysis/RequiredConfigFragmentsProvider.java:52
- Duplicated block (8 lines × 4) src/main/java/com/google/devtools/build/lib/analysis/platform/DeclaredToolchainInfo.java:55
- Duplicated block (6 lines × 6) src/main/java/com/google/devtools/build/lib/collect/compacthashset/CompactHashSetCodec.java:35
- Unstable project //src/main/cpp:rc_file
- SAST runs, but gates no merge
- No deployment automation
- Swallowed exception (caught, then discarded) src/main/java/com/google/devtools/build/lib/collect/nestedset/NestedSet.java:500
Minor — 326 finding(s)
- Orphaned file src/main/java/com/google/devtools/build/lib/skyframe/PackageFunctionWithMultipleGlobDeps.java:1
- Orphaned file src/main/java/com/google/devtools/build/lib/bazel/bzlmod/modcommand/ModuleArg.java:1
- Orphaned file src/main/java/com/google/devtools/build/lib/skyframe/RecursivePackageProviderBackedTargetPatternResolver.java:1
- Orphaned file src/main/java/com/google/devtools/build/lib/query2/RBuildFilesVisitor.java:1
- Orphaned file src/main/java/com/google/devtools/build/lib/skyframe/PrepareDepsOfPatternFunction.java:1
- Orphaned file src/main/java/com/google/devtools/build/lib/packages/GlobCache.java:1
- Orphaned file src/main/java/com/google/devtools/build/lib/packages/AspectsList.java:1
- Orphaned file src/main/java/com/google/devtools/build/lib/packages/RequiredProviders.java:1
- Orphaned file src/main/java/com/google/devtools/build/lib/exec/local/XcodeLocalEnvProvider.java:1
- Orphaned file src/main/java/com/google/devtools/build/lib/analysis/PrerequisitesCollection.java:1
- Orphaned file src/main/java/com/google/devtools/build/lib/skyframe/EnvironmentBackedRecursivePackageProvider.java:1
- Orphaned file src/main/java/com/google/devtools/build/lib/sandbox/LinuxSandboxCommandLineBuilder.java:1
- Orphaned file src/main/java/com/google/devtools/build/lib/rules/config/ConfigFeatureFlag.java:1
- Orphaned file src/main/java/com/google/devtools/build/lib/actions/ActionResult.java:1
- Orphaned file src/main/java/com/google/devtools/build/lib/analysis/starlark/StarlarkLateBoundDefault.java:1
- Orphaned file src/main/java/com/google/devtools/build/lib/skyframe/RecursiveDirectoryTraversalFunction.java:1
- Orphaned file src/main/java/com/google/devtools/build/lib/skyframe/GlobsFunction.java:1
- Orphaned file src/main/java/com/google/devtools/build/lib/packages/AspectPropagationEdgesSupplier.java:1
- Orphaned file src/main/java/com/google/devtools/build/lib/shell/Consumers.java:1
- Orphaned file src/main/java/com/google/devtools/build/lib/rules/cpp/Link.java:1
- Orphaned file src/main/java/com/google/devtools/build/lib/analysis/actions/BuildInfoFileWriteAction.java:1
- Orphaned file src/main/java/com/google/devtools/build/lib/packages/producers/PatternWithWildcardProducer.java:1
- Orphaned file src/main/java/com/google/devtools/build/lib/dynamic/LocalBranch.java:1
- Orphaned file src/main/java/com/google/devtools/build/lib/rules/java/JavaOutput.java:1
- Orphaned file src/main/java/com/google/devtools/build/lib/util/ShellEscaper.java:1
- README/code drift docs/help.mdx:45
- README/code drift docs/help.mdx:49
- README/code drift docs/about/faq.mdx:7
- README/code drift docs/about/faq.mdx:17
- README/code drift docs/about/faq.mdx:45
- README/code drift docs/about/faq.mdx:45
- README/code drift docs/about/faq.mdx:111
- README/code drift docs/about/faq.mdx:142
- README/code drift docs/about/faq.mdx:158
- README/code drift docs/about/faq.mdx:164
- README/code drift docs/about/faq.mdx:168
- README/code drift docs/about/intro.mdx:37
- README/code drift docs/about/intro.mdx:45
- README/code drift docs/about/intro.mdx:47
- README/code drift docs/about/intro.mdx:67
- README/code drift docs/about/intro.mdx:71
- README/code drift docs/about/intro.mdx:71
- README/code drift docs/about/intro.mdx:81
- README/code drift docs/about/intro.mdx:82
- README/code drift docs/about/intro.mdx:91
- README/code drift docs/about/intro.mdx:105
- README/code drift docs/about/intro.mdx:108
- README/code drift docs/about/intro.mdx:109
- README/code drift docs/about/intro.mdx:110
- README/code drift docs/about/intro.mdx:111
- Disabled test src/java_tools/import_deps_checker/javatests/com/google/devtools/build/importdeps/MainTest.java:33
- Disabled test src/java_tools/junitrunner/javatests/com/google/testing/junit/runner/internal/junit4/JUnit4TestXmlListenerTest.java:268
- Disabled test src/java_tools/junitrunner/javatests/com/google/testing/junit/runner/junit4/JUnit4TestModelBuilderTest.java:172
- Disabled test src/test/java/com/google/devtools/build/lib/analysis/BuildViewTest.java:553
- Disabled test src/test/java/com/google/devtools/build/lib/analysis/producers/BuildConfigurationKeyMapProducerTest.java:246
- Disabled test src/test/java/com/google/devtools/build/lib/analysis/producers/BuildConfigurationKeyProducerTest.java:397
- Disabled test src/test/java/com/google/devtools/build/lib/bazel/bzlmod/DiscoveryTest.java:676
- Disabled test src/test/java/com/google/devtools/build/lib/bazel/bzlmod/DiscoveryTest.java:725
- Disabled test src/test/java/com/google/devtools/build/lib/bazel/bzlmod/ModuleFileFunctionTest.java:794
- Disabled test src/test/java/com/google/devtools/build/lib/bazel/bzlmod/ModuleFileFunctionTest.java:1003
- Disabled test src/test/java/com/google/devtools/build/lib/bazel/bzlmod/ModuleFileFunctionTest.java:1853
- Disabled test src/test/java/com/google/devtools/build/lib/bazel/repository/downloader/HttpConnectorTest.java:303
- Disabled test src/test/java/com/google/devtools/build/lib/bazel/repository/downloader/HttpDownloaderTest.java:411
- Disabled test src/test/java/com/google/devtools/build/lib/bazel/repository/downloader/HttpDownloaderTest.java:480
- Disabled test src/test/java/com/google/devtools/build/lib/buildeventservice/BazelBuildEventServiceModuleTest.java:629
- Disabled test src/test/java/com/google/devtools/build/lib/buildeventservice/BazelBuildEventServiceModuleTest.java:655
- Disabled test src/test/java/com/google/devtools/build/lib/rules/cpp/CcCommonTest.java:362
- Disabled test src/test/java/com/google/devtools/build/lib/rules/cpp/CcCommonTest.java:378
- Disabled test src/test/java/com/google/devtools/build/lib/rules/cpp/CcCommonTest.java:622
- Disabled test src/test/java/com/google/devtools/build/lib/rules/java/proto/StarlarkJavaLiteProtoLibraryTest.java:114
- Disabled test src/test/java/com/google/devtools/build/lib/rules/java/proto/StarlarkJavaLiteProtoLibraryTest.java:325
- Disabled test src/test/java/com/google/devtools/build/lib/rules/java/proto/StarlarkJavaLiteProtoLibraryTest.java:539
- Disabled test src/test/java/com/google/devtools/build/lib/rules/java/proto/StarlarkJavaLiteProtoLibraryTest.java:589
- Disabled test src/test/java/com/google/devtools/build/lib/runtime/BuildEventStreamerTest.java:566
- Disabled test src/test/java/com/google/devtools/build/lib/runtime/SynchronizedOutputStreamTest.java:106
- Duplicated predicate src/main/java/com/google/devtools/build/lib/analysis/TargetCompleteEvent.java:245
- Duplicated predicate src/main/java/com/google/devtools/build/lib/analysis/BuildView.java:562
- Duplicated predicate src/main/java/com/google/devtools/build/lib/remote/RemoteSpawnCache.java:87
- Duplicated predicate src/main/java/com/google/devtools/build/lib/runtime/GcChurningDetector.java:94
- Duplicated predicate src/main/java/com/google/devtools/build/lib/shell/Command.java:199
- Duplicated predicate src/main/java/com/google/devtools/build/lib/skyframe/IgnoredSubdirectoriesFunction.java:208
- Duplicated predicate src/main/java/com/google/devtools/build/lib/exec/CompactSpawnLogContext.java:265
- Duplicated predicate src/main/java/com/google/devtools/build/lib/actions/cache/ActionCache.java:423
- Duplicated predicate src/main/java/com/google/devtools/build/skyframe/ParallelEvaluator.java:469
- Duplicated predicate src/main/java/com/google/devtools/build/lib/analysis/starlark/StarlarkAttributeTransitionProvider.java:185
- Duplicated predicate src/main/java/com/google/devtools/build/lib/skyframe/toolchains/RegisteredExecutionPlatformsValue.java:97
- Duplicated predicate src/main/java/com/google/devtools/build/lib/query2/query/BlazeQueryEnvironment.java:412
- Duplicated predicate src/main/java/com/google/devtools/build/lib/actions/ActionExecutedEvent.java:215
- Duplicated predicate src/main/java/com/google/devtools/build/lib/remote/RemoteExecutionService.java:595
- Duplicated predicate src/main/java/com/google/devtools/build/lib/runtime/AggregatingTestListener.java:182
- Duplicated predicate src/main/java/com/google/devtools/build/lib/rules/genquery/GenQueryPackageProviderFactory.java:402
- Duplicated predicate src/java_tools/buildjar/java/com/google/devtools/build/buildjar/BazelJavaBuilder.java:48
- Duplicated predicate src/main/java/com/google/devtools/build/lib/analysis/starlark/StarlarkAttrModule.java:243
- Duplicated predicate src/main/java/com/google/devtools/build/lib/vfs/FileSystemUtils.java:63
- Duplicated predicate src/main/java/com/google/devtools/build/lib/runtime/BlazeRuntime.java:399
- Duplicated predicate src/main/java/net/starlark/java/syntax/TypeTable.java:133
- Duplicated predicate src/main/java/com/google/devtools/build/lib/remote/RemoteModule.java:687
- Duplicated predicate src/main/java/com/google/devtools/build/lib/dynamic/DynamicExecutionModule.java:80
- Duplicated predicate src/main/java/com/google/devtools/build/lib/rules/java/JavaCompileAction.java:361
- Duplicated predicate src/java_tools/singlejar/java/com/google/devtools/build/zip/CentralDirectoryFileHeader.java:77
- Fat interface: VerificationTypeVisitor (27 abstract methods) third_party/java/proguard/proguard6.2.2/src/proguard/classfile/attribute/preverification/visitor/VerificationTypeVisitor.java:34
- Fat interface: AttributeVisitor (46 abstract methods) third_party/java/proguard/proguard6.2.2/src/proguard/classfile/attribute/visitor/AttributeVisitor.java:35
- Fat interface: ConstantVisitor (18 abstract methods) third_party/java/proguard/proguard6.2.2/src/proguard/classfile/constant/visitor/ConstantVisitor.java:33
- Fat interface: Clazz (38 abstract methods) third_party/java/proguard/proguard6.2.2/src/proguard/classfile/Clazz.java:33
- Fat interface: NodeEntry (38 abstract methods) src/main/java/com/google/devtools/build/skyframe/NodeEntry.java:34
- Fat interface: MemoizingEvaluator (19 abstract methods) src/main/java/com/google/devtools/build/skyframe/MemoizingEvaluator.java:37
- Fat interface: JavaInfoApi<FileT, JavaOutputT, JavaPluginDataT> (17 abstract methods) src/main/java/com/google/devtools/build/lib/starlarkbuildapi/java/JavaInfoApi.java:34
- Fat interface: JavaConfigurationApi (21 abstract methods) src/main/java/com/google/devtools/build/lib/starlarkbuildapi/java/JavaConfigurationApi.java:32
- Fat interface: CppConfigurationApi<InvalidConfigurationExceptionT> (24 abstract methods) src/main/java/com/google/devtools/build/lib/starlarkbuildapi/cpp/CppConfigurationApi.java:33
- Fat interface: CcCompilationContextApi<FileT> (25 abstract methods) src/main/java/com/google/devtools/build/lib/starlarkbuildapi/cpp/CcCompilationContextApi.java:35
- Fat interface: AndroidConfigurationApi (20 abstract methods) src/main/java/com/google/devtools/build/lib/starlarkbuildapi/android/AndroidConfigurationApi.java:32
- Fat interface: StarlarkRuleContextApi<ConstraintValueT> (36 abstract methods) src/main/java/com/google/devtools/build/lib/starlarkbuildapi/StarlarkRuleContextApi.java:58
- Fat interface: StarlarkAttrModuleApi (17 abstract methods) src/main/java/com/google/devtools/build/lib/starlarkbuildapi/StarlarkAttrModuleApi.java:57
- Fat interface: QueryEnvironment<T> (30 abstract methods) src/main/java/com/google/devtools/build/lib/query2/engine/QueryEnvironment.java:47
- Fat interface: TraceProfilerService (28 abstract methods) src/main/java/com/google/devtools/build/lib/profiler/TraceProfilerService.java:51
- Fat interface: SpawnExecutionContext (16 abstract methods) src/main/java/com/google/devtools/build/lib/exec/SpawnRunner.java:141
- Fat interface: ActionConstructionContext (22 abstract methods) src/main/java/com/google/devtools/build/lib/analysis/actions/ActionConstructionContext.java:37
- Fat interface: AnalysisEnvironment (20 abstract methods) src/main/java/com/google/devtools/build/lib/analysis/AnalysisEnvironment.java:40
- Fat interface: SpawnResult (18 abstract methods) src/main/java/com/google/devtools/build/lib/actions/SpawnResult.java:38
- Fat interface: ActionAnalysisMetadata (19 abstract methods) src/main/java/com/google/devtools/build/lib/actions/ActionAnalysisMetadata.java:27
- Off-boarding risk: anonymized user #1
- Off-boarding risk: anonymized user #2
- Off-boarding risk: anonymized user #3
- Off-boarding risk: anonymized user #4
- Off-boarding risk: anonymized user #5
- Off-boarding risk: anonymized user #6
- Off-boarding risk: anonymized user #7
- Off-boarding risk: anonymized user #8
- Off-boarding risk: anonymized user #9
- Off-boarding risk: anonymized user #10
- Off-boarding risk: anonymized user #11
- Off-boarding risk: anonymized user #12
- Off-boarding risk: anonymized user #13
- Empty method body src/java_tools/junitrunner/javatests/com/google/testing/junit/runner/testbed/JUnit4TestbridgeExercises.java:29
- Empty method body src/java_tools/junitrunner/javatests/com/google/testing/junit/runner/testbed/JUnit4TestbridgeOomExercises.java:27
- Empty method body src/main/java/com/google/devtools/build/lib/vfs/bazel/BazelHashFunctions.java:44
- Silent fallback default on parse failure src/main/java/com/google/devtools/build/lib/starlarkdebug/server/DebuggerSerialization.java:148
- Silent fallback default on parse failure src/main/java/com/google/devtools/build/lib/bazel/repository/downloader/HttpConnectorMultiplexer.java:172
- Further sole-owners (lower concentration)
- Documentation: no project overview docs/command-line-reference-suffix.html
- Projects may be oversized for their cohesion
- REDACTED
- Further orphaned files (smaller)
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- Logging is not universal
- Benchmarks don't track allocations src/test/java/com/google/devtools/build/lib/remote/ChunkedTransferBenchmark.java
- Java packages are not null-marked everywhere
- Hand-rolled JSON/XML parsing via regex src/main/java/com/google/devtools/build/lib/bazel/bzlmod/BazelLockFileFunction.java:54
Minor — 90 finding(s)
- Skipped (documented): createKey_platformFlags_accumulate src/test/java/com/google/devtools/build/lib/analysis/producers/BuildConfigurationKeyMapProducerTest.java:247
- Skipped (documented): createKey_platformFlags_accumulate src/test/java/com/google/devtools/build/lib/analysis/producers/BuildConfigurationKeyProducerTest.java:398
- Skipped (documented): testOutputFilterSeeWarning src/test/java/com/google/devtools/build/lib/analysis/BuildViewTest.java:554
- Skipped (documented): testNewChannel_unixSocketProxy_authorityIsTargetUrl src/test/java/com/google/devtools/build/lib/authandtls/GoogleAuthUtilsTest.java:359
- Skipped (documented): testNewChannel_unixSocket_authorityIsLocalhost src/test/java/com/google/devtools/build/lib/authandtls/GoogleAuthUtilsTest.java:344
- Skipped (documented): testBuiltinModules_forRoot src/test/java/com/google/devtools/build/lib/bazel/bzlmod/DiscoveryTest.java:729
- Skipped (documented): testLocalPathOverride src/test/java/com/google/devtools/build/lib/bazel/bzlmod/DiscoveryTest.java:680
- Skipped (documented): getLocalRegistryPath_unixAbsolutePath src/test/java/com/google/devtools/build/lib/bazel/bzlmod/IndexRegistryTest.java:1156
- Skipped (documented): getLocalRegistryPath_windowsDriveInPath src/test/java/com/google/devtools/build/lib/bazel/bzlmod/IndexRegistryTest.java:1163
- Skipped (documented): getLocalRegistryPath_windowsRejectsDriveLetterAsHost src/test/java/com/google/devtools/build/lib/bazel/bzlmod/IndexRegistryTest.java:1170
- Skipped (documented): testBuiltinModules_forBuiltinModules src/test/java/com/google/devtools/build/lib/bazel/bzlmod/ModuleFileFunctionTest.java:1857
- Skipped (documented): testCommandLineModuleOverrides src/test/java/com/google/devtools/build/lib/bazel/bzlmod/ModuleFileFunctionTest.java:1007
- Skipped (documented): testLocalPathOverride src/test/java/com/google/devtools/build/lib/bazel/bzlmod/ModuleFileFunctionTest.java:798
- Skipped (documented): getWatchedRegistryPath_absoluteFileUrl src/test/java/com/google/devtools/build/lib/bazel/bzlmod/RegistryFunctionTest.java:34
- Skipped (documented): httpBzlDocumentation src/test/java/com/google/devtools/build/lib/bazel/repository/decompressor/DecompressorValueTest.java:104
- Skipped (documented): setLastModifiedTime src/test/java/com/google/devtools/build/lib/bazel/repository/decompressor/GzFunctionTest.java:133
- Skipped (documented): downloadFrom2UrlsBothSocketTimeoutDuringBodyRead src/test/java/com/google/devtools/build/lib/bazel/repository/downloader/HttpDownloaderTest.java:482
- Skipped (documented): downloadFrom2UrlsFirstSocketTimeoutOnBodyReadSecondOk src/test/java/com/google/devtools/build/lib/bazel/repository/downloader/HttpDownloaderTest.java:413
- Skipped (documented): testReplaceWithSymlinkContents src/test/java/com/google/devtools/build/lib/blackbox/framework/PathUtilsTest.java:179
- Skipped (documented): testBeforeSecondCommand_fullyAsync_besTimeout_slowHalfCloseWarning src/test/java/com/google/devtools/build/lib/buildeventservice/BazelBuildEventServiceModuleTest.java:657
- Skipped (documented): testBeforeSecondCommand_fullyAsync_slowHalfCloseWarning src/test/java/com/google/devtools/build/lib/buildeventservice/BazelBuildEventServiceModuleTest.java:631
- Skipped (documented): hasExecutionStatistics src/test/java/com/google/devtools/build/lib/exec/local/LocalSpawnRunnerTest.java:846
- Skipped (documented): interruptWaitsForProcessExit src/test/java/com/google/devtools/build/lib/exec/local/LocalSpawnRunnerTest.java:607
- Skipped (documented): noProcessWrapper src/test/java/com/google/devtools/build/lib/exec/local/LocalSpawnRunnerTest.java:396
- Skipped (documented): nonZeroExit src/test/java/com/google/devtools/build/lib/exec/local/LocalSpawnRunnerTest.java:440
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-c03f94a3f4024b7e801e7047a983192f/history.json --exit-code 0 --source . | 27 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-c03f94a3f4024b7e801e7047a983192f/tree.json --exit-code 0 --source . | 17 | 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/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off . | 5 | 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 . | 3 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| 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. semgrep could not parse 6 file(s) — `src/main/java/net/starlark/java/eval/Printer.java`, `src/main/java/net/starlark/java/eval/Starlark.java`, `src/main/java/net/starlark/java/eval/StarlarkFunction.java`, `src/main/java/net/starlark/java/syntax/Parser.java`, `src/main/java/net/starlark/java/syntax/Resolver.java`, … (+1 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious 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 |