mirror of
https://github.com/block/goose.git
synced 2026-07-17 12:56:20 +02:00
morgmart
290870ad2a
When the UI sends a legacy session ID (e.g. "20260415_1") instead of a thread UUID, on_load_session previously hung indefinitely because get_thread returned an error that was silently swallowed or never reached the client. This caused a 30-second frontend timeout and a blank conversation view. Now the handler checks whether the requested ID corresponds to a known session in the sessions table, and returns an immediate, diagnostic error explaining what went wrong: - "Session X has linked thread Y, but was sent as the session_id instead of the thread UUID" — tells the engineer the UI needs to send the thread UUID instead. - "Session X exists but has no linked thread" — the session was not fully created via ACP (thread creation failed or was skipped). - "Session not found" — the ID doesn't match anything. Also bumps tauri-plugin-dialog to "2" to fix a version mismatch warning with @tauri-apps/plugin-dialog v2.7. Signed-off-by: morgmart <98432065+morgmart@users.noreply.github.com>