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

clone: concurrent interactive authentication

From
OWOliver W <oliver.warrick2@gmail.com>
Date
Oct 26, 2024, 22:51 UTC
Message-ID
<CAJpsEwqom8VqnS4SBem5Q=o3Mb6jUjYN9zg-a7FbtCyBO7idJg@mail.gmail.com>

When doing a multi-job recurse-submodules clone on a repo with http submodules that require interactive authentication, all submodule clones happen in parallel and the username password prompts are all printed at once, including disabling echo, making it effectively unusable as you don't know if you are entering a username or password. I think this could be fixed by passing some shared memory with a mutex to each of the parallel job processes, which they can then lock on if they do prompt for credentials. Since there is the workaround of omitting the -j, is this change worth making and would it be accepted?

Message 1 of 1 in “clone: concurrent interactive authentication”
  1. Oliver WOct 26, 2024

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.