{"thread":{"id":"44395","subject":"Can't get git to stop outputting to StdErr","startedAt":"2016-10-28T20:41:29Z","lastAt":"2016-12-19T15:04:49Z","messageCount":4,"participants":["Scott R. Chamberlain","Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"305125","messageId":"c09d32d8ab97418d98ddf356e20a6ff5@ES4.impromed.com","threadId":"44395","inReplyTo":null,"subject":"Can't get git to stop outputting to StdErr","fromName":"Scott R. Chamberlain","fromEmail":"srchamberlain@impromed.com","sentAt":"2016-10-28T20:31:02Z","receivedAt":"2016-10-28T20:41:29Z","isPatch":false,"sender":{"key":"srchamberlain@impromed.com","avatar":null},"body":"I am working on some build scripts that get run on TFS. During the build process I need to check in the changes that where done during the build process (A set of binaries other projects depend on).\n\nI would really like to leave the option \"Fail on Standard Error\" enabled for the script in TFS, however my push keeps writing to standard error even though I told it not to.\n\nThe line I do is:\n\n git push -q binaryRepo HEAD:\"$Env:BUILD_SOURCEBRANCH\"\n\nBut I get the following in my log after the build\n\n 2016-10-28T20:05:32.3179442Z ##[error]remote: \n remote: Analyzing objects... (3/3) (657 ms) \n remote: Storing packfile... done (40 ms) \n remote: Storing index... done (42 ms) \n \n 2016-10-28T20:05:32.3209423Z Done\n 2016-10-28T20:05:32.4019436Z ##[error]Process completed with exit code 0 and had 1 error(s) written to the error stream.\n 2016-10-28T20:05:32.4029436Z ##[debug]System.Exception: Process completed with exit code 0 and had 1 error(s) written to the error stream.\n\nWhy am I still getting output to standard error when I included the `-q` switch?\n\nFor reference, `git version` reports `2.10.0.windows.1` and HEAD is a detached HEAD.\n\n\nScott Chamberlain\nSoftware Engineer \nImproMed, LLC\n\n\n\n-- \nRely On Us.\nImproMed LLC\nHenry Schein Animal Health\n--\n\n"},{"id":"305128","messageId":"xmqq7f8syyhg.fsf@gitster.mtv.corp.google.com","threadId":"44395","inReplyTo":"c09d32d8ab97418d98ddf356e20a6ff5@ES4.impromed.com","subject":"Re: Can't get git to stop outputting to StdErr","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2016-10-28T21:06:51Z","receivedAt":"2016-10-28T21:06:59Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"\"Scott R. Chamberlain\" writes:\n\n> The line I do is:\n>\n> git push -q binaryRepo HEAD:\"$Env:BUILD_SOURCEBRANCH\"\n\nThis would \n\n (1) squelch the output from the sending side (i.e. local), and\n\n (2) ask \"quiet\" to the receiving side (i.e. remote), if they know\n how to be quiet.\n\n> But I get the following in my log after the build\n>\n> 2016-10-28T20:05:32.3179442Z ##[error]remote: \n> remote: Analyzing objects... (3/3) (657 ms) \n> remote: Storing packfile... done (40 ms) \n> remote: Storing index... done (42 ms) \n\nThese three lines prefixed with \"remote:\" are coming from the\nsoftware that runs on the remote machine that accepts your push, but\nthe way it says these three things do not look familiar to me. Is\nit possible that the remote machine is running a Git server that is\nnot ours, which lacks the support for \"quiet\" capability? If that\nis the case, the symptom is understandable.\n\nA quick archive search tells me that you are seeing the same issue\nas this one:\n\nhttps://public-inbox.org/git/20160516133731.GA6903@sigill.intra.peff.net/\n\nwhere the concluding remark, to which I agree, is:\n\n The server side here is clearly not stock git, from the content\n of those progress messages (some googling shows it looks like\n whatever visualstudio.com is running, but I don't know what that\n is). So either the server implementation doesn't support the\n \"quiet\" protocol extension, or it is ignoring it. It might be\n worth filing a bug with them.\n\n\n"},{"id":"305129","messageId":"824a1f973733418aa7486a3a30e41d93@ES4.impromed.com","threadId":"44395","inReplyTo":"xmqq7f8syyhg.fsf@gitster.mtv.corp.google.com","subject":"RE: Can't get git to stop outputting to StdErr","fromName":"Scott R. Chamberlain","fromEmail":"srchamberlain@impromed.com","sentAt":"2016-10-28T21:08:34Z","receivedAt":"2016-10-28T21:09:27Z","isPatch":false,"sender":{"key":"srchamberlain@impromed.com","avatar":null},"body":"This is talking to a visualstudio.com git repo. I will file a bug with them.\n\nScott Chamberlain\nSoftware Engineer \nImproMed, LLC\n(800) 925-7171\nwww.impromed.com\n\n\n-----Original Message-----\nFrom: Junio C Hamano [mailto:gitster@pobox.com] \nSent: Friday, October 28, 2016 4:07 PM\nTo: Scott R. Chamberlain \nCc: git@vger.kernel.org\nSubject: Re: Can't get git to stop outputting to StdErr\n\n\"Scott R. Chamberlain\" writes:\n\n> The line I do is:\n>\n> git push -q binaryRepo HEAD:\"$Env:BUILD_SOURCEBRANCH\"\n\nThis would \n\n (1) squelch the output from the sending side (i.e. local), and\n\n (2) ask \"quiet\" to the receiving side (i.e. remote), if they know\n how to be quiet.\n\n> But I get the following in my log after the build\n>\n> 2016-10-28T20:05:32.3179442Z ##[error]remote: \n> remote: Analyzing objects... (3/3) (657 ms) \n> remote: Storing packfile... done (40 ms) \n> remote: Storing index... done (42 ms) \n\nThese three lines prefixed with \"remote:\" are coming from the software that runs on the remote machine that accepts your push, but the way it says these three things do not look familiar to me. Is it possible that the remote machine is running a Git server that is not ours, which lacks the support for \"quiet\" capability? If that is the case, the symptom is understandable.\n\nA quick archive search tells me that you are seeing the same issue as this one:\n\nhttps://public-inbox.org/git/20160516133731.GA6903@sigill.intra.peff.net/\n\nwhere the concluding remark, to which I agree, is:\n\n The server side here is clearly not stock git, from the content\n of those progress messages (some googling shows it looks like\n whatever visualstudio.com is running, but I don't know what that\n is). So either the server implementation doesn't support the\n \"quiet\" protocol extension, or it is ignoring it. It might be\n worth filing a bug with them.\n\n\n\n-- \nRely On Us.\nImproMed LLC\nHenry Schein Animal Health\n--\n\n"},{"id":"308035","messageId":"77ad6aeef9a245f3adeab3751e7e94eb@ES5.impromed.com","threadId":"44395","inReplyTo":"xmqq7f8syyhg.fsf@gitster.mtv.corp.google.com","subject":"RE: Can't get git to stop outputting to StdErr","fromName":"Scott R. Chamberlain","fromEmail":"srchamberlain@impromed.com","sentAt":"2016-12-19T14:56:35Z","receivedAt":"2016-12-19T15:04:49Z","isPatch":false,"sender":{"key":"srchamberlain@impromed.com","avatar":null},"body":"Microsoft fixed their git repo implementation to no longer cause this problem.\n\nhttps://connect.microsoft.com/VisualStudio/feedback/details/3109654/git-host-on-visualstudio-com-does-not-respect-the-q-flag-for-pushes\n\nScott Chamberlain\nSoftware Engineer \nImproMed, LLC\n(800) 925-7171\nwww.impromed.com\n\n-----Original Message-----\nFrom: Scott R. Chamberlain \nSent: Friday, October 28, 2016 4:09 PM\nTo: 'Junio C Hamano' \nCc: git@vger.kernel.org\nSubject: RE: Can't get git to stop outputting to StdErr\n\nThis is talking to a visualstudio.com git repo. I will file a bug with them.\n\nScott Chamberlain\nSoftware Engineer \nImproMed, LLC\n(800) 925-7171\nwww.impromed.com\n\n\n-----Original Message-----\nFrom: Junio C Hamano [mailto:gitster@pobox.com] \nSent: Friday, October 28, 2016 4:07 PM\nTo: Scott R. Chamberlain \nCc: git@vger.kernel.org\nSubject: Re: Can't get git to stop outputting to StdErr\n\n\"Scott R. Chamberlain\" writes:\n\n> The line I do is:\n>\n> git push -q binaryRepo HEAD:\"$Env:BUILD_SOURCEBRANCH\"\n\nThis would \n\n (1) squelch the output from the sending side (i.e. local), and\n\n (2) ask \"quiet\" to the receiving side (i.e. remote), if they know\n how to be quiet.\n\n> But I get the following in my log after the build\n>\n> 2016-10-28T20:05:32.3179442Z ##[error]remote: \n> remote: Analyzing objects... (3/3) (657 ms) \n> remote: Storing packfile... done (40 ms) \n> remote: Storing index... done (42 ms) \n\nThese three lines prefixed with \"remote:\" are coming from the software that runs on the remote machine that accepts your push, but the way it says these three things do not look familiar to me. Is it possible that the remote machine is running a Git server that is not ours, which lacks the support for \"quiet\" capability? If that is the case, the symptom is understandable.\n\nA quick archive search tells me that you are seeing the same issue as this one:\n\nhttps://public-inbox.org/git/20160516133731.GA6903@sigill.intra.peff.net/\n\nwhere the concluding remark, to which I agree, is:\n\n The server side here is clearly not stock git, from the content\n of those progress messages (some googling shows it looks like\n whatever visualstudio.com is running, but I don't know what that\n is). So either the server implementation doesn't support the\n \"quiet\" protocol extension, or it is ignoring it. It might be\n worth filing a bug with them.\n\n\n\n-- \nRely On Us.\nImproMed LLC\nHenry Schein Animal Health\n--\n\n"}]}