randomUUID | Polyfill for randomUUID as being standardized in https | User Interface library

This is a Hibernate bug:https://hibernate.atlassian.net/browse/HHH-15142 Since the regression was only introduced with Hibernates version 5.6.6 you may avoid it by downgrading Hibernate to 5.6.5

You are having an issue with the nulatibility of your properties, as you can see even tough you are defining var properties some of them are not nullable ? so because you are deserializing a json message, the input of the rest services, Jackson is not being able to create the new instance of your model class user because some of the required fields are not present.

This is similar to when you try to create a new object but do not provide the required arguments in the constructor.

There is some recommendations to work with kotlin an Jax-RS and Hibernate-Panache here https://quarkus.io/guides/kotlin.

What you are trying to archive its perfectly possible but if you want to use you Entity as request body, you must make all the fields nullable, otherwise the underlying Json serializer will not be able to create the new instance of your model to pass the @Valid validations and generate the constraint violation report.

You have some options here.

1. You can create a Data class with all properties nullable so you will ensure that all javax validation annotations will be able to be checked because the request will be able to be deserialized. Then map this object to your Model entity class. You can see this class as a DTO because at the end you are moving data through a layer boundary and decoupling you service contract from within you entity model implementation, which tend to be convenient.
2. Even though the use of the javax.validation constraint annotations is quite handy, you can inject a validator and retrieve the Constraint violations and return a custom data class with the constraint violations in a more readable way, than the default report, which is not supported by quarkus in the reactive version of resteasy.

If you have more doubts i can provide an example.

I think this library https://github.com/cashapp/turbine by Jack Wharton will be of great help in the future when you need more complex scenarios.

What I think is happening is that in fragment you are calling .collect { } and that is ensuring the flow is started. Check the Terminal operator definition: Terminal operators on flows are suspending functions that start a collection of the flow. https://kotlinlang.org/docs/flow.html#terminal-flow-operators

This is not true for sharedFlow, which might be configured to be started eagerly.

So to solve your issue, you might just call

Replace the async fragments something like this, assuming they are meant to be executed sequentially.

You need to use the Junction's parentColumn and entityColumn parameters e.g.

In kafka config you can use reconnect.backoff.max.ms config parameter to set a maximum number of milliseconds to retry connecting. Additionally, set the parameter reconnect.backoff.ms to a base number of milliseconds to wait before retrying to connect.

If provided, the backoff per host will increase exponentially for each consecutive connection failure, up to this maximum.

Kafka documentation https://kafka.apache.org/31/documentation/#streamsconfigs

If you set the max milliseconds to reconnect to something fairly high, like a day, the connection will be reattempted for up to a day (With increasing intervals, 50,500,5000,50000 etc').

I had the same issue, one of the reasons can be that your bean is brought by a dependency and to fix it you need to add an empty beans.xml in main/resources/META-INF in this dependency in order for Quarkus to discover the beans as indicated by the documentation

Relevant extract:

The bean archive is synthesized from:

• the application classes,

• dependencies that contain a beans.xml descriptor (content is ignored),

• dependencies that contain a Jandex index - META-INF/jandex.idx,

• dependencies referenced by quarkus.index-dependency in application.properties,

• and Quarkus integration code.

Alright, seems it was an issue with Stackblitz's service worker. I've just implemented the same client-side solution in Chrome's plain console and the disconnecting is no longer happening.

The reverse seems to work fine when the list size is small, but crashes when the number of items is large. I was able to reproduce this with the following MRE: