docs: add WSL uv sync memory allocation troubleshooting#152
Open
octo-patch wants to merge 1 commit intoMiroMindAI:mainfrom
Open
docs: add WSL uv sync memory allocation troubleshooting#152octo-patch wants to merge 1 commit intoMiroMindAI:mainfrom
octo-patch wants to merge 1 commit intoMiroMindAI:mainfrom
Conversation
…ndAI#101) WSL2 default memory limits can cause uv sync to fail with a memory allocation error when building packages like transformers or pillow. Add a FAQ entry documenting two workarounds: increasing the WSL2 memory cap via .wslconfig, and limiting parallel builds with UV_CONCURRENT_BUILDS.
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
1 participant
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.
Fixes #101
Problem
On WSL2, running
uv syncinapps/miroflow-agentcan fail with a memory allocation error. WSL2 imposes a default memory cap (often 2–4 GB depending on host RAM) that is insufficient when building heavy packages liketransformersorpillowin parallel.Solution
Add a dedicated FAQ entry in the troubleshooting guide covering two workarounds:
%UserProfile%\.wslconfig(recommended, persistent)UV_CONCURRENT_BUILDS=1 uv sync(no restart required)Testing
Verified that the new FAQ entry renders correctly in Markdown and the commands are accurate per the UV and WSL2 documentation.