Migrate and Enable cleanupExpiredBans for PostgreSQL - #28
Conversation
… periodic execution - Updated `cleanupExpiredBans` in `Chat/backend/utils/moderation.js` to use `prisma.ban.deleteMany` with `BigInt` timestamp comparison. - Enabled `cleanupExpiredBans` in `Chat/backend/server.js` to run on startup. - Scheduled a periodic cleanup task to run every 12 hours. - Added error handling and logging for the cleanup process. Co-authored-by: Rukafuu <111822334+Rukafuu@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
1 participant
The
cleanupExpiredBansfunction has been refactored to use the project's PostgreSQL database via Prisma. It now correctly handlesBigIntcomparisons for theuntilfield. Additionally, the job has been enabled and scheduled to run every 12 hours in the backend server's startup routine.PR created automatically by Jules for task 4507734982390951293 started by @Rukafuu