Skip to content

fix(env): give the login shell probe 10 s, not 3 - #920

Merged
lacymorrow merged 1 commit into
mainfrom
fix/user-env-probe-timeout
Oct 31, 2026
Merged

lacymorrow merged 1 commit into
mainfrom
fix/user-env-probe-timeout

Conversation

@lacymorrow

Copy link
Copy Markdown
Owner

A live test of #917 on graphite (2019 Intel MacBook Pro) logged login shell probe timed out after 3s and User PATH resolved from Fallback on every launch. Timing zsh -ilc there: 3.02 s real.

The fallback still found npx there (Homebrew in /usr/local/bin), but anyone whose node comes from nvm, fnm or a shell-managed version would get a PATH without it, so MCP servers run through npx would not start.

The probe runs off the main thread and its result is cached for the process, so 10 s costs nothing on fast shells and only delays the first MCP server start on a slow one.

QA: launch Juno from the Dock on a machine with a slow shell; the log should say User PATH resolved from LoginShell.

A login zsh took 3.02 s on graphite, so the probe timed out on every launch
and fell back to the static PATH list, which misses nvm/fnm installs.
@lacymorrow
lacymorrow merged commit d0151cb into main Oct 31, 2026
6 checks passed
@lacymorrow
lacymorrow deleted the fix/user-env-probe-timeout branch October 31, 2026 00:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant