Andrew Osheroff

@sammacbeth As @mafintosh mentioned the FUSE components of the daemon won't work on Windows now (though hopefully we'll have support for that in the future), but the daemon installation and...

Thanks for the report @brechtcs, can you give me the output of `hyperdrive status` so I know what daemon/client version you're using?

Ah yeah GRPC error code 13 is the very informative "Internal" error, and if the daemon gets shut down (or crashes) it looks like this is how that error propagates...

The story around deletions is indeed very incomplete right now. There's one cleanup command that can be run when the daemon's offline (`hyperdrive cleanup:remove-readonly-drives`) that will remove all readonly drives....

Thanks all -- at the end of the day, we decided to drop the telemetry a few weeks back when the daemon moved out of the "beta" stage. Ultimately we'd...

Hey @paul90 thanks for this. There are a few separate issues in here so I'll try to pick them apart. For the FUSE one, In 1.13.12 we updated `fuse-setup` so...

Thanks @edrex. `hyperdrive stop` should do a full cleanup (it calls `pm2.delete` internally, which to my understanding should remove all traces of the process). I've noticed that this can bug...

Hey @juliangruber, thanks for this. In the last patch update I'd broken the FUSE API (did a bunch of refactoring and missed a spot). These commands should be fixed in...

Definitely highlights the need for some E2E tests for the FUSE API -- currently that testing is done manually (and can clearly be forgotten...).

Adding this to corestore would definitely simplify getting the temporary cores hooked up to networking, but as @mafintosh said it'd come with a complexity cost. I think the need for...