[pull] master from tensorflow:master #156
Open
Conversation
This file contains 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
![pull[bot]](https://avatars.githubusercontent.com/in/12910?s=60&v=4){kind=small}
PiperOrigin-RevId: 561849785
fixed typos
Fixed the broken links for eager execution, Transformer and tf.data: Build TensorFlow input pipelines in function.ipynb file.
PiperOrigin-RevId: 562804647
PiperOrigin-RevId: 562804659
PiperOrigin-RevId: 563392879
PiperOrigin-RevId: 563393266
PiperOrigin-RevId: 563950264
PiperOrigin-RevId: 563950730
PiperOrigin-RevId: 564257080
…ce for semantic versioning. Also document that the TF Lite C++, Objective-C, and Swift APIs are NOT part of the API surface for semantic versioning. [For background info, the TF Lite Android (Java) API has already been launched to "General Availability" for the public <https://blog.tensorflow.org/2022/09/announcing-tensorflow-lite-in-google-play-services-general-availability.html> as the "Google Play services API for TensorFlow Lite", and is the default API that we recommend for developers in the TF Lite QuickStart documentation.] PiperOrigin-RevId: 565052161
…nd for the TF Lite Extension APIs (custom ops + delegates), than for TensorFlow itself. PiperOrigin-RevId: 565723934
PiperOrigin-RevId: 565755200
PiperOrigin-RevId: 566367711
PiperOrigin-RevId: 566466742
…n to the Keras classification tutorial. PiperOrigin-RevId: 566758660
Updated the file as mentioned by MarkDaoust.
PiperOrigin-RevId: 568666099
Final copy of change
PiperOrigin-RevId: 568838728
PiperOrigin-RevId: 681508059
Signed-off-by: Tsai, Louie <[email protected]>
PiperOrigin-RevId: 684927870
PiperOrigin-RevId: 685572827
PiperOrigin-RevId: 686262704
PiperOrigin-RevId: 688216101
PiperOrigin-RevId: 689935512
PiperOrigin-RevId: 690771212
PiperOrigin-RevId: 691072187
PiperOrigin-RevId: 698150339
PiperOrigin-RevId: 698201896
PiperOrigin-RevId: 698202297
Signed-off-by: Emmanuel Ferdman <[email protected]>
Found one broken link in this tutorial and I have replaced it with right one.
Found one broken link in this tutorial and I have replaced with new one.
PiperOrigin-RevId: 713808292
PiperOrigin-RevId: 720736461
PiperOrigin-RevId: 721175407
…er it is re-directing to archived repo. PiperOrigin-RevId: 726073729
PiperOrigin-RevId: 728556611
…aintain reproducible wheel content and filename results.
It enables ability to pass defines values to `//tensorflow/core/public:release_version`.
Instead of having TF version in three places (`setup.py`, `version.h` and `tensorflow.bzl`), it should be located in one place only. Declaration of TF version in a new `tf_version.bzl` file will allow passing this value to build rules wrapping `setup.py` and `release_version.h`.
Dependency on `//tensorflow/core/public:release_version` should be added if `TF_MAJOR_VERSION, TF_MINOR_VERSION, TF_PATCH_VERSION, TF_VERSION_SUFFIX` values are used in the code.
Dependency on `//tensorflow/core/public:version` should be added if graphDef compatibility versions or checkpoint compatibility versions are used in the code.
The next step would be to change cc_library release_version in the following way:
```
cc_library(
name = "release_version",
hdrs = ["release_version.h"],
defines = [
"TF_MAJOR_VERSION={}".format(MAJOR_VERSION),
"TF_MINOR_VERSION={}".format(MINOR_VERSION),
"TF_PATCH_VERSION={}".format(PATCH_VERSION),
"TF_VERSION_SUFFIX={}".format(TF_SEMANTIC_VERSION_SUFFIX),
],
visibility = ["//visibility:public"],
)
```
The version chunks will be created from the value in `tf_version.bzl`. The version suffix will be created by a new repository rule, and it will be controlled by environment variables.
PiperOrigin-RevId: 729190812
PiperOrigin-RevId: 729458918
This change introduces a uniform way of building the TF wheel and controlling the filename version suffixes. A new repository rule `python_wheel_version_suffix_repository` provides information about project and wheel version suffixes. The final value depends on environment variables passed to Bazel command: `_ML_WHEEL_WHEEL_TYPE, _ML_WHEEL_BUILD_DATE, _ML_WHEEL_GIT_HASH, _ML_WHEEL_VERSION_SUFFIX` `tf_version.bzl` defines the TF project version and loads the version suffix information calculated by `python_wheel_version_suffix_repository`. The targets `//tensorflow/core/public:release_version, //tensorflow:tensorflow_bzl //tensorflow/tools/pip_package:setup_py` use the version chunks defined above. The version of the wheel in the build rule output depends on the environment variables. Environment variables combinations for creating wheels with different versions: * snapshot (default build rule behavior): `--repo_env=ML_WHEEL_TYPE=snapshot` * release: `--repo_env=ML_WHEEL_TYPE=release` * release candidate: `--repo_env=ML_WHEEL_TYPE=release --repo_env=ML_WHEEL_VERSION_SUFFIX=-rc1` * nightly build with date as version suffix: `--repo_env=ML_WHEEL_TYPE=nightly --repo_env=ML_WHEEL_BUILD_DATE=<YYYYmmdd>` * build with git data as version suffix: `--repo_env=ML_WHEEL_TYPE=custom --repo_env=ML_WHEEL_BUILD_DATE=$(git show -s --format=%as HEAD) --repo_env=ML_WHEEL_GIT_HASH=$(git rev-parse HEAD)` PiperOrigin-RevId: 733444080
PiperOrigin-RevId: 733943464
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
See Commits and Changes for more details.
Created by
pull[bot]
Can you help keep this open source service alive? 💖 Please sponsor : )