without-durability-sqlite 0.0.2__tar.gz → 0.0.3__tar.gz

{without_durability_sqlite-0.0.2 → without_durability_sqlite-0.0.3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: without-durability-sqlite
-Version: 0.0.2
+Version: 0.0.3
 Summary: A without-durability checkpoint store and queue backed by one SQLite file, with no server and no third-party driver.
 Author: Josh Karpel
 Author-email: Josh Karpel <josh.karpel@gmail.com>
@@ -14,7 +14,7 @@ Classifier: Programming Language :: Python :: 3 :: Only
 Classifier: Programming Language :: Python :: 3.14
 Classifier: Topic :: Software Development :: Libraries
 Classifier: Typing :: Typed
-Requires-Dist: without-durability==0.0.2
+Requires-Dist: without-durability==0.0.3
 Requires-Python: >=3.14
 Description-Content-Type: text/markdown
 
@@ -30,6 +30,8 @@ from without_durability_sqlite import SqliteCheckpointer, SqliteDurable, SqliteS
 database = connect("workflows.db")
 await migrate(database)
 durable = SqliteDurable(SqliteCheckpointer(database), SqliteScheduler(database))
+...
+await database.aclose()
 ```
 
 It is the smallest thing that still meets every requirement the interface states,
@@ -56,4 +58,5 @@ See the
 (with the [API reference](https://without.help/without-durability-sqlite/reference/))
 for the statements, why `connect` pays the fsync that the usual WAL advice trades
 away, why an effect here is a synchronous callback where the Postgres store's is
-`async`, and how the blocking driver is kept off the event loop.
+`async`, how the blocking driver is kept off the event loop, and why closing goes
+through `aclose` rather than the connection.

{without_durability_sqlite-0.0.2 → without_durability_sqlite-0.0.3}/README.md

@@ -10,6 +10,8 @@ from without_durability_sqlite import SqliteCheckpointer, SqliteDurable, SqliteS
 database = connect("workflows.db")
 await migrate(database)
 durable = SqliteDurable(SqliteCheckpointer(database), SqliteScheduler(database))
+...
+await database.aclose()
 ```
 
 It is the smallest thing that still meets every requirement the interface states,
@@ -36,4 +38,5 @@ See the
 (with the [API reference](https://without.help/without-durability-sqlite/reference/))
 for the statements, why `connect` pays the fsync that the usual WAL advice trades
 away, why an effect here is a synchronous callback where the Postgres store's is
-`async`, and how the blocking driver is kept off the event loop.
+`async`, how the blocking driver is kept off the event loop, and why closing goes
+through `aclose` rather than the connection.

{without_durability_sqlite-0.0.2 → without_durability_sqlite-0.0.3}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "uv_build"
 
 [project]
 name = "without-durability-sqlite"
-version = "0.0.2"
+version = "0.0.3"
 description = "A without-durability checkpoint store and queue backed by one SQLite file, with no server and no third-party driver."
 readme = "README.md"
 license = "MIT"
@@ -20,7 +20,7 @@ classifiers = [
     "Topic :: Software Development :: Libraries",
     "Typing :: Typed",
 ]
-dependencies = ["without-durability==0.0.2"]
+dependencies = ["without-durability==0.0.3"]
 
 [[project.authors]]
 name = "Josh Karpel"

{without_durability_sqlite-0.0.2 → without_durability_sqlite-0.0.3}/pyproject.toml.orig

@@ -4,7 +4,7 @@ build-backend = "uv_build"
 
 [project]
 name = "without-durability-sqlite"
-version = "0.0.2"
+version = "0.0.3"
 description = "A without-durability checkpoint store and queue backed by one SQLite file, with no server and no third-party driver."
 readme = "README.md"
 license = "MIT"
@@ -24,7 +24,7 @@ classifiers = [
     "Typing :: Typed",
 ]
 dependencies = [
-    "without-durability==0.0.2",
+    "without-durability==0.0.3",
 ]
 
 [tool.uv.sources]

{without_durability_sqlite-0.0.2 → without_durability_sqlite-0.0.3}/src/without_durability_sqlite/store.py

@@ -236,6 +236,7 @@ class Database:
     Build it with `connect`, which applies the pragmas that make this durable rather than
     merely persistent. Share one between the checkpoint store and the queue: that is what
     makes `SqliteDurable.arrive` a single commit, and it is checked rather than assumed.
+    Close it with `aclose`, never `connection.close()`, for the reason given there.
     """
 
     connection: sqlite3.Connection
@@ -272,6 +273,34 @@ class Database:
         running.add_done_callback(lambda _finished: self.guard.release())
         return await asyncio.shield(running)
 
+    async def aclose(self) -> None:
+        """
+        Close the connection once nobody is inside it.
+
+        The other half of `run`'s handshake, and the reason a caller must never reach
+        for `connection.close()` itself. `sqlite3.close()` frees the connection and
+        finalizes its statements; a thread still executing one is then reading freed
+        memory, which segfaults the process rather than raising. `run` makes that
+        reachable by design, since a cancelled caller unwinds while its thread runs on,
+        so a shutdown that follows a cancellation is exactly when the two meet: the
+        worker's task is cancelled, the statement it left behind is still in flight, and
+        the close lands on top of it.
+
+        Taking the guard is what waits that out, because `run` releases it from the
+        thread rather than from its caller. That wait is unbounded: an effect hung
+        inside a `run` thread holds the guard until it returns, and cancelling this
+        coroutine while it is parked on the guard abandons the close, leaving the
+        connection open. The guard is then let go again, so a `run` arriving after
+        this fails on a closed connection, which is the loud version of a bug that
+        would otherwise be silent.
+
+        The close itself goes to a thread like every other driver call: under WAL it
+        runs the final checkpoint (and, with `synchronous=FULL`, an fsync), which is
+        real disk I/O that does not belong on the event loop.
+        """
+        async with self.guard:
+            await asyncio.to_thread(self.connection.close)
+
 
 def connect(path: Path | str, *, timeout: timedelta = timedelta(seconds=5)) -> Database:
     """