Skip to content

Commit 9f30c9f

Browse files
author
jbossorg-bot
committed
Published latest aggregated blog posts
1 parent 15d423d commit 9f30c9f

19 files changed

+110
-110
lines changed

src/content/posts-aggregator/10.json

+6-6
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,13 @@
11
{
2-
"title": "JGroups 5.4 released",
3-
"link": "http://belaban.blogspot.com/2024/12/jgroups-54-released.html",
2+
"title": "Quarkus 3.17.3 - Maintenance release",
3+
"link": "https://quarkus.io/blog/quarkus-3-17-3-released/",
44
"author": [
55
{
6-
"name": "Bela Ban",
6+
"name": "Guillaume Smet",
77
"avatar": null
88
}
99
],
10-
"date": "2024-12-03T09:52:00.001Z",
11-
"feed_title": "Belas Blog",
12-
"content": "I'm happy to announce the release of 5.4!    It has roughly 60 bug fixes, performance improvements and new features. Details can be found here: [1]. The most important new features / enhancements are described below. Enjoy!   NAKACK4 NAKACK2 used to have unbounded message buffers (for retransmission and delivery). This required STABLE to purge messages seen by all members from retransmission buffers and MFC (= multicast flow control) to prevent fast senders from making receiver message buffers grow too large. NAKACK4 uses fixed sized buffers with a maximum capacity. When senders attempt to add messages to a full send-buffer, they block until there is space. Receivers also drop a message when there is no space. Receivers remove messages that have been delivered, and also send ACKs back to the sender. When a sender receives ACKs, it computes the minimum and then purges all messages lower than that from its send-buffer. Because stability is implemented by ACKing, STABLE can be removed from a configuration that has NAKACK4. Because senders block on full send-buffers, MFC can also be removed. Memory pressure should be smaller with NAKACK4 than with NAKACK2; the former doesn't need to dynamically increase and shrink its receive- and send-buffers, but always uses the same buffer for messages, and only changes write- and read-pointers. Examples of the new cpnfig are for example ./conf/udp-new.xml, ./conf/tcp-new.xml. https://issues.redhat.com/browse/JGRP-2780  Documentation: http://www.jgroups.org/manual5/index.html#NAKACK4   UNICAST4 Like NAKACK4, UNICAST4 also uses fixed-size buffers. When used in a configuration, unicast flow control (UFC) can be removed. https://issues.redhat.com/browse/JGRP-2843  Documentation: http://www.jgroups.org/manual5/index.html#UNICAST4   JDBC_PING2 JDBC_PING2 is a refactored version of JDBC_PING. Besides refactoring, the major changes are  * Text (rather than binary) column types; this provides for more legibility when looking at the DB. For example, a simple select allows to look at all members of a given cluster. * Support for stored procedures. This makes discovery faster https://issues.redhat.com/browse/JGRP-2795 Documentation: http://www.jgroups.org/manual5/index.html#JDBC_PING2   BETTER TIME UNITS IN ATTRIBUTES Time values in protocols can now be defined in a more simple way, e.g. * \"240000\" -> \"4m\" // 4 minutes * \"500\" -> \"0.5s\" // 0.5 seconds https://issues.redhat.com/browse/JGRP-2811  Documentation: http://www.jgroups.org/manual5/index.html#AttributeValues   MEASURING OF ROUND-TRIP TIMES BETWEEN MEMBERS Round-trip times, measured at the transport of a given stack, can now be fetched. This can be done programmatically, or via probe. https://issues.redhat.com/browse/JGRP-2812   FASTER PROCESSING OF LOOPBACK MESSAGES Loopback messages are messages from A -> A or from A -> all. (In the latter case, a message sent to all members is also looped back up to the sender). So far, loopback messages have always been passed to the thread pool to be passed up on a seperate thread one by one. This was inefficient, and increased lock contention with messages received from other members. Also, message bundling/batching was forfeited. This change passes loopback messages down to the message bundler, which queues and subsequently passes up message batches rather than individual messages. In other words, message bundling is now applied to loopback messages, too. https://issues.redhat.com/browse/JGRP-2831   MORE EFFICIENT AVERAGE Classes Average and AverageMinMax are used to collect statistics. The change introduced a fixed array of samples, avoiding a costly product and overflow check. This change should speed up collections of averages (used by many protocol stats). https://issues.redhat.com/browse/JGRP-2832   FASTARRAY IMPROVEMENTS Class FastArray is used internally over ArrayList. The latter compacts the array when iteration of it removes elements; the former only nulls them. This is a common scenario when handling message batches, leading to a performance increase. https://issues.redhat.com/browse/JGRP-2834 [1] https://issues.redhat.com/projects/JGRP/versions/12425884 "
10+
"date": "2024-12-04T00:00:00.000Z",
11+
"feed_title": "Quarkus",
12+
"content": "We released Quarkus 3.17.3, a maintenance release for our 3.17 release train. UPDATE To update to Quarkus 3.17, we recommend updating to the latest version of the Quarkus CLI and run: quarkus update Note that quarkus update can update your applications from any version of Quarkus (including 2.x) to Quarkus 3.17. For more information about the adjustments you need to make to your applications, please refer to the . FULL CHANGELOG You can get the full changelog of on GitHub. PLATFORM COMPONENT UPGRADES QUARKUS CXF We updated to Quarkus CXF 3.17.1 in the Quarkus Platform. Check the release notes for more information about what is new in this release. COME JOIN US We value your feedback a lot so please report bugs, ask for improvements… Let’s build something great together! If you are a Quarkus user or just curious, don’t be shy and join our welcoming community: * provide feedback on ; * craft some code and ; * discuss with us on and on the ; * ask your questions on ."
1313
}

