Since state is a reserved keyword in Truffle's guard mechanism, it should not be possible to use it in a guard definition as this can cause serious problems. The annotation processor should either reject the state keyword in guard definitions or the state temporary variable produced by the processor should be renamed to avoid this conflict.

Here's an example:
<img width="629" alt="screen

Describe your context
Please provide us your environment, so we can easily reproduce the issue.

• replace the result of pip list | grep dash below

dash                      2.0.0
dash-bootstrap-components 1.0.0

• if frontend related, tell us your Browser, Version and OS

  • OS: [e.g. iOS] Windows
  • Browser [e.g. chrome, safari]: Chrome 96.0x, Edge 96.0x, Firefox

make_future_dataframe doesn't support regressors currently. So code like:

m = Prophet()
m.add_regressor('var')
m.fit(df)
forecasts = m.predict(m.make_future_dataframe(periods=7))

gives an error like:

ValueError: Regressor 'var' missing from dataframe when attempting to generate forecasts

I know prophet may not know what exact values to put for var in each of the rows a

Short Description

I'm opening this RFC to propose the following:

all objects in the Python package which are intended to be internal should have names beginning with _

The convention "anything starting with _ is internal" is common in Python programming. If LightGBM's Python package followed that convention consistently, it would simplify LightGBM's position on which parts of

Problem:

_catboost.pyx in _catboost._set_features_order_data_pd_data_frame()

_catboost.pyx in _catboost.get_cat_factor_bytes_representation()

CatBoostError: Invalid type for cat_feature[non-default value idx=1,feature_idx=336]=2.0 : cat_features must be integer or string, real number values and NaN values should be converted to string.

Could you also print a feature name, not o

Enable the CMS menu to be configured without overriding the CMS data file.

We currently have read and write capabilities but do not support deleting. We could add a few calls like delete delete_all and some recursive way of deleting.

I'm happy to announce that I'll be writing the second edition of Data Science at the Command Line (O'Reilly, 2014). This issue explains why I think a second edition is needed, lists what changes I plan to make, and presents a tentative outline. Finally, I have a few words about the process and giving feedback.

Why a second edition?

While the command line as a technology and as a way of w

Discussed in h2oai/wave#1302