Upload a local run's report (simulator, emulator, device): the CLI side
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
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 内容生成。
描述
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
- A local mode. An explicit opt-in (
probe test --upload-localorhosted.mode: local), never implied by--upload-report. The envelope saysci.provider: "local"(an additive value); everything stays optional and the report JSON and itsschemavalue do not change.--upload-dry-runprints every field, as today. - Git facts without CI variables. Commit (
git rev-parse HEAD), branch (orHEADwhen 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 createversus a hash ofgit diff HEADplus untracked files). - Device identity without personal identifiers.
device_classand the platform/OS version already exist; add a short model string. Never a serial number or UDID, which identify a person's hardware. - 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_attemptof 1. - 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. - 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
schemakeep 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
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
AlphaWaveSystems/flutter-probe 的其他 Issue
-
agent: is checked on a wrapper holding several checkables answers from the first one in tree order未关闭bug
难度 2/5 1-3 小时 新手友好度 76/100
AlphaWaveSystems/flutter-probe#865 ·
维护者通常 1 天内回复
-
area/cli bug
难度 2/5 1-3 小时 新手友好度 73/100
AlphaWaveSystems/flutter-probe#424 ·
维护者通常 1 天内回复
-
area/docs documentation
难度 2/5 1-3 小时 新手友好度 70/100
AlphaWaveSystems/flutter-probe#409 ·
维护者通常 1 天内回复
-
Dial timeout error should say how long it waited and name the timeout setting可能已有人在做 @jay23606 于 2 天前认领。 未关闭area/cli bug
难度 2/5 1-3 小时 新手友好度 78/100
AlphaWaveSystems/flutter-probe#408 ·
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 45/100
AlphaWaveSystems/flutter-probe#888 ·
维护者通常 1 天内回复
查看 AlphaWaveSystems/flutter-probe 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 78/100
IBM-Cloud/terraform-provider-ibm#7115 ·
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 86/100
fluxcd/notification-controller#1441 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 66/100
volcengine/volcengine-go-sdk#163 · 1 条评论 ·
-
难度 2/5 1-3 小时 新手友好度 76/100
OneBusAway/maglev#2145 ·
维护者通常 2 天内回复
-
priority/medium status/ready type/chore
难度 2/5 1-3 小时 新手友好度 84/100
discobox-ai/discobox#1357 ·
维护者通常 1 天内回复