Skip to content
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

Change eager mode control inputs from exception to no-op, reflecting eager semantics. #158

Merged
merged 2 commits into from
Nov 28, 2020

Conversation

rnett
Copy link
Contributor

@rnett rnett commented Nov 27, 2020

Simple PR to fix #157. Makes adding control inputs in eager mode a no-op instead of an exception, for the reasons described in the issue (since it's eager mode, any control deps being added will already have been computed).

…eager semantics.

Signed-off-by: Ryan Nett <rnett@calpoly.edu>
Signed-off-by: Ryan Nett <rnett@calpoly.edu>
Copy link
Collaborator

@karllessard karllessard left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @rnett !

@karllessard karllessard merged commit fee1f59 into tensorflow:master Nov 28, 2020
@rnett rnett deleted the rn_noop_eager_control_deps branch December 5, 2020 04:41
rnett added a commit to rnett/tensorflow-java that referenced this pull request Dec 28, 2020
…eager semantics. (tensorflow#158)

* Change eager mode control inputs from exception to no-op, reflecting eager semantics.

Signed-off-by: Ryan Nett <rnett@calpoly.edu>

* fix test to reflect not throwing exception

Signed-off-by: Ryan Nett <rnett@calpoly.edu>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Gracefully handle control dependencies in Eager enviroments
2 participants