fix(desktop): correct health check endpoint URL to /global/health #8231
+1
−1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The desktop app was checking /health for server health, but the actual endpoint in server.ts is /global/health. This caused the desktop app to fail with 'Failed to spawn OpenCode Server' even though the server was running and listening. This fixes issues anomalyco#8149, anomalyco#8200, anomalyco#8206 and related spawn failures on Windows and other platforms.
Contributor
|
Thanks for your contribution! This PR doesn't have a linked issue. All PRs must reference an existing issue. Please:
See CONTRIBUTING.md for details. |
Contributor
|
The following comment was made by an LLM, it may be inaccurate: No duplicate PRs found |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Fixes the desktop app failing to start with "Failed to spawn OpenCode Server" even though the server is running and listening.
Root cause: The Tauri desktop app was checking
/healthfor server readiness, but the actual endpoint inserver.tsis/global/health.Changes
check_server_health()inlib.rsto use/global/healthinstead of/healthFixes
Error Message (before fix)
The logs show the server is listening, but the health check was hitting the wrong endpoint, causing a 30-second timeout and the error.