docs: record connection diagnostics fix under Unreleased

2026-09-07 11:04:51 +05:30
parent 6c47ae7b21
commit 360d1d29c8
1 changed files with 1 additions and 1 deletions
@@ -20,6 +20,7 @@ the frozen-backend fallback mirror it for their toolchains.

 ### Fixed

+- Backend connection errors report crashes only when recorded evidence exists, and diagnostic waits honor cancellation (#1810)

 ## [0.5.2] — 2026-09-02

@@ -60,7 +61,6 @@ the frozen-backend fallback mirror it for their toolchains.

 ### Fixed

- The "can't reach the backend" error no longer claims the backend crashed when nothing recorded a crash: the app now waits out the shell's death poll, so a real crash is reported with its exit code and crash notice, and a backend that is merely wedged on a heavy job is described as such instead of sending you to rebuild the Python environment (#1802, #1805)
 - The generation compute-time budget is now a Settings control (Performance & Device) instead of an env-var-only setting the timeout error recommended with no UI path — the error copy points there too, and long CPU/MPS renders get an upfront heads-up before they start (#1787)
 - Windows: the backend can now start when the install path contains non-English characters (e.g. a CJK username) on a non-UTF-8 system code page — a new or broken Python environment now builds at an ASCII-safe path automatically (a healthy existing one is never relocated), and a specific error message names the cause and a working fix if the interpreter still crashes in `site` (#1783)
 - Exports and other native-picker actions no longer 403 with "Invalid or expired desktop authorization" when the desktop app and backend resolve different data directories, e.g. dev mode or a custom data folder (#1781)