git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: StandardInput Not Continuing Process

From
Brian Gernhardt <benji@silverinsanity.com>
Date
Dec 23, 2010, 17:18 UTC
Message-ID
<345E4AAA-63E3-4949-8486-A636793DDBC8@silverinsanity.com>
In-Reply-To
<AANLkTikvrDWYT8h_MCESd9sg4_8ykSOq3XFEsoNsYDuZ@mail.gmail.com>
OnOn Wed, Dec 8, 2010 at 10:25 AM, Chase Brammer <cbrammer@gmail.com> wrote:
Show 15 quoted lines
> 
> I am try to directly interact with Git by using only stdin, stdout,
> and stderr.  So
> not going through a terminal at all, but calling Git directly.   I am
> having an issue
> with being able to continue a process that requires input.
> 
> For example, doing a clone from a HTTPS server may require a username/password.
> I writing the password as utf, and also tried just UTF byes (ie no
> prepended 16-bit int)
> but am unable to get the process to continue and start the clone process.
> 
> Is there some signal, or trick to getting the process to continue?  I
> thought that sending a
> "\n" would work, but that doesn't seem to be working either.
Depending on what language you're using and your pipe settings, you might need to issue an fflush(git_stdin).
~~ Brian
Previous: Chase BrammerNext: Junio C Hamano
Message 3 of 5 in “StandardInput Not Continuing Process”
  1. Chase BrammerDec 8, 2010
  2. Chase BrammerDec 23, 2010
  3. Brian GernhardtDec 23, 2010
  4. Junio C HamanoDec 23, 2010
  5. Tay Ray ChuanDec 25, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.