Pick any line to see why it is the way it is: the commit, the pull request and issue it came from, and what the agent was thinking.
| A computer whose runner is registered again takes its own runner's name back instead of being refused. When the desktop app's sandbox was made again (a new VM, its registration gone), its runners registered under the names the old sandbox's still held on g1t, were refused with a 409 asking for --replace, and tried again forever. A runner now says which computer it is when it registers: a fingerprint g1t-runner works out from the operating system's machine id (Windows' MachineGuid, macOS's platform UUID, Linux's /etc/machine-id), hashed so the id never leaves the computer, or from --machine / G1T_RUNNER_MACHINE; a container sends none, since its machine id is its image's, and g1t-runner sandbox passes the computer's to the runner in the VM. The actions service keeps it hashed again with the workspace (migration 0022 adds runners.machine_hash), and a registration of a name already taken replaces that runner when it was registered from the same computer, or, for a runner from before fingerprints, when the same person made both tokens and the old runner has been offline for 90 seconds; a runner of the same name from another computer is still refused without --replace, and the refusal says so. The self-hosted runners guide covers registering again and --machine. | 1 | -- Which computer a self-hosted runner registered from, as a hash of the |
| 2 | -- fingerprint it sent: a runner of the same name registered again from the | |
| 3 | -- same computer takes the old one's place without --replace. Null for | |
| 4 | -- runners that registered before runners said so. | |
| 5 | ALTER TABLE runners ADD COLUMN machine_hash TEXT; |
