dirsql 0.4.3__tar.gz → 0.4.5__tar.gz

{dirsql-0.4.3 → dirsql-0.4.5}/Cargo.lock

@@ -500,7 +500,7 @@ dependencies = [
 
 [[package]]
 name = "dirsql-py-ext"
-version = "0.4.3"
+version = "0.4.5"
 dependencies = [
  "dirsql",
  "pyo3",

{dirsql-0.4.3 → dirsql-0.4.5}/Cargo.toml

@@ -22,6 +22,18 @@ thiserror = "2"
 tokio = { version = "1", features = ["rt", "sync"] }
 futures-channel = "0.3"
 
+# Cargo's default release profile ships every binary unstripped, without
+# cross-crate optimization. The three published artifacts (CLI bin, pyo3
+# extension, napi addon) are each a statically linked copy of the whole core,
+# so the defaults cost ~31% of every download (#717).
+#
+# `panic` stays at the default `unwind`: pyo3 and napi turn Rust panics into
+# Python/JS exceptions, which requires unwinding.
+[profile.release]
+strip = "symbols"
+lto = "fat"
+codegen-units = 1
+
 [workspace.lints.rust]
 unsafe_code = "forbid"
 rust_2018_idioms = { level = "warn", priority = -1 }

{dirsql-0.4.3 → dirsql-0.4.5}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: dirsql
-Version: 0.4.3
+Version: 0.4.5
 Requires-Dist: tomli>=2 ; python_full_version < '3.11'
 Summary: Ephemeral SQL index over a local directory
 Keywords: sql,filesystem,directory,sqlite,index

{dirsql-0.4.3 → dirsql-0.4.5}/dirsql/_async.py

@@ -182,6 +182,23 @@ class DirSQL:
         assert db is not None  # ready() returned, so _init_bg set _db
         return await asyncio.to_thread(db.query, sql)
 
+    async def scan_failures(self):
+        """The files the initial scan could not index.
+
+        Each entry carries ``path`` (relative to the root) and ``message``
+        (the hook's own error). Empty after a clean scan, which is the signal
+        to check: a non-empty list means the index is *incomplete*, not wrong,
+        and those files are retried on the next scan.
+
+        Awaits :meth:`ready` first, so the scan has finished before the answer
+        is read -- otherwise a caller could see an empty list simply because
+        the scan had not reached the failing file yet.
+        """
+        await self.ready()
+        db = self._db
+        assert db is not None  # ready() returned, so _init_bg set _db
+        return db.scan_failures()
+
     def watch(self):
         """Start watching for file changes. Returns an async iterable of RowEvent.
 

{dirsql-0.4.3 → dirsql-0.4.5}/packages/python/Cargo.toml

@@ -4,7 +4,7 @@ name = "dirsql-py-ext"
 # pypi/maturin handler can rewrite it via `write-version` before
 # `maturin build`. `pyproject.toml` declares `dynamic = ["version"]`
 # and maturin reads this field. Mirrors `packages/rust/Cargo.toml`.
-version = "0.4.3"
+version = "0.4.5"
 # abi3 note: the `abi3-py310` pyo3 feature (below) builds ONE stable-ABI
 # `cp310-abi3` wheel per platform that loads on every CPython >= 3.10
 # (matching `pyproject.toml`'s `requires-python = ">=3.10"`), instead of

dirsql-0.4.5/packages/python/changelog.d/2026-08-02-release-profile.md

@@ -0,0 +1,5 @@
+**Changed** — the wheel's compiled artifacts are now stripped and built with
+fat LTO, shrinking the `_dirsql.abi3.so` extension ~28% (6.94 MB → 4.99 MB) and
+the bundled CLI binary ~33% (9.17 MB → 6.14 MB).
+
+Build-only: no API or behavior change.

dirsql-0.4.5/packages/python/changelog.d/2026-08-02-scan-failures.md

@@ -0,0 +1,18 @@
+**Added**
+
+`await db.scan_failures()` returns the files the initial scan could not index —
+a list of `ScanFailure`, each with `path` (relative to the root) and `message`
+(the hook's own error). Empty after a clean scan (#715).
+
+This closes a gap opened by #714. A file whose `on_file` hook raises, or whose
+row the table rejects under `strict`, is skipped rather than failing the scan —
+so a Python caller who previously got an exception got nothing at all: a
+database quietly holding fewer rows, with no way to ask which files were
+dropped. `scan_failures()` is that way.
+
+It reports; it does not gate. The rows that did land are unaffected, and a
+skipped file never enters the persistent index, so it is retried on the next
+scan — the index is incomplete, never wrong.
+
+Awaits `ready()` first, so an empty list means the scan finished cleanly rather
+than that it had not yet reached the failing file.

dirsql-0.4.5/packages/python/e2e-attestations/claude-715-binding-scan-failures.json

@@ -0,0 +1,7 @@
+{
+  "command": "uv run python -m pytest tests/e2e/ -x -q",
+  "ran_at": 1785678666,
+  "exit_code": 0,
+  "commit": "7de7557be856f19685344a4118e1ead9e4bae405",
+  "branch": "claude/715-binding-scan-failures"
+}

{dirsql-0.4.3 → dirsql-0.4.5}/packages/python/src/lib.rs

@@ -97,6 +97,31 @@ mod python {
         }
     }
 
+    /// One file the initial scan could not index, with the hook's own error.
+    ///
+    /// A scan failure is not a scan *error*: the other files are indexed and
+    /// the database is usable. This is how a caller learns the index is
+    /// incomplete, and which files are missing from it.
+    #[pyclass(name = "ScanFailure", frozen)]
+    struct PyScanFailure {
+        /// Path relative to the scan root.
+        #[pyo3(get)]
+        path: String,
+        /// The hook's error, as it rendered it.
+        #[pyo3(get)]
+        message: String,
+    }
+
+    #[pymethods]
+    impl PyScanFailure {
+        fn __repr__(&self) -> String {
+            format!(
+                "ScanFailure(path={:?}, message={:?})",
+                self.path, self.message
+            )
+        }
+    }
+
     /// Synchronous binding class. `dirsql._async.DirSQL` wraps it with
     /// `asyncio.to_thread` to produce the async public API.
     #[pyclass(name = "DirSQL")]
@@ -179,6 +204,17 @@ mod python {
             Ok(list.unbind())
         }
 
+        fn scan_failures(&self) -> Vec<PyScanFailure> {
+            self.inner
+                .scan_failures()
+                .iter()
+                .map(|f| PyScanFailure {
+                    path: f.path.clone(),
+                    message: f.message.clone(),
+                })
+                .collect()
+        }
+
         fn _start_watcher(&self, py: Python<'_>) -> PyResult<()> {
             let db = self.inner.clone();
             py.detach(move || db.start_watching()).map_err(to_py_err)
@@ -415,6 +451,7 @@ mod python {
         m.add_class::<PyTable>()?;
         m.add_class::<PyDirSQL>()?;
         m.add_class::<PyRowEvent>()?;
+        m.add_class::<PyScanFailure>()?;
         Ok(())
     }
 

dirsql-0.4.5/packages/rust/changelog.d/2026-08-02-release-profile.md

@@ -0,0 +1,7 @@
+**Changed** — release builds now strip symbols, run fat LTO, and use a single
+codegen unit, so the published `dirsql` binary is ~33% smaller (linux-x64:
+9.17 MB → 6.14 MB; 3.49 MB → 2.80 MB gzipped).
+
+Build-only: no API, CLI or behavior change. `panic` stays at the default
+`unwind`, which the pyo3 and napi bindings need to turn Rust panics into
+Python/JS exceptions. Release build time rises ~2m10s → ~2m38s.