Hardened repository corruption handling
Improved repository availability with enhanced corruption detection, safer optimization coordination, and atomic recovery.

Improved repository availability with enhanced corruption detection, safer optimization coordination, and atomic recovery.
To improve support for the largest codebases, Sourcegraph is now significantly more resilient to repository corruption events.
We have made coordinated improvements across optimization, corruption detection, and recovery so repositories stay available and searchable in more scenarios.
Repository corruption can occur when Git objects are missing or corrupted. This can happen for many reasons, including incomplete or interrupted clones/fetches, filesystem corruption, or other disk issues. When Git objects are missing or corrupted, Sourcegraph operations that require those objects (such as listing a repository directory tree, retrieving files, resolving references, or searching commits) can fail.
Here's what changed:
git fetch).You can monitor this recovery process from the repository settings page, which now reports reclone progress directly in the UI.