src/content/posts-aggregator/11.json

+5-5
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,14 @@
11
{
2-
"title": "Keycloak 26.0.7 released",
3-
"link": "https://www.keycloak.org/2024/12/keycloak-2607-released",
2+
"title": "Recap Keycloak at KubeCon NA 2024",
3+
"link": "https://www.keycloak.org/2024/12/keycloak-at-kubecon-na-2024-recap",
44
"author": [
55
{
6-
"name": null,
6+
"name": "Ryan Emerson",
77
"avatar": null
88
}
99
],
10-
"date": "2024-12-03T00:00:00.000Z",
10+
"date": "2024-12-04T00:00:00.000Z",
1111
"feed_title": "Keycloak Blog",
1212
"feed_avatar": "https://www.gravatar.com/avatar/87fe00619f08c241da8dfb23d907ffa2?s=50",
13-
"content": "To download the release go to . UPGRADING Before upgrading refer to for a complete list of changes. ALL RESOLVED ISSUES ENHANCEMENTS * Edits to Authorization Services guide * Addresse QE comments on Server Administration guide * Upgrade to ISPN 15.0.11.Final BUGS * Locale Setting for Update Password Mail admin/api * the InfoPage after an ExecuteActionsEmail is not localized based on the user's locale authentication * Upgrade to 25 throws: Statement violates GTID consistency core * UserId too long to add Security Key WebauthN authentication/webauthn * RP-Initiated logout using `POST` method fails in cross-origin setup oidc * Flaky test: org.keycloak.testsuite.forms.BrowserButtonsTest#appInitiatedRegistrationWithBackButton ci * RESTART_AUTHENTICATION_ERROR in Iphone devices (using safari and chrome browser) oidc * Any one Client role mapping to user/group generating two events on admin events tab. core * Stabilise my-resources.spec test account/ui * Service accounts visible under user search in Admin console admin/api * Error on \"check a11y\" tests on Cypress admin/ui * Switching 'Email as Username' alters existing custom usernames to email addresses, causing LDAP sync issues core * Text in \"Choose a policy type\" is not wrapping admin/ui * Attributes missing in OrganizationRepresentation when using Admin REST API in Keycloak 26 admin/api * [Admin UI] [Create resource-based permission] Resource input is disabled admin/ui * Deprecated CLI options and new options are not stable in their sorting dist/quarkus * On logout from admin console, a serverinfo call with 401 response in the logs admin/ui * Authentication Link and IDP Fails with 400 Bad Request After Migrating to Version 26 and Delete Authentification authentication * Upgrade 24 to 25 fails because db jpa changes drop nonexisting indexes. core * Update Email doesn't update username when Email as Username and Attributes are enabled user-profile * Adding \"sub\" claim to lightweight access token causes HTTP 403 Forbidden Error in Keycloak 26.0.5 oidc * getAll() organization members only returns the first 10 members organizations * KC25 Migration guide for caching options needs clarification * Mis-formatted unordered list in the caching docs * Flaky test: org.keycloak.testsuite.model.session.AuthenticationSessionTest#testConcurrentAuthenticationSessionsRemoval ci * Flaky test: org.keycloak.testsuite.model.session.AuthenticationSessionTest#testConcurrentAuthenticationSessionsCreation ci * Fix typo in v24 changelog: \"longer\" -> \"no longer\" docs * reCAPTCHA v3 not working login/ui * Your login attempt timed out authentication * [Keycloak CI] - Test PoC failing on Keycloak 26.0 branch * Upgrade 26.0.5 -> 26.0.6 completely breaks admin events in the admin UI admin/ui * Error when creating a permission ticket when there are 2 or more Keycloak servers in a cluster authorization-services"
13+
"content": "Keycloak had a very active presence at this year’s KubeCon NA in Salt Lake City, Utah. This blog presents a few of the highlights as well as ways you can contribute to Keycloak’s CNCF journey. PROJECT PAVILION Keycloak hosted a project pavilion stand during Wednesday, Thursday and Friday afternoon slots. Attending the booth were Keycloak contributors from Hitachi and , and from Red Hat. During these sessions, we discussed all things Keycloak with existing and prospective users, as well as provided the much requested Keycloak stickers plus additional swag for particularly enthusiastic users. It was great to hear war stories from the trenches with regard to both the good and bad of Keycloak. This feedback is essential for us to continue to evolve the project and plan the future roadmap. A special thanks to all of those who filled out our survey forms, we really appreciate your time. If you were unable to attend the pavilion, please consider filling out the . KEYCLOAK TALK and presented a talk titled “Running a Highly Available Identity and Access Management with Keycloak”. to hear about the recent developments in Keycloak’s HA story, including an overview of the architecture recommended in the Keycloak guides, the lessons learned during the development of said guides and the CNCF technologies used as part of our stack. A video of the talk is linked below. Thank you to all who attended and asked questions, there were good follow-up conservations that continued well after our time was up. KEYCLOAK SURVEY Are you a Keycloak user who is deploying in production or just considering starting with Keycloak? We would love to hear more from you about your success stories, what is crucial to your deployments and what can be done better. Please fill out the , so we can better understand your use cases. Your story maybe a candidate for a . If you would like to share your success story with our community, answer yes to the “Would you be interested to share your story with our broader community?” and we will be in touch shortly. KUBECON EU In 2025, will be held in London on April 1-4th, we hope to see you there and hear your latest Keycloak stories. As it’s still very much early days, we cannot provide any specifics, but be assured that we’ll publish more information in the near future."
1414
}

0 commit comments

Comments
 (0)