When de-serializing a Unix timestamp (e.g.: in the Historical API), the times are 1 or 2 seconds wrong: HistoricalEndpointTest
Testing the deserializing function itself, one can see that it's not a problem related to the Time class, but rather to decodeLong.
This happens both with String and InputStream as sources.
When de-serializing a Unix timestamp (e.g.: in the Historical API), the times are 1 or 2 seconds wrong: HistoricalEndpointTest Testing the deserializing function itself, one can see that it's not a problem related to the Time class, but rather to
decodeLong.This happens both with
StringandInputStreamas sources.