In _get_view_function_response, when span streaming is enabled (has_span_streaming_enabled) but no StreamedSpan segment is active (e.g. the Chalice app runs without the AWS Lambda integration, which is the only thing that creates the segment), segment stays None and the streaming branch never calls scope.set_transaction_name(...). Errors are still captured via capture_event, but the resulting events carry no transaction context. The non-streaming else branch always sets scope.set_transaction_name(app.lambda_context.function_name, source=TransactionSource.COMPONENT), so for any setup without an active segment this is a behavioral regression where error/message events lose their transaction name.

Also found at:

• tests/integrations/chalice/test_chalice.py:199-236

When has_span_streaming_enabled is True but no StreamedSpan is current (e.g. Chalice used without the AWS Lambda integration), segment stays None and a successful request returns without creating any span or setting a transaction name — no trace data is recorded at all. Only the error path calls client.flush(). Consider adding a test asserting the expected behavior in this case, or a guard that falls back to the else branch.

Also found at:

• tests/integrations/chalice/test_chalice.py:176