fix(memory): resolve() the shared-connection registry key; symlink test

Follow-ups for salvaged PR #43819: the registry key was
str(Path(db_path).expanduser()) — a symlinked or relative path to the
same DB file got its own connection, silently reintroducing the exact
multi-writer contention the registry prevents. Key on Path.resolve()
(OSError-tolerant fallback). Adds a symlink regression test and the
AUTHOR_MAP entry for adambiggs.
This commit is contained in:
teknium1 2026-07-09 17:21:15 -07:00 committed by Teknium
parent b5226caff8
commit a801046669
3 changed files with 26 additions and 1 deletions

View file

@ -258,6 +258,7 @@ AUTHOR_MAP = {
"sswdarius@gmail.com": "necoweb3",
"bassisho@Mac-mini-bassis.local": "hydracoco7", # PR #61382 salvage (id-less cron job freeze)
"AlexFucuson9@users.noreply.github.com": "AlexFucuson9", # PR #61209 salvage (hygiene compression data loss)
"email@adambig.gs": "adambiggs", # PR #43819 salvage (holographic shared SQLite connection)
"t.chen@aftership.com": "cypctlinux", # PR #52403 salvage (Slack bot/workflow auth before no-user-id guard)
"30854794+YLChen-007@users.noreply.github.com": "YLChen-007", # PR #26965 (approval remote command substitution)
"1078345+egilewski@users.noreply.github.com": "egilewski", # co-author, PR #40663