Actor cache TTL — fetched_at stored but never checked for staleness #3
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
ap_remote_actors.fetched_atis persisted on every actor fetch but no code path checks it for staleness. Long-lived cached actors will serve stale keys/endpoints indefinitely.Suggested fix: add a configurable TTL (e.g. 24h default). On actor dereference, if
fetched_at + ttl < now, re-fetch from origin and update the row.