Paulo Lopes

Yes we could improve the error messages (would you like to contribute them?) On the other hand look at the `leeway` configuration where we allow some time drifting while validating...

@pendula95 , please go ahead, ATM I'm focused on Json schema and updating openapi to the latest spec release

Synchronization can be troublesome because 2 requests on 2 events loops may create a dead lock, however, it's odd that an object is being shared, we may need to figure...

Looking at the session code, the only reason I can think why we're seeing duplicate references to user objects, is comming from the class `UserHolder` which is hold on the...

@bfreuden I'm running your reproducer. With 4.2.5 indeed the test fails for me too, yet with the latest 4.3.0-SNAPSHOT (it always passes) so I'm thinking that the improvements we're already...

Regarding the question about number of instances, the rule of thumb is that if the handlers are asynchronous (and all the ones you listed are), usually a single instance gives...

The small change above also ensures that even with blocking handlers, no `ConcurrentModificationException`s occur

To prevent the 403, we need some behavior change. We should make the API return immutable objects. This way multiple views will be independent at the cost of more garbage...

Currently the extensions are just a map on the options object. This should be deprecated (as it's currently a NOOP feature) and we should define a codegen interface/data object for...

@yanosz thanks for starting this discussion. The reason why you see `String` in `KeyStoreOptions` is because in vert.x option objects are annotated with `@DataObject` which means the compiler will generate...