Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

rust-analyzer fallback recurses through Homebrew’s wrapper

Open
  • Is something wrong?
#5,133 5 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@rami3l is already working on this.

Since Oct 9, 2026.

  • #5136 by @rami3l — open

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
rust
Domain
cli, tooling

Research direction

Read the issue’s Homebrew discussion #7111 and linked Homebrew PR #315977 to understand the wrapper’s settings override and proposed approaches. The issue names no rustup files or tests, and the solution is explicitly open for discussion; first determine an agreed solution shape before locating implementation entry points. Done means rustup and Homebrew can meet the settings requirement without recursive fallback.

Written by the indexing model from the issue text.

Description

enhancement O-macos
Problem you are trying to solve

When rustup is installed via homebrew and the active toolchain lacks rust-analyzer, homebrew-installed rustup selects its own shell wrapper as an external fallback and repeatedly executes it:

$ rust-analyzer -help
info: `rust-analyzer` is unavailable for the active toolchain
info: falling back to "/opt/homebrew/opt/rustup/bin/rust-analyzer"
...
error: infinite recursion detected

The proximate cause is that homebrew wraps rustup’s proxies to set RUSTUP_OVERRIDE_UNIX_FALLBACK_SETTINGS. rustup's fallback search excludes executables that are the same file as rustup, but the shell wrapper is a distinct file, so it passes that check, resulting in infinite recursion.

removing homebrew's binstubs avoids this recursion but those binstubs exist to override rustup's settings file, so removing the binstubs also requires patching rustup (take a look at the linked PR).

Is there another way to meet brew's needs? Should we add one? I'd be happy to send a patch, but I'd like some input on the shape of the solution (compile time env var?).

The original report is in Homebrew discussion #7111.

Solution you'd like

Up for discussion.

Notes

No response

Dominant language
Rust
Stars
7.1k
Forks
1.1k
Avg merge
1d 13h
Merged PRs (30d)
45

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from rust-lang/rustup

All issues in rust-lang/rustup

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.