Jaromir Hamala
Jaromir Hamala
thanks for the report. at first glance it appears it could be related to: https://github.com/EsotericSoftware/kryo/issues/320
hi @ohadpinch, I pushed an experiment into master. Try to build the latest master and add `serializerConfigurers=EnableSyntheticFields` into your `subzero-serializers.properties` file.
@MojoManagement: can you try the latest master? thanks!
@MojoManagement: did you have a chance to check it?
hi @mukul4u2005, what is your Hazelcast version? I can see you are using `3.6` in your XSD. Your XML references this schema: `
https://github.com/protostuff/protostuff-examples/blob/master/runtime-schema-usage/src/test/java/io/protostuff/examples/RuntimeSchemaUsage.java
@loudywen, @zoza: just add `defaultSerializer=CompatibleFieldSerializer` into your `subzero-serializers.properties` file.
@S4n60w3n It depends. *Usually* you do not want to include libraries in a `test` test scope in compliance checks. but this depends on a license. It's *probably* fine for GPL...
I can reproduce *a* failure when I decrease time out here: https://github.com/questdb/questdb/blob/aaa30eab284eaa53de1b3e6d32dcf5e464337df8/core/src/test/java/io/questdb/cutlass/line/tcp/AlterTableLineTcpReceiverTest.java#L491 With sufficiently short timeout `alterOperationFuture.await()` returns before it has a chance to throw `SqlException`. But this looks to...
ok, this is what's going on: 1. The UPDATE command is published 2. ILP rows are written 3. JVM/OS hiccup. 300ms. see the previous message. 4. `LineTcpWriterJob` is triggered 5....