pydocket 0.1.1__tar.gz → 0.1.2__tar.gz

pydocket-0.1.1/.cursorrules → pydocket-0.1.2/.cursor/rules/general.mdc

@@ -1,3 +1,10 @@
+---
+description:
+globs:
+alwaysApply: true
+---
+
+# about docket
 docket is a distributed background task system for Python functions with a focus
 on the scheduling of future work as seamlessly and efficiency as immediate work.
 
@@ -22,20 +29,3 @@ idempotency of an execution.
 
 A docket worker should be as easily usable in code as it is from the command line,
 and should be a breeze to use with test suites.
-
-# Code style
-
-When generating production code, always use full parameter and return type hints
-for every function. Never generate useless inline comments that just reiterate
-what the code is doing. It's okay to include comments in the rare case there is
-something tricky going on.
-
-When generating tests, always use parameter type hints, but never include the
-`-> None` return type hint for a test function. For `pytest` fixtures, always
-generate both the parameter and return type hints.
-
-When generating tests, favor smaller, focused tests that use fixtures for reuse.
-Don't include extraneous comments in the test code unless something needs more
-clarity. Always generate a docstring using "should" language to describe the
-aspect of the system the test is checking. Use simple direct language and avoid
-sounding stuffy, but make these complete sentences.

pydocket-0.1.2/.cursor/rules/python-style.mdc

@@ -0,0 +1,22 @@
+---
+description: how to write python
+globs: *.py
+alwaysApply: false
+---
+
+# Code style
+
+When generating production code, always use full parameter and return type hints
+for every function. Never generate useless inline comments that just reiterate
+what the code is doing. It's okay to include comments in the rare case there is
+something tricky going on.
+
+When generating tests, always use parameter type hints, but never include the
+`-> None` return type hint for a test function. For `pytest` fixtures, always
+generate both the parameter and return type hints.
+
+When generating tests, favor smaller, focused tests that use fixtures for reuse.
+Don't include extraneous comments in the test code unless something needs more
+clarity. Always generate a docstring using "should" language to describe the
+aspect of the system the test is checking. Use simple direct language and avoid
+sounding stuffy, but make these complete sentences.

{pydocket-0.1.1 → pydocket-0.1.2}/.github/workflows/ci.yml

@@ -7,6 +7,7 @@ on:
     branches: [main]
   workflow_call:
 
+
 jobs:
   test:
     name: Test Python ${{ matrix.python-version }}

{pydocket-0.1.1 → pydocket-0.1.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: pydocket
-Version: 0.1.1
+Version: 0.1.2
 Summary: A distributed background task system for Python functions
 Project-URL: Homepage, https://github.com/chrisguidry/docket
 Project-URL: Bug Tracker, https://github.com/chrisguidry/docket/issues

{pydocket-0.1.1 → pydocket-0.1.2}/pyproject.toml

@@ -68,6 +68,8 @@ packages = ["src/docket"]
 addopts = "--cov=src/docket --cov=tests --cov-report=term-missing --cov-branch"
 asyncio_mode = "auto"
 asyncio_default_fixture_loop_scope = "session"
+filterwarnings = ["error"]
+
 
 [tool.pyright]
 include = ["src", "tests"]

{pydocket-0.1.1 → pydocket-0.1.2}/src/docket/worker.py

@@ -262,7 +262,7 @@ class Worker:
                         )
 
                     redeliveries: RedisMessages
-                    _, redeliveries, _ = await redis.xautoclaim(
+                    _, redeliveries, *_ = await redis.xautoclaim(
                         name=self.docket.stream_key,
                         groupname=self.docket.worker_group_name,
                         consumername=self.name,

{pydocket-0.1.1 → pydocket-0.1.2}/tests/conftest.py

@@ -1,7 +1,7 @@
 import time
 from datetime import datetime, timezone
 from functools import partial
-from typing import AsyncGenerator, Callable, Generator, Iterable, cast
+from typing import Any, AsyncGenerator, Callable, Generator, Iterable, cast
 from unittest.mock import AsyncMock
 from uuid import uuid4
 
@@ -46,12 +46,14 @@ def redis_server(redis_port: int) -> Generator[Container, None, None]:
         auto_remove=True,
     )
 
+    url = f"redis://localhost:{redis_port}/0"
+
     while True:
         try:
-            with Redis.from_url(f"redis://localhost:{redis_port}/0") as r:  # type: ignore
+            with Redis.from_url(url) as r:  # type: ignore
                 if r.ping():  # type: ignore
                     break
-        except redis.exceptions.ConnectionError:
+        except redis.exceptions.ConnectionError:  # pragma: no cover
             pass
 
         time.sleep(0.1)
@@ -59,8 +61,17 @@ def redis_server(redis_port: int) -> Generator[Container, None, None]:
     try:
         yield container
     finally:
+        with Redis.from_url(url) as r:  # type: ignore
+            info: dict[str, Any] = r.info()  # type: ignore
+
         container.stop()
 
+        # By the time the test suite finishes, there should have been no more open
+        # Redis connections (just the one that we used to ask about client connections).
+        assert info["connected_clients"] == 1, (
+            f"Expected 1 connected clients, but found {info['connected_clients']}"
+        )
+
 
 @pytest.fixture
 def redis_url(redis_server: Container, redis_port: int) -> str: