New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
make_iterator_one_shot
results in IndexError: list index out of range on first call (only)
#17
Comments
Hi @javierluraschi, could you take a look and see if this should have been eliminated by your fix to tensorflow/tensorflow#23388? W.r.t. rstudio/tensorflow#272 I tested that weeks ago, but this case might be slightly different. Here I think it's the deprecation warning that's issued the first time you call something deprecated in a session,- then all further calls go through "undecorated". BTW this can be tested with a nightly install of |
I think we have no choice than changing all methods that use deprecated code (there are many of them, tests get aborted b/c too many errors). But that can only be temporary... Their real updating advice is:
We need to think how to do that on our side ... |
Just noting this for some time later:
https://github.com/tensorflow/docs/blob/master/site/en/r2/guide/effective_tf2.md which describes this as being the action automatically taken by |
R-side workaround in but I'll leave it open until I've created an issue in TF |
It's already fixed in TF master, as I can confirm locally removing our workaround and doing
Now we just need to see if it still makes its way into 1.13 (I've asked) |
seems like it made it into 1.13 "Added bounds checking to printing deprecation warnings." |
Reminding of rstudio/tensorflow#272, but with current
master
.This only happens on first call, second execution works:
The text was updated successfully, but these errors were encountered: