[2.x] fix: Allow dependencyTree to run despite eviction errors#8554
Merged
eed3si9n merged 6 commits intosbt:developfrom Jan 16, 2026
Merged
Conversation
Contributor
Author
|
@eed3si9n would you review this PR and give me feedback if you have any? |
Member
|
Awesome. Could you also modify one of the scripted tests or add a fresh one to demonstrate the fix please? |
**Problem** When binary compatibility eviction errors occur, users cannot run `dependencyTree` to debug the dependency conflict because it fails with the same eviction error. **Solution** Set `evictionErrorLevel` and `assumedEvictionErrorLevel` to `Level.Warn` for the `dependencyTreeIgnoreMissingUpdate` task, allowing the dependency tree to be displayed even when eviction errors are present. Fixes sbt#7255
Add a scripted test that verifies dependencyTree works despite binary incompatible eviction errors, demonstrating the fix for sbt#7255. The test creates a controlled eviction scenario using local modules: - base 1.0.0 and 2.0.0 with early-semver versioning - middle depends on base 1.0.0 - app depends on middle + base 2.0.0 (eviction conflict) Before the fix, dependencyTree would fail with the eviction error. After the fix, it displays the tree with eviction shown as warning.
eureka928
force-pushed
the
fix/7255-dependency-tree-eviction-errors
branch
from
422ba66 to
04a2793
Compare
Use Def.uncached for the checkDependencyTree task and remove the unused checkEvictionError task that caused HashWriter errors.
Use external Maven dependencies (fs2-core + cats-effect) to create eviction scenario instead of multi-project local publish approach. This is simpler and avoids task caching issues.
Contributor
Author
|
@eed3si9n this might fix the whole ci process, please review again |
Remove empty comment lines that cause parsing errors. Scripted test format doesn't support standalone '#' lines.
Contributor
Author
|
Can you allow testing for this ci workflow? |
Contributor
Author
|
@eed3si9n passed the testing! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
When binary compatibility eviction errors occur, users cannot run
dependencyTreeto debug the dependency conflict because it fails with the same eviction error.Solution
Set
evictionErrorLevelandassumedEvictionErrorLeveltoLevel.Warnfor thedependencyTreeIgnoreMissingUpdatetask, allowing the dependency tree to be displayed even when eviction errors are present.Fixes #7255
Contribution by Gittensor, see my contribution statistics at https://gittensor.io/miners/details?githubId=42954461