Keybase filesystem errors

[write something useful and descriptive here]
Wow, that's a high bar :)

I expect this is a macOS Sierra beta issue. Upon first start, there was an error popup. I don't recall the wording, so hopefully the log does. I believe it was saying something about kext stuff not working. I clicked through figuring there'd be a submit diagnostics button or something, but instead the client app just opened up the rest of the way and things seemed fine.

A bit later I tried out the Keybase filesystem, and at that point things started hanging. In particular, in a terminal window I hit tab to path complete /keybase and the terminal hung. Control-C wouldn't break out, had to close the window. Started another, didn't do completion, but just tried a ls on the example /keybase/public/chris directory. Same hang happened. Tried a couple more variants, same result, I think one eventually timed out with a "Device not configured", so I rebooted. After reboot, I could do a ls, open, etc. without hangs, but /keybase is empty, and direct patch attempts got things like:

[rob@Leo ~]$ open /keybase/public/chris
The file /keybase/public/chris does not exist.
[rob@Leo ~]$ cd /keybase/public/chris
-bash: cd: /keybase/public/chris: Permission denied

So seems the filesystem mount didn't happen. Will try a client reinstall and pay more attention, but figure it is a Sierra issue.

[update: so as I went back to re download and try the install again to get better data, I see a little badge now I didn't notice a few hours ago: MAC OS BETA TESTERS Keybase isn't compatible with the macOS "Sierra" beta yet. Hang in there.

heh. So, yeah. Nevermind?]

my log id: fb50a3e14e5521029810c21c

The report concerns KBFS mounting and terminal hangs on macOS Sierra beta, with log id fb50a3e14e5521029810c21c. The update says the client was not compatible with the Sierra beta; no actionable code location or test is named, so compatibility status is the relevant resolution.