Skip to main content

Module bundle

Module bundle 

Source
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§

TraceClock
Where a trace’s timestamps come from; replaceable for golden tests.
TraceLimits
Size ceilings; None keeps the default.
TraceProblem
Something a trace could not record, as listed in a stopped trace’s result.

Enums§

TraceRecordError
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§

TraceClockFn
A source of milliseconds.