-
Notifications
You must be signed in to change notification settings - Fork 4
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
Error running updating drive with hyperdrive import
#7
Comments
I wonder, in the readme...
But, running I notice that beaker starts hyperspace with the |
@paul90 Thanks for reporting this -- definitely looks like a bug. Hyperspace actually isn't moving any cores that were previously in Have you tried the new Mind letting me know if |
I had wondered about using But, when I used It also looks as if So, it doesn't look as if |
No, For the drive with the mount, the contents of the mounted drive were deleted as well as the mount point. I will create an issue against the cli for this, and for there being no ignore file support. It also appears to have updated all the files - though this might be due to an issue with original hyperdrive daemon import with files showing, in beaker at least, the date of the import rather than their creation date from the file system. |
Any progress to report on getting this fixed? |
Just trying to update a drive with some updated a hyperdrive that was created with the original hyperdrive daemon, and getting the following error:
drive name shortened, as it's a development drive
The /plugins directory was part of the original import when the drive was created, and the contents have not changes since the last update back in August. And the drive contains a lot more than 55 files!
Running with
--trace-warnings
gives a little extra information, if that helps.The text was updated successfully, but these errors were encountered: