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

SmallRye Fault Tolerance 6.7.3 release announcement #111

Merged
merged 1 commit into from
Jan 10, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 21 additions & 0 deletions _posts/2025-01-09-fault-tolerance-6-7-3.adoc
Original file line number Diff line number Diff line change
@@ -0,0 +1,21 @@
:page-layout: post
:page-title: Fault Tolerance 6.7.3
:page-synopsis: SmallRye Fault Tolerance 6.7.3 released!
:page-tags: [announcement, microprofile]
:page-date: 2025-01-09 17:00:00.000 +0100
:page-author: lthon
:smallrye-ft: SmallRye Fault Tolerance
:microprofile-ft: MicroProfile Fault Tolerance

= Fault Tolerance 6.7.3

Today, we announce the https://github.com/smallrye/smallrye-fault-tolerance/releases/tag/6.7.3[release] of {smallrye-ft} 6.7.3.
This release contains one bugfix.

In the link:/blog/fault-tolerance-6-7-2[previous release], the event loop integration was significantly improved.
That improvement, alas, contains a bug in the Vert.x integration.
We assumed that a Vert.x thread is always associated with a current Vert.x context, but that doesn't have to be the case.
Especially in case of a worker thread pool, which can be (in Quarkus, for example) used as a classic thread pool as well and tasks can be submitted to it outside of a Vert.x context.
This wrong assumption lead to a NPE, which is fixed now.

As usual, if you have any ideas for improvements, please https://github.com/smallrye/smallrye-fault-tolerance/issues[file an issue]!
Loading