Spurious error message when Flux's Source controller checks to see if there are any updates

[nogweii]

Describe the bug
I'm getting a ton of errors (the default behavior is to check once a minute) in my system logs, whenever Flux's Source controller checks to see if there were any changes to the git repo.

To Reproduce
Steps to reproduce the behavior:

1. Have a fresh kubernetes cluster (kind makes it easy: kind create cluster)
2. Create a repo in soft-serve
3. Perform the flux bootstrap process to install it into the cluster and monitor the git repo: flux bootstrap git --private-key-file flux.key --url=ssh://[email protected]:12345/sys/flux-config.git --path=clusters/my-cluster/
4. Wait a few miuntes, see errors in the output of soft-serve.

Expected behavior
No errors would occur for this typical behavior (assuming Flux is behaving correctly, which I'm not certain about), or at least, no log messages would be sent.

Screenshots

Aug 17 18:44:11 soft.example soft[1853579]: time="2024-08-17 18:44:11" level=error prefix=ssh msg="failed to handle git service" service=git-upload-pack err="signal: killed" repo=sys/flux-config
Aug 17 18:45:11 soft.example soft[1853579]: time="2024-08-17 18:45:11" level=error prefix=ssh msg="failed to handle git service" service=git-upload-pack err="signal: killed" repo=sys/flux-config
Aug 17 18:46:11 soft.example soft[1853579]: time="2024-08-17 18:46:11" level=error prefix=ssh msg="failed to handle git service" service=git-upload-pack err="signal: killed" repo=sys/flux-config
Aug 17 18:47:34 soft.example soft[1853579]: time="2024-08-17 18:47:34" level=error prefix=ssh msg="failed to handle git service" service=git-upload-pack err="signal: killed" repo=sys/flux-config
Aug 17 18:48:13 server.example soft[1853579]: time="2024-08-17 18:48:13" level=error prefix=ssh msg="failed to handle git service" service=git-upload-pack err="signal: killed" repo=sys/flux-config

Environment (please complete the following information):

• OS: Arch Linux
• Version: 0.7.6

Additional context
This may actually be a problem with how Flux checks the repo for changes, I'm not certain. Hopefully the process of debugging this would reveal what the exact cause is for the error.