Price Validation Failure with Custom Data - Precision Issue?

[daydayup789]

Description:
I'm encountering a price validation error when using custom data. Could this be caused by precision issues? What should I do?

I stored local BTCUSDT futures data in .fth format. After converting the data with the required fields, I ran Example 1 and received this error:

    raise make_exception(
ValueError: low was > close

During troubleshooting, I reduced tens of thousands of records to a single test row where close and low are identical:

timestamp	volume	open	high	low	close
2025-06-30 17:59:00	52.835	107442.1	107442.1	107428.0	107428.0

This data appears logically valid since:

• High ≥ Open/Low/Close
• Low ≤ Open/High/Close

I fully support the Bar data validation logic:

Condition.is_true(high._mem.raw >= open._mem.raw, "high was < open")
Condition.is_true(high._mem.raw >= low._mem.raw, "high was < low")
Condition.is_true(high._mem.raw >= close._mem.raw, "high was < close")
Condition.is_true(low._mem.raw <= close._mem.raw, "low was > close")
Condition.is_true(low._mem.raw <= open._mem.raw, "low was > open")

Problem:
Despite low == close in my test data (which should pass low <= close), the validation fails with low was > close. I cannot identify the root cause.