This repository was archived by the owner on Apr 19, 2026. It is now read-only.
Mark global_step_init as used to prevent spurious warning msg#14
Open
gar1t wants to merge 1 commit into
Open
Conversation
Without this, TF displays a warning message that looks like an error (contains traceback): ``` E1121 12:34:00.888499 139860141586240 tf_logging.py:105] ================================== Object was never used (type <class 'tensorflow.python.framework.ops.Operation'>): <tf.Operation 'init' type=NoOp> If you want to mark it as used call its "mark_used()" method. It was originally created here: ... ``` This behavior occurs on TF 1.12.0 but reports suggest that these warnings started appearing as early as TF 1.2.0.
Contributor
|
Hmm, I think a better solution is for |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
Without this, TF displays a warning message that looks like an
error (contains traceback):
This behavior occurs on TF 1.12.0 but reports suggest that these
warnings started appearing as early as TF 1.2.0.