chore：fix windows uv #772
Closed
chore：fix windows uv #772
+47
−8
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
Wendong-Fan
reviewed
Nov 27, 2025
Contributor
There was a problem hiding this comment.
thanks @fengju0213 , I think we could fix this issue by creating a unified getUvEnv() function in process.ts, which doesn't require hardcoded env path, also more easy to maintain: #773
|
|
||
| try { | ||
| // Check if python executable exists but is corrupted | ||
| const pythonPath = path.join(getCachePath('uv_python'), 'cpython-3.10.16-windows-x86_64-none', 'python.exe'); |
Contributor
There was a problem hiding this comment.
this path only works on Windows x86_64. The repair logic will not work correctly on macos
Comment on lines
+168
to
+169
| UV_PYTHON_INSTALL_DIR: getCachePath('uv_python'), | ||
| UV_TOOL_DIR: getCachePath('uv_tool'), |
Contributor
There was a problem hiding this comment.
The UV environment variables are now defined separately in both install-deps.ts and init.ts, which could lead to inconsistencies if one is updated but not the other
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Problem: Backend startup fails on Windows after a system restart with the error Backend environment check failed: No Python at .... This occurs because uv cannot locate the Python environment specified during installation. Additionally, the existing auto-repair mechanism fails to recover when the Python installation is corrupted (i.e., the directory exists but python.exe is missing).
Changes:
Consistent Environment Variables: Explicitly injected UV_PYTHON_INSTALL_DIR and UV_TOOL_DIR in
startBackend
to ensure the runtime configuration matches the installation configuration, allowing uv to correctly locate the cached Python environment.
Enhanced Auto-Repair: Improved the repair logic upon pre-flight check failure:
Added detection and cleanup for corrupted Python installations (where the directory exists but the executable is missing).
Added an explicit uv python install step before running uv sync to ensure the Python interpreter is correctly reinstalled.
What is the purpose of this pull request?