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

waitpid errors with shell aliases

From
SSshubham sharma <shubhamsharma4060@gmail.com>
Date
Oct 21, 2022, 09:26 UTC
Message-ID
<CADUYy5vwfOJOFBQ+zUmkrsxGO=E9N5vUbsVRgjBn_MMY2X6H=A@mail.gmail.com>
Hi,

I am using git shell aliases in config and was facing some weird error. The error is not reproducible in all runs and occurs randomly between runs...consider the minimal config(alias section) below for usage idea:

[alias]
    A = "!f(){ \
        ( \
              // implementation
              git \"$1\"; \
        ) 250<dir/tmp; \
    }; f"
    B = "!f(){ \
        ssh <server> <command>; \
    }; f"
    C= "!f(){ \
        git A B; \
    }; f"

when firing "git C" from shell,in some cases(not deterministically reproducible) i observed weird waitpid errors of the type :

error: waitpid for f(){         ssh <server> <command>;    }; f
failed: No child processes
fatal: while expanding alias 'B': 'f(){       ssh <server> <command>;
     }; f': No child processes
error: waitpid for f(){     (//implementation; git "$1"; )250<dir/tmp;
   }; f failed: No child processes
fatal: while expanding alias 'A': 'f(){        (//implementation; git
"$1"; )250<dir/tmp;      }; f': No child processes
error: waitpid for f(){    git A B;    }; f failed: No child processes
fatal: while expanding alias 'C': 'f(){       git A B;      }; f': No
child processes
can anyone please help as to what could possibly be the reason for this?

Thanks, Shubham

Next: brian m. carlson
Message 1 of 3 in “waitpid errors with shell aliases”
  1. shubham sharmaOct 21, 2022
  2. brian m. carlsonOct 24, 2022
  3. shubham sharmaOct 25, 2022

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.