An OS X Notification consistently reports this message when starting the Keybase.app:
/keybase/System is not a Keybase folder. All folders begin with /keybase/private or /keybase/public.
This is likely being triggered by something I have installed that's looking for mounted disks. Based on what I'm seeing with "opensnoop", I would guess Carbon Copy Cloner. Maybe I'll hack up pathopens.d later to find out for sure.
In general, notifications like this are pretty much out of the user's control, especially when it's third party software triggering it. If you can only notify when it is initiated by a user initiated operation (tty linked execution) as opposed to a LaunchAgent/LaunchDaemon, that would be better.
Interesting, it looks like other exceptions are already in the code.
Adding "System" to "var noErrorNames = map[string]bool{" in "kbfs/libkbfs/reporter_kbpki.go" would likely fix this.
An OS X Notification consistently reports this message when starting the Keybase.app: /keybase/System is not a Keybase folder. All folders begin with /keybase/private or /keybase/public.
This is likely being triggered by something I have installed that's looking for mounted disks. Based on what I'm seeing with "opensnoop", I would guess Carbon Copy Cloner. Maybe I'll hack up pathopens.d later to find out for sure.
In general, notifications like this are pretty much out of the user's control, especially when it's third party software triggering it. If you can only notify when it is initiated by a user initiated operation (tty linked execution) as opposed to a LaunchAgent/LaunchDaemon, that would be better.
my log id: cd5c1d799ce79bb59c6b2f1c