Xevion / Xevion/dynamic-preauth
Session Purging
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 0
- Forks
- 0
- Avg merge
- 9d 3h
- Merged PRs (30d)
- 4
Description
Sessions accumulate over time and should be cleaned up after periods of inactivity to avoid bloating the deployment and wasting resources. Active sessions with open websockets should obviously be kept, but there might be edge cases where connections appear active but are actually stale or improperly disconnected.
Considerations:
- What's a reasonable inactivity threshold? (72 hours seems reasonable)
- How to detect truly active vs zombie connections
- Cleanup strategy that doesn't disrupt legitimate users
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by locating session storage and the websocket connection lifecycle, then clarify the inactivity threshold and how active versus zombie connections should be identified. Done means inactive sessions are removed without disrupting legitimate active users, with edge cases covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- authentication, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100