Open pyro2927 opened 10 years ago
Same problem here...
My initial thoughts were that it was due to fast-stats updating to 0.0.2 a few months ago, but rolling back to 0.0.1 didn't appear to resolve the issue.
It points to the fast stats github master, maybe i should have locked down a SHA of it.
On Nov 7, 2013, at 0:54, Nik Voss notifications@github.com wrote:
Same problem here...
— Reply to this email directly or view it on GitHub.
That might work, would just need to figure out which SHA it was working on. I tried https://github.com/bluesmoon/node-faststats/commit/a664ac602e6a0bebdc34fa51339c85f87aee2641 as that was the first commit over 7 months ago, but it's still returning NaN for me :(
now i meet same issue, how do you solve it?
Thor is returning NaN for latency values.