oven-sh/bun

Bun.spawn with a non-existant cwd prints error with wrong path

Open

#8,024 opened on Jan 7, 2024

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Rust (90,348 stars) (4,486 forks)batch import
bugbun:spawngood first issue

Description

What version of Bun is running?

No response

What platform is your computer?

No response

What steps can reproduce the bug?

adapted from my journal processing code:

    Bun.spawnSync({
      cmd: ['python3'],
      stdio: ["inherit", "inherit", "inherit"],
      cwd: `/something/that/doesnt/exist`
    });

What is the expected behavior?

print that the current working directory doesnt exist

What do you see instead?

it says the binary doesnt exist

Additional information

No response

Contributor guide

Tech stack
javascriptrust
Domain
backend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
familiarity with Bun's spawn APIbasic Rust reading abilityability to build Bun
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Investigate Bun's spawn implementation, likely in `src/bun.js/api/bun/spawn.zig` or similar. The error message for a non existent cwd is being confused with the binary not found. Look for where the error is constructed and ensure that the cwd check happens before the binary check. Consider testing with both absolute and relative paths.