06/01/2022, 2:09 PM
I'm trying out the new migrate to a self contained vault and keep getting a EBUSY error. I assume this is a Windows error but no other program should be accessing the files at the moment. Any advice please?


06/01/2022, 3:36 PM
can you share the
diagnostics report
when you run the migrate command? tag @SeriousBug here for visibility


06/01/2022, 3:40 PM
Yeah let me raise a GitHub issue as I don't have discord on my work laptop and don't fancy typing it up, I might also need to remove some paths/hostnames for security but will keep the main content
I just did the migration manually anyway so no real concern I should be able to reproduce as needed from a specific commit I'd those logs aren't what you need


06/01/2022, 3:54 PM
I'll try to reproduce this in Windows to see if it's a Windows-only problem. On UNIX systems renaming a folder wouldn't cause an EBUSY error which is what the migration does, but looks like it might on Windows. Thanks for the report!
Huh interesting, I don't get EBUSY but I get EPERM. I'll dig into this to figure out why, again thanks for the report. Edit: Oh, and trying to rename the folder manually while VSCode is open gives me an error that the folder is busy. I guess for Windows we'll have to take a different approach, I'll look into it.