Upload a local run's report (simulator, emulator, device): the CLI side
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Idoneità per principianti
- 35/100
Direzione di ricerca
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.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
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.
- Lingua principale
- Go
- Stelle
- 6
- Fork
- 3
- Merge medio
- 6h 28m
- PR unite (30g)
- 362
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di AlphaWaveSystems/flutter-probe
-
agent: is checked on a wrapper holding several checkables answers from the first one in tree orderApertabug
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
AlphaWaveSystems/flutter-probe#865 ·
I maintainer di solito rispondono entro 1 giorno
-
area/cli bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 73/100
AlphaWaveSystems/flutter-probe#424 ·
I maintainer di solito rispondono entro 1 giorno
-
area/docs documentation
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
AlphaWaveSystems/flutter-probe#409 ·
I maintainer di solito rispondono entro 1 giorno
-
Dial timeout error should say how long it waited and name the timeout settingForse già presa @jay23606 l’ha presa 2 giorni fa. Apertaarea/cli bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
AlphaWaveSystems/flutter-probe#408 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 45/100
AlphaWaveSystems/flutter-probe#888 ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di AlphaWaveSystems/flutter-probe
Issue simili
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
IBM-Cloud/terraform-provider-ibm#7115 ·
I maintainer di solito rispondono entro 2 giorni
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 86/100
fluxcd/notification-controller#1441 ·
I maintainer di solito rispondono entro 1 giorno
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 66/100
volcengine/volcengine-go-sdk#163 · 1 commento ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
OneBusAway/maglev#2145 ·
I maintainer di solito rispondono entro 2 giorni
-
priority/medium status/ready type/chore
Difficoltà 2/5 1-3 ore Idoneità per principianti 84/100
discobox-ai/discobox#1357 ·
I maintainer di solito rispondono entro 1 giorno