In v0.7.0, the date and time calculated for X-RateLimit-Reset is incorrect. Rather than a value relative to the current time, it's a value a shortly after the Unix epoch:
0.6.0: X-RateLimit-Reset: Fri, 10 Sep 2021 15:23:06 UTC
0.7.0: X-RateLimit-Reset: Fri, 02 Jan 1970 13:24:25 UTC
This seems to be because the timestamp being returned from fasttime.Now() does not represent the current time, which seems to be due to the switch to runtime.nanotime instead of runtime.walltime. I'm seeing this behaviour on Go 1.17 darwin/amd64.
In v0.7.0, the date and time calculated for X-RateLimit-Reset is incorrect. Rather than a value relative to the current time, it's a value a shortly after the Unix epoch:
0.6.0:
X-RateLimit-Reset: Fri, 10 Sep 2021 15:23:06 UTC
0.7.0:
X-RateLimit-Reset: Fri, 02 Jan 1970 13:24:25 UTC
This seems to be because the timestamp being returned from fasttime.Now() does not represent the current time, which seems to be due to the switch to
runtime.nanotime
instead ofruntime.walltime
. I'm seeing this behaviour on Go 1.17 darwin/amd64.