Re: Meaning of "fatal: protocol error: bad line length character"?
- From
Bill Lear <rael@zopyra.com>
- Date
- Jan 22, 2007, 18:58 UTC
- Message-ID
- <17845.2402.105688.56648@lisa.zopyra.com>
- In-Reply-To
- <7v7ivh77md.fsf@assigned-by-dhcp.cox.net>
On Saturday, January 20, 2007 at 12:42:18 (-0800) Junio C Hamano writes:
Show 16 quoted lines
>Junio C Hamano <junkio@cox.net> writes: >... >That was output to stdout made from the update hook in my case. >I do not know your setup, but if you make sure your update hook >does not spit out anything to its stdout (diag can go to stderr), >you should be able to work it around. > >Funny thing is, at least in recent enough git, I think we set up >redirection to force output from hook scripts to stderr, but I >do not remember when it happened. Let's see... > > ...goes and looks... > >That was supposed to have been fixed with commit cd83c74c (Dec >30, 2006), but this indicates the fix is not working at all when >your login shell is tcsh. ...
One of our developers who uses bash is seeing this error in his pushes from his private repo to his public repo, through the file system.
Here is one example he conveyed:
% git push error: remote 'refs/heads/master' is not a strict subset of local ref 'refs/heads/master'. maybe you are not up-to-date and need to pull first? error: remote 'refs/heads/origin' is not a strict subset of local ref 'refs/heads/origin'. maybe you are not up-to-date and need to pull first? updating 'refs/heads/fig_mt_1' from 85f1ff556f95b0177e69f99d1196a2db26213812 to 0a5a7ac9b81a90500b9c9c44a22793890513cd5a Generating pack... Done counting 16 objects. Result has 10 objects. Deltifying 10 objects. 100% (10/10) done Writing 10 objects. 100% (10/10) done Total 10, written 10 (delta 6), reused 0 (delta 0) Unpacking 10 objects 100% (10/10) done fatal: protocol error: bad line length character xiphi:~/devel/fig_mt_1/fusion | fig_mt_1 % refs/heads/fig_mt_1: 85f1ff556f95b01 77e69f99d1196a2db26213812 -> 0a5a7ac9b81a90500b9c9c44a22793890513cd5a
In this case, he forgot to limit the push to his fig_mt_1 branch, but last night he did a similar push (git push origin fig_mt_1), and got the same bad line length character error report. His pushes seem to be propagating, but he's a bit nervous nonetheless.
He has an active update hook in his public repo, to send notices to his collaborators when his work is ready for them to pull, but we looked through it and don't see any printing to stdout.
Bill