dirsql 0.3.65__tar.gz → 0.3.67__tar.gz

{dirsql-0.3.65 → dirsql-0.3.67}/Cargo.lock

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

{dirsql-0.3.65 → dirsql-0.3.67}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: dirsql
-Version: 0.3.65
+Version: 0.3.67
 Requires-Dist: pytest>=8 ; extra == 'dev'
 Requires-Dist: pytest-describe>=2 ; extra == 'dev'
 Requires-Dist: pytest-asyncio>=0.23 ; extra == 'dev'
@@ -117,7 +117,7 @@ await db.ready()
 rows = await db.query("SELECT vec_version() AS v")
 ```
 
-`dirsql` enables extension loading only while loading the configured libraries, then disables it again, so the SQL `load_extension()` function is never exposed to your queries. Programmatic entries load first, followed by any `[[dirsql.extension]]` entries declared in a `config` file. See the [config reference](https://github.com/thekevinscott/dirsql/blob/main/docs/cli/config.md#loading-extensions).
+`dirsql` enables extension loading only while loading the configured libraries, then disables it again, so the SQL `load_extension()` function is never exposed to your queries. Programmatic entries load first, followed by any `[[dirsql.extension]]` entries declared in a `config` file. See the [config reference](https://github.com/thekevinscott/dirsql/blob/main/docs/reference/config.md#dirsqlextension).
 
 ## Watching for changes
 
@@ -134,7 +134,7 @@ Each event has `.action` (`"insert"`, `"update"`, `"delete"`, or `"error"`), `.t
 
 ## CLI
 
