-
Notifications
You must be signed in to change notification settings - Fork 25
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
Regression between 0.2.0 and 0.2.1: git fetch -> bad line length character: PACK #33
Comments
Seems @prologic had the same issue. Here's an unsolved issue in the go-git issue tracker: And here is a pin of legit on v.0.2.0 that solves the issue by going back before the regression: |
I was never able to solve this, despite the many suggestions and comments. See gitxt |
Hm, looks like the go-git git-upload-pack implementation is a source of constant annoyance. While I haven't run into the bug mentioned here, I am facing a perhaps related issue with UploadPack blowing up the stack and crashing every time someone tries to clone (see: go-git/go-git#1062). I think the intermediate fix until go-git gets their shit together would be to switch back to using the gitkit lib. |
@gl-yziquel Hi, I've tagged a new release that reverts back to using the system's git upload-pack. It of course, requires git to be in PATH. Let me know if this fixes it for you, and if not I'll re-open this. |
Hi.
I determined, recently, that a buggy behaviour of legit was due to a regression between 0.2.0 and 0.2.1.
Problematic behaviour on 0.2.1:
legit is the server serving these git repos.
Correct behaviour on 0.2.0:
Current behaviour on 0.2.2 is still buggy.
The reason seems linked to the following note in the following release:
Release: https://github.com/icyphox/legit/releases/tag/v0.2.1
That same error pops up sporadically: src-d/go-billy#11
The text was updated successfully, but these errors were encountered: