RE: Bug report: parallel fetch tries to unlock SSH keys over and over again

>What did you do before the bug happened? (Steps to reproduce your issue) git
>fetch --all --tags --prune --jobs=10
>
>What did you expect to happen? (Expected behavior) Being asked for the password
>of my SSH key, then git updating all of the remotes.
>
>What happened instead? (Actual behavior) I get asked for my SSH key many times
>over, and the fetch does not succeed.
>
>What's different between what you expected and what actually happened?
>I should only be asked to unlock my SSH key once. All fetch jobs should wait for this
>and then use the unlocked (cached) key.
>
>Anything else you want to add:
>If I do just `git fetch` and unlock my key (once), it does get added to the SSH agent
>properly, and afterwards I can execute the command above with no issues.
>
>[System Info]
>git version:
>git version 2.48.1
>cpu: x86_64
>no commit associated with this build
>sizeof-long: 8
>sizeof-size_t: 8
>shell-path: /bin/sh
>libcurl: 8.11.1
>OpenSSL: OpenSSL 3.4.0 22 Oct 2024
>zlib: 1.3.1
>uname: Linux 6.12.10-arch1-1 #1 SMP PREEMPT_DYNAMIC Sat, 18 Jan 2025
>02:26:57 +0000 x86_64
>compiler info: gnuc: 14.2
>libc info: glibc: 2.40
>$SHELL (typically, interactive shell): /bin/bash
>
>[Enabled Hooks]