Skip to content

Improve Muzzle version range failure diagnostics - #12539

Closed
aalbertjay wants to merge 2 commits into
DataDog:masterfrom
aalbertjay:codex/muzzle-report-aether-result-exceptions
Closed

aalbertjay wants to merge 2 commits into
DataDog:masterfrom
aalbertjay:codex/muzzle-report-aether-result-exceptions

Conversation

@aalbertjay

Copy link
Copy Markdown
Contributor

Summary

  • retain exceptions embedded in Aether VersionRangeResult objects across retries
  • include each exception and its cause chain in the final Muzzle version-range failure message
  • add regression coverage for empty results returned with embedded exceptions

Why

Aether may return a VersionRangeResult with no bounds while recording metadata download, checksum, local-file, or parsing failures in VersionRangeResult.exceptions. Muzzle currently reports only the empty bounds and version count, which hides the client-side cause of intermittent resolution failures.

Testing

  • ./gradlew -p buildSrc :test -PrunBuildSrcTests --tests datadog.gradle.plugin.muzzle.MuzzleMavenRepoUtilsTest -x :call-site-instrumentation-plugin:test -x :modifiable-config-agent:test
  • ./gradlew -p buildSrc spotlessCheck

@bric3
bric3 force-pushed the codex/muzzle-report-aether-result-exceptions branch from 657b422 to 84de5f8 Compare September 21, 2026 15:35
@bric3 bric3 added tag: no release notes Changes to exclude from release notes comp: tooling Build & Tooling labels Sep 21, 2026
@bric3

bric3 commented Sep 21, 2026

Copy link
Copy Markdown
Contributor

@aalbertjay The CI won't work on forks. So I mirrored yours here : #12592, and will close this one.

@bric3 bric3 closed this Sep 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

comp: tooling Build & Tooling tag: no release notes Changes to exclude from release notes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants