{"thread":{"id":"62410","subject":"clone: concurrent interactive authentication","startedAt":"2024-10-26T22:51:50Z","lastAt":"2024-10-26T22:51:50Z","messageCount":1,"participants":["Oliver W"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"506142","messageId":"CAJpsEwqom8VqnS4SBem5Q=o3Mb6jUjYN9zg-a7FbtCyBO7idJg@mail.gmail.com","threadId":"62410","inReplyTo":null,"subject":"clone: concurrent interactive authentication","fromName":"Oliver W","fromEmail":"oliver.warrick2@gmail.com","sentAt":"2024-10-26T22:51:38Z","receivedAt":"2024-10-26T22:51:50Z","isPatch":false,"sender":{"key":"oliver.warrick2@gmail.com","avatar":null},"body":"When doing a multi-job recurse-submodules clone on a repo with http\nsubmodules that require interactive authentication, all submodule\nclones happen in parallel and the username password prompts are all\nprinted at once, including disabling echo, making it effectively\nunusable as you don't know if you are entering a username or password.\nI think this could be fixed by passing some shared memory with a mutex\nto each of the parallel job processes, which they can then lock on if\nthey do prompt for credentials.\nSince there is the workaround of omitting the -j, is this change worth\nmaking and would it be accepted?\n"}]}