-
Notifications
You must be signed in to change notification settings - Fork 3k
[3.27] 3.27.2 backports 2 #51707
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
base: 3.27
Are you sure you want to change the base?
[3.27] 3.27.2 backports 2 #51707
Conversation
Fixes: # 51035 (cherry picked from commit 85c7a97)
(cherry picked from commit f6fed11)
(cherry picked from commit 7a4b827)
…file (cherry picked from commit 94f76e8)
It is sometimes confusion and cumbersome to explicitly call the right mode before going offline. For example if you are about to board a plane you might forget to give the option to also download dependencies for dev mode. (I actually had that last week). This introduces a new option that downloads dev, test and prod dependencies and makes this the new default. This allows developers to go offline without having to specify the mode explicitly. Furthermore, adjust the usage through the docs and CI to align with the previous state. For building native images we don't need the dev and test dependencies. For running on CI we don't need the dev dependencies either. (cherry picked from commit 7f514f5)
This has proven to cause many issues so let's disable it entirely at the Maven level. (cherry picked from commit 04ee40f)
(cherry picked from commit e520c21)
(cherry picked from commit 02cb12f)
(cherry picked from commit 8459c5b)
Fixes quarkusio#51245 Docker v29 changed the behavior of Network.getContainers() to return null instead of an empty map when no containers are present. This causes a NullPointerException when filtering networks to find the default network with containers. This commit adds a null check before calling isEmpty() to handle both the old behavior (empty map) and the new behavior (null). (cherry picked from commit 676d299)
…nner (cherry picked from commit 18688d0)
This is needed because the session launcher might stay open for several test runs if surefire reruns tests. (cherry picked from commit 6bf4f0a)
Signed-off-by: shjones <[email protected]> (cherry picked from commit 3884a23)
Signed-off-by: shjones <[email protected]> (cherry picked from commit c09dbc4)
Add missing imports for jakarta.enterprise.inject.Decorated and jakarta.enterprise.inject.spi.Bean for consistency ... and remove newline. (cherry picked from commit 6331542)
The dependency can be found here: https://central.sonatype.com/artifact/org.graalvm.sdk/nativebridge Follow-up to quarkusio#50288 (cherry picked from commit 01b6335)
To keep the docs in line with the recent config property names scheme (enable => enabled): https://github.com/quarkusio/quarkus/wiki/Migration-Guide-3.26#enable-enabled-in-configuration-properties-gear-white_check_mark (cherry picked from commit 02a9f9c)
Signed-off-by: Maciej Lisowski <[email protected]> (cherry picked from commit 7213273)
This is causing warnings in the website after an Asciidoc update. (cherry picked from commit aad38b3)
|
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.27), @gastaldi (3.27), @gsmet (3.27), @rsvoboda (3.27) |
This comment has been minimized.
This comment has been minimized.
|
🎊 PR Preview a38a111 has been successfully built and deployed to https://quarkus-pr-main-51707-preview.surge.sh/version/main/guides/
|
…en Hibernate ORM (blocking) and Hibernate Reactive by validating datasource configuration at build time. - Blocking persistence units are not created when only reactive datasources are configured - Reactive persistence units are not created when only blocking datasources are configured - Clear error messages are provided when datasources are missing - Created HibernateDataSourceUtil with shared datasource lookup logic - Extracted ReactiveDataSourceBuildItem to new `quarkus-reactive-datasource-spi` module to enable reactive data source checking in the Hibernate ORM extension - Convert new SPI build item to the old one in a single BuildStep (skippable) - Refactored HibernateOrmProcessor and HibernateReactiveProcessor to validate datasource types and don't create the PU when there's no appropriate DS - Fail correctly when using a single extension but the datasource name is mismatched - Fixed ORMReactiveCompatbilityDifferentNamedDataSourceNamedPersistenceUnitBothUnitTest which was incorrectly passing due to dev services - Added new test cases for mixed datasource scenarios Fixes quarkusio#50634 quarkusio#47036 (cherry picked from commit 80d18ac)
Status for workflow
|
Status for workflow
|
| Status | Name | Step | Failures | Logs | Raw logs | Build scan |
|---|---|---|---|---|---|---|
| ❌ | Native Tests - Misc2 | Build |
Failures | Logs | Raw logs | 🔍 |
Full information is available in the Build summary check run.
You can consult the Develocity build scans.
Failures
⚙️ Native Tests - Misc2 #
- Failing: integration-tests/mailer
📦 integration-tests/mailer
❌ io.quarkus.it.mailer.MailerIT.sendHtmlEmail - History - More details - Source on GitHub
Details
java.lang.RuntimeException: java.util.concurrent.CompletionException: java.lang.RuntimeException: Unable to start Quarkus test resource class io.quarkus.it.mailer.MailpitTestResource
at io.quarkus.test.junit.QuarkusIntegrationTestExtension.throwBootFailureException(QuarkusIntegrationTestExtension.java:346)
at io.quarkus.test.junit.QuarkusIntegrationTestExtension.beforeEach(QuarkusIntegrationTestExtension.java:114)
at java.base/java.util.ArrayList.forEach(ArrayList.java:1511)
at java.base/java.util.ArrayList.forEach(ArrayList.java:1511)
Caused by: java.util.concurrent.CompletionException: java.lang.RuntimeException: Unable to start Quarkus test resource class io.quarkus.it.mailer.MailpitTestResource
at java.base/java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:315)
at java.base/java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:320)
Flaky tests - Develocity
⚙️ MicroProfile TCKs Tests
📦 tcks/microprofile-lra
❌ org.eclipse.microprofile.lra.tck.TckRecoveryTests.testCancelWhenParticipantIsUnavailable - History
Expecting the metric Compensated callback was called Expected: a value equal to or greater than <1> but: <0> was less than <1>-java.lang.AssertionError
Details
java.lang.AssertionError:
Expecting the metric Compensated callback was called
Expected: a value equal to or greater than <1>
but: <0> was less than <1>
at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20)
at org.eclipse.microprofile.lra.tck.TckRecoveryTests.assertMetricCallbackCalled(TckRecoveryTests.java:210)
at org.eclipse.microprofile.lra.tck.TckRecoveryTests.testCancelWhenParticipantIsUnavailable(TckRecoveryTests.java:195)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

No description provided.