3.6.4 backports 1 #37815
Merged
3.6.4 backports 1 #37815
Conversation
This file contains 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
Bumps [io.quarkus:quarkus-platform-bom-maven-plugin](https://github.com/quarkusio/quarkus-platform-bom-generator) from 0.0.100 to 0.0.101. - [Release notes](https://github.com/quarkusio/quarkus-platform-bom-generator/releases) - [Commits](quarkusio/quarkus-platform-bom-generator@0.0.100...0.0.101) --- updated-dependencies: - dependency-name: io.quarkus:quarkus-platform-bom-maven-plugin dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> (cherry picked from commit 6e1f5a8)
It should be `dev mode` with a space and no capitalization. (cherry picked from commit 33a4b25)
This is done because the stacktrace produced is completely useless and only makes it harder to focus on the real problem Relates to: quarkiverse/quarkus-langchain4j#140 (cherry picked from commit 542e93b)
…ention guide (cherry picked from commit 72afeac)
(cherry picked from commit 0e4097c)
(cherry picked from commit 7e3b81a)
replace MINE type with MIME type (cherry picked from commit aecf4a6)
This is done because this type exists in Java 21 but not Java 17. Fixes: quarkusio#37768 (cherry picked from commit 674eac2)
This is necessary for REST Client MessageBodyReader and MessageBodyWriter registration (cherry picked from commit e7fcd32)
Not having this file is probably due to GitHub infra issues but let's not fail the build for that. (cherry picked from commit 0f38872)
- we observed NPE in some edge cases during live reload (cherry picked from commit 3fb7924)
…time.MongoOperations (cherry picked from commit f3746cb)
We had a problem here as most options are only valid in the context of the root command (for instance -D) so trying to parse them in the context of a subcommand or on their own will most probably fail. Also parsing recursively the command is non-efficient as we do a lot of parsing, especially since it was done twice (this was fixed too). The new approach uses the ParseResult generated once and get the knownledge from there. From my tests, it provides similar results and avoid false positives and running the parsing too many times. This should fix CliHelpTest#testCommandHelp() being flaky as not being able to interpret the options ended up triggering the missing command branch and then the JBang support. (cherry picked from commit fb4a379)
quarkus-bot
bot
added
area/arc
|
🙈 The PR is closed and the preview is expired. |
|
✔️ The latest workflow run for the pull request has completed successfully. It should be safe to merge provided you have a look at the other checks in the summary. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Please don't merge, I will merge it myself.