--
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/repo-discuss/7d2e8894-cc5f-4f11-a941-88260d6bb5a1n%40googlegroups.com.
Hello,
After a major upgrade from 2.11.2 -> 3.4 there is a new behavior that sometimes happens.Is there some new functionality or changes to the way Gerrit handles commits that causes this error to happen more often than not? It did not happen almost ever in 2.11.2.
Thanks!
```
remote: Counting objects: 62004, done
error: remote unpack failed: error Missing tree
123344a567b889a900c2934785
fatal: Unpack error, check server log```
Thanks Nassar,
Nassar, unfortunately nothing in error_log, but Clark hit the nail on the head (so it seems).
On Jul 28, 2021, at 11:32 AM, Nate Dreier <ndr...@maystreet.com> wrote:Ah okay, I found some error related to this. They are pretty close to identical.
Is there much debugging that can be done given this is a bug with JGit? They are able to successfully push when using --no-thin
Though is this can be remedied without the above workaround that would be sweet!nateOn Wednesday, July 28, 2021 at 10:23:23 AM UTC-7 clark....@gmail.com wrote:On Wed, Jul 28, 2021 at 10:13 AM Nate Dreier <ndr...@maystreet.com> wrote:Thanks Nassar,
Nassar, unfortunately nothing in error_log, but Clark hit the nail on the head (so it seems).I was able to dig up logs from a recent occurrence on our server and have attached them. I've edited them to remove any specific info, but if necessary we can probably share more. These logs were generated by Gerrit 3.2.11-7-gb1242861dd-dirty. The user reported they were running Ubuntu Focal's git version 2.25.1.On Wednesday, July 28, 2021 at 9:50:42 AM UTC-7 nas...@codeaurora.org wrote:On Jul 28, 2021, at 10:47 AM, Nate Dreier <ndr...@maystreet.com> wrote:Hello,
After a major upgrade from 2.11.2 -> 3.4 there is a new behavior that sometimes happens.Is there some new functionality or changes to the way Gerrit handles commits that causes this error to happen more often than not? It did not happen almost ever in 2.11.2.
Thanks!
```
remote: Counting objects: 62004, done
error: remote unpack failed: error Missing tree
123344a567b889a900c2934785
fatal: Unpack error, check server log```Hey Nate,Many many things changed between 2.11 and 3.4. It might be hard to narrow it down.What’s the server-side error in error_log that’s recorded when this happens?Thanks,Nasser
--
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/repo-discuss/e262d1e2-6055-4d18-8b54-70d5bdc03126n%40googlegroups.com.
On Jul 28, 2021, at 12:02 PM, Nate Dreier <ndr...@maystreet.com> wrote:Oh thanks! I appreciate all that extra info. What do you mean by "security tradeoff"? What exactly is JGit checking per push?
To view this discussion on the web visit https://groups.google.com/d/msgid/repo-discuss/6cfe3256-95e7-4be2-ad46-d209ac8b2fd9n%40googlegroups.com.
On Jul 28, 2021, at 11:32 AM, Nate Dreier <ndr...@maystreet.com> wrote:Ah okay, I found some error related to this. They are pretty close to identical.
Is there much debugging that can be done given this is a bug with JGit? They are able to successfully push when using --no-thinAh yes, this classic issue. You can see in https://git.eclipse.org/r/c/jgit/jgit/+/31081 that it was fixed at some point, but that fix introduced an enormous performance problem. The solution needs someone to spend some serious time in JGit to resolve it without adding a perf penalty. The other workaround that has been used is setting the Gerrit server config “receive.checkReferencedObjectsAreReachable” to false, as you see suggested in https://bugs.chromium.org/p/gerrit/issues/detail?id=1582. That provides a Gerrit-wide solution that doesn’t require clients to change their behavior, but it is a security tradeoff since JGit will do fewer checks on pushes.