Skip to content

Conversation

@bigdaz
Copy link
Member

@bigdaz bigdaz commented Jan 27, 2024

In certain cases, the exception message reported by Gradle was insufficient or incorrect.
This PR improves a couple of things:

  1. Propagate failure received in FinishEvent, rather than reporting incorrectly (handleBuildOperationTypeRaw masks failed build operations #103)
  2. Use a contextual exception for missing input parameters, to ensure that the underlying cause is correctly reported.

Gradle provides special handling for certain exception types.
We now use `DefaultMultiCauseException` consistently to ensure consistent
failure reporting.
@bigdaz bigdaz merged commit 2857e3f into main Jan 27, 2024
@bigdaz bigdaz deleted the dd/failure-reporting branch January 27, 2024 21:12
}
if (details == null && result == null) {
return
} else if (details == null || result == null) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm curious what causes these types to not align such that one is null but not the other.

I definitely think this is the right fix, but I'm confused why this exception was being thrown

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See #103 for more background

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants