trim daemon-fix changelog entry under the 60-word cap
test / unit + widget + golden + a11y (push) Failing after 27s
test / integration_test (xvfb) (push) Has been skipped
test / bundle smoke (xvfb 5s) (push) Has been skipped
test / daemon subprocess + web WASM smoke (push) Has been skipped
test / dart doc (lib API) (push) Failing after 23s
test / unit + widget + golden + a11y (push) Failing after 27s
test / integration_test (xvfb) (push) Has been skipped
test / bundle smoke (xvfb 5s) (push) Has been skipped
test / daemon subprocess + web WASM smoke (push) Has been skipped
test / dart doc (lib API) (push) Failing after 23s
Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
+4
-7
@@ -92,13 +92,10 @@ heading, and (b) bumping `pubspec.yaml` `version:` in the same commit.
|
|||||||
|
|
||||||
### Fixed
|
### Fixed
|
||||||
|
|
||||||
- Daemon not connected on startup — the socket-loopback `DaemonClient`
|
- Daemon-not-connected on startup — panels and the Claude pane raced
|
||||||
raced the UI: panels queried before the socket finished connecting
|
the socket loopback. Requests now wait briefly for an in-flight
|
||||||
and cached a "daemon not connected" error, and the Claude pane's
|
connection, the server isn't restarted for the same workspace, and
|
||||||
spawn gate tripped. Requests now wait briefly for the in-flight
|
the client connects once instead of twice.
|
||||||
connection instead of failing instantly, the server is no longer
|
|
||||||
needlessly restarted when the opened project matches the launch
|
|
||||||
workspace, and the client connects once instead of twice.
|
|
||||||
|
|
||||||
### Security
|
### Security
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user