[3.33] 3.33.4 backports 4 - #56511
Open
jmartisk wants to merge 7 commits into
Open
Conversation
|
Thanks for your pull request! Your pull request does not follow our editorial rules. Could you have a look?
This message is automatically generated by a bot. |
|
/cc @aloubyansky (3.33), @gsmet (3.33), @rsvoboda (3.33) |
quarkus-bot
Bot
added
area/dependencies
jmartisk
force-pushed
the
3.33.4-backports-4
branch
from
September 9, 2026 12:21
b6473cb to
3bd85fd
Compare
quarkus-bot
Bot
added
area/cli
This comment has been minimized.
This comment has been minimized.
An empty or delimiter-only bearer token has zero StringTokenizer tokens, so the unguarded nextToken() in getJwtContentPart threw NoSuchElementException. That is not an AuthenticationFailedException, so it escaped BearerAuthenticationMechanism and AbstractHttpAuthorizer turned it into routingContext.fail(t) -- HTTP 500 plus an ERROR stack trace, remotely triggerable by any unauthenticated caller on any bearer-protected endpoint. The method already returns null for 'not a JWT', so hoisting a hasMoreTokens() check above the first nextToken() needs no caller changes: isOpaqueToken correctly returns true and the request falls through to normal 401 handling. decodeJwtHeaders and decodeJwtHeadersAsString in OidcUtils carried the identical unguarded call and are fixed the same way. Fixes quarkusio#55887 (cherry picked from commit 56247e9)
…tics guides (cherry picked from commit e5881b2)
Signed-off-by: Vaibhav Srivastava <vaibhavsri1712@gmail.com> (cherry picked from commit 7768746)
(cherry picked from commit 7fc6601)
Bumps [org.jsoup:jsoup](https://github.com/jhy/jsoup) from 1.23.1 to 1.23.2. - [Release notes](https://github.com/jhy/jsoup/releases) - [Changelog](https://github.com/jhy/jsoup/blob/master/CHANGES.md) - [Commits](jhy/jsoup@jsoup-1.23.1...jsoup-1.23.2) --- updated-dependencies: - dependency-name: org.jsoup:jsoup dependency-version: 1.23.2 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> (cherry picked from commit 8a4538b)
We see the occasional timeout being reached in our Mandrel CI which tests graal/master builds (GraalVM CE Innovation builds). What's more the CI runs on free GHA runners, with 4 CPU cores and 14GB of memory. Those builds received features which increase build time. For example: - Priority inliner (approx. 30-40% longer build times) oracle/graal#14138 Some successful builds take around up to 2 minutes 50-ish seconds to complete for the said native IT test. We only see failures of the test after this upstream PR merged. This seems in-line with the build time increase. Note that older builds of graal/master from July 2026 took about 2 minutes and 30 seconds at most. (cherry picked from commit e57529f)
(cherry picked from commit 979adf7)
jmartisk
force-pushed
the
3.33.4-backports-4
branch
from
September 9, 2026 12:41
3bd85fd to
5562896
Compare
Status for workflow
|
|
🎊 PR Preview d4ff032 has been successfully built and deployed to https://quarkus-pr-main-56511-preview.surge.sh/version/main/guides/
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.