You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
AI posting on behalf of @dblock: opened #55 with explicit opt-in stale-session cleanup for both adapters: MongoidStore.delete_stale_sessions(before: 1.week.ago) or MongoStore.delete_stale_sessions(before: 1.week.ago). It bulk-deletes records whose updated_at precedes the cutoff and returns the count, using the configured collection. No default maximum age, automatic deletion, background job or TTL index is installed; scheduling and retention stay with the application. The README explains callback bypass and why last-save timestamps are not necessarily last-activity timestamps. Thanks @jbarrantes for the original request. Leaving this issue open until the implementation merges.
AI posting on behalf of @dblock: #55 is now merged. We deliberately chose explicit cleanup rather than automatic expiry: retention is application-specific, and updated_at reflects the last session save, not necessarily the last request. Automatically deleting by that timestamp could unexpectedly sign out active users whose sessions were not rewritten. The library therefore installs no default maximum age, scheduler, background job, or TTL index.
Applications can automate cleanup on their own schedule with MongoidStore.delete_stale_sessions(before: 1.week.ago) or MongoStore.delete_stale_sessions(before: 1.week.ago), choosing their own retention policy. The call bulk-deletes records strictly older than the cutoff from the configured collection and returns the deleted count. It is maintenance cleanup, not an inactivity-logout guarantee. Thanks again @jbarrantes for the request.
Activity
dblock commentedon Oct 17, 2026
AI posting on behalf of @dblock: opened #55 with explicit opt-in stale-session cleanup for both adapters: MongoidStore.delete_stale_sessions(before: 1.week.ago) or MongoStore.delete_stale_sessions(before: 1.week.ago). It bulk-deletes records whose updated_at precedes the cutoff and returns the count, using the configured collection. No default maximum age, automatic deletion, background job or TTL index is installed; scheduling and retention stay with the application. The README explains callback bypass and why last-save timestamps are not necessarily last-activity timestamps. Thanks @jbarrantes for the original request. Leaving this issue open until the implementation merges.
dblock commentedon Oct 17, 2026
AI posting on behalf of @dblock: #55 is now merged. We deliberately chose explicit cleanup rather than automatic expiry: retention is application-specific, and updated_at reflects the last session save, not necessarily the last request. Automatically deleting by that timestamp could unexpectedly sign out active users whose sessions were not rewritten. The library therefore installs no default maximum age, scheduler, background job, or TTL index.
Applications can automate cleanup on their own schedule with MongoidStore.delete_stale_sessions(before: 1.week.ago) or MongoStore.delete_stale_sessions(before: 1.week.ago), choosing their own retention policy. The call bulk-deletes records strictly older than the cutoff from the configured collection and returns the deleted count. It is maintenance cleanup, not an inactivity-logout guarantee. Thanks again @jbarrantes for the request.