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

better handling of hex encoding #2

Open
bap2pecs opened this issue Aug 7, 2024 · 0 comments
Open

better handling of hex encoding #2

bap2pecs opened this issue Aug 7, 2024 · 0 comments

Comments

@bap2pecs
Copy link
Member

bap2pecs commented Aug 7, 2024

if we have one key that's a byte array whose hex-encoded form is eacf2435ba6c2a29a58aba776e3cccbe7c54def6402518e63e9b3b042dbefcc4 and another key which is simply a string "eacf2435ba6c2a29a58aba776e3cccbe7c54def6402518e63e9b3b042dbefcc4", it will still display only one of them in the GUI

and this can lead to confusion b/c there are two data entries but we only show one

This already caused some trouble when we were debugging why FP daemon cannot start ("Err: cannot parse invalid wire-format data") even after we did the DB migration. it turned out that there is still a string key that we forgot to delete

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant