Expand description
Writing a trace bundle to disk (issue #108).
The same layout and the same bytes as js/src/traces/bundle.js. Every
write is best-effort by default: a trace exists to explain a run, so failing
to record something leaves a visible dropped record instead of breaking
the automation being recorded. Strict mode turns that record into an error.
Structs§
- Trace
Clock - Where a trace’s timestamps come from; replaceable for golden tests.
- Trace
Limits - Size ceilings;
Nonekeeps the default. - Trace
Problem - Something a trace could not record, as listed in a stopped trace’s result.
Enums§
- Trace
Record Error - Why recording could not go on.
Constants§
- DEFAULT_
MAX_ BUNDLE_ BYTES - Default ceiling for a whole bundle.
- DEFAULT_
MAX_ RESOURCE_ BYTES - Default ceiling for one member.
- TRACE_
DIRECTORY_ MODE - Owner-only directory mode for the bundle root.
- TRACE_
FILE_ MODE - Owner-only file mode: a trace may hold form values and page content.
Functions§
- iso_
timestamp new Date(ms).toISOString().- trace_
platform {os} {arch}of the running process.- trace_
runtime rust {version}of this crate.
Type Aliases§
- Trace
Clock Fn - A source of milliseconds.