Add troubleshooting page for TF sessions used in predict method #1141
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
deliahu
approved these changes
Jun 25, 2020
deliahu
added a commit
that referenced
this pull request
Jun 26, 2020
Co-authored-by: David Eliahu <deliahu@users.noreply.github.com> (cherry picked from commit 54d3d26)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When a
tf.Sessionobject is used in thepredictmethod of aPythonPredictorobject that had its session initialized in the constructor, due to using it in a separate thread, the following error is returned:To avoid this, calling the
with self.sess.graph.as_default()context manager solves the issue by bringing the graph in the current context.Thank you @danielricks for reporting this!
checklist:
make testandmake lintsummary.md(view in gitbook after merging)