fix(desktop): support macOS runtime installation paths - #101
Merged
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
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.
Summary
Library/Application Supportuvunused_mutwarning from the Tauri build scriptRoot cause
Bundled
uv0.12 splits the value supplied to--constraintson spaces even when the operating system provides it as a single argument. On a fresh macOS setup, the absolute constraints path underLibrary/Application Supportwas therefore truncated to/Users/grayhat/Library/Application, causing package installation to fail with exit status 2.The dependency invocation now runs from the staged constraints directory and supplies
runtime-constraints.txtas a local file name. Existing staged-runtime cleanup and active-runtime rollback behavior remain unchanged.Impact
Fresh macOS configuration can install the managed VidXP runtime from the standard application-support directory. Windows and Linux retain their existing runtime paths, while non-Windows builds no longer emit the build-script mutability warning.
The lockfile refresh intentionally excludes the broader Uvicorn, Tokenizers, and PyArrow upgrades. VidXP's exact
0.4.0-b.2release marker is preserved.Validation
uv lock --checkuvx --from ruff==0.16.1 ruff check src testsBEGIN_COMMIT_OVERRIDE
fix(desktop): install managed runtimes from macOS Application Support paths
END_COMMIT_OVERRIDE