-
Notifications
You must be signed in to change notification settings - Fork 201
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
Vertx client doesn't deal correctly with a byte array set to null #1477
Comments
Same error trace, but using io.vertx.pgclient.data.Point. I changed |
Hi there! I have the same error, but for
There is no custom
In case of the real Such behaviour was definitely introduced in #1464 |
We have this entity:
Hibernate generated the following schema for that entity:
|
See eclipse-vertx#1477 This is a regression introduced in eclipse-vertx#1464 When the value is null, the extractor throws a failure. Then, in ErrorMessageFactory.buildWhenArgumentsTypeNotMatched, a NPE is thrown because the value of the class cannot be determined. Signed-off-by: Thomas Segismont <[email protected]>
…1486) See #1477 This is a regression introduced in #1464 When the value is null, the extractor throws a failure. Then, in ErrorMessageFactory.buildWhenArgumentsTypeNotMatched, a NPE is thrown because the value of the class cannot be determined. Signed-off-by: Thomas Segismont <[email protected]>
…clipse-vertx#1486) See eclipse-vertx#1477 This is a regression introduced in eclipse-vertx#1464 When the value is null, the extractor throws a failure. Then, in ErrorMessageFactory.buildWhenArgumentsTypeNotMatched, a NPE is thrown because the value of the class cannot be determined. Signed-off-by: Thomas Segismont <[email protected]>
…1486) (#1487) See #1477 This is a regression introduced in #1464 When the value is null, the extractor throws a failure. Then, in ErrorMessageFactory.buildWhenArgumentsTypeNotMatched, a NPE is thrown because the value of the class cannot be determined. Signed-off-by: Thomas Segismont <[email protected]>
Fixed by #1487 |
Questions
After updating our application to Quarkus 3.16.4 see https://github.com/quarkusio/quarkus/releases/tag/3.16.4 we noticed that we got a test failure for the case when we try to persist a Hibernate entity that has a byte array field set to null. This used to work before upgrading to Quarkus 3.16.4 which also upgrades Vert.x to 4.5.11
We get the following exception:
Which can be resolved to setting the entity field to an empty byte array instead of null. Then it is able to persist the entity.
Version
Vert.x 4.5.11
Context
Quarkus app with Hibernate Reactive and Reactive PostgreSQL Client
Do you have a reproducer?
no yet
But can be reproduced by creating a Hibernate entity with a field like this:
And set the field to null, then it doesn't work. If you set it to an empty byte array it will work again.
Extra
Looks like this was introduced by this PR here #1464
The text was updated successfully, but these errors were encountered: