sushreebarsa
sushreebarsa
@MatthewWiens101 TF v2.3 is not actively supported, we recommend you to kindly upgrade to latest TF version. I tried to replicate this issue on colab, could you please find the...
@MatthewWiens101 Could you have look at this [gist](https://colab.research.google.com/gist/sushreebarsa/cba04967e31f6723226dae8648a5cab2/16700.ipynb) and let us know if it is the current behaviour of the issue reported ? Thank you!
@sachinprasadhs Was able to reproduce this issue on colab using TF v2.8.0 ,please find the gist [here](https://colab.research.google.com/gist/sushreebarsa/df6f6648c96bc7d0a79be01cee656ce4/keras-16143.ipynb#scrollTo=ZJ2F2cu_qwIK).Thanks!
@innat I tried to replicate the issue and faced a different error. Could you please find the gist [here](https://colab.research.google.com/gist/sushreebarsa/d9651608ea4f1e6433bf9a4d8cfe4db0/16654.ipynb) and let me know if I am missing something to reproduce...
@innat Thank you for the update! @gowthamkpr I was able to replicate the issue on colab using TF v2.8.0, please find the gist [here](https://colab.research.google.com/gist/sushreebarsa/3ae2d647f4fa155d07b695b002b7624b/16654.ipynb#scrollTo=PB-hGUM4ROXt) for reference. Thank you!
@JunHyunjae Could you please try using latest stable version of TF 2.6.0 and let us know if the issue still persists ? Thank you!
@JiashuGuo We see that you are using older version of tensorflow (1.15.5 )which is out of support window.We recommend that you upgrade to latest stable version of TF 2.6.0 and...
@chunduriv I was able to replicate the issue on colab using TF v2.6.0,2.8.0 and tf-nightly, please find the gist [here](https://colab.research.google.com/gist/sushreebarsa/428f7dabedbb9d6979902216202a84dc/55570.ipynb#scrollTo=mgADfBQBI2LR) .Thanks!
@maybeLee I tried to replicate the issue on colab using TF v2.9 and tf-nightly(2.11.0.dev20220906), but I didn’t face any issue as reported in tf-nightly. Could you please find the gist...
@fangxuehouwuming In order to expedite the trouble-shooting process, please provide a complete code snippet to reproduce the issue reported here. Thank you!