-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide context for Reactive Rest Client exceptions #22103
Conversation
var webApplicationException = (WebApplicationException) res; | ||
var message = webApplicationException.getMessage(); | ||
var invokedMethodObject = properties.get(MP_INVOKED_METHOD_PROP); | ||
if ((invokedMethodObject instanceof Method)) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
double brackets :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oops! Fixed
that's a really useful thing, thanks @geoand ! |
I think we coudl backport it, WDYT? |
Yup, very good idea |
@michalszynkiewicz I had to exclude some of the TCK tests because it was asserting the exact exception message |
11cdafa
to
599429c
Compare
I introduced a property for reverting to the spec behavior simply so we can pass the stupid tests... |
We now add the exact method that caused the exception in order to make it easier for users to identity where the exception is coming from Fixes: quarkusio#22090
This workflow status is outdated as a new workflow run has been triggered. Failing Jobs - Building 903eb34
Full information is available in the Build summary check run. Failures⚙️ JVM Tests - JDK 11 Windows #- Failing: integration-tests/rest-client
📦 integration-tests/rest-client✖
✖
✖
✖
|
Failing Jobs - Building 903eb34
Full information is available in the Build summary check run. Failures⚙️ JVM Tests - JDK 11 Windows #- Failing: extensions/opentelemetry/opentelemetry/deployment
! Skipped: extensions/opentelemetry/opentelemetry-exporter-jaeger/deployment extensions/opentelemetry/opentelemetry-exporter-otlp/deployment integration-tests/opentelemetry and 2 more 📦 extensions/opentelemetry/opentelemetry/deployment✖
|
@radcortez |
Yes, I've already noticed it too. I'll have a look. |
Thanks |
Is there a way to get the old exception message back? I tried |
I'm asking because I need the exception message to be unchanged, otherwise it will break something (which could be fixed with an ugly workaround) in our app. |
For the time being, |
Thanks! I can disable the new behavior with a It would be great if |
I thought there was an issue that that tracks the request, but in any case yeah, it should be done. |
Isn't #22777 tracking it as you initially commented? |
Right, I got mixed up reading too many issues at the same time... |
Now I'm bit confused by the exchange, but I take it nobody is working on making the |
Yeah, exactly that @TomasHofman. Sorry for the mixup |
No problem, thanks for confirming :). |
We now add the exact method that caused the exception
in order to make it easier for users to identity where
the exception is coming from
Fixes: #22090