Skip to main content
W&B Weave supports tracing both sync and async generator functions, including deeply nested patterns. This page shows you how to decorate generator functions with @weave.op so that Weave captures their inputs, yielded outputs, and the full hierarchy of nested calls. Use this when you have streaming or lazily evaluated code paths whose outputs you want to inspect in the Weave UI alongside your other traces.
Because generators yield values lazily, Weave logs outputs only when you fully consume the generator (for example, when you convert it to a list). To ensure Weave captures outputs in the trace, fully consume the generator (for example, with list()).
The following screenshot shows the Traces page with a selected trace of the preceding code. The center panel shows the trace tree for the selected trace. The trace tree shows the deeply_nested_generator, nested_generator, and inner Ops in the trace tree hierarchy. Weave Traces page showing a selected trace tree illustrating deeply nested Ops

Consume generators

The following section explains why you must consume generators for Weave to record their outputs, and which consumption patterns work. Weave captures generator outputs only after you fully consume the generator. Consume the generator by iterating over it (for example, with list(), a for loop, or next() until exhaustion). The same applies to async generators when you use async for or equivalent consumption. For more information about decorating functions and methods with @weave.op, see Create calls.

Accumulate yielded values into a single trace

If you want Weave to record a combined result (such as a joined string or a list) instead of the raw sequence of yielded values, use an accumulator. You can use the accumulator parameter of weave.op to customize how yielded values are combined from generator functions, for example, to join streamed text tokens into a single string. The accumulator is a two-argument function that Weave calls once per yielded value, building up a result incrementally.
The accumulator parameter isn’t available for TypeScript.
The following example demonstrates a custom accumulator that appends each yielded value to a list, so Weave records that list as the call output after you fully consume the generator.