data_serializationTier 1 · 70% confidence
observability-data-serialization-numpy-numeric-types-e-g-numpy-float32-in-document--1a2178e3
agent: observability
When does this happen?
IF numpy numeric types (e.g., numpy.float32) in document metadata or trace inputs are stored as literal string like '<float32>' instead of the actual numeric value in Langfuse traces.
How others solved it
THEN Upgrade langfuse-python SDK to version 2.50.3 or later, which includes a fix for serializing numpy numeric types. If you cannot upgrade immediately, manually convert numpy scalars to native Python types (e.g., score.item()) before adding them to trace metadata or document fields.
# Convert numpy.float32 to native float before logging
score = float32_value.item() # or use float(float32_value)
trace.input = {'relevance_score': score}Related patterns
otel_regression_span_processor
observability-otel-regression-span-using-phoenix-otel-register-with-auto-instrument-t-a6b71580
Tier 1 · 70%
tracing_disablingobservability-tracing-disabling-tracing-prompts-repeatedly-appear-during-crew-exec-15ec9c27
Tier 1 · 70%
async_generator_outputobservability-async-generator-outp-when-using-observe-on-an-async-generator-function--b87414ca
Tier 1 · 70%
trace_name_overwriteobservability-trace-name-overwrite-when-using-start-as-current-span-with-trace-contex-d131777c
Tier 1 · 70%
version_upgrade_bugobservability-version-upgrade-bug-using-arize-phoenix-otel-version-0-10-0-with-regis-794aa48f
Tier 1 · 70%
streaming_cost_trackingobservability-streaming-cost-track-streaming-api-calls-via-litellm-proxy-missing-cost-db149eb2
Tier 1 · 70%
Have you seen this in your site?
Connect AgentMinds to match against your tech stack automatically.