Thomas Heigl

There is not much we can do. The data seems to have been corrupted somehow and cannot be read. Kryo could only throw a different exception and this is what...

In my project, we usually do this when we don't want a page to be serialized after an ajax request: ```java private void untouchPage(Page page) { if (Session.exists()) { //...

> No. You do this after each AJAX request? > > I just want to be able to mark some requests as "do not generate" a page serialization. Yes, after...

Thanks for the report @ams45. Can you try to reproduce this using Kryo alone? At the moment the setup is much too complicated for me to look into. The best...

Is the fix backwards compatible? If it is, you could provide a PR that backports it to Kryo 4. I don't actively maintain Kryo 4 anymore, but if users provide...

We also ran into connection issues with 5.1.0 that were resolved by downgrading back to 5.0.1. @slbejaranom could you check if downgrading to 5.0.1 fixes your issue as well?

Most commits since 5.0.1 seem harmless except for this one c2148006ceff26085bd731b650b9a5a3ef0e45f6. Unfortunately we can’t reproduce the issue easily. We hit the issue in production and reverted immediately.

Is this really necessary? The Javadoc for `MarkupFactory` reads: ```java * MarkupParser's can be extended by means of {@link IMarkupFilter}. You can add your own filter * as follows: *...

What's your Kryo configuration? The default `FieldSerializer` does *not support* changes to the class structure. It doesn't write a schema for the class so it has no possibility to detect...

`FieldSerializer` is the fastest generic serializer because it **does not write a schema**. That means there is nothing we can compare or validate. What FieldSerializer writes looks something like this:...