You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug hyperdrive start command keeps running (I only let it run for 5 minutes).
hyperdrive-daemon/1.13.13 linux-x64 node-v12.17.0
To Reproduce
I installed hyperdrive using the command : npm i hyperdrive-daemon -g
I purged my ~/Hyperdrive and ~/.hyperdrive (which might have originally been created by beaker browser) hyperdrive start
Expected Behavior
I expected the hyperdrive start to complete in a few seconds.
** OS **
Ubuntu 18.04 LTS
** Node version **
v12.17.0
** Was the daemon installed from NPM or bundled with Beaker? **
Installed via NPM
Add any other context about the problem here.
Important Note: Daemon errors are likely to be found in ~/.hyperdrive/log.json or ~/.hyperdrive/output.log (the latter is for unexpected, non-JSON output). These files might contain sensitive drive keys, so don't upload the whole thing -- just extract any stack traces or odd error messages!
The text was updated successfully, but these errors were encountered:
Describe the bug
hyperdrive start
command keeps running (I only let it run for 5 minutes).To Reproduce
I installed hyperdrive using the command :
npm i hyperdrive-daemon -g
I purged my
~/Hyperdrive
and~/.hyperdrive
(which might have originally been created by beaker browser)hyperdrive start
Expected Behavior
I expected the hyperdrive start to complete in a few seconds.
** OS **
Ubuntu 18.04 LTS
** Node version **
v12.17.0
** Was the daemon installed from NPM or bundled with Beaker? **
Installed via NPM
Add any other context about the problem here.
Important Note: Daemon errors are likely to be found in
~/.hyperdrive/log.json
or~/.hyperdrive/output.log
(the latter is for unexpected, non-JSON output). These files might contain sensitive drive keys, so don't upload the whole thing -- just extract any stack traces or odd error messages!The text was updated successfully, but these errors were encountered: