{"thread":{"id":"18133","subject":"[PATCH] Clarify the \"cannot lock existing info/refs\" error","startedAt":"2009-03-04T15:37:06Z","lastAt":"2009-03-05T08:50:52Z","messageCount":4,"participants":["John Tapsell","Clemens Buchacher"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"106986","messageId":"1236181026-15385-1-git-send-email-johnflux@gmail.com","threadId":"18133","inReplyTo":null,"subject":"[PATCH] Clarify the \"cannot lock existing info/refs\" error","fromName":"John Tapsell","fromEmail":"johnflux@gmail.com","sentAt":"2009-03-04T15:37:06Z","receivedAt":"2009-03-04T15:37:06Z","isPatch":true,"sender":{"key":"johnflux@gmail.com","avatar":"https://gravatar.com/avatar/25f70d4c0f96396b84a2e34bcd9bdc233462c7b4be29b5fdca8266fc53f30b0c?d=mp&s=160"},"body":"---\n http-push.c |    2 +-\n 1 files changed, 1 insertions(+), 1 deletions(-)\n\ndiff --git a/http-push.c b/http-push.c\nindex 30d2d34..6666956 100644\n--- a/http-push.c\n+++ b/http-push.c\n@@ -2293,7 +2293,7 @@ int main(int argc, char **argv)\n \t\tif (info_ref_lock)\n \t\t\tremote->can_update_info_refs = 1;\n \t\telse {\n-\t\t\tfprintf(stderr, \"Error: cannot lock existing info/refs\\n\");\n+\t\t\terror(\"cannot lock existing info/refs on remote server\\nPerhaps the server is currently busy, or your ~/.netrc file is not configured correctly.\");\n \t\t\trc = 1;\n \t\t\tgoto cleanup;\n \t\t}\n-- \n1.6.2.rc2.23.g77740\n"},{"id":"107003","messageId":"20090304192853.GA10567@localhost","threadId":"18133","inReplyTo":"1236181026-15385-1-git-send-email-johnflux@gmail.com","subject":"Re: [PATCH] Clarify the \"cannot lock existing info/refs\" error","fromName":"Clemens Buchacher","fromEmail":"drizzd@aon.at","sentAt":"2009-03-04T19:28:53Z","receivedAt":"2009-03-04T19:28:53Z","isPatch":true,"sender":{"key":"drizzd@gmx.net","avatar":"https://avatars.githubusercontent.com/u/59082?v=4"},"body":"On Wed, Mar 04, 2009 at 03:37:06PM +0000, John Tapsell wrote:\n> -fprintf(stderr, \"Error: cannot lock existing info/refs\\n\");\n> +error(\"cannot lock existing info/refs on remote server\\nPerhaps the\n> server is currently busy, or your ~/.netrc file is not configured\n> correctly.\");\n\nIn my experience this is usually caused by http-push crashing and leaving\nstale locks behind until it times out after 10 minutes. I don't think we\nshould speculate here unless we can narrow down the error condition.\n"},{"id":"107026","messageId":"43d8ce650903050000g4466ab2fne5fb8ed009808346@mail.gmail.com","threadId":"18133","inReplyTo":"20090304192853.GA10567@localhost","subject":"Re: [PATCH] Clarify the \"cannot lock existing info/refs\" error","fromName":"John Tapsell","fromEmail":"johnflux@gmail.com","sentAt":"2009-03-05T08:00:37Z","receivedAt":"2009-03-05T08:00:37Z","isPatch":true,"sender":{"key":"johnflux@gmail.com","avatar":"https://gravatar.com/avatar/25f70d4c0f96396b84a2e34bcd9bdc233462c7b4be29b5fdca8266fc53f30b0c?d=mp&s=160"},"body":"2009/3/4 Clemens Buchacher <drizzd@aon.at>:\n> On Wed, Mar 04, 2009 at 03:37:06PM +0000, John Tapsell wrote:\n>> -fprintf(stderr, \"Error: cannot lock existing info/refs\\n\");\n>> +error(\"cannot lock existing info/refs on remote server\\nPerhaps the\n>> server is currently busy, or your ~/.netrc file is not configured\n>> correctly.\");\n>\n> In my experience this is usually caused by http-push crashing and leaving\n> stale locks behind until it times out after 10 minutes. I don't think we\n> should speculate here unless we can narrow down the error condition.\n\nYeah, I was thinking of trying to narrow it down as well.\n\nI personally get that error 3 out of 4 times, roughly, that I try to\npush.  But that's probably because I'm using a very busy git server.\nSo in my case, I just keep retrying until it succeeds.\n\nOn google I found that people had been getting that error if they have\nthe wrong password.\n\nCan we at least change it to:\n\n-fprintf(stderr, \"Error: cannot lock existing info/refs\\n\");\n+error(\"cannot lock existing info/refs on remote server\\n\");\n\nIt's currently confusing as to whether it's a local error or a remote error.\n\nJohn\n"},{"id":"107030","messageId":"20090305085052.GA24669@localhost","threadId":"18133","inReplyTo":"43d8ce650903050000g4466ab2fne5fb8ed009808346@mail.gmail.com","subject":"Re: [PATCH] Clarify the \"cannot lock existing info/refs\" error","fromName":"Clemens Buchacher","fromEmail":"drizzd@aon.at","sentAt":"2009-03-05T08:50:52Z","receivedAt":"2009-03-05T08:50:52Z","isPatch":true,"sender":{"key":"drizzd@gmx.net","avatar":"https://avatars.githubusercontent.com/u/59082?v=4"},"body":"On Thu, Mar 05, 2009 at 08:00:37AM +0000, John Tapsell wrote:\n> On google I found that people had been getting that error if they have\n> the wrong password.\n\nThat's easy enough to verify. Using the wrong username/password I get\n\n\terror: Cannot access URL $url, return code 22\n\terror: failed to push some refs to '$url'\n\nwhich is not very helpful, but otherwise unrelated.\n\n> -fprintf(stderr, \"Error: cannot lock existing info/refs\\n\");\n> +error(\"cannot lock existing info/refs on remote server\\n\");\n\nThat's a less ambiguous but equally unhelpful error message.\n"}]}