As mentioned in the reference, clp now has a UtcOffsetChange packet in its IR stream. This PR ignores this packet so that log viewer won't give out errors when opening this format.
To properly handle this, a TIMESTAMP_UTC_OFFSET_CHANGE tag is added to PROTOCOL.js with value 0x3F. TIMESTAMP_NULL and TIMESTAMP_NULL_VAL are removed accordingly because:
No one is currently using these variables;
The current value of TIMESTAMP_NULL conflicts with the new value TIMESTAMP_UTC_OFFSET_CHANGE.
Then in FourByteClpIrStreamReader.js, _readLogEvent catches TIMESTAMP_UTC_OFFSET_CHANGE tag and then drop the 64 bit packet.
References
clp UtcOffsetChange PR
Description
As mentioned in the reference, clp now has a
UtcOffsetChange
packet in its IR stream. This PR ignores this packet so that log viewer won't give out errors when opening this format.To properly handle this, a
TIMESTAMP_UTC_OFFSET_CHANGE
tag is added toPROTOCOL.js
with value0x3F
.TIMESTAMP_NULL
andTIMESTAMP_NULL_VAL
are removed accordingly because:TIMESTAMP_NULL
conflicts with the new valueTIMESTAMP_UTC_OFFSET_CHANGE
.Then in
FourByteClpIrStreamReader.js
,_readLogEvent
catchesTIMESTAMP_UTC_OFFSET_CHANGE
tag and then drop the 64 bit packet.Validation performed
four-byte.clp.zst.zip
tofour-byte.clp.zst
first)