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
Method calls from a Hyperdrive instance hang indefinitely if the Hyperdrive Daemon was stopped or crashed. Because the HyperdriveClient is
To Reproduce
Node REPL with --experimental-repl-await flag enabled, if necessary:
>const{ HyperdriveClient }=require("hyperdrive-daemon-client");>constclient=newHyperdriveClient;>awaitclient.ready();>constdrive=awaitclient.drive.get();>awaitdrive.readdir();[]>// In another terminal, stop the Hyperdrive Daemon// Back in the first terminal, repeat:>awaitclient.readdir();
Expected Behavior
Eventual timeout and error, similar to HyperdriveClient.ready when the Hyperdrive Daemon is stopped or crashed.
OS
Windows 10
Node version
14.3.0
Was the daemon installed from NPM or bundled with Beaker?
NPM