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.

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

Add FAQs for debugging msgpack serialization issues #487

Open
ThetaSinner opened this issue Apr 10, 2024 · 4 comments
Open

Add FAQs for debugging msgpack serialization issues #487

ThetaSinner opened this issue Apr 10, 2024 · 4 comments

Comments

@ThetaSinner
Copy link
Member

We often get questions about how to debug serialization issues. The first few times you face them it can be challenging to figure out what the problem is. With msgpack being a binary protocol, it's a bit more tricky to figure out than something like JSON would be. At this point though, we (core team) have a pretty well-established process for debugging these issues. We should write these steps up as an FAQ page to help people figure these problems out.

@ThetaSinner
Copy link
Member Author

ThetaSinner commented Apr 10, 2024

I also got a suggestion recently from @alastairong that we make error serialization messages more readable or easier to debug. At the moment we dump the msgpack binary which you do need but it isn't readable. Perhaps we could consider dumping a readable representation, as long as that doesn't introduce more confusion with ambiguous encodings to another format like JSON. Something to think about and maybe split into another ticket at some point

Copy link

This item has been open for 30 days with no activity.

@ThetaSinner
Copy link
Member Author

Depends on holochain/holochain#3597

Copy link

This item has been open for 30 days with no activity.

@jost-s jost-s transferred this issue from holochain/holochain Oct 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Backlog
Development

No branches or pull requests

1 participant