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

Failure to process a drive with old, invalid entries #337

Open
domob1812 opened this issue May 21, 2023 · 0 comments
Open

Failure to process a drive with old, invalid entries #337

domob1812 opened this issue May 21, 2023 · 0 comments

Comments

@domob1812
Copy link

domob1812 commented May 21, 2023

I'm using Ardrive CLI 1.22.0. I have a massive, private drive that was created a long time ago (ID is b25a41bc-1b0d-4697-83ff-6805e1f0472a). Due to bugs in an ancient version of Ardrive (not sure if it was the web or the old "sync" CLI), I have some entries in the drive that fail to properly decrypt. All of them have been superseded by later transactions, overriding the same entity, providing correct data.

The old "sync" CLI is able to handle this drive. I wasn't able to sync it with the web app, which might be just due to the size of the drive (171 GB and 50k files), or perhaps this same issue. With Ardrive CLI, when I try to list-folder the root folder (or any other operation), it fails with:

Error decrypting file data
SyntaxError: Unexpected token 'E', "Error" is not valid JSON
Error decrypting file data
Error decrypting file data
Error decrypting file data
Error decrypting file data
Error decrypting file data
Error decrypting file data

I think the CLI should be able to process my drive. Ideally it should just ignore transactions with data it can't decrypt, which in my case would be fine since those entities will receive proper data in a later transaction anyway.

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