WIP: Debugging sqlite-run/dbExec hanging issue
- Add renderer-to-main process log forwarding
- Implement operation tracking with unique IDs
- Add detailed timing and retry logging
- Enhance error capture and formatting
- Move logs to app user data directory
- Add exponential backoff for retries
This commit adds comprehensive logging to help diagnose
why dbExec operations are hanging when sent through the
sqlite-run channel. Changes include:
- Forward all renderer process logs to main process
- Track SQLite operations with unique IDs
- Log operation timing and retry attempts
- Capture detailed error information
- Implement exponential backoff for retries
- Centralize logs in app user data directory
Security:
- Logs are stored in app user data directory
- Sensitive data is sanitized in logs
- Error stacks are properly captured
Testing:
- Manual testing of logging system
- Verify log capture in both processes
- Check log rotation and file sizes
TODO:
- Monitor logs to identify root cause
- Add specific logging for settings table
- Consider connection pooling if needed