morluto/rea

Fork 0

mirror of https://github.com/morluto/rea.git synced 2026-11-05 07:47:29 +00:00

[GH-ISSUE #1335] [Bug] Nobara 44 (Fedora-based) reported as unsupported_host #467

New issue

Closed

opened 2026-10-15 18:25:18 +00:00 by bsakaguchi · 2 comments

bsakaguchi commented

2026-10-15 18:25:18 +00:00

Owner

Originally created by @CassieFox23 on GitHub (Oct 9, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/1335

TL;DR: REA runs fine on Nobara, a Fedora-based distro, but doctor calls the host unsupported because only an exact ID=fedora counts.

Before submitting

I searched the open and closed issues for a related report.
I removed credentials, tokens, private paths, and sensitive target data.

Area

Setup, packaging, or upgrade

Observed behavior

rea doctor --skill --json reports {"name":"host","ok":false,"classification":"unsupported_host","detail":"nobara 44"}, so healthy is false.

Reproduction

On Nobara Linux 44 (/etc/os-release: ID=nobara, ID_LIKE="rhel centos fedora", VERSION_ID=44), run rea doctor --json.

Expected behavior

Either an explicit nobara entry gated on VERSION_ID the way Fedora is, or a "derivative, untested" classification that warns but doesn't fail healthy.

Impact and scope

Only the host check and automated Hopper setup are affected. The providers work fine on this host: Ghidra imported and analysed a 60 MB x86-64 PE (219,702 functions) and decompiled from it, and JADX read an APK through inspect-android-package. So doctor reports unhealthy without anything actually being wrong.

REA version

6.1.0

Runtime and platform

Node.js 22.22.2, Nobara Linux 44 x86-64, Ghidra 12.1.4, Temurin JDK 21

Target and artifact context

No response

Interface

CLI

Earliest failure stage

Setup or provider admission

Relevant output or evidence

{"name":"host","ok":false,"classification":"unsupported_host","detail":"nobara 44","remediation":"REA supports macOS 12+, Ubuntu 24.04+, Fedora 41+, 64-bit Arch Linux, CachyOS, and the experimental Windows x64 Ghidra P0 boundary."}

Typed outcome or recovery expected

No response

Analysis or suspected cause

Source-derived: dist/application/LinuxHopper.js gives the host packageFamily: "rpm" from ID_LIKE but marks it supported only for an exact ID of fedora (41+), ubuntu (24+), arch or cachyos.

Additional context

I see #963 deliberately avoided treating every Arch derivative as supported, so either of the options above would work for me. Happy to run the verify scripts here if that helps.

🤖 Generated with Claude Code (Opus 5.5) 🦊

Originally created by @CassieFox23 on GitHub (Oct 9, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/1335 **TL;DR:** REA runs fine on Nobara, a Fedora-based distro, but `doctor` calls the host unsupported because only an exact `ID=fedora` counts. ### Before submitting - [X] I searched the open and closed issues for a related report. - [X] I removed credentials, tokens, private paths, and sensitive target data. ### Area Setup, packaging, or upgrade ### Observed behavior `rea doctor --skill --json` reports `{"name":"host","ok":false,"classification":"unsupported_host","detail":"nobara 44"}`, so `healthy` is false. ### Reproduction On Nobara Linux 44 (`/etc/os-release`: `ID=nobara`, `ID_LIKE="rhel centos fedora"`, `VERSION_ID=44`), run `rea doctor --json`. ### Expected behavior Either an explicit `nobara` entry gated on `VERSION_ID` the way Fedora is, or a "derivative, untested" classification that warns but doesn't fail `healthy`. ### Impact and scope Only the host check and automated Hopper setup are affected. The providers work fine on this host: Ghidra imported and analysed a 60 MB x86-64 PE (219,702 functions) and decompiled from it, and JADX read an APK through `inspect-android-package`. So `doctor` reports unhealthy without anything actually being wrong. ### REA version 6.1.0 ### Runtime and platform Node.js 22.22.2, Nobara Linux 44 x86-64, Ghidra 12.1.4, Temurin JDK 21 ### Target and artifact context _No response_ ### Interface CLI ### Earliest failure stage Setup or provider admission ### Relevant output or evidence ```json {"name":"host","ok":false,"classification":"unsupported_host","detail":"nobara 44","remediation":"REA supports macOS 12+, Ubuntu 24.04+, Fedora 41+, 64-bit Arch Linux, CachyOS, and the experimental Windows x64 Ghidra P0 boundary."} ``` ### Typed outcome or recovery expected _No response_ ### Analysis or suspected cause Source-derived: `dist/application/LinuxHopper.js` gives the host `packageFamily: "rpm"` from `ID_LIKE` but marks it supported only for an exact `ID` of `fedora` (41+), `ubuntu` (24+), `arch` or `cachyos`. ### Additional context I see #963 deliberately avoided treating every Arch derivative as supported, so either of the options above would work for me. Happy to run the verify scripts here if that helps. 🤖 Generated with Claude Code (Opus 5.5) 🦊

bsakaguchi

2026-10-15 18:25:18 +00:00

closed this issue
added the
area: cli

bug

P2: medium
labels

bsakaguchi commented

2026-10-15 18:25:19 +00:00

Author

Owner

@N0zoM1z0 commented on GitHub (Oct 9, 2026):

Fixed on main in f0dc233d64. The shared host policy now explicitly admits Nobara 44+ and derives its RPM package family from ID_LIKE; doctor and setup consume the same policy. Older Nobara releases and unrelated Fedora derivatives remain unsupported.

Verified 68 focused Linux host-policy, doctor and setup-recovery tests, plus the green main CI at 750fb65650. This verifies the reported admission bug; I have not run Hopper on a real Nobara host. The fix is on main and is not included in the already-published npm 6.2.0.

@N0zoM1z0 commented on GitHub (Oct 9, 2026): Fixed on main in f0dc233d64de4c215c453c346e516b7622713e95. The shared host policy now explicitly admits Nobara 44+ and derives its RPM package family from ID_LIKE; doctor and setup consume the same policy. Older Nobara releases and unrelated Fedora derivatives remain unsupported. Verified 68 focused Linux host-policy, doctor and setup-recovery tests, plus the green main CI at 750fb6565052e9eaad40b946b6a284d0730d14f8. This verifies the reported admission bug; I have not run Hopper on a real Nobara host. The fix is on main and is not included in the already-published npm 6.2.0.

bsakaguchi commented

2026-10-15 18:25:19 +00:00

Author

Owner

@CassieFox23 commented on GitHub (Oct 9, 2026):

TL;DR: The fix works on my Nobara 44 box. Thanks morluto for the fix, and N0zoM1z0 for checking it! On main, doctor now calls this host healthy. The released 6.2.0 still flags it, as expected.

What I ran, on the same machine as the report:

/etc/os-release: ID=nobara, ID_LIKE="rhel centos fedora", VERSION_ID=44.
Published 6.2.0, plain rea doctor: host: unsupported_host (nobara 44).
Main at 9c4a68b (which includes f0dc233d), built locally, plain rea doctor: host: healthy (nobara 44).
Main's readLinuxDistribution() returns {"id":"nobara","versionId":"44","packageFamily":"rpm","supported":true}.
For Hopper, linuxPackageManagerCommands plans pkexec dnf install -y <rpm> xorg-x11-server-Xvfb xorg-x11-xauth python3 libX11 libXtst. dnf repoquery finds all five in Nobara's own repo. Four are already installed here.

Like you, I didn't install or run Hopper.

🤖 Generated with Claude Code (Opus 5.5) 🦊

@CassieFox23 commented on GitHub (Oct 9, 2026): **TL;DR:** The fix works on my Nobara 44 box. Thanks morluto for the fix, and N0zoM1z0 for checking it! On main, `doctor` now calls this host healthy. The released 6.2.0 still flags it, as expected. What I ran, on the same machine as the report: - `/etc/os-release`: `ID=nobara`, `ID_LIKE="rhel centos fedora"`, `VERSION_ID=44`. - Published 6.2.0, plain `rea doctor`: `host: unsupported_host` (`nobara 44`). - Main at 9c4a68b (which includes f0dc233d), built locally, plain `rea doctor`: `host: healthy` (`nobara 44`). - Main's `readLinuxDistribution()` returns `{"id":"nobara","versionId":"44","packageFamily":"rpm","supported":true}`. - For Hopper, `linuxPackageManagerCommands` plans `pkexec dnf install -y <rpm> xorg-x11-server-Xvfb xorg-x11-xauth python3 libX11 libXtst`. `dnf repoquery` finds all five in Nobara's own repo. Four are already installed here. Like you, I didn't install or run Hopper. 🤖 Generated with Claude Code (Opus 5.5) 🦊

bsakaguchi referenced this issue

2026-10-16 21:13:22 +00:00

[PR #467] [MERGED] fix: harden structured configuration comparisons #2013

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

morluto/rea#467

No description provided.

Rows
Columns