You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Initialized GUI process logging before the Tauri builder starts.
6
+
- Resolved the GUI log directory with the same config-relative rules used by the log viewer.
7
+
- Kept the tracing non-blocking worker guard alive for the full GUI process lifetime.
8
+
9
+
## Impact
10
+
11
+
- Embedded gateway logs can be written to the configured file directory.
12
+
- Settings > General > Gateway Logs can read the same files created by the embedded gateway.
13
+
- CLI logging behavior is unchanged.
14
+
15
+
## Root Cause
16
+
17
+
The GUI embedded gateway bypassed the CLI entrypoint, so it never called the shared tracing initialization used by `agent-diva-cli`. The log viewer also reads config-relative log paths, so GUI logging must initialize with the same resolved directory.
-`cargo test -p agent-diva-gui embedded_gateway_serves_health_endpoint -- --nocapture`
9
+
-`cargo test -p agent-diva-gui log_dir`
10
+
11
+
## Result
12
+
13
+
-`cargo fmt --check -p agent-diva-gui`: passed.
14
+
-`cargo check -p agent-diva-gui`: passed.
15
+
-`cargo test -p agent-diva-gui`: failed because existing `embedded_server::tests::embedded_gateway_serves_health_endpoint` did not become ready and returned Windows TCP connection refused. 20 tests passed, including the new logging path tests.
16
+
-`cargo test -p agent-diva-gui embedded_gateway_serves_health_endpoint -- --nocapture`: failed with the same connection refused health check result.
0 commit comments