Error during setup on a fresh machine #135

New issue

Open

opened 2026-04-26 13:05:31 +00:00 by mahmoud · 5 comments

mahmoud commented

2026-04-26 13:05:31 +00:00

Owner

No description provided.

Screenshot 2026-04-26 at 3.50.38 PM.png

478 KiB

mahmoud referenced this issue

2026-04-28 06:28:03 +00:00

multi_user_template_create: improve preflight + error UX when /home is not btrfs #150

mahmoud referenced this issue

2026-04-28 06:28:07 +00:00

Hero client commands should suggest --root when only the root-scoped daemon socket exists #151

mahmoud commented

2026-04-28 06:28:31 +00:00

Author

Owner

Triage from kristof6. The screenshot captures two distinct problems, both UX/error-message rather than functional bugs. Splitting into focused follow-ups so each can land independently:

#150 — multi_user_template_create: improve preflight + error UX when /home is not btrfs
- The btrfs check at tools/modules/installers/lib.nu:119 is correct (the multi-user flow legitimately needs subvolumes per tools/docs/template.md:9), but on a fresh Ubuntu/Debian box /home is ext4 by default and the error gives no remediation. Onboarding hits this with the very first non-trivial command.
#151 — Hero client commands should suggest --root when only the root-scoped daemon socket exists
- After service_mycelium start --root, running mycelium address (no --root) raises a generic "Socket not found" pointing at tools/modules/openrpc.nu:56. The user has to guess that --root is the answer. Same trap applies to proc, router, proxy. Suggested fix is a shared helper in tools/modules/clients/mod.nu so each client wrapper produces a useful, scope-aware error instead of leaking the openrpc internal one.

Leaving this issue open as the reporter's original context; happy to close once #150 and #151 land.

Triage from `kristof6`. The screenshot captures **two distinct problems**, both UX/error-message rather than functional bugs. Splitting into focused follow-ups so each can land independently: - **#150** — `multi_user_template_create: improve preflight + error UX when /home is not btrfs` - The btrfs check at `tools/modules/installers/lib.nu:119` is correct (the multi-user flow legitimately needs subvolumes per `tools/docs/template.md:9`), but on a fresh Ubuntu/Debian box `/home` is ext4 by default and the error gives no remediation. Onboarding hits this with the very first non-trivial command. - **#151** — Hero client commands should suggest `--root` when only the root-scoped daemon socket exists - After `service_mycelium start --root`, running `mycelium address` (no `--root`) raises a generic "Socket not found" pointing at `tools/modules/openrpc.nu:56`. The user has to guess that `--root` is the answer. Same trap applies to `proc`, `router`, `proxy`. Suggested fix is a shared helper in `tools/modules/clients/mod.nu` so each client wrapper produces a useful, scope-aware error instead of leaking the openrpc internal one. Leaving this issue open as the reporter's original context; happy to close once #150 and #151 land.

mahmoud commented

2026-04-28 07:18:30 +00:00

Author

Owner

Starting on #150 first (btrfs error UX). #151 to follow.

mahmoud commented

2026-04-28 07:57:08 +00:00

Author

Owner

#150 → PR #152. Moving on to #151.

mahmoud commented

2026-04-28 08:30:55 +00:00

Author

Owner

Plan for #151 posted (covers 5 clients including codescalers, not 4 as originally listed).

mahmoud commented

2026-04-28 14:37:35 +00:00

Author

Owner

Both follow-ups are open as PRs:

#150 → PR #152 (btrfs error UX)
#151 → PR #161 (--root hint in clients)

This issue can be closed once both merge.

Both follow-ups are open as PRs: - #150 → PR #152 (btrfs error UX) - #151 → PR #161 (`--root` hint in clients) This issue can be closed once both merge.