nedb-engine-client 3.0.0__tar.gz → 3.2.0__tar.gz

{nedb_engine_client-3.0.0 → nedb_engine_client-3.2.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: nedb-engine-client
-Version: 3.0.0
+Version: 3.2.0
 Summary: Async Python client for nedbd — the nedb-engine server daemon
 Author: Eth-Interchained
 License: MIT
@@ -37,11 +37,20 @@ Connect to any running `nedbd` instance — local or remote — with a clean asy
 
 ---
 
-## ⚠️ Upgrade your server to nedbd 2.8.6
+## ⚠️ Upgrade your server to nedbd 3.2.0
 
-This client talks to `nedbd`, so its durability comes from the server. **2.8.6 fixes three defects in
-2.8.5 and earlier** — a flush that hit a full disk silently discarded acknowledged writes, flush
-failures were unobservable, and `nedb-cli repair` could not actually rebuild a damaged id index.
+This client talks to `nedbd`, so its durability comes from the server. **Upgrade if you are on
+anything earlier than 3.2.0.**
+
+**3.2.0 — the embedded engine was pinning its own data directory.** The background flush ticker held
+a strong reference to the database in a loop that never exited, so the handle was never dropped: the
+exclusive data-dir `LOCK` was never released, reopening the same path in the same process failed with
+"locked by another process" naming your *own* pid, and every open leaked a thread and the whole
+database for the life of the process. Live in **2.8.5 through 3.1.0**.
+
+**2.8.6 fixed three defects in 2.8.5 and earlier** — a flush that hit a full disk silently discarded
+acknowledged writes, flush failures were unobservable, and `nedb-cli repair` could not actually
+rebuild a damaged id index.
 
 If a database ever returned rows and now returns none while `/verify` reports every object healthy,
 that is the lost-id-index symptom and it is recoverable:
@@ -126,7 +135,7 @@ NEDBD_DAG=1 NEDBD_CAST=1 nedbd --data ./data
 
 # Check health
 curl http://127.0.0.1:7070/health
-# {"ok":true,"version":"2.8.0","service":"nedbd","encrypted":true}
+# {"ok":true,"version":"3.2.0","service":"nedbd","encrypted":true}
 ```
 
 ---

{nedb_engine_client-3.0.0 → nedb_engine_client-3.2.0}/README.md

@@ -12,11 +12,20 @@ Connect to any running `nedbd` instance — local or remote — with a clean asy
 
 ---
 
-## ⚠️ Upgrade your server to nedbd 2.8.6
+## ⚠️ Upgrade your server to nedbd 3.2.0
 
-This client talks to `nedbd`, so its durability comes from the server. **2.8.6 fixes three defects in
-2.8.5 and earlier** — a flush that hit a full disk silently discarded acknowledged writes, flush
-failures were unobservable, and `nedb-cli repair` could not actually rebuild a damaged id index.
+This client talks to `nedbd`, so its durability comes from the server. **Upgrade if you are on
+anything earlier than 3.2.0.**
+
+**3.2.0 — the embedded engine was pinning its own data directory.** The background flush ticker held
+a strong reference to the database in a loop that never exited, so the handle was never dropped: the
+exclusive data-dir `LOCK` was never released, reopening the same path in the same process failed with
+"locked by another process" naming your *own* pid, and every open leaked a thread and the whole
+database for the life of the process. Live in **2.8.5 through 3.1.0**.
+
+**2.8.6 fixed three defects in 2.8.5 and earlier** — a flush that hit a full disk silently discarded
+acknowledged writes, flush failures were unobservable, and `nedb-cli repair` could not actually
+rebuild a damaged id index.
 
 If a database ever returned rows and now returns none while `/verify` reports every object healthy,
 that is the lost-id-index symptom and it is recoverable:
@@ -101,7 +110,7 @@ NEDBD_DAG=1 NEDBD_CAST=1 nedbd --data ./data
 
 # Check health
 curl http://127.0.0.1:7070/health
-# {"ok":true,"version":"2.8.0","service":"nedbd","encrypted":true}
+# {"ok":true,"version":"3.2.0","service":"nedbd","encrypted":true}
 ```
 
 ---

{nedb_engine_client-3.0.0 → nedb_engine_client-3.2.0}/nedb_client/__init__.py

@@ -12,5 +12,5 @@ Usage:
 
 from .client import NedbClient, NedbError
 
-__version__ = "3.0.0"
+__version__ = "3.2.0"
 __all__ = ["NedbClient", "NedbError"]

{nedb_engine_client-3.0.0 → nedb_engine_client-3.2.0}/nedb_engine_client.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: nedb-engine-client
-Version: 3.0.0
+Version: 3.2.0
 Summary: Async Python client for nedbd — the nedb-engine server daemon
 Author: Eth-Interchained
 License: MIT
@@ -37,11 +37,20 @@ Connect to any running `nedbd` instance — local or remote — with a clean asy
 
 ---
 
-## ⚠️ Upgrade your server to nedbd 2.8.6
+## ⚠️ Upgrade your server to nedbd 3.2.0
 
-This client talks to `nedbd`, so its durability comes from the server. **2.8.6 fixes three defects in
-2.8.5 and earlier** — a flush that hit a full disk silently discarded acknowledged writes, flush
-failures were unobservable, and `nedb-cli repair` could not actually rebuild a damaged id index.
+This client talks to `nedbd`, so its durability comes from the server. **Upgrade if you are on
+anything earlier than 3.2.0.**
+
+**3.2.0 — the embedded engine was pinning its own data directory.** The background flush ticker held
+a strong reference to the database in a loop that never exited, so the handle was never dropped: the
+exclusive data-dir `LOCK` was never released, reopening the same path in the same process failed with
+"locked by another process" naming your *own* pid, and every open leaked a thread and the whole
+database for the life of the process. Live in **2.8.5 through 3.1.0**.
+
+**2.8.6 fixed three defects in 2.8.5 and earlier** — a flush that hit a full disk silently discarded
+acknowledged writes, flush failures were unobservable, and `nedb-cli repair` could not actually
+rebuild a damaged id index.
 
 If a database ever returned rows and now returns none while `/verify` reports every object healthy,
 that is the lost-id-index symptom and it is recoverable:
@@ -126,7 +135,7 @@ NEDBD_DAG=1 NEDBD_CAST=1 nedbd --data ./data
 
 # Check health
 curl http://127.0.0.1:7070/health
-# {"ok":true,"version":"2.8.0","service":"nedbd","encrypted":true}
+# {"ok":true,"version":"3.2.0","service":"nedbd","encrypted":true}
 ```
 
 ---

{nedb_engine_client-3.0.0 → nedb_engine_client-3.2.0}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "nedb-engine-client"
-version = "3.0.0"
+version = "3.2.0"
 description = "Async Python client for nedbd — the nedb-engine server daemon"
 readme = "README.md"
 license = { text = "MIT" }