[Bug] DB::Exception: Value nan cannot be parsed as Int64 for query parameter 'HYPERDX_PARAM_78043'

[galvesribeiro]

Hello!

On a fresh deploy with the latest 1.0.0/release of clickstack, I'm getting spammed with an error coming from hyperDX:

Code: 457. DB::Exception: Value nan cannot be parsed as Int64 for query parameter 'HYPERDX_PARAM_78043'
  because it isn't parsed completely: only 0 of 3 bytes was parsed

What's Happening

Issue	Detail
Parameter	param_HYPERDX_PARAM_78043=nan
Expected	Valid Int64 timestamp (milliseconds)
Actual	nan (Not a Number)
Query	Trace lookup query for otel_traces_distributed

The Failing Query:

  SELECT Timestamp, ResourceAttributes['rum.sessionId'], ...
  FROM clickstack.otel_traces_distributed
  WHERE Timestamp >= fromUnixTimestamp64Milli({HYPERDX_PARAM_78043:Int64})  -- nan here!
    AND Timestamp <= fromUnixTimestamp64Milli({HYPERDX_PARAM_78043:Int64})  -- nan here!
    AND TraceId = 'undefined'  -- Also suspicious

This is an application bug in clickstack (HyperDX) apparently. When a user clicks on a log entry to view trace details:

1. The log entry has no associated trace (TraceId = 'undefined')
2. The frontend/API fails to extract valid timestamp bounds
3. It passes nan instead of a valid timestamp to ClickHouse
4. ClickHouse rejects the query with error 457

This doesnt seems to be an infrastructure issue - more likely a bug in the clickstack application that doesn't handle log entries without associated traces properly. The error occurs when viewing log details for entries that weren't part of a distributed trace.

[pulpdrew]

Thanks for reporting @galvesribeiro! This should be fixed in the next release.

[galvesribeiro]

Thanks for reporting @galvesribeiro! This should be fixed in the next release.

Thank you for the quick fix!