refactor:Refactors transaction management and datetime usage

Signed-off-by: -LAN- <laipz8200@outlook.com>

api/events/event_handlers/update_provider_when_message_created.py

@@ -1,6 +1,6 @@
 import logging
 import time as time_module
-from datetime import UTC, datetime
+from datetime import datetime
 from typing import Any, Optional
 
 from pydantic import BaseModel
@@ -12,6 +12,7 @@ from core.entities.provider_entities import QuotaUnit, SystemConfiguration
 from core.plugin.entities.plugin import ModelProviderID
 from events.message_event import message_was_created
 from extensions.ext_database import db
+from libs import datetime_utils
 from models.model import Message
 from models.provider import Provider, ProviderType
 
@@ -69,7 +70,7 @@ def handle(sender: Message, **kwargs):
 
     tenant_id = application_generate_entity.app_config.tenant_id
     provider_name = application_generate_entity.model_conf.provider
-    current_time = datetime.now(UTC).replace(tzinfo=None)
+    current_time = datetime_utils.naive_utc_now()
 
     # Prepare updates for both scenarios
     updates_to_perform: list[_ProviderUpdateOperation] = []
@@ -171,7 +172,7 @@ def _calculate_quota_usage(
             return 1
         return None
     except Exception as e:
-        logger.warning(f"Failed to calculate quota usage: {e}")
+        logger.exception("Failed to calculate quota usage")
         return None
 
 
@@ -182,7 +183,6 @@ def _execute_provider_updates(updates_to_perform: list[_ProviderUpdateOperation]
 
     # Use SQLAlchemy's context manager for transaction management
     # This automatically handles commit/rollback
-    try:
     with db.session.begin():
         # Use a single transaction for all updates
         for update_operation in updates_to_perform:
@@ -231,8 +231,3 @@ def _execute_provider_updates(updates_to_perform: list[_ProviderUpdateOperation]
                 )
 
         logger.debug(f"Successfully processed {len(updates_to_perform)} Provider updates")
-
-    except Exception as e:
-        # The context manager automatically handles rollback
-        logger.exception("Failed to update Provider")
-        raise