[PR #2918] [CLOSED] docs: list the procps ps prerequisite for Linux analysis #5493

New issue

Closed

opened 2026-10-31 01:07:04 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-31 01:07:04 +00:00

Owner

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/2918
Author: @CodeAlex52
Created: 10/13/2026
Status: ❌ Closed

Base: main ← Head: docs/linux-procps-prerequisite

📝 Commits (1)

d92763a docs: list the procps ps prerequisite for Linux analysis

📊 Changes

2 files changed (+6 additions, -2 deletions)

View changed files

📝 README.md (+5 -1)
📝 docs/installation.md (+1 -1)

📄 Description

Summary

Fixes #2763.

Document the procps-compatible ps requirement for Linux in the README requirements and in docs/installation.md.

Problem and expected behavior

On a minimal Linux host without procps, rea analyze-javascript-application fails with capability_unavailable, because owned provider launches call ps for process ownership inspection. The README requirements listed only "Node.js and npm" for JavaScript / Electron targets and docs/installation.md did not mention ps; the requirement was stated only in docs/testing.md.

Expected: the prerequisite is discoverable from the requirements paragraph above the target table and from the installation guide, before the first analysis fails.

Change and scope

README.md: the requirements paragraph above the target table now states the Linux ps prerequisite and the failure it causes when missing.
docs/installation.md: the runtime-requirements paragraph under "Package runners and global installation" now states it as well.

Documentation only — no code or behavior changes. The rea doctor check suggested in the issue is left as a follow-up, since it is a code change with its own tests.

Verification

Documentation-only change; no executable path is touched.
The edit is prose-only: it deliberately does not touch the padded target table, so the table alignment is unchanged. I could not run oxfmt --check in this environment (no local checkout), so please let CI confirm formatting.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/morluto/rea/pull/2918 **Author:** [@CodeAlex52](https://github.com/CodeAlex52) **Created:** 10/13/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `docs/linux-procps-prerequisite` --- ### 📝 Commits (1) - [`d92763a`](https://github.com/morluto/rea/commit/d92763a962b47fbf925dbc3743daf55d8b81f94e) docs: list the procps ps prerequisite for Linux analysis ### 📊 Changes **2 files changed** (+6 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `README.md` (+5 -1) 📝 `docs/installation.md` (+1 -1) </details> ### 📄 Description ## Summary Fixes #2763. Document the `procps`-compatible `ps` requirement for Linux in the README requirements and in `docs/installation.md`. ## Problem and expected behavior On a minimal Linux host without `procps`, `rea analyze-javascript-application` fails with `capability_unavailable`, because owned provider launches call `ps` for process ownership inspection. The README requirements listed only "Node.js and npm" for JavaScript / Electron targets and `docs/installation.md` did not mention `ps`; the requirement was stated only in `docs/testing.md`. Expected: the prerequisite is discoverable from the requirements paragraph above the target table and from the installation guide, before the first analysis fails. ## Change and scope - `README.md`: the requirements paragraph above the target table now states the Linux `ps` prerequisite and the failure it causes when missing. - `docs/installation.md`: the runtime-requirements paragraph under "Package runners and global installation" now states it as well. Documentation only — no code or behavior changes. The `rea doctor` check suggested in the issue is left as a follow-up, since it is a code change with its own tests. ## Verification - Documentation-only change; no executable path is touched. - The edit is prose-only: it deliberately does not touch the padded target table, so the table alignment is unchanged. I could not run `oxfmt --check` in this environment (no local checkout), so please let CI confirm formatting. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

bsakaguchi

2026-10-31 01:07:04 +00:00