feat: prune pg session interval

[amhsirak]

ref #561

Summary by CodeRabbit

• Chores
  • Improved session management by enabling periodic cleanup of expired sessions and centralized error logging for session-related issues.

[coderabbitai]

Walkthrough

The session middleware configuration for the server was updated to include two additional options for the PostgreSQL-backed session store. A pruneSessionInterval of 3600 seconds was introduced to periodically remove expired sessions, and an errorLog function was added to route session store errors to the central logger at the error level. No changes were made to public or exported entities.

Changes

File(s)	Change Summary
server/src/server.ts	Added pruneSessionInterval (set to 3600 seconds) and errorLog (centralized error logging) to the PostgreSQL session store configuration.

Sequence Diagram(s)

sequenceDiagram
    participant Client
    participant Server
    participant SessionStore
    participant Logger

    Client->>Server: Send request (with session)
    Server->>SessionStore: Access session
    Note over SessionStore: Periodically (every 3600s)<br>prune expired sessions
    SessionStore->>Logger: Log errors via errorLog function
    Server->>Client: Respond to request

Loading

Possibly related PRs

• feat: migrate session storage to postgres #495: Adds PostgreSQL session storage, which is now enhanced with session pruning and error logging in this PR.

Poem

🐇
In the warren where sessions grow,
Pruning old burrows, an hourly show.
If errors arise, don’t hop in fear—
The logger will catch them, loud and clear.
With tidy tunnels and logs in sight,
The server hops on, running right!

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1e3e159 and 2ec59ad.

📒 Files selected for processing (1)

• server/src/server.ts (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• server/src/server.ts

✨ Finishing Touches

• 📝 Generate Docstrings

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.