{"thread":{"id":"16157","subject":"git clone over HTTP failing one time out of four","startedAt":"2008-11-03T21:25:15Z","lastAt":"2008-11-03T21:25:15Z","messageCount":1,"participants":["Bryan Larsen"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"94813","messageId":"490F6C3B.4020108@larsen.st","threadId":"16157","inReplyTo":null,"subject":"git clone over HTTP failing one time out of four","fromName":"Bryan Larsen","fromEmail":"bryan@larsen.st","sentAt":"2008-11-03T21:25:15Z","receivedAt":"2008-11-03T21:25:15Z","isPatch":false,"sender":{"key":"bryan@larsen.st","avatar":"https://avatars.githubusercontent.com/u/32073?v=4"},"body":"Given the discussion about HTTP clones on October 12th, this isn't a \nhuge surprise, but I thought I'd throw this out there.\n\nI've been doing a large number of clones of \nhttp://repo.or.cz/r/kdebase.git.  Approximately 1 time in 4 this fails \nwith an error like:\n\nerror: Unable to find fdb3... under http://repo.or.cz/r/kdebase.git\nCannot obtain needed tree fdb3...\nwhile processing commit 3ce5...\n\nI assume that repo.or.cz has the post hooks properly set up to do \nupdate-server-info.   Perhaps more is needed?\n\nkdebase.git is the largest tree I could find, so the clone takes a long \ntime to complete, and changes are being pushed regularly.\n\nBryan\n"}]}