threads / bug / 26207

[BUG?] "git submodule foreach" when command is ssh

Subject: [BUG?] "git submodule foreach" when command is ssh

## tl;dr

5 messages between Jan 5, 2011 and Jan 5, 2011.

replies: 4people: 3as markdown or json

Chris Packham· Jan 5, 2011, 22:32 UTC · lore
Hi All,

I just noticed something odd with "git submodule foreach". I was running a script to create a backup of each submodule on a server I have ssh access to. I was surprised to find that git submodule foreach stopped silently after the first submodule.

A little debugging and I find that

git submodule foreach 'ssh localhost "ls /"' - stops silently after the first module (note that the command does produce the expected listing and there is no error about the command failing).

git submodule foreach 'echo foo' - works as expected
Any thoughts as to whats going on?

--- git version 1.7.3.2

Chris Packham· Jan 5, 2011, 22:50 UTC · re: Chris Packham · lore

Re: [BUG?] "git submodule foreach" when command is ssh

On Thu, Jan 6, 2011 at 11:32 AM, Chris Packham <judge.packham@gmail.com> wrote:
Show 20 quoted lines
> Hi All,
>
> I just noticed something odd with "git submodule foreach". I was
> running a script to create a backup of each submodule on a server I
> have ssh access to. I was surprised to find that git submodule foreach
> stopped silently after the first submodule.
>
> A little debugging and I find that
>
> git submodule foreach 'ssh localhost "ls /"' - stops silently after
> the first module (note that the command does produce the expected
> listing and there is no error about the command failing).
>
> git submodule foreach 'echo foo' - works as expected
>
> Any thoughts as to whats going on?
>
> ---
> git version 1.7.3.2
>

Actually this might be a ssh/bash bug (feature?). There is different behaviour between

  find . -maxdepth 1 -type d -a ! -name '\.*' | while read; do echo
$REPLY && ssh localhost ls /; done
and
  find . -maxdepth 1 -type d -a ! -name '\.*' | while read; do echo
$REPLY && ls /; done
Jeff King· Jan 5, 2011, 23:03 UTC · re: Chris Packham · lore

Re: [BUG?] "git submodule foreach" when command is ssh

On Thu, Jan 06, 2011 at 11:50:58AM +1300, Chris Packham wrote:
Show 10 quoted lines
> Actually this might be a ssh/bash bug (feature?). There is different
> behaviour between
> 
>   find . -maxdepth 1 -type d -a ! -name '\.*' | while read; do echo
> $REPLY && ssh localhost ls /; done
> 
> and
> 
>   find . -maxdepth 1 -type d -a ! -name '\.*' | while read; do echo
> $REPLY && ls /; done

Ssh will opportunistically eat data on stdin to send to the other side, even though the command on the other side ("ls" in this case) will never read it. Because of course ssh has no way of knowing that, and is trying to be an interactive terminal. So it ends up eating some random amount of the data you expected to go to the "read" call.

You can use the "-n" option to suppress it. For example:
  $ (echo foo; echo bar) |
    while read line; do
      echo local $line
      ssh host "echo remote $line"
    done
produces:
  local foo
  remote foo
but:
  $ (echo foo; echo bar) |
    while read line; do
      echo local $line
      ssh -n host "echo remote $line"
    done
produces:
  local foo
  remote foo
  local bar
  remote bar
which is what you want.
-Peff
Chris Packham· Jan 5, 2011, 23:22 UTC · re: Jeff King · lore

Re: [BUG?] "git submodule foreach" when command is ssh

On Thu, Jan 6, 2011 at 12:03 PM, Jeff King <peff@peff.net> wrote:
Show 50 quoted lines
> On Thu, Jan 06, 2011 at 11:50:58AM +1300, Chris Packham wrote:
>
>> Actually this might be a ssh/bash bug (feature?). There is different
>> behaviour between
>>
>>   find . -maxdepth 1 -type d -a ! -name '\.*' | while read; do echo
>> $REPLY && ssh localhost ls /; done
>>
>> and
>>
>>   find . -maxdepth 1 -type d -a ! -name '\.*' | while read; do echo
>> $REPLY && ls /; done
>
> Ssh will opportunistically eat data on stdin to send to the other side,
> even though the command on the other side ("ls" in this case) will never
> read it. Because of course ssh has no way of knowing that, and is trying
> to be an interactive terminal. So it ends up eating some random amount
> of the data you expected to go to the "read" call.
>
> You can use the "-n" option to suppress it. For example:
>
>  $ (echo foo; echo bar) |
>    while read line; do
>      echo local $line
>      ssh host "echo remote $line"
>    done
>
> produces:
>
>  local foo
>  remote foo
>
> but:
>
>  $ (echo foo; echo bar) |
>    while read line; do
>      echo local $line
>      ssh -n host "echo remote $line"
>    done
>
> produces:
>
>  local foo
>  remote foo
>  local bar
>  remote bar
>
> which is what you want.
>
> -Peff
Thanks that makes sense and adding -n to my ssh invocations solves the problem.
Seth Robertson· Jan 5, 2011, 23:02 UTC · re: Chris Packham · lore

Re: [BUG?] "git submodule foreach" when command is ssh

In message <AANLkTi=x2i6NvDNRzbszhk-a-z5AYe46-iUBxQsxJJHC@mail.gmail.com>, Chri s Packham writes:

    I just noticed something odd with "git submodule foreach". I was
    running a script to create a backup of each submodule on a server I
    have ssh access to. I was surprised to find that git submodule foreach
    stopped silently after the first submodule.
    A little debugging and I find that
    git submodule foreach 'ssh localhost "ls /"' - stops silently after

Putting some input redirection will work around the problem. Presumably some pipe input is going into the ssh accidentally.

git submodule foreach 'ssh localhost "ls /" < /dev/null'

I'll also just take this moment to advertise gitslave (http://gitslave.sf.net) as an alternate to submodules which may help (or hinder) you--depending on your workflow. It doesn't suffer from this particular problem in any case.

					-Seth Robertson

← back to recent threads