ReferenceCLI commands
sdods trace
Open the traces of a run, or a trace zip, in the trace viewer.
sdods trace [zip] [--last] [--run <id>] [--artifacts-dir <dir>] [--list] [--json]| Argument / flag | Meaning |
|---|---|
zip | a trace.zip file, or a directory to search recursively |
--last | the most recent run under the artifacts directory (default when nothing else is given) |
--run <id> | a specific run id |
--artifacts-dir | where runs live (default .sdods/runs, or SDODS_ARTIFACTS_DIR) |
--list | print the trace files instead of opening them (--json prints { source, traces }) |
Traces are recorded on the first retry (evidence.trace: on-first-retry), so a fully green run has none. Change it per project or environment with evidence.trace, or per run with sdods run --trace <mode> (off disables traces).
A trace contains credentials: request cookies and Authorization headers, Set-Cookie responses,
the signed-in account's localStorage, sessionStorage and IndexedDB, and typed values. sdods run
redacts those after the run (evidence.redactTraces: true, the default), but not request or
response bodies or page text. Open traces locally; never attach them to issues, commit them or
upload them anywhere public.
sdods trace --last
sdods trace --run 0193f0c2-… --list
sdods trace .sdods/runs/<id>/pw-output/demo-shop--ui--chromium/login/trace.zipExit code 2 when no run or no trace file is found.