Skip to content

[Quick Fix] Update op generation - #375

Closed
rnett wants to merge 1 commit into
tensorflow:masterfrom
rnett:rn_update_generation
Closed

[Quick Fix] Update op generation#375
rnett wants to merge 1 commit into
tensorflow:masterfrom
rnett:rn_update_generation

Conversation

@rnett

@rnett rnett commented Aug 28, 2021

Copy link
Copy Markdown
Contributor

I forgot to re-run generation before merging init scopes. This fixes that. There's also a few ops that apparently weren't generated last time we added some? Not sure why, but they are in ops.pb, so I'm guessing they just weren't committed.

Signed-off-by: Ryan Nett <JNett96@gmail.com>
This was referenced Aug 28, 2021
@karllessard

Copy link
Copy Markdown
Collaborator

A lot of changes here are undesirable, many ops that were classified before (e.g. under data or xla) now ends up in the core. That's the result of some changes in the ops-generator?

@rnett

rnett commented Sep 3, 2021

Copy link
Copy Markdown
Contributor Author

No, that's the thing, I didn't change anything, just re-ran op generation locally. Can you run it on your machine and compare it to what is here? ops.pb, the api defs, and the op generation code is all unchanged, afaik.

@rnett

rnett commented Sep 3, 2021

Copy link
Copy Markdown
Contributor Author

Might be best to just do this as part of #378, and make sure to commit the newly generated files.

@karllessard

Copy link
Copy Markdown
Collaborator

Yes I was also thinking about cleaning that up while I'm working on #378, we can close this one

@rnett rnett closed this Sep 8, 2021
@rnett
rnett deleted the rn_update_generation branch October 16, 2021 21:28
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.

2 participants