-
Notifications
You must be signed in to change notification settings - Fork 31
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
Fix pip build #779
Fix pip build #779
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the PR!
@tilakrayal as I am not familiar with the merging process of tf-keras, can this get merged? Or is there more action needed from my side? |
hi @haifeng-jin can this be merged? It's blocking us downstreams in spack to release new TFP versions |
FYI / For response: @tilakrayal @sachinprasadhs or @tilakrayal and @haifeng-jin: What does it take to get this approved PR merged? As the submitter @jonas-eschle pointed out in July, this would be ready for merge (for 5 months now). It blocks a stack of pull requests of the spack package manager project, starting with this PR: spack/spack#43688 |
Imported from GitHub PR #779 As discussed in #776 I tried but actually run into the issue that layers/experimental cannot be used as a build target, as the builds _inside_ experimental _require_ layers -> circular deps. The other folders in `layers` circumvent this by specifying only the specific build targets. Instead of changing the logic (i.e. is experimental meant to be dev-built only?), I did what the error advertised and added it to the ignored builds, as it's seemingly not made to be built Copybara import of the project: -- 9d3bb64 by Jonas Eschle <[email protected]>: docs: update CONTRIBUTING.md with new name tf-keras (cherry picked from commit fb79960) -- 7bd7b3d by Jonas Eschle <[email protected]>: fix: python build ignore experimental due to circular refs (cherry picked from commit 9b349e3) Merging this change closes #779 FUTURE_COPYBARA_INTEGRATE_REVIEW=#779 from jonas-eschle:fix_pip_build 7bd7b3d PiperOrigin-RevId: 685927076
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Imported from GitHub PR #779 As discussed in #776 I tried but actually run into the issue that layers/experimental cannot be used as a build target, as the builds _inside_ experimental _require_ layers -> circular deps. The other folders in `layers` circumvent this by specifying only the specific build targets. Instead of changing the logic (i.e. is experimental meant to be dev-built only?), I did what the error advertised and added it to the ignored builds, as it's seemingly not made to be built Copybara import of the project: -- 9d3bb64 by Jonas Eschle <[email protected]>: docs: update CONTRIBUTING.md with new name tf-keras (cherry picked from commit fb79960) -- 7bd7b3d by Jonas Eschle <[email protected]>: fix: python build ignore experimental due to circular refs (cherry picked from commit 9b349e3) Merging this change closes #779 FUTURE_COPYBARA_INTEGRATE_REVIEW=#779 from jonas-eschle:fix_pip_build 7bd7b3d PiperOrigin-RevId: 685927076
As discussed in #776
I tried but actually run into the issue that layers/experimental cannot be used as a build target, as the builds inside experimental require layers -> circular deps. The other folders in
layers
circumvent this by specifying only the specific build targets.Instead of changing the logic (i.e. is experimental meant to be dev-built only?), I did what the error advertised and added it to the ignored builds, as it's seemingly not made to be built