Beaker: Can't load any hyperdrives

[aadilayub]

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:

1. Install the new Beaker beta on Windows or Linux
2. Set up your profile
3. After some time (perhaps an hour), try to open your profile feed in Beaker.

Screenshots
Linux:

Windows:

Desktop (please complete the following information):

• OS: Windows, Ubuntu 20.04
• Version: Beaker v1.0.0-prerelease.1

Additional context
This happened to me on both Linux and Windows. On Linux, I installed Beaker by building from source.

[aadilayub]

Possibly related: Webterm doesn't load while in this state

Console output on launching webterm:

  <rejected> TypeError: Cannot read property 'browserView' of null
      at findContainingWindow$1 (/home/aadil/Applications/beaker/app/main.build.js:10735:33)
      at App.<anonymous> (/home/aadil/Applications/beaker/app/main.build.js:8651:22)
} reason: TypeError: Cannot read property 'browserView' of null
    at findContainingWindow$1 (/home/aadil/Applications/beaker/app/main.build.js:10735:33)
    at App.<anonymous> (/home/aadil/Applications/beaker/app/main.build.js:8651:22)
error:    Unhandled Rejection at: Promise [object Promise] reason: TypeError: Cannot read property 'browserView' of null {"category":"browser"}

[programmarchy]

@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.

[aadilayub]

@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

[pfrazee]

@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?

[aadilayub]

@aadilayub Do you get the "daemon not available" in your settings?

@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.

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?

nope

[aadilayub]

okay i think @programmarchy was right. I restarted beaker on both linux and windows and that fixed things

[pfrazee]

Yeesh. Maybe some bugs with the daemon surfacing here.

[aadilayub]

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:

aadil@x230:~/Applications/beaker/scripts$ npm start

> beakerbrowser@ start /home/aadil/Applications/beaker/scripts
> gulp start

[20:07:31] Using gulpfile ~/Applications/beaker/scripts/gulpfile.js
[20:07:31] Starting 'start'...
[20:07:31] Starting '<anonymous>'...
Spawning electron /home/aadil/Applications/beaker/scripts/node_modules/electron/dist/electron
info:     Logger started
info:     Initializing databases {"category":"browser","subcategory":"init"}
info:     Starting hyperdrive {"category":"browser","subcategory":"init"}
info:     Failed to connect to an external daemon. Launching the daemon... {"category":"hyper","subcategory":"daemon"}
info:     Starting daemon process, assuming process control {"category":"hyper","subcategory":"daemon"}
2020-05-15T20:07:58: PM2 log: Launching in no daemon mode
2020-05-15T20:07:58: PM2 error: (node:32604) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
2020-05-15T20:07:58: PM2 error: (node:32604) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
2020-05-15T20:07:58: PM2 log: App [hyperdrive:0] starting in -fork mode-
2020-05-15T20:07:58: PM2 log: App [hyperdrive:0] online
info:     Failed to connect to daemon, retrying {"category":"hyper","subcategory":"daemon"}
info:     Failed to connect to daemon, retrying {"category":"hyper","subcategory":"daemon"}
info:     Initialized dat daemon {"category":"hyper","subcategory":"drives"}
info:     Initializing hyperdrive filesystem {"category":"browser","subcategory":"init"}
info:     Loading root drive {"category":"hyper","subcategory":"filesystem","url":"hyper://-/"}
info:     Initializing Web APIs {"category":"browser","subcategory":"init"}
info:     Initializing browser {"category":"browser","subcategory":"init"}
info:     Registering protocols {"category":"browser","subcategory":"init"}
info:     Running setup flow {"category":"browser","subcategory":"init"}
info:     Initializing window menu {"category":"browser","subcategory":"init"}
info:     Initializing context menus {"category":"browser","subcategory":"init"}
info:     Initializing tray icon {"category":"browser","subcategory":"init"}
info:     Initializing browser windows {"category":"browser","subcategory":"init"}
info:     Initializing downloads manager {"category":"browser","subcategory":"init"}
info:     Initializing permissions manager {"category":"browser","subcategory":"init"}
info:     Program setup complete {"category":"browser","subcategory":"init"}
info:     Hyperdrive daemon has been restored {"category":"hyper","subcategory":"daemon"}
info:     Destroyed browser window that attempted to navigate to https://beaker.dev/ {"category":"browser"}
2020-05-15T20:08:03: PM2 log: TypeError: Object has been destroyed
info:     Destroyed browser window that attempted to navigate to https://github.com/beakerbrowser/beaker/discussions {"category":"browser"}
2020-05-15T20:08:03: PM2 log: TypeError: Object has been destroyed
info:     Destroyed browser window that attempted to navigate to https://docs.beakerbrowser.com/ {"category":"browser"}
2020-05-15T20:08:03: PM2 log: TypeError: Object has been destroyed
2020-05-15T20:08:05: PM2 log: TypeError: Object has been destroyed
2020-05-15T20:08:05: PM2 log: TypeError: Object has been destroyed
2020-05-15T20:08:05: PM2 log: TypeError: Object has been destroyed
2020-05-15T20:08:27: PM2 log: TypeError: Object has been destroyed
2020-05-15T20:08:27: PM2 log: TypeError: Object has been destroyed
2020-05-15T20:08:48: PM2 log: TypeError: Object has been destroyed
2020-05-15T20:08:48: PM2 log: TypeError: Object has been destroyed

(The TypeErrors at the bottom are from #1585)

[pfrazee]

@aadilayub small thing but might be helpful, the Destroyed browser window that attempted to navigate to errors in the log were a bug that _should_ have been fixed before release, just want to check in that you're on latest master

[aadilayub]

Hmm it looks like I'm on the latest master

[pfrazee]

Okay must not have nailed that other bug yet.

[mafintosh]

This sounds a lot to me like the session mismatch bug that’ll be fixed in the next release

[aadilayub]

It’s likely that this is a duplicate of #1625, should I close?

[pfrazee]

@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.

[aadilayub]

Ah, yes. I can load my own drives.

[pfrazee]

Good deal

On Sat, May 23, 2020 at 11:37 AM Aadil Ayub [e-mail]
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
https://github.com/beakerbrowser/beaker/issues/1579#issuecomment-633090305,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJWCU2FIMLBSNOT7DRSSNTRS73TTANCNFSM4NBO2J6A
.