-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
We should use kryo.setRegistrationRequired( true ) #836
Labels
bug
Something isn't working
good first issue
Good for newcomers
refactoring
Restructure or improve existing code
Comments
martin-v
added
bug
Something isn't working
good first issue
Good for newcomers
refactoring
Restructure or improve existing code
labels
Mar 4, 2021
martin-v
added a commit
that referenced
this issue
Mar 5, 2021
rebazer
pushed a commit
that referenced
this issue
Mar 5, 2021
martin-v
added a commit
that referenced
this issue
May 28, 2021
rebazer
pushed a commit
that referenced
this issue
May 28, 2021
martin-v
added a commit
that referenced
this issue
Jun 1, 2021
rebazer
pushed a commit
that referenced
this issue
Jun 1, 2021
martin-v
added a commit
that referenced
this issue
Jun 25, 2021
martin-v
added a commit
that referenced
this issue
Jun 25, 2021
rebazer
pushed a commit
that referenced
this issue
Jun 28, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
Something isn't working
good first issue
Good for newcomers
refactoring
Restructure or improve existing code
It's since kryo 5 it's for good reasons the default to register classes, for more details see
EsotericSoftware/kryo#398
In KryoPersistence.java#81 remove the line and add registration for all used classes.
The text was updated successfully, but these errors were encountered: