You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For new users who have different version of client H2O (R or Python) and H2O-3 backend, they will get an error message telling them the version mismatch. However, it will be better if we can tell them the work-around as well but warn them that it is a bad idea. Please include telling users to set strict_version_check=False in the error message so the users can fix the issue and start using H2O
The text was updated successfully, but these errors were encountered:
…version mismatch error.
GH-6707 : remove R unit test because test environment cannot generate the correct error. It will error out at packageVersion(h2o). Pointed out by Tomas Fryda, we source and run the code and do not install the h2o packate.
…ersion mismatch error [nocheck] (#15596)
* GH-6707 : added extended message to h2o.init to help user get around version mismatch error.
GH-6707 : remove R unit test because test environment cannot generate the correct error. It will error out at packageVersion(h2o). Pointed out by Tomas Fryda, we source and run the code and do not install the h2o packate.
* replace circumvent with avoid from Tomas.
…und version mismatch error [nocheck] (h2oai#15596)
* h2oaiGH-6707 : added extended message to h2o.init to help user get around version mismatch error.
h2oaiGH-6707 : remove R unit test because test environment cannot generate the correct error. It will error out at packageVersion(h2o). Pointed out by Tomas Fryda, we source and run the code and do not install the h2o packate.
* replace circumvent with avoid from Tomas.
JIRA link: https://h2oai.atlassian.net/browse/PUBDEV-9046
For new users who have different version of client H2O (R or Python) and H2O-3 backend, they will get an error message telling them the version mismatch. However, it will be better if we can tell them the work-around as well but warn them that it is a bad idea. Please include telling users to set strict_version_check=False in the error message so the users can fix the issue and start using H2O
The text was updated successfully, but these errors were encountered: