fix: background workers not spawning in compiled binary#44
Merged
encrypted-soul merged 1 commit intoworkstream-labs:mainfrom Mar 19, 2026
Merged
fix: background workers not spawning in compiled binary#44encrypted-soul merged 1 commit intoworkstream-labs:mainfrom
encrypted-soul merged 1 commit intoworkstream-labs:mainfrom
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.
What
ws runreports success but agents never start - they remain stuck in queued status forever[process.execPath, ...]for compiled binaries,["bun", Bun.main, ...]for sourceWhy
["bun", Bun.main, "run", ...]. In a compiled binary, Bun.main points to the binary itself, so it tries to run bun/usr/local/bin/ws run ... -which silently fails since you can't pass a compiled Bun binary through bunTest plan
bun testpasseswsCLIbun build --compile --target bun-darwin-arm64and comparing both behaviours.