StandardInput Not Continuing Process

StandardInput Not Continuing Process

[Chase Brammer]

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.

Thanks for any help!

Chase

Re: StandardInput Not Continuing Process

[Chase Brammer]

Bump, any ideas?

Chase


On Wed, Dec 8, 2010 at 10:25 AM, Chase Brammer <cbrammer@gmail.com> wrote:
>
> 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.
>
> Thanks for any help!
>
> Chase

Re: StandardInput Not Continuing Process

[Brian Gernhardt]

OnOn Wed, Dec 8, 2010 at 10:25 AM, Chase Brammer <cbrammer@gmail.com> wrote:
> 
> 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

Re: StandardInput Not Continuing Process

[Junio C Hamano]

Certain things do want a real user sitting at the terminal (or GUI) even
when the standard streams are connected elsewhere, and password input
is one of the obvious things that would explicitly want to read from the
tty.

Perhaps driving whatever script you are writing via "expect" would work?

Re: StandardInput Not Continuing Process

[Tay Ray Chuan]

On Thu, Dec 9, 2010 at 1:25 AM, Chase Brammer <cbrammer@gmail.com> wrote:
> 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.

Try putting the username and password in ~/.netrc, or in the url with
https://user:pwd@foo.com/ - that way, you can skip the "input process"
altogether.

-- 
Cheers,
Ray Chuan