f2d043eb08
Follow-ups to the salvaged #95947 cron commit: - Wrap the lock probe in its own try/except: a crashing probe is 'unknown', not 'dead' — the pid scan still decides instead of the whole tri-state collapsing to None. - Regression tests (shape adapted from #94155 by @liuhao1024): lock held + empty pid scan -> alive (the reported false alarm); lock inactive -> pid-scan fallback both ways; crashing lock probe still falls back. - patch_liveness now pins the lock probe inactive by default so the pre-existing pid-scan tests stay deterministic on machines where a real gateway holds the real lock. - contributors mapping for magnus.lundstedt@infidyne.com. Co-authored-by: liuhao1024 <sunsky.lau@gmail.com>
Contributor email → GitHub login mappings
This directory replaces appending entries to AUTHOR_MAP in
scripts/release.py. The old dict caused constant merge conflicts when
several salvage PRs landed at once — every PR edited the same lines of the
same file. Here, each mapping is its own file, and file additions never
conflict.
Adding a mapping
One file per commit-author email, under emails/:
python3 scripts/add_contributor.py <email> <github-login>
# or by hand:
echo "<github-login>" > contributors/emails/<email>
- File name = the exact commit-author email (as shown by
git log --format='%ae'). - File content = the GitHub login on the first non-comment line.
Lines starting with
#are comments (use them for the PR reference).
Example — contributors/emails/jane.doe@example.com:
janedoe
# PR #12345 salvage (gateway: fix session key routing)
Rules
- Do NOT add new entries to
AUTHOR_MAPinscripts/release.py. That dict is frozen legacy data; the release tooling merges it with this directory (directory entries win on duplicates). - GitHub noreply emails (
<id>+<login>@users.noreply.github.comand<login>@users.noreply.github.com) auto-resolve — no file needed. - The
Contributor Attribution CheckCI job fails a PR whose commits carry an unmapped email; the failure message prints the exact command to run.