webui: "Invalid Date" shown for both begin and end dates in Ingestion Details panel

[junhaoliao]

Bug

Starting with a clean CLP package, after submitting a compression job, occasionally "Invalid Date" is shown for both begin and end dates in Ingestion Details panel, until the next compression statistic update which happens 5 seconds after.

CLP version

91b7bd9

Environment

Ubuntu 22.04

Reproduction steps

1. Build and launch CLP package
2. Launch WebUI in a browser.
3. Run ./sbin/compress.sh <logs-path>
4. Observe "Invalid Date" shown for both begin and end dates in Ingestion Details panel

[junhaoliao]

Initial Analysis

1. By extending STATS_REFRESH_INTERVAL_MILLIS from 5000 to a longer interval, I was able to inspect the compression stats document. It was found that both end_timestamp and begin_timestamp has extremely small/large values:
   

2. Looking into the CLP core code, it was found that we define epochtime_t as an int64_t and uses the extreme values of int64_t for cEpochTimeMin=-9223372036854775808 and cEpochTimeMax=9223372036854775807:
   

   clp/components/core/src/clp/Defs.h

   Lines 10 to 12 in 91b7bd9

   	typedef int64_t epochtime_t;
   	constexpr epochtime_t cEpochTimeMin = std::numeric_limits<epochtime_t>::min();
   	constexpr epochtime_t cEpochTimeMax = std::numeric_limits<epochtime_t>::max();

3. Those extreme values are not convertible to JS dates.

   A Number can exactly represent all integers from -9,007,199,254,740,992 to 9,007,199,254,740,992 (21.1.2.8 and 21.1.2.6). A time value supports a slightly smaller range of -8,640,000,000,000,000 to 8,640,000,000,000,000 milliseconds. This yields a supported time value range of exactly -100,000,000 days to 100,000,000 days relative to midnight at the beginning of 1 January 1970 UTC.