Expand description
The portable browser trace format, as Rust knows it (issue #87).
A trace is written by the JavaScript recorder and read by JavaScript,
Python and Rust. The layout is the contract between them, so every name and
value a reader has to agree on lives here, mirroring
js/src/traces/schema.js.
Structs§
- Trace
Checkpoint Reason - Why a checkpoint was taken.
- Trace
Counts - How many members of each kind a bundle holds.
- Trace
Drop Reason - Why a record was dropped.
- Trace
Event - Event kinds that share the one ordered timeline.
- Trace
Files - Names every reader looks for inside a bundle.
- Trace
Live State - What a
live-staterecord changed. - Trace
Manifest - What a bundle says about the run that produced it.
- Trace
Mode - What the recorder captures.
- Trace
Mutation Kind - Record kinds inside a mutation batch.
- Trace
Outcome - How a trace ended, recorded in the manifest.
- Trace
Replay Support - What a bundle’s records let a viewer reproduce.
Constants§
- TRACE_
EVENT_ SOURCES - Event families a caller can subscribe the recorder to.
- TRACE_
FORMAT - Value of
manifest.json’sformatfield, for every version. - TRACE_
SCHEMA_ VERSION - Schema version of the bundle.
Functions§
- assert_
readable_ manifest - Check that a manifest can be read by this version of the format.
- sequence_
name - Format a bundle member’s sequence number.