Files
hipmi/CHANGELOG_BRANCH.md
bagasbanuna d43f3762a3 Fixed Bug Server
## Summary
This branch contains several bug fixes and performance improvements, primarily focusing on:
- Database connection management
- MQTT client stability
- Logging optimization
- API enhancements

## Detailed Changes

### Fixed Issues
1. **Database Connection Management**
   - Removed  from user-validate API route to prevent connection pool exhaustion
   - Added proper connection handling in global Prisma setup
   - Reduced logging verbosity in production environments

2. **MQTT Client Improvements**
   - Enhanced MQTT client initialization with proper error handling
   - Added reconnection logic with configurable intervals
   - Implemented cleanup functions to prevent memory leaks
   - Added separate initialization logic for server and client-side code

3. **Logging Optimization**
   - Removed excessive logging in middleware that was causing high CPU usage
   - Configured appropriate log levels for development and production

4. **Component Stability**
   - Added safety checks in text editor component to prevent MQTT operations on the server side
   - Improved MQTT publishing logic with client availability checks

### New Files
-  - Utility functions for safe database operations

### Modified Files
1.
   - Removed problematic  call

2.
   - Configured different logging levels for dev/prod
   - Removed process listeners that were causing disconnections
   - Exported prisma instance separately

3.
   - Removed excessive logging statements

4.
   - Enhanced initialization with error handling
   - Added reconnection and timeout configurations

5.
   - Added proper cleanup functions
   - Improved connection handling

6.
   - Added MQTT client availability checks
   - Prevented server-side MQTT operations

### Performance Improvements
- Reduced database connection overhead
- Optimized MQTT connection handling
- Eliminated unnecessary logging in production
- Better memory management with proper cleanup functions

### No Issue
2026-02-12 16:29:03 +08:00

2.2 KiB

Changelog for Branch: fixed-bug/12-feb-26

Summary

This branch contains several bug fixes and performance improvements, primarily focusing on:

  • Database connection management
  • MQTT client stability
  • Logging optimization
  • API enhancements

Detailed Changes

Fixed Issues

  1. Database Connection Management

    • Removed prisma.$disconnect() from user-validate API route to prevent connection pool exhaustion
    • Added proper connection handling in global Prisma setup
    • Reduced logging verbosity in production environments
  2. MQTT Client Improvements

    • Enhanced MQTT client initialization with proper error handling
    • Added reconnection logic with configurable intervals
    • Implemented cleanup functions to prevent memory leaks
    • Added separate initialization logic for server and client-side code
  3. Logging Optimization

    • Removed excessive logging in middleware that was causing high CPU usage
    • Configured appropriate log levels for development and production
  4. Component Stability

    • Added safety checks in text editor component to prevent MQTT operations on the server side
    • Improved MQTT publishing logic with client availability checks

New Files

  • src/lib/prismaUtils.ts - Utility functions for safe database operations

Modified Files

  1. src/app/api/user-validate/route.ts

    • Removed problematic prisma.$disconnect() call
  2. src/lib/prisma.ts

    • Configured different logging levels for dev/prod
    • Removed process listeners that were causing disconnections
    • Exported prisma instance separately
  3. src/middleware.tsx

    • Removed excessive logging statements
  4. src/util/mqtt_client.ts

    • Enhanced initialization with error handling
    • Added reconnection and timeout configurations
  5. src/util/mqtt_loader.tsx

    • Added proper cleanup functions
    • Improved connection handling
  6. src/app_modules/_global/component/new/comp_V3_text_editor_stiker.tsx

    • Added MQTT client availability checks
    • Prevented server-side MQTT operations

Performance Improvements

  • Reduced database connection overhead
  • Optimized MQTT connection handling
  • Eliminated unnecessary logging in production
  • Better memory management with proper cleanup functions