-
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
Update to Apicurio Registry 2.1.1.Final and use Vert.x HTTP client #20495
Conversation
cc @Ladicek |
Ah does this have the new HTTP client SPI? I will dig out the commit I have to use that. That can be a separate PR I believe. |
This workflow status is outdated as a new workflow run has been triggered. Failing Jobs - Building bc29317
Failures⚙️ Initial JDK 11 Build #- Failing: extensions/apicurio-registry-avro/runtime
! Skipped: devtools/bom-descriptor-json docs extensions/apicurio-registry-avro/deployment and 7 more 📦 extensions/apicurio-registry-avro/runtime✖ |
Yes. This also removes the need for Keycloak libraries. I can do the changes if you want, just give me the pointers to the code :). |
Ok, I've figured out what's going on with the failed build and I'm working to get it fixed. I'll ping here once is resolved. |
@Ladicek do you mind approving the workflow run? :) |
@Ladicek there's one failing test. I think it has something to do with the SPI not working in native mode. Anyway, we need to force it to use the Vert.x client, so I can leave it to you or I can do it if you give me some hints/pointers about where to do that and I can do it, whatever you prefer, thanks. |
This workflow status is outdated as a new workflow run has been triggered. Failing Jobs - Building 431de09
Full information is available in the Build summary check run. Failures⚙️ JVM Tests - JDK 11 #- Failing: integration-tests/oidc
📦 integration-tests/oidc✖
⚙️ JVM Tests - JDK 17 #- Failing: integration-tests/oidc
📦 integration-tests/oidc✖
⚙️ Native Tests - Messaging1 #- Failing: integration-tests/kafka-avro-apicurio2
📦 integration-tests/kafka-avro-apicurio2✖
✖
|
@@ -22,7 +22,7 @@ | |||
--> | |||
|
|||
<properties> | |||
<apicurio.version>2.0.1.Final</apicurio.version> | |||
<apicurio.version>2.1.1.Final</apicurio.version> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can't apicurio-registry.version
be used in place of this property?
@@ -29,7 +29,7 @@ public static String getApicurioSchemaRegistryUrl() { | |||
@Override | |||
public Map<String, String> start() { | |||
kafka.start(); | |||
registry = new GenericContainer<>("apicurio/apicurio-registry-mem:2.0.1.Final") | |||
registry = new GenericContainer<>("apicurio/apicurio-registry-mem:2.1.1.Final") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This version should also be read from a property (added to the surefire plugin config).
@carlesarnal I see you tried to integrate the Vert.x client. That is a bit more complex, I have a branch somewhere, but the most important question is: what version of Vert.x is Apicurio Registry 2.1 compiled against? In 2.0, it used to be Vert.x 3.9, so I had to copy the Vert.x client to Quarkus (that's sitting on that branch I have), but if 2.1 is compiled against Vert.x 4, then I could remove that. In any case, I think I'd just bump Apicurio Registry to 2.1 in this PR, and moved to using the Vert.x client in another PR. WDYT? EDIT: if that is not possible, maybe I can add a commit to your branch? |
Hi @Ladicek, sorry for the delay, I was on PTO. I only added the required dependencies, I was expecting this to be more complex than just that :). Apicurio Registry 2.1.1.Final is working with Vert.x 4.x and Quarkus 2.2.3.Final, so you should be able to remove the client there. I think it's better if you add the commit to this branch directly. |
OK, I'll try to take a look, but I'm rather busy with CDI Lite these days. I should get to it next week. For the record, here's the commit I did back when we discussed this: Ladicek@29c4624 The most interesting change is the one in |
I've added a commit with something similar to what you did in yours but using the client on our side. Just check it when you have some time. |
2884de3
to
49e56f1
Compare
@carlesarnal I've rebased and squashed your branch, plus made a few tiny changes (excluded the JDK client, removed a dependency on the Vert.x client library from the |
@@ -201,7 +201,8 @@ | |||
<log4j2-jboss-logmanager.version>1.0.0.Final</log4j2-jboss-logmanager.version> | |||
<log4j-jboss-logmanager.version>1.2.2.Final</log4j-jboss-logmanager.version> | |||
<avro.version>1.10.2</avro.version> | |||
<apicurio-registry.version>2.0.1.Final</apicurio-registry.version> | |||
<apicurio-registry.version>2.1.1.Final</apicurio-registry.version> | |||
<apicurio-common-rest-client.version>0.0.9.Final</apicurio-common-rest-client.version> <!-- must be the version Apicurio Registry uses --> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Right, nice comment.
@@ -17,6 +17,16 @@ | |||
<dependency> | |||
<groupId>io.apicurio</groupId> | |||
<artifactId>apicurio-registry-serdes-avro-serde</artifactId> | |||
<exclusions> | |||
<exclusion> | |||
<groupId>io.apicurio</groupId> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch.
It does, yes. Let's see what CI says. Thanks a lot, @Ladicek. |
Also FYI @cescoffier, it finally happens :-) |
This workflow status is outdated as a new workflow run has been triggered. Failing Jobs - Building 49e56f1
Full information is available in the Build summary check run. Failures⚙️ MicroProfile TCKs Tests #- Failing: tcks/microprofile-fault-tolerance
📦 tcks/microprofile-fault-tolerance✖
⚙️ Native Tests - Messaging1 #- Failing: integration-tests/kafka-avro-apicurio2
📦 integration-tests/kafka-avro-apicurio2✖
✖
|
|
Yes, it looks like the AtomicReference has not been properly set. Maybe due to the native nature of the test? I'm not sure tbh. We're using the factory and the reference in our testing with no issues but they're not native. |
Found the problem. The thing is that |
49e56f1
to
3d850f5
Compare
Pushed a fix. |
This workflow status is outdated as a new workflow run has been triggered. Failing Jobs - Building 3d850f5
Full information is available in the Build summary check run. Failures⚙️ Native Tests - Messaging2 #- Failing: integration-tests/reactive-messaging-rabbitmq
📦 integration-tests/reactive-messaging-rabbitmq✖
|
I can't see how this test failure could be relevant. @cescoffier @ozangunalp do you perhaps know if |
Thanks a lot! |
@Ladicek any update on this? I would like to get this into the next release, if possible. |
Ouch, I thought it's already merged. Whoops! Let me see if I can resolve the conflict real quick. |
3d850f5
to
a23c7b9
Compare
OK, done. Hopefully CI will end up green :-) |
Failing Jobs - Building a23c7b9
Failures⚙️ JVM Tests - JDK 11 #- Failing: extensions/hibernate-orm/deployment
! Skipped: docs extensions/hibernate-envers/deployment extensions/hibernate-reactive/deployment and 85 more 📦 extensions/hibernate-orm/deployment✖ ⚙️ Native Tests - Windows - hibernate-validator #- Failing: integration-tests/hibernate-validator
📦 integration-tests/hibernate-validator✖ |
I have no idea why these tests fail or if they're flaky :-/ |
Apparently these tests are flaky, so this is good to go! |
Nice, thanks for merging @Ladicek! |
Thanks for your patience! :-) |
We (the Apicurio Team) released a new version of Registry recently. This PR updates the usage of Registry to the new version.