Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[Java] print read objects when deserialization fail for better trouble shooting #1419

Closed
chaokunyang opened this issue Mar 23, 2024 · 0 comments · Fixed by #1420
Closed

[Java] print read objects when deserialization fail for better trouble shooting #1419

chaokunyang opened this issue Mar 23, 2024 · 0 comments · Fixed by #1420
Labels
enhancement New feature or request

Comments

@chaokunyang
Copy link
Collaborator

Is your feature request related to a problem? Please describe.

Currently when deserialization fail, it's hard to locate which object deserialization failed. We must debug locally line by line to find the issue.

Describe the solution you'd like

We can carry with read objects in exception, so when this exception is printed, we can know which objects are serialized correctly. Then we more close to the root cause.

Additional context
@chaokunyang chaokunyang added the enhancement New feature or request label Mar 23, 2024
@chaokunyang chaokunyang mentioned this issue Mar 23, 2024
Merged
chaokunyang added a commit that referenced this issue Mar 23, 2024
@chaokunyang
feat(java): carry read objects when deserialization fail for better t…
ab8f480 
…rouble shooting (#1420)

This PR carry read objects when deserialization fail for better trouble
shooting.

Closes #1419
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
1 participant
@chaokunyang