Skip to content
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

[3.8 Backport] Fix StorkClientRequestFilter exception handling #39939

Conversation

damianorenfer
Copy link
Contributor

Exceptions were not caught properly because a Uni subscription was done outside a try-catch block.

(cherry picked from commit 04cffc5)

Exceptions were not caught properly because a Uni subscription was done
outside a try-catch block.

(cherry picked from commit 04cffc5)
@quarkus-bot
Copy link

quarkus-bot bot commented Apr 8, 2024

Thanks for your pull request!

The title of your pull request does not follow our editorial rules. Could you have a look?

  • title should preferably start with an uppercase character (if it makes sense!)

This message is automatically generated by a bot.

@damianorenfer
Copy link
Contributor Author

@gsmet I opened the 3.8 backport as I proposed at #39731
I hope I did it right

@gsmet
Copy link
Member

gsmet commented Apr 9, 2024

Thanks for the effort but we usually backport things in batch, especially for LTS as we discuss potentially problematic backports in a meeting.

I will close this PR but I marked the PR for consideration for 3.8 backport.

Thanks!

@gsmet gsmet closed this Apr 9, 2024
@quarkus-bot quarkus-bot bot added the triage/invalid This doesn't seem right label Apr 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/stork triage/invalid This doesn't seem right
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants