There are a lot of hacks in 'ItemStateStorage' ('ReconstitutionContext' is however OK enough in comparison). This is mostly working around either Chill, or some rather dubious coding practices in 'FieldSerializer' where the kryo instance is squirreled away in the serializer on construction, rather than taken as transient data during a serialization call.
I'm hoping that porting to Kryo v5 may help out with this too, and possibly Chill will have advanced in the meantime, so let's bring that work under this issue too.
Using a context may be enough in the meantime to be able to remove the hacks.
There are a lot of hacks in 'ItemStateStorage' ('ReconstitutionContext' is however OK enough in comparison). This is mostly working around either Chill, or some rather dubious coding practices in 'FieldSerializer' where the kryo instance is squirreled away in the serializer on construction, rather than taken as transient data during a serialization call.
I'm hoping that porting to Kryo v5 may help out with this too, and possibly Chill will have advanced in the meantime, so let's bring that work under this issue too.
Using a context may be enough in the meantime to be able to remove the hacks.