Java 17 causes "InaccessibleObjectException" for ArraysAsListSerializer about paper HOT 5 OPEN

Seems to me that this part could be solved by this StackOverflow post.

https://stackoverflow.com/a/75473860

from paper.

They say that Kryo5 should work:
magro/kryo-serializers#131 (comment)

Any plans for PaperDB to update to Kryo5?

from paper.

Any plans for PaperDB to update to Kryo5?

I don't have such plans at the moment. I believe you can add your custom serializer as a workaround.

from paper.

I don't have such plans at the moment. I believe you can add your custom serializer as a workaround.

Was looking into this topic, as I am currently facing the same problem and adding a custom serializer it is not enough I believe.
The error occurs on the creation of the Kryo Instance here, which calls the constructor of the ArraysAsListSerializer containing the "problematic code".

So even if I add a custom serializer, the code will still fail at the same line.

from paper.

Due to PaperDB's use of kryo-serializers, "ArraysAsListSerializer" is not compatible with Java 17. magro/kryo-serializers#131

Is there anyway we can make "ArraysAsListSerializer" compatible with Java 17?

Hello! Did you found a solution for this? I have the same issue but it can only be reproduced when running unit tests.

from paper.