Skip to content

Conversation

@droberts195
Copy link

The change detector would crash during restoration if seasonal
components existed at the time it was originally created, but
had been discarded by the time it was persisted.

This change ensures that the change models within the change
detector reflect the status of seasonality at the time of
restoration from state.

The change detector would crash during restoration if seasonal components existed at the time it was originally created, but had been discarded by the time it was persisted. This change ensures that the change models within the change detector reflect the status of seasonality at the time of restoration from state.
Copy link
Contributor

@tveasey tveasey left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for debugging this! LGTM.

droberts195 pushed a commit to droberts195/ml-cpp that referenced this pull request Jul 9, 2020
The change detector would crash during restoration if seasonal components existed at the time it was originally created, but had been discarded by the time it was persisted. This change ensures that the change models within the change detector reflect the status of seasonality at the time of restoration from state. Backport of elastic#1391
droberts195 pushed a commit to droberts195/ml-cpp that referenced this pull request Jul 9, 2020
The change detector would crash during restoration if seasonal components existed at the time it was originally created, but had been discarded by the time it was persisted. This change ensures that the change models within the change detector reflect the status of seasonality at the time of restoration from state. Backport of elastic#1391
droberts195 pushed a commit to droberts195/ml-cpp that referenced this pull request Jul 9, 2020
The change detector would crash during restoration if seasonal components existed at the time it was originally created, but had been discarded by the time it was persisted. This change ensures that the change models within the change detector reflect the status of seasonality at the time of restoration from state. Backport of elastic#1391
@droberts195 droberts195 merged commit c134dd5 into elastic:master Jul 9, 2020
@droberts195 droberts195 deleted the fix_change_detector_restore branch July 9, 2020 18:16
droberts195 pushed a commit that referenced this pull request Jul 9, 2020
The change detector would crash during restoration if seasonal components existed at the time it was originally created, but had been discarded by the time it was persisted. This change ensures that the change models within the change detector reflect the status of seasonality at the time of restoration from state. Backport of #1391
droberts195 pushed a commit that referenced this pull request Jul 9, 2020
The change detector would crash during restoration if seasonal components existed at the time it was originally created, but had been discarded by the time it was persisted. This change ensures that the change models within the change detector reflect the status of seasonality at the time of restoration from state. Backport of #1391
droberts195 pushed a commit that referenced this pull request Jul 10, 2020
The change detector would crash during restoration if seasonal components existed at the time it was originally created, but had been discarded by the time it was persisted. This change ensures that the change models within the change detector reflect the status of seasonality at the time of restoration from state. Backport of #1391
tveasey added a commit that referenced this pull request Jul 17, 2020
Change #1391 introduced a subtle error: when computing the likelihood of no change we should use a reference to the current time series trend model, not the copy of the model which assumes a change is occurring.
tveasey added a commit to tveasey/ml-cpp-1 that referenced this pull request Jul 17, 2020
Change elastic#1391 introduced a subtle error: when computing the likelihood of no change we should use a reference to the current time series trend model, not the copy of the model which assumes a change is occurring.
tveasey added a commit to tveasey/ml-cpp-1 that referenced this pull request Jul 17, 2020
Change elastic#1391 introduced a subtle error: when computing the likelihood of no change we should use a reference to the current time series trend model, not the copy of the model which assumes a change is occurring.
tveasey added a commit to tveasey/ml-cpp-1 that referenced this pull request Jul 17, 2020
Change elastic#1391 introduced a subtle error: when computing the likelihood of no change we should use a reference to the current time series trend model, not the copy of the model which assumes a change is occurring.
tveasey added a commit to tveasey/ml-cpp-1 that referenced this pull request Jul 17, 2020
Change elastic#1391 introduced a subtle error: when computing the likelihood of no change we should use a reference to the current time series trend model, not the copy of the model which assumes a change is occurring.
tveasey added a commit that referenced this pull request Jul 17, 2020
Change #1391 introduced a subtle error: when computing the likelihood of no change we should use a reference to the current time series trend model, not the copy of the model which assumes a change is occurring. Backport #1415.
tveasey added a commit that referenced this pull request Jul 17, 2020
Change #1391 introduced a subtle error: when computing the likelihood of no change we should use a reference to the current time series trend model, not the copy of the model which assumes a change is occurring. Backport #1415.
tveasey added a commit that referenced this pull request Jul 20, 2020
Change #1391 introduced a subtle error: when computing the likelihood of no change we should use a reference to the current time series trend model, not the copy of the model which assumes a change is occurring. Backport #1415.
tveasey added a commit that referenced this pull request Jul 20, 2020
Change #1391 introduced a subtle error: when computing the likelihood of no change we should use a reference to the current time series trend model, not the copy of the model which assumes a change is occurring. Backport #1415.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment