Updating auto increment value causes server to "go away" [ZN7myrocks10ha_rocksdb31update_auto_incr_val_from_fieldEv]

https://github.com/georgelorchpercona/percona-server/tree/ps-5.7-MYR-235-236

https://jenkins.percona.com/view/5.7/job/mysql-5.7-param/1630/

https://github.com/percona/percona-server/pull/2173

These crashes are limited to auto increment columns that are of DOUBLE or FLOAT type only. Not at all a common use case. Particularly in a largely unused storage engine. Upstream already has responded to the issue and provided fixes.

These crashes are seen all through the runs (screenfillers). This basically breaks auto_increment as we know, is a serious bug, and it makes MyRocks un-GA imho. I am setting this to "blocker" as that is what it is IMHO. Could we un-cherry-pick the offending patch from the tree to make MyRocks stable again before release?

Reproducible upstream on prod201704, likely introduced by one of these five commits :

NOPE  https://github.com/facebook/mysql-5.6/commit/bb8183d38b401a0c24dcebb785d624ad34fe755f : Load autoincrement and hidden pk only once

NOPE https://github.com/facebook/mysql-5.6/commit/9f53fae746084823d35177b70a314d14c93a441b : Implement inplace alter for auto_increment

NOPE https://github.com/facebook/mysql-5.6/commit/3e68a8cd409ea63e296a5c788daec188d3a4b864 : Fix loading auto_increment values in tables with hidden pk

NOPE https://github.com/facebook/mysql-5.6/commit/b016d55a315277c0adf07d330bdeb9172f283b44 : Implement persistent auto_increment values

>>> this one >>> https://github.com/facebook/mysql-5.6/commit/4d66a663abfa60c6c1739d0612959b3457b5f2b1 : Fix auto_increment bugs with large values

Found similar issue with different error string (ZN7myrocks10ha_rocksdb18get_auto_incrementEyyyPyS1):

Test case: