Comparing changes

* fix(otel): share one AnyValue decoder across all OTLP paths Three AnyValue decoders had drifted apart. extraction's flatten_otlp_attributes silently dropped array/kvlist/bytes attributes, and the OTLP JSON loader json.dumps()'d the raw proto wrapper instead of decoding it. gen_ai.response.finish_reasons therefore surfaced as '{"values": [{"stringValue": "stop"}]}' on one path and vanished on another, where both should yield ["stop"]. Move the already-correct recursive decoder out of api/otlp_processing.py into a dependency-free module and route all three call sites through it. The new module imports only the standard library, so extraction, loader.otlp and api.otlp_processing can all share it without creating an import cycle. bytesValue is returned unchanged: MessageToDict base64-encodes protobuf bytes fields, so callers already receive a str today. Decoding it here would change existing behaviour, which is out of scope for this fix. Adds coverage for array/kvlist/bytes attributes, which previously had none on either path. Fixes #173 * fix(otel): decode AnyValue when promoting span event attributes Strands stores gen_ai.input.messages in span events, and newer GenAI semconv makes messages a complex array, so the stringValue-only promotion in the OTLP loader silently dropped anything that was not a plain string. Route it through the shared decoder like the other paths. * fix(otel): read session_name and eval_set_id as strings only flatten_otlp_attributes used to guarantee a scalar or nothing. Now that it delegates to the shared AnyValue decoder it can also return lists and dicts, which are unhashable and raise TypeError where these values are used as dict keys (_active_session_for_name in ws_server.py and otlp_processing.py). Add a string-only accessor and use it for both fields, matching what _extract_conversation_id already did; that function now shares the same implementation. The decoded value stays available in resource_attrs. * fix(otel): narrow spec-string attributes once at the decode boundary The per-field accessor only covered the two dict-key sites we had found; flatten_otlp_attributes still handed containers to every other consumer via span.tags, so the same unhashable hazard survived elsewhere. Move the guard into decode_attributes, keyed by SPEC_STRING_ATTRS in trace_attrs. Attributes the spec types as strings come back str-or-absent; a container in one of those slots is dropped with a warning rather than JSON-dumped, since dumping would put the literal blob back into user-visible output. Attributes the spec types as arrays or structured values keep their decoded containers, which is what #173 fixes. The registry is hand-maintained: opentelemetry-semantic-conventions exposes constants and prose docstrings only, so attribute value types are not machine-readable and the set cannot be derived from the package. _extract_string_attribute is gone and _extract_conversation_id is back to its original form. Tests now assert through extract_extended_model_info_from_attrs and extract_user_text_from_attrs, the layers #173's symptom actually names, instead of stopping at the decoder and span.tags. * fix(otel): decode containers on an opt-in allowlist instead of a denylist SPEC_STRING_ATTRS listed the attributes to narrow, so a missing entry let an unhashable value reach a dict key on an unauthenticated receiver port. It missed the whole gcp.vertex.agent.* namespace. Replace it with SPEC_CONTAINER_ATTRS: the seven keys the GenAI semconv types as arrays or structured values. Those decode to native containers; every other key decodes to a scalar or is dropped, which is what extraction.py did before the decoder was shared. A missing entry now drops one value rather than crashing ingestion, and attributes neither of us has thought about are safe by construction rather than by enumeration. decode_attribute() carries the rule so the OTLP-array path and the span-event promotion path share one implementation. bytesValue now survives as the base64 string it already was, which #173 asks for and is hashable. The default for unlisted container values is tracked in #208; the nested-dict loader path that bypasses this decoder entirely is #207.

Bumps the python group with 2 updates: [click](https://github.com/pallets/click) and [langchain](https://github.com/langchain-ai/langchain). Updates `click` from 8.4.2 to 8.5.0 - [Release notes](https://github.com/pallets/click/releases) - [Changelog](https://github.com/pallets/click/blob/main/CHANGES.md) - [Commits](pallets/click@8.4.2...8.5.0) Updates `langchain` from 1.3.16 to 1.3.17 - [Release notes](https://github.com/langchain-ai/langchain/releases) - [Commits](langchain-ai/langchain@langchain==1.3.16...langchain==1.3.17) --- updated-dependencies: - dependency-name: click dependency-version: 8.5.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: python - dependency-name: langchain dependency-version: 1.3.17 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: python ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Bumps the docker-base-images group with 1 update in the / directory: node. Updates `node` from 25-bookworm-slim to 26-bookworm-slim --- updated-dependencies: - dependency-name: node dependency-version: 26-bookworm-slim dependency-type: direct:production dependency-group: docker-base-images ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Navigation Menu

Repository navigation

Comparing changes

Open a pull request

Commits on Aug 31, 2026

Commits on Sep 1, 2026

This comparison is taking too long to generate.

Uh oh!