Skip to content

Conversation

@tveasey
Copy link
Contributor

@tveasey tveasey commented Jul 14, 2020

It is possible that a model which hasn't received any recent updates is removed. In this case, when forecasting we'd hit a null pointer dereference. This moves the offending code under the check that the model still exists.

Fixes #1401.

Copy link

@droberts195 droberts195 left a comment

Choose a reason for hiding this comment

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

LGTM

@tveasey tveasey merged commit 2ba03ec into elastic:master Jul 14, 2020
@tveasey tveasey deleted the forecast-crash branch July 14, 2020 11:54
tveasey added a commit to tveasey/ml-cpp-1 that referenced this pull request Jul 14, 2020
It is possible that a model which hasn't received any recent updates is removed. In this case, when forecasting we'd hit a null pointer dereference. This moves the offending code under the check that the model still exists.
tveasey added a commit to tveasey/ml-cpp-1 that referenced this pull request Jul 14, 2020
It is possible that a model which hasn't received any recent updates is removed. In this case, when forecasting we'd hit a null pointer dereference. This moves the offending code under the check that the model still exists.
@tveasey tveasey removed the v6.8.12 label Jul 14, 2020
tveasey added a commit that referenced this pull request Jul 14, 2020
It is possible that a model which hasn't received any recent updates is removed. In this case, when forecasting we'd hit a null pointer dereference. This moves the offending code under the check that the model still exists. Backport #1402.
tveasey added a commit that referenced this pull request Jul 14, 2020
It is possible that a model which hasn't received any recent updates is removed. In this case, when forecasting we'd hit a null pointer dereference. This moves the offending code under the check that the model still exists. Backport #1402.
@droberts195 droberts195 added v7.8.1 and removed v7.8.2 labels Jul 16, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment