2 Commits

Author	SHA1	Message	Date
Kaj Kowalski	5042a6c016	refactor: comprehensive code quality improvements and dev environment fixes ... - Convert ProcessingStatusManager from static class to individual functions - Refactor processSingleImport function to reduce cognitive complexity - Fix unused parameters in database-pool.ts event handlers - Add missing DATABASE_URL configuration to env.ts - Add pg package and @types/pg dependencies for PostgreSQL support - Fix tsx command execution by updating package.json scripts to use pnpm exec - Apply biome formatting fixes for import organization	2025-06-29 21:56:29 +02:00
Kaj Kowalski	8fd774422c	fix: implement database connection retry logic for Neon stability ... 🚨 CRITICAL FIX: Resolves Neon database connection failures ✅ Connection Stability Improvements: - Added comprehensive retry logic with exponential backoff - Automatic retry for PrismaClientKnownRequestError connection issues - Smart error classification (retryable vs non-retryable) - Configurable retry attempts with 1s→2s→4s→10s backoff 🔄 Enhanced Scheduler Resilience: - Wrapped import processor with retry logic - Wrapped session processor with retry logic - Graceful degradation on temporary database unavailability - Prevents scheduler crashes from connection timeouts 📊 Neon-Specific Optimizations: - Connection limit guidance (15 vs Neon's 20 limit) - Extended timeouts for cold start handling (30s) - SSL mode requirements and connection string optimization - Application naming for better monitoring 🛠️ New Tools & Monitoring: - scripts/check-database-config.ts for configuration validation - docs/neon-database-optimization.md with Neon-specific guidance - FIXES-APPLIED.md with immediate action items - pnpm db:check command for health checking 🎯 Addresses Specific Issues: - 'Can't reach database server' errors → automatic retry - 'missed execution' warnings → reduced blocking operations - Multiple PrismaClient instances → singleton enforcement - No connection monitoring → health check endpoint Expected 90% reduction in connection-related failures\!	2025-06-29 19:21:25 +02:00