--
--
To unsubscribe, email repo-discuss...@googlegroups.com
More info at http://groups.google.com/group/repo-discuss?hl=en
---
You received this message because you are subscribed to the Google Groups "Repo and Gerrit Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to repo-discuss...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
On 5 Apr 2018, at 11:20, Sven Selberg <sven.s...@axis.com> wrote:What you will probably find in the error log is a MissingObjectException.What kind of GC are you doing on the repositories and which Gerrit version are you using?What does git fsck on the repo server side show?If you prune the repos and are running a Gerrit version <=v2.13 it could be this bug https://bugs.chromium.org/p/gerrit/issues/detail?id=6965
BRSven Selberg
On Thursday, April 5, 2018 at 11:20:17 AM UTC+2, suman...@gmail.com wrote:
Thanks for the support
we checked the error_log , we did not find any error code :500 , error message is broken link from commit a27ef8 (refs/heads/develop@{1522387485})
to tree c1ed4a1ac (refs/heads/develop@{1522387485}:)
On Thursday, April 5, 2018 at 12:06:23 PM UTC+5:30, suman...@gmail.com wrote:
Hi Team,
we need your help to resolve the broken links from commit to tree ?
and we try to clone the project ,getting the below error once . we already did the git fsckfatal: internal server error
remote: internal server error
fatal: early EOF
fatal: index-pack failed
Can anyone help on this problem
On Thursday, April 5, 2018 at 12:06:23 PM UTC+5:30, suman...@gmail.com wrote:
Hi Team,
we need your help to resolve the broken links from commit to tree ?
and we try to clone the project ,getting the below error once . we already did the git fsckfatal: internal server error
remote: internal server error
fatal: early EOF
fatal: index-pack failed
Can anyone help on this problem
To unsubscribe, email repo-disc...@googlegroups.com
On 5 Apr 2018, at 12:33, Sven Selberg <sven.s...@axis.com> wrote:
@LucaI don't remember ever filing the bug to JGit and I cannot find an issue about it.