Gregory SchierandClaude Opus 5 c9e884d4fe fix(models): return a database error instead of panicking when the pool is exhausted
Two users on 2026.7.x reported the app going half-dead: local editing kept
working, but Send did nothing and every encrypted secret rendered blank until
they restarted. The webview console carried a Rust task panic —

    Delete task failed: task 1314 panicked with message
    "Failed to get new DB connection from the pool: Error(None)"

`Error(None)` is r2d2's acquire timeout. `QueryManager::connect` and `with_tx`
turned that timeout into `expect`, so a pool that was momentarily full took down
whatever task asked for a connection instead of reporting a failure the caller
could show, retry, or ignore. Every DB-backed path shares those two functions,
which is why one stalled pool reads as "Send is dead and the secrets are gone".

Acquisition is now fallible end to end: `connect()` and `BlobManager::connect()`
return `Result`, and so do the `db()`/`blobs()` accessors on every host. Call
sites propagate with `?` where they already returned a result; the fire-and-forget
writers (streaming events, the model-change poller) log and carry on. `with_conn`
had no callers and only added a third panic, so it is gone.

Two places held a pooled connection across work that has nothing to do with the
database and can block for a long time — the OS keyring in
`EncryptionManager::get_workspace_key`, and the sync directory walk in
`cmd_sync_calculate`. Both now hand the connection back first. Those are the
paths behind the two visible symptoms.

Not fixed here: the gRPC streaming block in yaak-app-client still `.unwrap()`s
its database writes, as it did before, so acquisition failures panic there too.
`ProxyQueryManager` in the separate proxy app keeps its own `expect`.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-10 17:09:02 -07:00
2026-07-05 06:56:58 -07:00
2026-07-02 10:17:53 -07:00
2026-05-13 14:22:43 -07:00
2026-08-16 22:32:33 -07:00
2026-05-07 15:50:10 -07:00
2026-05-07 15:50:10 -07:00
2026-03-13 06:46:27 -07:00
2026-05-07 15:50:10 -07:00
2024-09-10 11:29:31 -07:00
2025-12-13 08:10:12 -08:00
2026-04-30 09:00:12 -07:00

💫 Yaak ➟ Desktop API Client 💫

A fast, privacy-first API client for REST, GraphQL, SSE, WebSocket, and gRPC – built with Tauri, Rust, and React.

Development is funded by community-purchased licenses. You can also become a sponsor to have your logo appear below. 💖


User avatar: MVST-Solutions  User avatar: dharsanb  User avatar: railwayapp  User avatar: caseyamcl  User avatar: bytebase  User avatar: rauchg  User avatar:   

User avatar: seanwash  User avatar: jerath  User avatar: itsa-sh  User avatar: dmmulroy  User avatar: timcole  User avatar: VLZH  User avatar: terasaka2k  User avatar: andriyor  User avatar: majudhu  User avatar: axelrindle  User avatar: jirizverina  User avatar: chip-well  User avatar: GRAYAH  User avatar: flashblaze  User avatar: Frostist  User avatar: PurplProto  

Yaak API Client

Features

Yaak is an offline-first API client designed to stay out of your way while giving you everything you need when you need it. Built with Tauri, Rust, and React, it’s fast, lightweight, and private. No telemetry, no VC funding, and no cloud lock-in.

🌐 Work with any API

  • Import collections from Postman, Insomnia, OpenAPI, Swagger, or Curl.
  • Send requests via REST, GraphQL, gRPC, WebSocket, or Server-Sent Events.
  • Filter and inspect responses with JSONPath or XPath.

🔐 Stay secure

  • Use OAuth 2.0, JWT, Basic Auth, or custom plugins for authentication.
  • Secure sensitive values with encrypted secrets.
  • Store secrets in your OS keychain.

☁️ Organize & collaborate

  • Group requests into workspaces and nested folders.
  • Use environment variables to switch between dev, staging, and prod.
  • Mirror workspaces to your filesystem for versioning in Git or syncing with Dropbox.

🧩 Extend & customize

  • Insert dynamic values like UUIDs or timestamps with template tags.
  • Pick from built-in themes or build your own.
  • Create plugins to extend authentication, template tags, or the UI.

Contribution Policy

Important

Community PRs are currently limited to bug fixes. If your PR is not a bug fix, link the feedback item where @gschier explicitly gave you permission to work on it. See CONTRIBUTING.md for policy details and DEVELOPMENT.md for local setup.

Useful Resources

S
Description
No description provided
Readme MIT
107 MiB
0 Stars 1 Watchers 0 Forks
Latest
2025-12-11 18:23:08 +01:00
Languages
Rust 50.1%
TypeScript 47.5%
JavaScript 2%
CSS 0.3%