Issues with `prophet` cause variables to be left undefined
cgobat opened this issue · comments
Issue was originally noted in facebook/prophet#2392.
In this module's __init__.py, there is a try block wherein a BuildProphet instance is created and BuildProphet.fit() is called. If an exception is raised within this block, the except Exception as e statement will catch it and print the error, but variables such as forecast_df_folds will not be defined, which raises an error when forecast_df_folds is referenced a few lines later.
For posterity, it is worth noting that this issue seems to be either related to or the same as #39.
Yes I have added this forecast_df_folds = Nonein the except part of the code.
Please upgrade to the latest version 0.71 and try again.
ThanksAuto Vimal On Monday, March 27, 2023 at 06:30:23 PM EDT, Caden Gobat ***@***.***> wrote:
For posterity, it is worth noting that this issue seems to be either related to or the same as #39.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you modified the open/close state.Message ID: ***@***.***>