Upload a local run's report (simulator, emulator, device): the CLI side

未关闭
#442 2 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
冷清
技术栈
flutter, go
领域
cli, testing

调研方向

Start at the probe test --upload-report CLI path, then read hosted.CIFromEnv and hosted.Preflight, which the issue names as the current blockers. The requested work spans local Git and device facts, run sequencing, optional key enrollment, and updates to MCP descriptions, CLI and configuration docs, VS Code surfaces, and the changelog; the dirty-tree hash and keychain behavior are still open questions. Done means the acceptance criteria pass and all existing flags, report JSON, and envelope schema remain compatible.

由索引模型根据 Issue 内容生成。

描述

area/cli area/cloud enhancement

What this is

Today probe test --upload-report only works inside GitHub Actions: hosted.CIFromEnv returns nothing elsewhere and hosted.Preflight refuses a payload without CI facts ("only --upload-dry-run works outside CI"). A developer who runs the suite on a local simulator, emulator or device has no way to send that run's report. This issue describes only what the CLI would need. No code yet; how a service treats such a run is out of scope here.

What the CLI would need

  1. A local mode. An explicit opt-in (probe test --upload-local or hosted.mode: local), never implied by --upload-report. The envelope says ci.provider: "local" (an additive value); everything stays optional and the report JSON and its schema value do not change. --upload-dry-run prints every field, as today.
  2. Git facts without CI variables. Commit (git rev-parse HEAD), branch (or HEAD when detached), and a dirty-tree flag plus a hash of the working tree so a run on uncommitted changes is never labelled as "the result of commit C". The hash definition must be stable across platforms and cheap on large repositories (open question: git stash create versus a hash of git diff HEAD plus untracked files).
  3. Device identity without personal identifiers. device_class and the platform/OS version already exist; add a short model string. Never a serial number or UDID, which identify a person's hardware.
  4. A run sequence. Outside CI there is no run id, so the client makes a monotonic one (for example milliseconds since the epoch plus a per-key counter) and a run_attempt of 1.
  5. Signer key enrolment (optional, later). An Ed25519 key generated on the developer's machine and stored in the OS keychain (macOS, Linux and Windows differ), enrolled once through a documented command (probe cloud enrol), with the envelope signed over its canonical bytes. The envelope carries only the key fingerprint (16 hex characters). No name or email goes into the envelope.
  6. Scrubbing and size limits are unchanged: relative paths, secret patterns, no artifacts, the 1 MiB / 5,000-result caps, retries on a busy service.

Constraints

  • Additive only: existing flags, config, the report JSON and the envelope schema keep working.
  • Nothing is sent unless the user opts in, and the docs state the hosted service is a preview and not live yet.
  • Any new flag or config key also updates the MCP descriptions, the CLI reference, the configuration page, the VS Code surfaces and the CHANGELOG.

Acceptance criteria (for a later implementation PR)

  • Tests: a local run builds an envelope with the git facts; a dirty tree sets the flag and the tree hash; a detached HEAD gives HEAD; a repository without commits and a non-git directory give a clear refusal, never a half-filled envelope.
  • No serial, UDID, user name, e-mail address or absolute path appears in the dry-run output.
  • Key custody: the private key never leaves the keychain, is never printed or logged, and signing fails closed when the keychain is unavailable.

Open questions

  • The dirty-tree hash definition (see 2).
  • Keychain access on each OS and a fallback for headless machines.
  • Whether the sequence needs a hash of the previous envelope so that a missing or reordered run is detectable on the client side.
主要语言
Go
星标
6
派生
3
平均合并
6 小时 28 分钟
30 天内合并 PR
362

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

AlphaWaveSystems/flutter-probe 的其他 Issue

查看 AlphaWaveSystems/flutter-probe 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。