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
Crash on decoding value using CLI #1399
Comments
Thanks for the quick reply @jarifibrahim -- I've pulled master and tried to restore the backup, but with the same result:
Should I regenerate the backup? |
Can you make a copy of your data directory and share it with me? I'd like to reproduce the bug on my end. @ammmir Yes, try doing a new backup and restore but please keep the old directory. |
@jarifibrahim unfortunately, I can't send any files since it's customer data. is there anything else that might help you? if nothing else, I'll write my own backup tool to export the data from v1 and reimport to v2, since all I really care about are the keys and values, TTL, and UserMeta. |
Github issues have been deprecated. |
What version of Go are you using (
go version
)?What operating system are you using?
MacOS X
What version of Badger are you using?
2.0.3
Does this issue reproduce with the latest master?
Not tested
What Badger options were set?
default
What did you do?
Database was migrated from manifest v4 to v7 (badger 1.6.0 or thereabouts to 2.0.3) via badger backup/restore.
badger info --dir db --show-keys --with-prefix 019a4730021f457ba087a255a58f49 --read-only=false
What did you see instead?
If
--with-prefix
is omitted it doesn't crash.The text was updated successfully, but these errors were encountered: