f680a4dc7d
Widen #96038's fail-closed classifier to the gateway transcript retry path: SessionStore._is_fts_corruption_error no longer treats a generic 'database disk image is malformed' as FTS-only damage. It now delegates to SessionDB._is_fts_write_corruption_error (SQLITE_CORRUPT_VTAB result code or explicit fts5 corrupt-structure text) and only keeps the messages_fts-named cases. Structural corruption falls through to the bounded retry/backoff path instead of rebuilding FTS and retrying writes against a damaged database. Sibling site spotted in PR #98090 by @fangliquanflq.
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.