-
Notifications
You must be signed in to change notification settings - Fork 492
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[1.0.0~beta1] .Time returns different values #627
Comments
@ljagiello When using holt-winters it may return less data then asked if the prediction algorithm becomes unstable. This might be what you are seeing. Can you add a |
@nathanielc quick question where I should see result of that |
That's DOT when it's triggered by
|
@ljagiello The output of |
Bad
Good
|
@ljagiello Yeah, something is definitely odd about that. Could you create a recording of your test data and share it with me so I can play around with it locally?
A file with the recording ID will be placed in |
@ljagiello Thanks for the replay file it was useful in fixing the issue. I have merged a fix. Can you confirm that its working as expected? The fix will be in the next nightly build and part of the 1.0.0-beta3 release. |
@nathanielc I build the latest master and behaviour is still the same.
That's the result of the same test triggered by kapacitord:
|
Kapacitor: 1.0.0~beta1-1 (official deb package)
OS: Ubuntu 14.04 LTS
I was playing with
holtWinters
and I've noticed weird behaviour of.Time
. It returns different values depends on how it was triggered.TICK file (almost like example):
When I run:
Result is:
and that is correct (it's future time).
When kapacitor triggers task result is:
This is current time when task was triggered.
Question is how to keep
.Time
always the same?The text was updated successfully, but these errors were encountered: