Explicitly raise a (clearer) error message when models end up in invalid...
Explicitly raise a (clearer) error message when models end up in invalid states due to interleaving graph and eager. In rare cases code may have run w/o crashing when in these invalid states, but it's safer to error with an explanation rather than risk silent failures/fragile behavior. PiperOrigin-RevId: 321192744
Loading
Please register or sign in to comment