Process completed with exit code 1.

YAMLException: duplicated mapping key at line 5, column -142: npmScopes: ^ at generateError (/usr/lib/node_modules/yarn/lib/cli.js:126542:10) at throwError (/usr/lib/node_modules/yarn/lib/cli.js:126548:9) at storeMappingPair (/usr/lib/node_modules/yarn/lib/cli.js:126710:7) at readBlockMapping (/usr/lib/node_modules/yarn/lib/cli.js:127473:9) at composeNode (/usr/lib/node_modules/yarn/lib/cli.js:127734:12) at readDocument (/usr/lib/node_modules/yarn/lib/cli.js:127894:3) at loadDocuments (/usr/lib/node_modules/yarn/lib/cli.js:127950:5) at load (/usr/lib/node_modules/yarn/lib/cli.js:127971:19) at safeLoad (/usr/lib/node_modules/yarn/lib/cli.js:127993:10) at parse (/usr/lib/node_modules/yarn/lib/cli.js:64242:18)

YAMLException: duplicated mapping key at line 5, column -142: npmScopes: ^ at generateError (/usr/lib/node_modules/yarn/lib/cli.js:126542:10) at throwError (/usr/lib/node_modules/yarn/lib/cli.js:126548:9) at storeMappingPair (/usr/lib/node_modules/yarn/lib/cli.js:126710:7) at readBlockMapping (/usr/lib/node_modules/yarn/lib/cli.js:127473:9) at composeNode (/usr/lib/node_modules/yarn/lib/cli.js:127734:12) at readDocument (/usr/lib/node_modules/yarn/lib/cli.js:127894:3) at loadDocuments (/usr/lib/node_modules/yarn/lib/cli.js:127950:5) at load (/usr/lib/node_modules/yarn/lib/cli.js:127971:19) at safeLoad (/usr/lib/node_modules/yarn/lib/cli.js:127993:10) at parse (/usr/lib/node_modules/yarn/lib/cli.js:64242:18)

YAMLException: duplicated mapping key at line 5, column -142: npmScopes: ^ at generateError (/usr/lib/node_modules/yarn/lib/cli.js:126542:10) at throwError (/usr/lib/node_modules/yarn/lib/cli.js:126548:9) at storeMappingPair (/usr/lib/node_modules/yarn/lib/cli.js:126710:7) at readBlockMapping (/usr/lib/node_modules/yarn/lib/cli.js:127473:9) at composeNode (/usr/lib/node_modules/yarn/lib/cli.js:127734:12) at readDocument (/usr/lib/node_modules/yarn/lib/cli.js:127894:3) at loadDocuments (/usr/lib/node_modules/yarn/lib/cli.js:127950:5) at load (/usr/lib/node_modules/yarn/lib/cli.js:127971:19) at safeLoad (/usr/lib/node_modules/yarn/lib/cli.js:127993:10) at parse (/usr/lib/node_modules/yarn/lib/cli.js:64242:18)

The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.

The operation was canceled.

The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.

The operation was canceled.

The self-hosted runner: lace-setup-runner-dzd2d-lhpbv 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.

The self-hosted runner: lace-setup-runner-dzd2d-dpm89 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.

The self-hosted runner: lace-setup-runner-dzd2d-tf7fh 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.

The self-hosted runner: lace-setup-runner-dzd2d-n664k 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.

The self-hosted runner: lace-setup-runner-dzd2d-wwgxh 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.

The self-hosted runner: lace-setup-runner-dzd2d-sdn76 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.