Keybase reads causing Alfred not to work correctly
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
I noticed that Alfred 2 wasn't responding to its hotkey, so I tried quitting and relaunching it; no joy. But I noticed the Alfred hotkey seemed to trigger a Keybase read timeout notification, albeit with a significant delay. Quitting Keybase via the menubar item immediately resolved the issue, and it did not begin again when I relaunched Keybase.app (and thus the menubar app).
Seems likely this has something to do with kbfuse and possibly Spotlight, since Alfred uses Spotlight for file indexing and I have it set to index a directory in my Keybase public folder.
my log id: 10a424bb546f37e2fe9a9f1c
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with log id 10a424bb546f37e2fe9a9f1c and reproduce the delayed Alfred hotkey while Keybase, kbfuse, and Spotlight index a Keybase public folder. Investigate the reported interaction between Keybase reads and Spotlight, with the issue resolved when Alfred responds normally while Keybase is running.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, macos
- Domain
- desktop, search
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100