-
Notifications
You must be signed in to change notification settings - Fork 545
Can't load any hyperdrives #1579
Comments
@aadilayub I had something similar happen. When I went to beaker://settings/ it told me my daemon was disconnected (had a red error alert on the top of the page). Restarting Beaker resolved the issue for me, but guessing that's the state it's getting into -- communication with daemon is hung / crashed. |
@programmarchy unfortunately restarting didn't seem to fix it for me. The Linux screenshot is just a few seconds after relaunch... Though I agree it's probably the daemon |
@aadilayub Do you get the "daemon not available" in your settings? Is there any chance you ran an earlier version of beaker 1.0 in the past year, or are running a hyperdrive-daemon via the CLI? |
@pfrazee I did for a few seconds but that was yesterday and restarting the daemon fixed it (was able to access all my drives). When I took these screenshots there was no "daemon not available" error in the settings.
nope |
okay i think @programmarchy was right. I restarted beaker on both linux and windows and that fixed things |
Yeesh. Maybe some bugs with the daemon surfacing here. |
Update: few minutes after restart, it's back to not loading drives. Strangely it isn't showing any daemon related errors in the terminal currently, but it did log a few when the browser was starting up:
(The TypeErrors at the bottom are from #1585) |
@aadilayub small thing but might be helpful, the |
Okay must not have nailed that other bug yet. |
This sounds a lot to me like the session mismatch bug that’ll be fixed in the next release |
It’s likely that this is a duplicate of #1625, should I close? |
@aadilayub are you able to load your own drives now? That's what this issue is about, where as #1625 seems to be about loading other people's drives. If you can load your own drives than this one can close as fixed. |
Ah, yes. I can load my own drives. |
Good deal
…On Sat, May 23, 2020 at 11:37 AM Aadil Ayub ***@***.***> wrote:
Ah, yes. I can load my own drives.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1579 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAJWCU2FIMLBSNOT7DRSSNTRS73TTANCNFSM4NBO2J6A>
.
|
Describe the bug
After installing Beaker and creating my profile, I can't load any hyperdrives. They just keep loading indefinitely. Initially, I thought the drives just didn't have any seeds, but I can't even access my own hyperdrives.
To Reproduce
Steps to reproduce the behavior:
Screenshots
Linux:
Windows:
Desktop (please complete the following information):
Additional context
This happened to me on both Linux and Windows. On Linux, I installed Beaker by building from source.
The text was updated successfully, but these errors were encountered: