{"thread":{"id":"2722","subject":"unexpected EOF?","startedAt":"2005-12-01T13:42:02Z","lastAt":"2005-12-01T18:40:17Z","messageCount":3,"participants":["Jon Loeliger","Tim O'Callaghan","Linus Torvalds"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"13045","messageId":"E1EhohG-0001iZ-IB@jdl.com","threadId":"2722","inReplyTo":null,"subject":"unexpected EOF?","fromName":"Jon Loeliger","fromEmail":"jdl@freescale.com","sentAt":"2005-12-01T13:42:02Z","receivedAt":"2005-12-01T13:42:02Z","isPatch":false,"sender":{"key":"jdl@jdl.com","avatar":"https://gravatar.com/avatar/75ce9a10b151acd2c28ec4ab2136dba7b2ff1634530bd04b155981a749d08a64?d=mp&s=160"},"body":"\nI thought I had imagined this last time, but now \nthat it has happened twice, I'm not so sure what\nis going on.  First pull attempt garners an\nunexpected EOF message; immediately pull again\nseems to work.\n\nSome state:\n\njdl@ubuntu:/usr/src/git-core$ git --version\ngit version 0.99.9j\n\njdl@ubuntu:/usr/src/git-core$ cat .git/remotes/origin\nURL: git://git.kernel.org/pub/scm/git/git.git/\nPull: master:origin\nPull: todo:todo\nPull: maint:maint\nPull: pu:pu\n\nAnd the error capture:\n\njdl@ubuntu:/usr/src/git-core$ git pull origin\nfatal: unexpected EOF\nFetch failure: git://git.kernel.org/pub/scm/git/git.git/\njdl@ubuntu:/usr/src/git-core$ git pull origin\nUnpacking 17 objects\n 100% (17/17) done\n* committish: d175455acaaba6bd39dd2d5ec71961bf238f06d4\n  branch 'todo' of git://git.kernel.org/pub/scm/git/git\n* refs/heads/todo: same as branch 'todo' of git://git.kernel.org/pub/scm/git/git* committish: 93dcab2937624ebb97f91807576cddb242a55a46\n  branch 'maint' of git://git.kernel.org/pub/scm/git/git\n* refs/heads/maint: same as branch 'maint' of git://git.kernel.org/pub/scm/git/git\n* committish: b34403aa97047f90c0cdd5177e63a8e7530e3388\n  branch 'master' of git://git.kernel.org/pub/scm/git/git\n* refs/heads/origin: same as branch 'master' of git://git.kernel.org/pub/scm/git/git\n* committish: 6e35634a4d595d554423b04438bfa8b523414c54\n  branch 'pu' of git://git.kernel.org/pub/scm/git/git\n* refs/heads/pu: does not fast forward to branch 'pu' of git://git.kernel.org/pub/scm/git/git;\n  not updating.\nAlready up-to-date.\n"},{"id":"13046","messageId":"20051201134917.GH2188@ELSAMSW37164","threadId":"2722","inReplyTo":"E1EhohG-0001iZ-IB@jdl.com","subject":"Re: unexpected EOF?","fromName":"Tim O'Callaghan","fromEmail":"timo@dspsrv.com","sentAt":"2005-12-01T13:49:17Z","receivedAt":"2005-12-01T13:49:17Z","isPatch":false,"sender":{"key":"timo@dspsrv.com","avatar":null},"body":"On Thu, Dec 01, 2005 at 07:42:02AM -0600, Jon Loeliger wrote:\n> \n> I thought I had imagined this last time, but now \n> that it has happened twice, I'm not so sure what\n> is going on.  First pull attempt garners an\n> unexpected EOF message; immediately pull again\n> seems to work.\n> \n> Some state:\n> \n> jdl@ubuntu:/usr/src/git-core$ git --version\n> git version 0.99.9j\n> \n> jdl@ubuntu:/usr/src/git-core$ cat .git/remotes/origin\n> URL: git://git.kernel.org/pub/scm/git/git.git/\n> Pull: master:origin\n> Pull: todo:todo\n> Pull: maint:maint\n> Pull: pu:pu\n> \n> And the error capture:\n> \n> jdl@ubuntu:/usr/src/git-core$ git pull origin\n> fatal: unexpected EOF\n> Fetch failure: git://git.kernel.org/pub/scm/git/git.git/\n> jdl@ubuntu:/usr/src/git-core$ git pull origin\n> Unpacking 17 objects\n>  100% (17/17) done\n> * committish: d175455acaaba6bd39dd2d5ec71961bf238f06d4\n>   branch 'todo' of git://git.kernel.org/pub/scm/git/git\n> * refs/heads/todo: same as branch 'todo' of git://git.kernel.org/pub/scm/git/git* committish: 93dcab2937624ebb97f91807576cddb242a55a46\n>   branch 'maint' of git://git.kernel.org/pub/scm/git/git\n> * refs/heads/maint: same as branch 'maint' of git://git.kernel.org/pub/scm/git/git\n> * committish: b34403aa97047f90c0cdd5177e63a8e7530e3388\n>   branch 'master' of git://git.kernel.org/pub/scm/git/git\n> * refs/heads/origin: same as branch 'master' of git://git.kernel.org/pub/scm/git/git\n> * committish: 6e35634a4d595d554423b04438bfa8b523414c54\n>   branch 'pu' of git://git.kernel.org/pub/scm/git/git\n> * refs/heads/pu: does not fast forward to branch 'pu' of git://git.kernel.org/pub/scm/git/git;\n>   not updating.\n> Already up-to-date.\n\n\nI noticed this myself this morning. It happened twice, then after leaving it\nfor a minute or two, it worked. Possibly traffic problems to kernel.org?\n\n\nI should also report that if a spurious lockfile exists (under cygwin at\nleast), git just dies with the cryptic \"unable to create new cachefile\".\n\nTim.\n\"I've worked myself up from nothing to a state of supreme poverty.\"\n-- Groucho Marx\n"},{"id":"13055","messageId":"Pine.LNX.4.64.0512011036120.3099@g5.osdl.org","threadId":"2722","inReplyTo":"E1EhohG-0001iZ-IB@jdl.com","subject":"Re: unexpected EOF?","fromName":"Linus Torvalds","fromEmail":"torvalds@osdl.org","sentAt":"2005-12-01T18:40:17Z","receivedAt":"2005-12-01T18:40:17Z","isPatch":false,"sender":{"key":"torvalds@linux-foundation.org","avatar":"https://avatars.githubusercontent.com/u/1024025?v=4"},"body":"\n\nOn Thu, 1 Dec 2005, Jon Loeliger wrote:\n> \n> I thought I had imagined this last time, but now \n> that it has happened twice, I'm not so sure what\n> is going on.  First pull attempt garners an\n> unexpected EOF message; immediately pull again\n> seems to work.\n> \n> jdl@ubuntu:/usr/src/git-core$ git pull origin\n> fatal: unexpected EOF\n> Fetch failure: git://git.kernel.org/pub/scm/git/git.git/\n> jdl@ubuntu:/usr/src/git-core$ git pull origin\n> Unpacking 17 objects\n\nThe public kernel.org machines are actually _two_ different machines, and \nhave two different addresses:\n\n\tNon-authoritative answer:\n\tgit.kernel.org  canonical name = zeus-pub.kernel.org.\n\tName:   zeus-pub.kernel.org\n\tAddress: 204.152.191.5\n\tName:   zeus-pub.kernel.org\n\tAddress: 204.152.191.37\n\nso with a round-robin kind of DNS resolution, you'd get alternate \nmachines. Maybe one of them isn't up-to-date due to mirroring problems?\n\nYou can test by using the IP addresses explicitly, of course.\n\nIn particular, if the directory doesn't exist at all, or if the directory \ndoesn't have the \"git-daemon-export-ok\" flag, the git daemon on the other \nend will just close the connection and refuse to talk to you (I thought \nthat was preferable to give any indication of why it fails: from a \nsecurity standpoint, you do _not_ want to be able to test if a random \ndirectory exists by looking at the return value of git-daemon).\n\n\t\t\tLinus\n"}]}