-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
[3.15] 3.15.2 backports 3 #44476
[3.15] 3.15.2 backports 3 #44476
Conversation
Bumps `microprofile-reactive-streams-operators.version` from 3.0 to 3.0.1. Updates `org.eclipse.microprofile.reactive-streams-operators:microprofile-reactive-streams-operators-api` from 3.0 to 3.0.1 - [Release notes](https://github.com/eclipse/microprofile-reactive-streams-operators/releases) - [Commits](eclipse/microprofile-reactive-streams-operators@3.0...3.0.1) Updates `org.eclipse.microprofile.reactive-streams-operators:microprofile-reactive-streams-operators-core` from 3.0 to 3.0.1 - [Release notes](https://github.com/eclipse/microprofile-reactive-streams-operators/releases) - [Commits](eclipse/microprofile-reactive-streams-operators@3.0...3.0.1) --- updated-dependencies: - dependency-name: org.eclipse.microprofile.reactive-streams-operators:microprofile-reactive-streams-operators-api dependency-type: direct:production update-type: version-update:semver-patch - dependency-name: org.eclipse.microprofile.reactive-streams-operators:microprofile-reactive-streams-operators-core dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]> (cherry picked from commit bb9af16)
Bumps `hibernate-orm.version` from 6.6.0.Final to 6.6.1.Final. Updates `org.hibernate.orm:hibernate-core` from 6.6.0.Final to 6.6.1.Final - [Release notes](https://github.com/hibernate/hibernate-orm/releases) - [Changelog](https://github.com/hibernate/hibernate-orm/blob/6.6.1/changelog.txt) - [Commits](hibernate/hibernate-orm@6.6.0...6.6.1) Updates `org.hibernate.orm:hibernate-graalvm` from 6.6.0.Final to 6.6.1.Final - [Release notes](https://github.com/hibernate/hibernate-orm/releases) - [Changelog](https://github.com/hibernate/hibernate-orm/blob/6.6.1/changelog.txt) - [Commits](hibernate/hibernate-orm@6.6.0...6.6.1) Updates `org.hibernate.orm:hibernate-envers` from 6.6.0.Final to 6.6.1.Final - [Release notes](https://github.com/hibernate/hibernate-orm/releases) - [Changelog](https://github.com/hibernate/hibernate-orm/blob/6.6.1/changelog.txt) - [Commits](hibernate/hibernate-orm@6.6.0...6.6.1) Updates `org.hibernate.orm:hibernate-jpamodelgen` from 6.6.0.Final to 6.6.1.Final - [Release notes](https://github.com/hibernate/hibernate-orm/releases) - [Changelog](https://github.com/hibernate/hibernate-orm/blob/6.6.1/changelog.txt) - [Commits](hibernate/hibernate-orm@6.6.0...6.6.1) Updates `org.hibernate:hibernate-jpamodelgen` from 6.6.0.Final to 6.6.1.Final - [Release notes](https://github.com/hibernate/hibernate-orm/releases) - [Changelog](https://github.com/hibernate/hibernate-orm/blob/6.6.1/changelog.txt) - [Commits](hibernate/hibernate-orm@6.6.0...6.6.1) Updates `org.hibernate.orm:hibernate-community-dialects` from 6.6.0.Final to 6.6.1.Final - [Release notes](https://github.com/hibernate/hibernate-orm/releases) - [Changelog](https://github.com/hibernate/hibernate-orm/blob/6.6.1/changelog.txt) - [Commits](hibernate/hibernate-orm@6.6.0...6.6.1) --- updated-dependencies: - dependency-name: org.hibernate.orm:hibernate-core dependency-type: direct:production update-type: version-update:semver-patch - dependency-name: org.hibernate.orm:hibernate-graalvm dependency-type: direct:production update-type: version-update:semver-patch - dependency-name: org.hibernate.orm:hibernate-envers dependency-type: direct:production update-type: version-update:semver-patch - dependency-name: org.hibernate.orm:hibernate-jpamodelgen dependency-type: direct:production update-type: version-update:semver-patch - dependency-name: org.hibernate:hibernate-jpamodelgen dependency-type: direct:production update-type: version-update:semver-patch - dependency-name: org.hibernate.orm:hibernate-community-dialects dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]> (cherry picked from commit 9640b89)
(cherry picked from commit 58d79a9)
(cherry picked from commit 5ae6c3b)
(cherry picked from commit 4f02189)
…us Sec (cherry picked from commit 5a48e6d)
- even if only mail template record is used - get rid of unnecessary programmatic lookup in MailTemplateProducer - fixes quarkusio#43518 (cherry picked from commit 3c243a6)
(cherry picked from commit 40020d0)
(cherry picked from commit 6ccff48)
(cherry picked from commit c9ea0c6)
- fixes quarkusio#43489 - consider default methods in class hierarchy; previously, interface default methods were only considered if a ValueResolver was generated for an interface - also consider inherited fields in a class hierarchy (cherry picked from commit bc206a1)
- follows up on quarkusio#43602 (cherry picked from commit fdd1ae4)
…to 2.4.2.Final (cherry picked from commit 7e616d1)
(cherry picked from commit aa6bf6c)
RESTEasy Classic's MP RestClient implementation produces annotations at runtime, so they are not created by ArC and therefore don't extend `AbstractAnnotationLiteral`. At the same time, that implementation produces an `ArcInvocationContext` and puts interceptor bindings into its context map under the ArC key. Some places may expect that an `ArcInvocationContext` would always contain ArC-created `AbstractAnnotationLiteral` instances, but alas, per the description above, that is not the case. There are multiple options for fixing that collision. My preferred one would be to get rid of `AbstractAnnotationLiteral` and treat all annotations uniformly. That unfortunately has negative performance implications on the `CacheInterceptor`, so is not an option yet [1]. This commit chooses another path: it modifies the only place in Quarkus that actually depends on `AbstractAnnotationLiteral` to check whether the `Set<AbstractAnnotationLiteral>` actually contains instances of `AbstractAnnotationLiteral`. I hope that before more places in Quarkus start depending on `AbstractAnnotationLiteral`, we can get rid of it. This commit only checks the first annotation in the set, because if the bindings come from RESTEasy Classic, then none of them are instances of `AbstractAnnotationLiteral`, and if they come from ArC, then all of them are instances of `AbstractAnnotationLiteral`. [1] The performance issue (JDK-8180450) is fixed in JDK 23 and has not been backported to any LTS release as of this writing. (cherry picked from commit 6a4fbd6)
(cherry picked from commit 9f917a7)
(cherry picked from commit 0ae451c)
(cherry picked from commit cd4d579)
(cherry picked from commit 9257b63)
No change at runtime, as 7.0.3.Final is identical to 7.0.1.Final except for some build plugins. This is mainly useful to allow rebuilding Quarkus and all its dependencies from source, as 7.0.1.Final has build-time dependencies on artifacts that were hosted on JCenter and are no longer available. (cherry picked from commit 8a0f9e4)
Fixes quarkusio#43854 (cherry picked from commit 750cec2)
Avoids writing a null bean name to the bean archive, which causes a later build failure. Fixes quarkusio#43825 (cherry picked from commit df4696b)
bd0d306
to
04abe53
Compare
This comment has been minimized.
This comment has been minimized.
🙈 The PR is closed and the preview is expired. |
This comment has been minimized.
This comment has been minimized.
@michalvavrik we may need you to look into |
The error is the following:
I think we should really drop the log silencing in this test as it's going to be very hard to understand what's going on when the test fails. |
these failures tells you that security checks are not performed eagerly; @gsmet is this test failing on main or is it flaky on main? If not, I think I need to look into differences between 3.16 and 3.15.
@gsmet this is the reason why I added the silencing #43017. I don't think you will get any useful information if the test is not failing or when the test is failing and it is not flaky; anyway, you know CI possibilities better than I do, if it is fine, let's enable it. btw, the log message above didn't provide me information that I didn't already know from 500 :-) |
@gsmet @rsvoboda it is wild guess, but I think I know where the issue is, In 3.16 I think I changed utils and on the current main, the change was only needed at one place. however on 3.15 it is probably needed in more than one place. it should be pretty trivial, I'll look in an hour and report back. |
If you add this commit 255ffdb in addition to the commits you already have, the failure will be fixed. |
(cherry picked from commit de34b6f)
- 25 -> 10; the Quartz thread pool is not used to execute scheduled methods anyway (cherry picked from commit a1e65b1)
This is extremely important as some recipes are additive and changing the order will affect the result. I noticed that because a project updated from 3.5 to 3.15 was updated to use quarkus-resteasy-client-jackson instead of quarkus-rest-client-jackson due to the recipes not applied in order. (cherry picked from commit c211c89)
- Follow up from quarkusio@235f0a7 (cherry picked from commit bcb01b2)
…rator ArC-generated classes for framework beans are by default _not_ application classes. This causes problems in hierarchical classloader environments (dev/test mode) when there is an application decorator that applies to the framework bean. This commit fixes that issue by turning the ArC-generated classes for framework beans into application classes whenever an application decorator applies. This makes package access impossible, which is an unfortunate downside. The problem doesn't exist in a flat classloading environment, such as prod mode. (cherry picked from commit f9b2164)
(cherry picked from commit 077f1a9)
Signed-off-by: Phillip Kruger <[email protected]> (cherry picked from commit ebe0750)
(cherry picked from commit d8ff7e4)
@michalvavrik I amended the commit with your additional change and the test passes locally, thanks!
No really, you never know. It could have been a completely different issue. I think we need something better than disabling 500 entirely as we need logging to understand what's going on. If not for you, for other people having to understand what's going on. |
04abe53
to
85900e9
Compare
Understood, I re-read that commit and there is |
Status for workflow
|
JPA oracle native failed with
|
This comment has been minimized.
This comment has been minimized.
Status for workflow
|
Please don't merge, I will merge it myself.
This is not the final payload, I still need to work on some individual items.