Thomas Heigl

It seems that has been discussed a couple of times in the past: - https://github.com/EsotericSoftware/kryo/issues/151 - https://github.com/EsotericSoftware/kryo/issues/604 Nate was against including any "unsafe" serializers, i.e. serializers depending on internal state...

I came here to say the same. It would be great if it was possible to register a custom factory for beans, so Lombok classes could be instantiated via @Builder...

It is quite trivial to add support for `script` to `LocaleSerializer`, but I'm afraid it is not possible to do it in a backwards-compatible way. For now, you can register...

Closing for now. Please re-open if you can provide a reproducer.

That makes a lot of sense. In my experience, Kryo is 3-5x faster than JDK serialization when using the default `FieldSerializer`. Performance gains are lower for the [compatible serializers](https://github.com/EsotericSoftware/kryo?tab=readme-ov-file#compatibility), but...

Closing for now. Please re-open if you can provide additional info.

This would probably be fixed by passing all URLs in `allowNavigation` instead of the `server.url` as suggested in #7454.

This can usually only happen if your data model or your Kryo config changes between serialization and deserialization. Can you reproduce this when you serialize and deserialize in a unit...

Can you explain in more detail what you mean by that or what you want to achieve?

Understood. As I said before, this error usually only happens if deserialization happens with a different Kryo configuration or if your classes changed between serialization and deserialization. Are you sure...