Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

Complete recording coordination and recoverable stop semantics

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

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

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

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
12/100
issue の種類
リファクタリング
明瞭さ
説明が足りない
活発さ
活発
技術スタック
android, ios, typescript
領域
mobile, tooling

調査の方向性

Start with the linked Proposed ADR 0024 (docs/adr/0024-screen-recording-provable-signal.md) and the accepted-ADR follow-up under #3744, since this issue is an ordered design plan rather than a code edit. Coordinate with #2376 on process identity before touching any backend. Done means each backend (iOS, Android, HarmonyOS, transport) passes ordinary stop, recovery, retry, and stale-owner tests, and the superseded recovery controls are removed.

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

説明

enhancement

Purpose

Finish the shared recording lifecycle without loss of recoverable output. This continues the Proposed ADR 0024 (screen recording: one coordinator, two facts). Its implemented decisions move to an accepted ADR under #3744, and the proposal is then deleted.

Required behavior

  • Track export completion and recorder termination as two independent facts.
  • Keep the native-path disposition together with both facts.
  • Use one coordinator for a live stop and for an authorized recovery.
  • Keep signal selection and identity checks inside each backend.
  • Keep the manifest and the ownership fence.
  • Before a replacement, retain unresolved recordings by fence generation.
  • Return a playable committed export together with its recorder observation.
  • If collection, finalization, or commit fails, keep the retry material.
  • After the export completes, let recovery settle an unresolved termination.

Completion conditions

  • Each supported backend proves an ordinary stop, recovery after daemon loss, a retry after failed collection, and refusal of a stale owner.
  • A retry cannot apply processing twice.
  • A replacement cannot overwrite unresolved evidence.
  • The superseded recording recovery controls are removed only after equivalent behavior is proven.
  • HarmonyOS and transport recording use the shared finish sequence.

Decisions so far

  • Uncertain process identity is not a reason to discard usable output.
  • No public probe or signal levels: backends own the sequence.
  • Process markers are not a second lifecycle store. Keep markers only for launch windows that nothing else covers.
  • Recovery does not signal independently: that would bypass the coordinator guards.
  • Unresolved evidence is never retired.
  • Below Android API 34, keep the rotation. Evaluate unlimited recording on API 34+ separately.

Dependencies

  • Coordinate process identity with #2376.
  • Change other durable kinds only with their own failed-finish evidence.

Source proposal: https://github.com/callstack/agent-device/blob/0149438faf/docs/adr/0024-screen-recording-provable-signal.md

主要言語
TypeScript
スター
5.1k
フォーク
339
平均マージ
12時間 50分
マージ済み PR（30日）
632

環境構築

はじめの一歩

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

callstack/agent-device のほかの issue

callstack/agent-device の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

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

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