{"thread":{"id":"46739","subject":"Buffered value should be shown when requesting username for remote authentication","startedAt":"2017-09-12T12:47:35Z","lastAt":"2017-09-13T09:07:40Z","messageCount":3,"participants":["Kaartic Sivaraam","Jeff King"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"327888","messageId":"1505220449.27800.23.camel@gmail.com","threadId":"46739","inReplyTo":null,"subject":"Buffered value should be shown when requesting username for remote authentication","fromName":"Kaartic Sivaraam","fromEmail":"kaarticsivaraam91196@gmail.com","sentAt":"2017-09-12T12:47:29Z","receivedAt":"2017-09-12T12:47:35Z","isPatch":false,"sender":{"key":"kaartic.sivaraam@gmail.com","avatar":"https://avatars.githubusercontent.com/u/12448084?v=4"},"body":"Hello all,\n\nI noted a little issue with the interaction to a remote git repository.\nThe issue occurs when the network used for remote communication is a\nbit sluggish. The main issue is illustrated by the following shell\ninteraction,\n\n    $ git push -u fork \n    sivaraamUsername for '    https://github.com'    : sivaraam\n    Password for '    https://sivaraamsivaraam@github.com':     \n\n    It's a little odd that the (buffered) input found before the request\n    for 'Username' is also appended to the input found after the request.\n    This might not be obvious to the user and he has to retype the\n    'Username' in the next try.\n\n    I have seen some utilities handle this correctly by doing something\n    like,\n\n    $ <some-utility> \n    sivaUsername for '    https://github.com'    : siva\n\n        Further, unlike the request string, the buffered input that gets\n        printed after the request was editable. I'm not able to recollect the\n        <some-utility> correctly, though.\n\n        Any ideas about how to fix this?\n\n        -- \n        Kaartic\n"},{"id":"327894","messageId":"20170912153355.mbsybuy3kqtfvmtd@sigill.intra.peff.net","threadId":"46739","inReplyTo":"1505220449.27800.23.camel@gmail.com","subject":"Re: Buffered value should be shown when requesting username for remote authentication","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2017-09-12T15:33:55Z","receivedAt":"2017-09-12T15:34:01Z","isPatch":false,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Tue, Sep 12, 2017 at 06:17:29PM +0530, Kaartic Sivaraam wrote:\n\n> I noted a little issue with the interaction to a remote git repository.\n> The issue occurs when the network used for remote communication is a\n> bit sluggish. The main issue is illustrated by the following shell\n> interaction,\n> \n>     $ git push -u fork \n>     sivaraamUsername for '    https://github.com'    : sivaraam\n>     Password for '    https://sivaraamsivaraam@github.com':     \n> \n>     It's a little odd that the (buffered) input found before the request\n>     for 'Username' is also appended to the input found after the request.\n>     This might not be obvious to the user and he has to retype the\n>     'Username' in the next try.\n\nIf I understand right, you typed \"sivaraam\" once, then the network\nlagged, then you typed \"sivaraam\" again.\n\nThat isn't really something that Git can fix reliably. Reading those\ncharacters and echoing them back to the terminal is handled by your\nterminal driver (and potentially other things like ssh).  Git may have\nreceived \"sivaraamsivaraam\" all at once, depending on where the lag is.\n\n-Peff\n"},{"id":"327917","messageId":"f07d9416-bf2b-83ac-176a-14411d6e8aca@gmail.com","threadId":"46739","inReplyTo":"20170912153355.mbsybuy3kqtfvmtd@sigill.intra.peff.net","subject":"Re: Buffered value should be shown when requesting username for remote authentication","fromName":"Kaartic Sivaraam","fromEmail":"kaarticsivaraam91196@gmail.com","sentAt":"2017-09-13T09:07:39Z","receivedAt":"2017-09-13T09:07:40Z","isPatch":false,"sender":{"key":"kaartic.sivaraam@gmail.com","avatar":"https://avatars.githubusercontent.com/u/12448084?v=4"},"body":"On Tuesday 12 September 2017 09:03 PM, Jeff King wrote:\n> If I understand right, you typed \"sivaraam\" once, then the network\n> lagged, then you typed \"sivaraam\" again.\nAlmost there but I should have been more clearer. What I actually did was I\nrun `git push` and knowing it would ask for a username I started typing \nit immediately\nwithout looking at the terminal to notice that the request for the \nusername hasn't\nshown up yet due to the slow network. the terminal was like this before \nthe request showed up,\n\n    $ git push\n    sivaraam\n\nAfter the request showed up the terminal was like,\n\n    $ git push\n    sivaraamUsername for 'https://github.com' :\n\nI thought the buffered input wasn't recognised as it didn't show up \nafter the request.\nSo, I typed the username once more to get this,\n\n      $ git push -u fork\n      sivaraamUsername for 'https://github.com' : sivaraam\n      Password for 'https://sivaraamsivaraam@github.com :\n\nI have been accustomed with this now a days that I don't do the same \nmistake now. I thought\nit would nice if this could be fixed as I have seen utilities show the \nbuffered input after the\nrequest but as I stated before I'm not able to recollect which utility \nit was (hope I had better\nmemory)\n\n> That isn't really something that Git can fix reliably. Reading those\n> characters and echoing them back to the terminal is handled by your\n> terminal driver (and potentially other things like ssh).  Git may have\n> received \"sivaraamsivaraam\" all at once, depending on where the lag is.\n\nI expected this but wasn't sure which \"potential thing\" was handling the \n'https' handling in the background.\nI guess it's 'curl' but not sure.\n\n---\nKaartic\n"}]}