Tensorflow 2.17 updates#181
Merged
Merged
Conversation
Collaborator
Author
|
As a separate comment, I also have this occasionally, but I cannot figure out where they come from, this is not fatal, but might indicate some bugs: |
Contributor
I came across that and with the help of AI, enabling eager mode helped: |
Collaborator
Author
|
@de-code It works. Thanks 😄 Question: why did you remove the different allocation of loss function? EDIT: actually I did not manage to get pass the second epoch... 😭 |
5148b00 to
a212306
Compare
86686e2 to
2b3aa3d
Compare
… allowing existing paths.
Signed-off-by: Luca Foppiano <luca@foppiano.org>
Signed-off-by: Luca Foppiano <luca@foppiano.org>
Signed-off-by: Luca Foppiano <luca@foppiano.org>
Signed-off-by: Luca Foppiano <luca@foppiano.org>
Signed-off-by: Luca Foppiano <luca@foppiano.org>
Fix Tensorflow 2.17 training
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
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.
@kermitt2 I've got an issue when training with 2.17 (it seems that the TensorFlow docker image uses python 3.11, though).
I've got this issue when training even a simple model like
date:The fix in this branch solved the issue for me (the libraries updates are just minor)