YoursFunny eecd4320f8 fix(state): keep failed and stale reads from poisoning the chat cache ...

Three related races in ChatStore. A read that errored (busy/IO) was indistinguishable from an absent row, so the default got cached — and the next update would write that default back over the chat's real settings (forward channel, templates, formats). A cache-miss backfill inserted unconditionally, letting a stale DB snapshot overwrite the value a concurrent set had just written. And sweep eviction removed per-chat locks unconditionally, so a lock pulled out from under an in-flight update let a second writer create a fresh one and enter the critical section concurrently; eviction now keeps any lock with a holder (the same rule rate_limit's prune applies), which still bounds the map because an uncontended leftover is caught by a later sweep. Two regression tests pin the failed-read and contended-lock cases.

2026-09-24 02:47:49 +08:00

..

x-media

fix(pixiv): treat an empty refresh token as unset

2026-09-24 00:48:29 +08:00

xmedia-bot

fix(state): keep failed and stale reads from poisoning the chat cache

2026-09-24 02:47:49 +08:00