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

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

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: log-foundry
-Version: 0.10.2.dev116
+Version: 0.10.2.dev117
 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.dev117}/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.dev117"
 
 [project.urls]
 Homepage = "https://github.com/agriffi10/log-forge"

{log_foundry-0.10.2.dev116 → log_foundry-0.10.2.dev117}/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.