| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
| |
Apparently some corruption to an object can cause cat-file to say it's N
bytes long, but only output N-M bytes of data. This causes Git.CatFile
to stall waiting for the rest. To fix, add a 1 minute timeout to the
cat-file, which should be enough time to read any reasonable object.
|
| |
|
|
|
| |
Aguably, I should make cat-file only throw IO exceptions, but currently it
throws some errors too.
|
| | |
|
| |
|
|
|
|
| |
It turned out to be broken, and led to failures.
6d67245728bbbc07ad1eeaf5b3c49f64c6bbcd11 was a better fix for the problem
that code tried to fix.
|
| | |
|
| |
|
|
|
|
|
| |
Sometimes git fsck outputs no shas even with --verbose, but fails, due to
badly corrupt objects. The best thing to do in this situation is to try to
pull and rsync from remotes, hoping that the bad objects will be
overwritten.
|
| |
|
