The self-hosted runner: boom-containers lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.

unable to read sha1 file of .cargo/config.toml (29dc3bc2114432373e415ffe2c3e6f944c21df48)

unable to read sha1 file of .env.sample (d90f3fd8a6f22c3d27a1a22b49363894b9c4e29d)

unable to read sha1 file of .ghjk/.gitignore (abf95c16188365bfc645f48caebaefa008c4c10b)

unable to read sha1 file of .ghjk/deno.lock (0223fbf5091713fbc773102dd7c611936912b902)

unable to read sha1 file of .git-branches.toml (01f73cf3f902f496239eb172c58a9dae8f300a21)

unable to read sha1 file of .github/dependabot.yml (ac1436916d07c65eed3e76d8915f2ee0ffefb815)

unable to read sha1 file of .github/pull_request_template.md (cb9d567e8324bd93c2bc8fde5a40bd4350b3401e)

unable to read sha1 file of .github/workflows/autoupdate.yml (0d315ab541862c19a3e14f75823327cbffd672a7)

unable to read sha1 file of .github/workflows/nightly.yml (aa9b11126608f06176a52329d45e373aa5ed3eeb)