Home stops when the terminal or SSH session that started it closes

オープン
  • 何か問題がありますか？
#518 コメント 2 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
18/100
issue の種類
機能追加
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
linux, macos, rust
領域
devops, infrastructure

調査の方向性

Read draft #350 and its failed service-removal CI run, then compare the nine changed files against current develop. Trace install locks, data paths, the update controller, and the recovery journal before implementing the Linux systemd user service and macOS LaunchAgent behavior. Run the acceptance journeys on Linux x86-64, Jetson, and macOS; done means service lifecycle, autostart, update/undo, recovery, and uninstall all meet the listed checks.

索引モデルが issue の本文から書いたものです。

説明

documentation enhancement

Problem

In 2.0.0, Home runs only while the terminal that started it stays open. Closing the terminal, or the SSH session on a Jetson or Linux server, stops Home, and updates stop arriving too. The only workaround is tmux or screen.

Expected behaviour

  • The installer registers Home as a background service for the current user (systemd user service on Linux, LaunchAgent on macOS) and starts it.
  • elastos home and elastos home --browser open the running Home, starting it if needed. Closing them leaves Home running.
  • Stop ends the running Home. Autostart on/off changes only Home's own service, never account-wide settings; opening Home with autostart off does not turn it back on.
  • Status shows starting, ready, stopped or failed, with the reason. Ready means this installation's Home and its update controller run, not just that a port answers.
  • If the service cannot start, Home shows the failure and one repair step instead of quietly running in the terminal. Terminal mode stays as an explicit diagnostic option.
  • Update, Undo and interrupted-update recovery never leave two Runtimes or a restart loop.

Scope

Carry the needed behaviour from draft #350 onto current develop: 9 of its 11 files have changed since, and its last CI run failed the service-removal tests. Recheck install locks, data paths, the update controller and the recovery journal. Drop the terminal fall-back; add autostart on/off.

macOS: a LaunchAgent survives closing Terminal but not logout, and starts only at login. Running with nobody logged in needs a system daemon and a separate review.

Docs (INSTALL.md): what keeps running and when; the computer must stay awake; closing an SSH tunnel disconnects the browser but does not stop Home.

Acceptance

On Linux x86-64, Jetson and macOS:

  • Install, close the terminal or SSH session, reconnect: Home works.
  • Kill the Runtime: the service restarts it.
  • Stop: Home stays stopped until opened or the next login.
  • Autostart off: Home does not start at login; elastos home --browser still opens it.
  • Update and Undo: one Runtime afterwards, service still registered.
  • Interrupted update: recovery completes once, no loop.
  • Uninstall removes only this installation's service; data kept unless asked.
  • Linux: the sub-issue's logout and reboot journeys pass.

Out of scope

Tray or desktop app (#394). Isolation and service limits (#183).

Links

#350, failed CI run https://github.com/elastos/elastos-runtime/actions/runs/38211869253, #183, #394.

主要言語
Rust
スター
6
フォーク
2
平均マージ
1日 3時間
マージ済み PR（30日）
42

環境構築

このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

elastos/elastos-runtime のほかの issue

elastos/elastos-runtime の issue をすべて見る

似ている issue

Rust の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。