stateous 0.2.1__tar.gz → 0.2.2__tar.gz

{stateous-0.2.1 → stateous-0.2.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: stateous
-Version: 0.2.1
+Version: 0.2.2
 Summary: A process as a graph of states. A control plane keeps every token durable.
 Project-URL: Homepage, https://github.com/StateousLabs/stateous
 Project-URL: Source, https://github.com/StateousLabs/stateous
@@ -38,6 +38,12 @@ Description-Content-Type: text/markdown
 
 # Stateous
 
+[![CI](https://github.com/StateousLabs/stateous/actions/workflows/ci.yml/badge.svg)](https://github.com/StateousLabs/stateous/actions/workflows/ci.yml)
+[![PyPI](https://img.shields.io/pypi/v/stateous?cacheSeconds=3600)](https://pypi.org/project/stateous/)
+[![Python](https://img.shields.io/pypi/pyversions/stateous?cacheSeconds=3600)](https://pypi.org/project/stateous/)
+[![Docs](https://img.shields.io/badge/docs-GitHub%20Pages-blue)](https://stateouslabs.github.io/stateous/)
+[![License](https://img.shields.io/pypi/l/stateous?cacheSeconds=3600)](https://github.com/StateousLabs/stateous/blob/main/LICENSE)
+
 Stateous runs a process as a graph of states, and keeps every token of it durable.
 
 You write the graph in Python. A control plane keeps every token and chooses each next state. A supervisor, on any computer, does the work and reports what happened. The supervisor never sees the graph. It knows only which states it serves, and which outcomes each state allows.

{stateous-0.2.1 → stateous-0.2.2}/README.md

@@ -1,5 +1,11 @@
 # Stateous
 
+[![CI](https://github.com/StateousLabs/stateous/actions/workflows/ci.yml/badge.svg)](https://github.com/StateousLabs/stateous/actions/workflows/ci.yml)
+[![PyPI](https://img.shields.io/pypi/v/stateous?cacheSeconds=3600)](https://pypi.org/project/stateous/)
+[![Python](https://img.shields.io/pypi/pyversions/stateous?cacheSeconds=3600)](https://pypi.org/project/stateous/)
+[![Docs](https://img.shields.io/badge/docs-GitHub%20Pages-blue)](https://stateouslabs.github.io/stateous/)
+[![License](https://img.shields.io/pypi/l/stateous?cacheSeconds=3600)](https://github.com/StateousLabs/stateous/blob/main/LICENSE)
+
 Stateous runs a process as a graph of states, and keeps every token of it durable.
 
 You write the graph in Python. A control plane keeps every token and chooses each next state. A supervisor, on any computer, does the work and reports what happened. The supervisor never sees the graph. It knows only which states it serves, and which outcomes each state allows.

{stateous-0.2.1 → stateous-0.2.2}/docs/reference/files.md

@@ -149,7 +149,7 @@ With `--stateous-path PATH`, the file also has a `[tool.uv.sources]` table. The
 name = "sdlc-supervisor"
 version = "0.1.0"
 requires-python = ">=3.12"
-dependencies = ["stateous>=0.2.1"]
+dependencies = ["stateous>=0.2.2"]
 
 # A local checkout of Stateous: delete this table to use Stateous from PyPI.
 [tool.uv.sources]

{stateous-0.2.1 → stateous-0.2.2}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "stateous"
-version = "0.2.1"
+version = "0.2.2"
 description = "A process as a graph of states. A control plane keeps every token durable."
 license = "Apache-2.0"
 license-files = ["LICENSE", "NOTICE"]

{stateous-0.2.1 → stateous-0.2.2}/scripts/check.py

@@ -1,8 +1,8 @@
 """Every check, in order: `uv run python scripts/check.py`.
 
-GitHub Actions does not run for this repository, so this script is the gate
-before a commit. It runs the lint rules, the format check, the types, the import
-contracts, the build of the documentation site and the tests. It stops at the first
+Run it before a commit. CI (.github/workflows/ci.yml) runs it too. It runs the lint
+rules, the format check, the types, the import contracts, the build of the
+documentation site and the tests. It stops at the first
 check that fails, and names it.
 """
 

{stateous-0.2.1 → stateous-0.2.2}/src/stateous/cli/main.py

@@ -294,12 +294,15 @@ def main() -> None:
     except OSError as error:
         if not _closed_pipe(error, stdout.failure):
             raise
-        # Python flushes stdout again at exit: send it to nothing, so that flush cannot fail.
-        nothing = os.open(os.devnull, os.O_WRONLY)
-        os.dup2(nothing, sys.stdout.fileno())
         sys.exit(1)
     finally:
         sys.stdout = stdout.stream
+        # Python flushes stdout again at exit: send it to nothing, so that flush cannot
+        # fail. Also when Click caught the EPIPE itself and exited with code 1.
+        if stdout.failure is not None and _closed_pipe(stdout.failure, stdout.failure):
+            nothing = os.open(os.devnull, os.O_WRONLY)
+            os.dup2(nothing, sys.stdout.fileno())
+            os.close(nothing)
 
 
 class _Stdout:

{stateous-0.2.1 → stateous-0.2.2}/tests/unit/cli/test_closed_output.py

@@ -107,3 +107,31 @@ def test_einval_from_a_write_to_stdout_is_quiet(
 
     assert raised.value.code == 1
     assert capsys.readouterr().err == ""
+
+
+class BrokenStdout(ClosedStdout):
+    """Stdout whose reader closed the pipe, as Linux and macOS report it: EPIPE. Click
+    catches EPIPE itself and exits with code 1."""
+
+    def write(self, text: str) -> int:
+        raise BrokenPipeError(errno.EPIPE, "Broken pipe")
+
+
+def test_epipe_sends_the_rest_of_stdout_to_nothing(
+    tmp_path: Path, monkeypatch: pytest.MonkeyPatch
+) -> None:
+    """Else Python flushes stdout again at exit, that flush fails, and the exit code is 120."""
+    target = tmp_path / "stdout"
+    fd = os.open(target, os.O_WRONLY | os.O_CREAT)
+    try:
+        monkeypatch.setattr(sys, "stdout", BrokenStdout(fd))
+
+        with pytest.raises(SystemExit) as raised:
+            run_main("compile", str(FLOW), "--out", str(tmp_path / "sdlc.json"))
+
+        os.write(fd, b"after the command")
+    finally:
+        os.close(fd)
+
+    assert raised.value.code == 1
+    assert target.read_bytes() == b""