django-lambda-tasks 0.6.2__tar.gz → 0.6.4__tar.gz

{django_lambda_tasks-0.6.2 → django_lambda_tasks-0.6.4}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: django-lambda-tasks
-Version: 0.6.2
+Version: 0.6.4
 Summary: Run async tasks in a lambda function
 Requires-Python: >=3.10
 Requires-Dist: awslambdaric

{django_lambda_tasks-0.6.2 → django_lambda_tasks-0.6.4}/lambda_tasks/local_executor.py

@@ -2,6 +2,7 @@
 
 import atexit
 import logging
+import multiprocessing
 import signal
 import threading
 import uuid
@@ -23,14 +24,22 @@ def _pool_initializer() -> None:
     atexit as a fallback). This prevents workers from being killed
     mid-operation and leaking semaphores.
 
+    Closes all database connections before setting up Django. With the
+    forkserver context, workers don't inherit the parent's connections,
+    but AppConfig.ready() hooks may open connections during django.setup()
+    that should be closed before task execution begins.
+
     Then sets up Django for task execution.
     """
     signal.signal(signal.SIGINT, signal.SIG_IGN)
 
     import django
+    from django.db import connections
 
     django.setup()
 
+    connections.close_all()
+
 
 def _shutdown_pool() -> None:
     """Shut down the pool, releasing its POSIX semaphores promptly.
@@ -111,12 +120,22 @@ def _install_shutdown_handlers() -> None:
 
 
 def get_pool() -> ProcessPoolExecutor:
-    """Return the shared ProcessPoolExecutor, creating it on first call."""
+    """Return the shared ProcessPoolExecutor, creating it on first call.
+
+    Uses the "forkserver" multiprocessing context so that worker processes
+    are forked from a clean server process rather than from the Django parent.
+    This prevents workers from inheriting the parent's open database
+    connections (and other file descriptors), which would otherwise cause
+    "server closed the connection unexpectedly" errors in containerized
+    environments where close() in the child tears down the shared socket.
+    """
     global _pool
     if _pool is None:
         conf = LambdaTasksSettings()
+        mp_context = multiprocessing.get_context("forkserver")
         _pool = ProcessPoolExecutor(
             max_workers=conf.LOCAL_WORKERS,
+            mp_context=mp_context,
             initializer=_pool_initializer,
         )
         atexit.register(_shutdown_pool)

{django_lambda_tasks-0.6.2 → django_lambda_tasks-0.6.4}/pyproject.toml

@@ -7,7 +7,7 @@ packages = ["lambda_tasks"]
 
 [project]
 name = "django-lambda-tasks"
-version = "0.6.2"
+version = "0.6.4"
 description = "Run async tasks in a lambda function"
 readme = "README.md"
 requires-python = ">=3.10"

{django_lambda_tasks-0.6.2 → django_lambda_tasks-0.6.4}/tests/test_local_executor.py

@@ -189,6 +189,25 @@ class TestGetPool:
 
         assert lambda_tasks.local_executor._pool is pool
 
+    @pytest.mark.usefixtures("_reset_pool")
+    def test_get_pool_uses_forkserver_context(self, settings):
+        """get_pool() uses the forkserver multiprocessing context.
+
+        This prevents workers from inheriting the parent's open database
+        connections, which would cause connection errors in containerized
+        environments.
+        """
+        import lambda_tasks.local_executor
+
+        settings.LAMBDA_TASKS_LOCAL_WORKERS = 2
+        settings.LAMBDA_TASKS_EAGER = False
+
+        pool = lambda_tasks.local_executor.get_pool()
+
+        # ProcessPoolExecutor stores the context; forkserver processes
+        # use the ForkServerProcess type
+        assert pool._mp_context.get_start_method() == "forkserver"
+
 
 # ---------------------------------------------------------------------------
 # Property-based tests: get_pool() (Requirement 2)