Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

`rs` command collides with the pre-installed BSD rs (reshape) utility on macOS/BSD, causing a silent, CPU-idle hang

Fechada
  • Algo errado?
#518 0 comentários 0 reações 1 responsável Ver no GitHub

Mantenedores costumam responder em até 1 dia

@chenjiahan já está trabalhando nisso.

Desde 24/9/2026.

Avaliação

Esta issue ainda não foi avaliada.

Descrição

Environment

  • rstack: 0.8.0
  • Node.js: v24.21.0
  • pnpm: 12.6.0
  • OS: macOS 27
  • Package manager mode: pnpm strict node_modules

Summary

On macOS and other BSD-derived operating systems (FreeBSD, NetBSD, OpenBSD), /usr/bin/rs is a standard pre-installed utility (BSD rs — "reshape a data array", part of the base system since 4.2BSD). When Rstack CLI's rs binary is not resolved first on $PATH (e.g. when typed directly in an interactive shell rather than invoked through a package.json script), the shell falls back to the OS-native /usr/bin/rs instead of node_modules/.bin/rs.

Steps to reproduce

  1. In a project using [email protected], open a plain shell (not through pnpm run <script>) and run:
rs check
  1. The command hangs indefinitely with no output.
  2. Ctrl+C exits with no error message.
  3. Running npx rs check (which forces resolution to the local node_modules/.bin/rs) works correctly and completes.

Root cause

BSD's rs utility reads from standard input by default and blocks waiting for piped input when invoked with no valid input stream — this matches the observed symptoms exactly:

  • Near-zero CPU usage during the hang (blocked on a read() call, not computing)
  • No output before or after interruption
  • Resolved entirely by forcing local binary resolution via npx/pnpm exec

Impact

This affects any BSD-derived OS (macOS included) where /usr/bin/rs precedes the project's node_modules/.bin in $PATH — which is the default shell behavior outside of npm/pnpm script execution contexts. Linux (GNU coreutils-based) is unaffected, as it has no native rs command.

Suggested fix

Since renaming the rs binary would be a breaking change, consider:

  • Documenting the $PATH collision explicitly in the README, alongside a recommendation to invoke via pnpm exec rs / npx rs rather than a bare rs in interactive shells
  • Optionally detecting this collision at runtime (e.g., checking which rs resolves to the expected package path) and warning the user

Related

This was discovered while investigating what first appeared to be an unrelated hang in rs check --type-check; see #519 for the original (now corrected) report.

Linguagem predominante
TypeScript
Estrelas
28
Forks
1
Merge médio
6h 58min
PRs com merge (30d)
91

Preparar o ambiente

Ainda não verificamos os arquivos de configuração deste projeto. Comece pelo README e veja nosso guia da primeira contribuição para os passos gerais.

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de rstackjs/rstack-cli

Todas as issues de rstackjs/rstack-cli

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.