Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

push failed for branch (n/a (unpacker error)) #704

Closed
gitblit opened this issue Aug 12, 2015 · 7 comments
Closed

push failed for branch (n/a (unpacker error)) #704

gitblit opened this issue Aug 12, 2015 · 7 comments

Comments

@gitblit
Copy link
Owner

gitblit commented Aug 12, 2015

Originally reported on Google Code with ID 408

What steps will reproduce the problem?
see below

What is the expected output? What do you see instead?
I am using git-flow and need to push & pull develop and master branch from gitblit.
It works fine several days ago but right now it produce
errors for develop branch (only for push, pull seems fine). The error messhage looks
like (master branch is exactly fine!!!)
 [remote rejected] develop -> develop (n/a (unpacker error))
updating local tracking ref 'refs/remotes/origin/master'
error: failed to push some refs to 'https://admin@xx.xx.xx.xx:xxxx/r/~xxx/workplace.git'

I try other branch (newly created), also shows the same message. And the same probelm
for all other repository.

I then try to restart the gitblit and windows, nothing changes...

I also try to delete the repository from the webUI, it shows error messages too. 

What version of the product are you using? On what operating system?

v1.4.1 (windows 7 64bit)

Please provide any additional information below.


Reported by ray4working on 2014-04-17 00:49:57

@gitblit
Copy link
Owner Author

gitblit commented Aug 12, 2015

This appears to be a bug in JGit [1, 2].  You didn't share the server-side stacktraces,
but I will assume they each point to the same thing: missing tree or missing blob.

Newer git clients are optimized to send less data on the wire.  JGit doesn't like this
at the moment.  There is a receive pack setting which may help, but Gitblit does not
allow you to configure it.  I will take care of that later today for the upcoming 1.5.0
release, but that is just a workaround.  To really fix this issue, JGit has to be updated
to handle the newer git client optimizations.

For now, it looks like the current client-side recommendation is to downgrade your
git client to an older version that isn't as smart/optimized.  It looks like 1.8.3
or older might work.

[1]: https://code.google.com/p/gerrit/issues/detail?id=2296
[2]: https://code.google.com/p/gerrit/issues/detail?id=1582

Reported by James.Moger on 2014-04-17 13:19:03

@gitblit
Copy link
Owner Author

gitblit commented Aug 12, 2015

I've pushed changes to master to expose the newer receivepack settings, but like I said,
this is a workaround. The real fix needs to be implemented by the JGit team within
JGit's internals.

Reported by James.Moger on 2014-04-17 16:07:12

  • Status changed: Started

@gitblit
Copy link
Owner Author

gitblit commented Aug 12, 2015

Hi, Thank you very much.
I've done a clean installation yesterday (remove everything and push repos after clean
installation), so it is hard to directly test whether an older git client can solve
the problem(e.g. downgrade)at the moment. However, I am using sourcetree and the internal
git client is version 1.8.3 (so it seems that an even older version might be better,
though I have not tried them yet).
btw, I will built your updated version to see if it can reduce the problems(at least
temporarily). 
Do I need to also report this issue to JGIT? 

Reported by ray4working on 2014-04-18 00:45:27

@gitblit
Copy link
Owner Author

gitblit commented Aug 12, 2015

It has already been reported to Bugzilla [1].  Now we'll have to see when it gets resolved.
 :)

[1]: https://bugs.eclipse.org/bugs/show_bug.cgi?id=422988

Reported by James.Moger on 2014-04-18 01:09:29

@gitblit
Copy link
Owner Author

gitblit commented Aug 12, 2015

This is a shitty bug.  I get hit by it a few times a month.  Disabling the reachable
check is the workaround until a fix lands in JGit. I've updated the FAQ - this is now
the first entry.

Reported by James.Moger on 2014-06-17 00:32:21

@gitblit
Copy link
Owner Author

gitblit commented Aug 12, 2015

Appears to now be fixed upstream, in link from comment 4.

Reported by soruk42 on 2014-11-24 18:29:58

@gitblit
Copy link
Owner Author

gitblit commented Aug 12, 2015

Release 1.6.1 included the updated JGit with the fix.

Reported by James.Moger on 2015-03-07 15:47:32

  • Status changed: Fixed
  • Labels added: Milestone-1.6.1

@gitblit gitblit closed this as completed Aug 12, 2015
@flaix flaix modified the milestone: 1.6.1 Dec 13, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants