The GitHub Actions job "Build Sphinx Documentation" on burr.git/stefan/improve-generator-spans has failed. Run started by GitHub user skrawcz (triggered by skrawcz).
Head commit for run: 7f34286be6cfb473a671d9f77c2420ba3764597d / Stefan Krawczyk <[email protected]> Add streaming timing to Burr tracker, UI, and documentation Surface generation-vs-consumer timing data in the Burr tracker and UI, independent of the OpenTelemetry streaming telemetry modes. Tracker changes: - Extend StreamState with timing fields (generation_time_ns, consumer_time_ns, first_item_time_ns, etc.) accumulated via PreStreamGenerateHook/PostStreamGenerateHook - Add generate hooks to SyncTrackingClient in both base.py and client.py with defensive getattr for subclass compatibility - Add optional timing fields to EndStreamModel (generation_time_ms, consumer_time_ms, first_item_time_ms) with None defaults for backwards compatibility - Update post_end_stream in both LocalTrackingClient and S3TrackingClient to convert and write accumulated timing UI changes: - Add timing fields to EndStreamModel.ts TypeScript type - Update StepList.tsx end_stream rendering to show "gen: Xms · consumer: Yms · N items · TTFT: Zms" when timing data is available, falling back to legacy throughput display Documentation: - Add "Streaming Telemetry Modes" section to additional-visibility.rst - Add StreamingTelemetryMode to opentelemetry.rst API reference - Add 4 new generate hook classes to lifecycle.rst - Add "Telemetry & Observability" section to streaming-actions.rst - Add "Streaming Timing" section to tracking.rst - Update monitoring.rst and examples/opentelemetry/README.md - Update design doc to reflect final implementation Example: - Add --tracker flag to streaming_telemetry_modes.py for validating timing data in the Burr UI Tests: - 6 new tests covering StreamState defaults, timing accumulation, defensive noop, EndStreamModel backwards compat, and sync/async end-to-end with LocalTrackingClient Report URL: https://github.com/apache/burr/actions/runs/22537869499 With regards, GitHub Actions via GitBox
