fix(web): Fix "repository not found for file: x" error #761
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
In #537, I added a exception to throw whenever a orphaned shard* was found during search. One way or another, some users had their SB instances get into a weird state where
.sourcebot/indexand the database got out of sync, resulting in this exception hitting and search completely breaking.Solution
This PR relaxes the exception into a error message s.t., we don't completely error out; it does not address the underlying cause for the shards and database getting out of sync. We could address this desync by checking for orphaned shards at startup and deleting them, but I would first like to gather some data on how often this is happening in the first place. To that end, I've added the posthog event
wa_repo_not_found_for_zoekt_file.What do I do if I'm getting this error?
If you are hitting the above error message (will look like
Unable to find repository x in database for file y), then the best course of action is to wipe your.sourcebot/indexfolder and re-index all repositories.Fixes #669