Github user walter-weinmann commented on the issue:
https://github.com/apache/thrift/pull/1346
The `erlang:timestamp/0` method seems to be a very old kernel methods -
from the [release notes](http://erlang.org/doc/apps/kernel/notes.html) (current
kernel release is 5.3):
> 1.42 Kernel 2.13.2
>
> Fixed Bugs and Malfunctions
>
> A bug when doing io:get_line (among other calls) from a file opened with
encoding other than latin1, causing false unicode errors to occur, is now
corrected.
>
> Own Id: OTP-7974
>
> Improvements and New Features
>
> Added functionality to get higher resolution timestamp from system. The
erlang:now function returns a timestamp that's not always consistent with the
actual operating system time (due to resilience against large time changes in
the operating system). The function os:timestamp/0 is added to get a similar
timestamp as the one being returned by erlang:now, but untouched by Erlangs
time correcting and smoothing algorithms. The timestamp returned by
os:timestamp is always consistent with the operating systems view of time, like
the calendar functions for getting wall clock time, but with higher resolution.
Example of usage can be found in the os manual page.
>
> Own Id: OTP-7971
---
