log-foundry 0.10.2.dev116__tar.gz → 0.10.2.dev118__tar.gz

{log_foundry-0.10.2.dev116 → log_foundry-0.10.2.dev118}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: log-foundry
-Version: 0.10.2.dev116
+Version: 0.10.2.dev118
 Summary: Generate logs for your console and JSON events for downstream consumption.
 License-Expression: MIT
 License-File: LICENSE

{log_foundry-0.10.2.dev116 → log_foundry-0.10.2.dev118}/pyproject.toml

@@ -74,7 +74,7 @@ keywords = [
 # vulnerability-reporting channel. The repository is still named `log-forge` — the ORIGINAL name,
 # which PyPI rejected for the distribution — so these URLs deliberately do not match the package
 # name. See the note on `name` above before "correcting" them.
-version = "0.10.2.dev116"
+version = "0.10.2.dev118"
 
 [project.urls]
 Homepage = "https://github.com/agriffi10/log-forge"
@@ -127,12 +127,13 @@ exclude = [
 pytest = "^9.0"
 pytest-asyncio = "^1.4.0"        # for testing async @trace (guide Phase 8)
 pytest-cov = "^7.1.0"
-# The suite is sleep-bound, not CPU-bound: 1,871 tests spend ~116 s of wall clock at 7%
+# The suite is sleep-bound, not CPU-bound: it spends most of its wall clock at single-digit
 # CPU, because the bounds this library promises (a 30 s shutdown budget, a backoff, a
 # wedged drain) are proved by waiting for them. Two tests block 30 s each. Distributing
-# across processes therefore buys almost the whole wall clock back — measured 125.9 s ->
-# 34.8 s at `-n 12 --dist worksteal` — where caching the dependency install could only ever
-# save the 18 s that install takes.
+# across processes therefore buys almost the whole wall clock back — measured at `e565e22`
+# as 125.9 s -> 34.8 s at `-n 12 --dist worksteal`, where caching the dependency install
+# could only ever save the 18 s that install takes. The test count that stood here is gone:
+# it moved with every spec, and the argument never rested on it.
 pytest-xdist = "^3.8"
 # Bounded to a minor, not left open. Ruff's DEFAULT rule set is not stable across minors —
 # 0.16.0 widened it from 59 rules to 413 — so an open constraint lets a release change what
@@ -230,8 +231,11 @@ select = [
     "F",                    # pyflakes
     "E4", "E7", "E9",       # pycodestyle errors. NOT E5: `line-length` above is advisory
                             # today (it feeds `ruff format`, which this repo does not run) and
-                            # 52 lines in src+tests exceed it. Enforcing it is 52 reflows and
-                            # its own decision.
+                            # enough lines in src+tests exceed it that enforcing it is a reflow
+                            # sweep, which is its own decision. No count here on purpose: the one
+                            # this comment carried was 52, and `3c973b9` measured 86. Get the
+                            # current cost from
+                            # `ruff check --select E5 --statistics src tests` before deciding.
     "W",
     "I",                    # import sorting
     "B",                    # bugbear

{log_foundry-0.10.2.dev116 → log_foundry-0.10.2.dev118}/src/log_foundry/worker.py

@@ -905,9 +905,14 @@ class Worker:
         state the caller is being told about either way, and it bounds only the slice — a negative
         or zero remainder clamps to an immediate attempt rather than raising, where ``Queue.put``
         rejects a negative timeout before it even looks at capacity. That makes the **put** total,
-        which is what ``Raises: None`` said all along; the *wait* below is unchanged and a timeout
-        large enough to overflow ``time_t`` still raises out of it, on this tree and on every
-        earlier one.
+        which is what ``Raises: None`` said all along. That raise was never *public*, on two separate
+        counts: ``Worker`` is not exported, so this is not a public call, and
+        ``_lifecycle._flush_worker``'s bare ``except Exception`` caught that ``ValueError`` and reported
+        ``"thread-died"`` on a live thread with ``stopped_reason`` at ``None``, so what a caller
+        sees change is the token, not an exception. The *wait* below is unchanged and a timeout
+        large enough to overflow ``time_t`` still raises out of **this** method, on this tree and
+        every earlier one — and is caught by that same ``except Exception`` before a public caller
+        sees it, exactly as the ``ValueError`` was. The distinction drawn above holds there too.
 
         Args:
           marker: The marker to enqueue.