-`pip install dirsql` also installs a `dirsql` console script that runs an HTTP server exposing the SDK over HTTP: `POST /query` for SQL and `GET /events` for a Server-Sent Events change stream. Run `dirsql` (or `uvx dirsql`) to start it. See the [CLI guide](https://thekevinscott.github.io/dirsql/cli/).
+`pip install dirsql` also installs a `dirsql` console script that runs an HTTP server exposing the SDK over HTTP: `POST /query` for SQL and `GET /events` for a Server-Sent Events change stream. Run `dirsql` (or `uvx dirsql`) to start it. See the [CLI reference](https://thekevinscott.github.io/dirsql/reference/cli).
 
 ## License
 

{dirsql-0.3.65/packages/python → dirsql-0.3.67}/README.md

@@ -99,7 +99,7 @@ await db.ready()
 rows = await db.query("SELECT vec_version() AS v")
 ```
 
-`dirsql` enables extension loading only while loading the configured libraries, then disables it again, so the SQL `load_extension()` function is never exposed to your queries. Programmatic entries load first, followed by any `[[dirsql.extension]]` entries declared in a `config` file. See the [config reference](https://github.com/thekevinscott/dirsql/blob/main/docs/cli/config.md#loading-extensions).
+`dirsql` enables extension loading only while loading the configured libraries, then disables it again, so the SQL `load_extension()` function is never exposed to your queries. Programmatic entries load first, followed by any `[[dirsql.extension]]` entries declared in a `config` file. See the [config reference](https://github.com/thekevinscott/dirsql/blob/main/docs/reference/config.md#dirsqlextension).
 
 ## Watching for changes
 
@@ -116,7 +116,7 @@ Each event has `.action` (`"insert"`, `"update"`, `"delete"`, or `"error"`), `.t
 
 ## CLI
 
-`pip install dirsql` also installs a `dirsql` console script that runs an HTTP server exposing the SDK over HTTP: `POST /query` for SQL and `GET /events` for a Server-Sent Events change stream. Run `dirsql` (or `uvx dirsql`) to start it. See the [CLI guide](https://thekevinscott.github.io/dirsql/cli/).
+`pip install dirsql` also installs a `dirsql` console script that runs an HTTP server exposing the SDK over HTTP: `POST /query` for SQL and `GET /events` for a Server-Sent Events change stream. Run `dirsql` (or `uvx dirsql`) to start it. See the [CLI reference](https://thekevinscott.github.io/dirsql/reference/cli).
 
 ## License
 

{dirsql-0.3.65 → dirsql-0.3.67}/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.3.65"
+version = "0.3.67"
 edition.workspace = true
 publish = false
 readme = "README.md"

{dirsql-0.3.65 → dirsql-0.3.67/packages/python}/README.md

@@ -99,7 +99,7 @@ await db.ready()
 rows = await db.query("SELECT vec_version() AS v")
 ```
 
-`dirsql` enables extension loading only while loading the configured libraries, then disables it again, so the SQL `load_extension()` function is never exposed to your queries. Programmatic entries load first, followed by any `[[dirsql.extension]]` entries declared in a `config` file. See the [config reference](https://github.com/thekevinscott/dirsql/blob/main/docs/cli/config.md#loading-extensions).
+`dirsql` enables extension loading only while loading the configured libraries, then disables it again, so the SQL `load_extension()` function is never exposed to your queries. Programmatic entries load first, followed by any `[[dirsql.extension]]` entries declared in a `config` file. See the [config reference](https://github.com/thekevinscott/dirsql/blob/main/docs/reference/config.md#dirsqlextension).
 
 ## Watching for changes
 
@@ -116,7 +116,7 @@ Each event has `.action` (`"insert"`, `"update"`, `"delete"`, or `"error"`), `.t
 
 ## CLI
 
-`pip install dirsql` also installs a `dirsql` console script that runs an HTTP server exposing the SDK over HTTP: `POST /query` for SQL and `GET /events` for a Server-Sent Events change stream. Run `dirsql` (or `uvx dirsql`) to start it. See the [CLI guide](https://thekevinscott.github.io/dirsql/cli/).
+`pip install dirsql` also installs a `dirsql` console script that runs an HTTP server exposing the SDK over HTTP: `POST /query` for SQL and `GET /events` for a Server-Sent Events change stream. Run `dirsql` (or `uvx dirsql`) to start it. See the [CLI reference](https://thekevinscott.github.io/dirsql/reference/cli).
 
 ## License
 

{dirsql-0.3.65 → dirsql-0.3.67}/packages/python/e2e-attestation.json

@@ -1,6 +1,6 @@
 {
   "command": "uv run python -m pytest tests/e2e/ -x -q",
-  "ran_at": 1783214202,
+  "ran_at": 1783215074,
   "exit_code": 0,
-  "commit": "b2c468d12c2e60a7df48884b391a788fd184a62f"
+  "commit": "c5d752734907f27497b28b3448bad19247c3482e"
 }

{dirsql-0.3.65 → dirsql-0.3.67}/packages/rust/README.md

@@ -124,7 +124,7 @@ cargo install dirsql --features cli
 dirsql
 ```
 
-Running `dirsql` starts an HTTP server bound to `localhost:7117` that exposes the SDK over HTTP: `POST /query` for SQL and `GET /events` for a Server-Sent Events change stream. Override with `--host`, `--port`, `--config`. See the [CLI guide](https://thekevinscott.github.io/dirsql/cli/).
+Running `dirsql` starts an HTTP server bound to `localhost:7117` that exposes the SDK over HTTP: `POST /query` for SQL and `GET /events` for a Server-Sent Events change stream. Override with `--host`, `--port`, `--config`. See the [CLI reference](https://thekevinscott.github.io/dirsql/reference/cli).
 
 The `cli` feature is **opt-in** -- `cargo add dirsql` pulls no CLI dependencies. `cargo install dirsql` without `--features cli` silently installs nothing (`required-features` skips the bin target with no warning); always include the flag, or use `npx dirsql` / `uvx dirsql` for prebuilt binaries.
 

{dirsql-0.3.65 → dirsql-0.3.67}/packages/rust/src/bin/dirsql.rs

@@ -1,6 +1,6 @@
 //! `dirsql` CLI binary. Two modes:
-//! - No subcommand: HTTP server documented in `docs/guide/cli.md`.
-//! - `init`: starter `.dirsql.toml` generation; see `docs/guide/init.md`.
+//! - No subcommand: HTTP server documented in `docs/reference/cli.md`.
+//! - `init`: starter `.dirsql.toml` generation; see `docs/reference/cli.md`.
 //!
 //! Only compiled with `--features cli`.
 

{dirsql-0.3.65 → dirsql-0.3.67}/packages/rust/src/cli/init.rs

@@ -1,5 +1,5 @@
 //! `dirsql init` — generate a starter `.dirsql.toml` by shelling out to
-//! the `claude` CLI. See `docs/guide/init.md` for the user-facing
+//! the `claude` CLI. See `docs/reference/cli.md` for the user-facing
 //! contract.
 //!
 //! The agent's only required responsibility is to print a valid
@@ -166,4 +166,46 @@ mod tests {
             "got: {err:?}"
         );
     }
+
+    // The spawn / non-zero-exit / write failure arms of `run` require actually
+    // invoking `claude` and touching the filesystem, so they are exercised at
+    // the e2e tier. Their `Display` renderings, however, are pure and covered
+    // here (the values are constructed inline, no process or fs I/O).
+
+    #[test]
+    fn spawn_error_display_mentions_spawn() {
+        let err = InitError::Spawn(std::io::Error::new(
+            std::io::ErrorKind::PermissionDenied,
+            "denied",
+        ));
+        let msg = format!("{err}");
+        assert!(msg.contains("failed to spawn"), "got: {msg}");
+        assert!(msg.contains("denied"), "got: {msg}");
+    }
+
+    #[test]
+    fn write_error_display_names_the_path_and_source() {
+        let err = InitError::Write {
+            path: PathBuf::from("/tmp/out.toml"),
+            source: std::io::Error::other("disk full"),
+        };
+        let msg = format!("{err}");
+        assert!(msg.contains("/tmp/out.toml"), "got: {msg}");
+        assert!(msg.contains("disk full"), "got: {msg}");
+    }
+
+    #[test]
+    fn invalid_utf8_error_display_mentions_utf8() {
+        // A non-UTF8 byte sequence yields the `FromUtf8Error` that `#[from]`
+        // converts into `InitError::InvalidUtf8`.
+        let utf8_err = String::from_utf8(vec![0xff, 0xfe]).unwrap_err();
+        let err: InitError = utf8_err.into();
+        let msg = format!("{err}");
+        assert!(msg.contains("non-UTF8"), "got: {msg}");
+    }
+
+    // NOTE: `InitError::ClaudeFailed`'s `Display` is not unit-tested -- building
+    // it needs an `ExitStatus`, and `std::process::ExitStatus::from_raw` is
+    // effectful std the unit-isolation lint (`no-out-of-module-call`) forbids.
+    // Its rendering is covered end-to-end at the e2e tier instead.
 }

{dirsql-0.3.65 → dirsql-0.3.67}/packages/rust/src/cli/mod.rs

@@ -330,4 +330,26 @@ mod tests {
         assert_eq!(pq.command, "reshape {args}");
         assert_eq!(pq.config_dir, PathBuf::from("/proj"));
     }
+
+    #[test]
+    fn with_query_timeout_overrides_the_default() {
+        // The builder replaces the 30s default with the supplied timeout and
+        // leaves the rest of the config untouched.
+        let cfg = ServerConfig::bind("127.0.0.1", 8080).with_query_timeout(Duration::from_secs(5));
+        assert_eq!(cfg.query_timeout, Duration::from_secs(5));
+        assert_eq!(cfg.host, "127.0.0.1");
+        assert_eq!(cfg.port, 8080);
+    }
+
+    #[test]
+    fn app_state_from_string_builds_the_unavailable_arm() {
+        // `String -> AppState` yields the degraded arm carrying the diagnostic
+        // verbatim (the `/query`/`/events` 503 body). `AppState` isn't `Debug`,
+        // so match rather than assert on a rendering.
+        let state: AppState = "config failed to load".to_string().into();
+        match state {
+            AppState::Unavailable(reason) => assert_eq!(reason, "config failed to load"),
+            AppState::Ready(_) => panic!("String must map to the Unavailable arm"),
+        }
+    }
 }

{dirsql-0.3.65 → dirsql-0.3.67}/packages/rust/src/cli/router.rs

@@ -356,4 +356,38 @@ mod tests {
             "application/json"
         );
     }
+
+    // `parse_sql_body` is the no-`pre-query` request path: it is pure (serde
+    // only), so it is unit-tested here directly rather than through the async
+    // `handle_query` handler (which needs a live server and is covered at the
+    // integration tier).
+
+    #[test]
+    fn parse_sql_body_returns_trimmed_sql() {
+        // Surrounding whitespace is stripped; the inner SQL is returned as-is.
+        let sql = parse_sql_body(r#"{"sql": "  SELECT 1  "}"#).expect("valid body");
+        assert_eq!(sql, "SELECT 1");
+    }
+
+    #[test]
+    fn parse_sql_body_rejects_malformed_json() {
+        // A body that isn't JSON fails at the serde step -> 400.
+        let resp = parse_sql_body("not json").expect_err("malformed JSON must be rejected");
+        assert_eq!(resp.status(), StatusCode::BAD_REQUEST);
+    }
+
+    #[test]
+    fn parse_sql_body_rejects_whitespace_only_sql() {
+        // A present-but-blank `sql` trims to empty -> 400 (the `Some(_)` arm,
+        // and the `false` side of the `!s.is_empty()` guard).
+        let resp = parse_sql_body(r#"{"sql": "   "}"#).expect_err("empty sql must be rejected");
+        assert_eq!(resp.status(), StatusCode::BAD_REQUEST);
+    }
+
+    #[test]
+    fn parse_sql_body_rejects_missing_sql_field() {
+        // Valid JSON object with no `sql` key -> the `None` arm -> 400.
+        let resp = parse_sql_body("{}").expect_err("missing sql must be rejected");
+        assert_eq!(resp.status(), StatusCode::BAD_REQUEST);
+    }
 }

{dirsql-0.3.65 → dirsql-0.3.67}/packages/rust/src/lib.rs

@@ -987,7 +987,7 @@ impl DirSQLBuilder {
     /// written to `<root>/.dirsql/cache.db` (override via
     /// [`persist_path`](Self::persist_path)) so subsequent startups only
     /// re-parse files that have actually changed. See
-    /// `docs/guide/persistence.md` for the reconcile contract.
+    /// `docs/howto/persist.md` for the reconcile contract.
     pub fn persist(mut self, persist: bool) -> Self {
         self.persist = persist;
         self