Fixing a small issue in OpRegularizerManager.#169
Open
Conversation
Internally, OpRegularizerManager was passing output_boundary as a list to _dfs_for_source_ops, which was packaging it again as a list. The fix now allows _dfs_for_source_ops to support a single output_boundary node or a list of nodes. PiperOrigin-RevId: 300625458
mn-robot
force-pushed
the
test_300625458
branch
from
ff8725d to
4020f04
Compare
mn-robot
changed the title
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
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.
Fixing a small issue in OpRegularizerManager.
Internally, OpRegularizerManager was passing output_boundary as a list to _dfs_for_source_ops, which was packaging it again as a list. The fix now allows _dfs_for_source_ops to support a single output_boundary node or a list of nodes.