Skip to content

Conversation

@nhuthai
Copy link

@nhuthai nhuthai commented Aug 18, 2019

Implement Rectified Adam.
Paper: https://arxiv.org/pdf/1908.03265v1.pdf

rohan100jain and others added 30 commits December 17, 2018 18:34
… are in different graphs. This is in preparation for the next TF release where this warning would become an error.

PiperOrigin-RevId: 225875718
r1.13-rc0 cherrypick request: Raise warning for dataset pipeline in different graphs
PiperOrigin-RevId: 225548043
Add a warning message which happens when contrib is imported.
PiperOrigin-RevId: 226075926
PiperOrigin-RevId: 226087365
1.13.0-rc0 cherry-pick request: Add k8 to toolchains
PiperOrigin-RevId: 226115035
1.13.0-rc0 cherry-pick request: add armebi toolchain
PiperOrigin-RevId: 226115035
PiperOrigin-RevId: 226087365
PiperOrigin-RevId: 226087680
This had previously been done but not uniformly. Change to remove
#!/usr/bin/env python in October caused this problems in latest release.

PiperOrigin-RevId: 226221579
PiperOrigin-RevId: 226094885
PiperOrigin-RevId: 226233807
toolchains from CROSSTOOL files.

PiperOrigin-RevId: 226385901
PiperOrigin-RevId: 226386044
This allows conversion of TFLite models with support for select
TF ops via the standard pip installation.

Note that support for *executing* TFLite models with select TF
ops, via Python, will land separately.

PiperOrigin-RevId: 226355228
PiperOrigin-RevId: 226419504
PiperOrigin-RevId: 226385826
yifeif and others added 10 commits July 11, 2019 20:50
This also adds the 3 compatibility flags on windows builds, as I missed
doing that in #30583
pip_smoke_test only does `bazel cquery` so it doesn't need the build
flags I added in the past few commits (#30651, #30583).

This should now fix sanity build.
Remove additional bazel flags in pip_smoke_test
Python3.5 and Python3.6 have errors while building:

```
ERROR: /tmpfs/src/github/tensorflow/bazel_pip/tensorflow/tools/api/tests/BUILD:16:1: in py_test rule //bazel_pip/tensorflow/tools/api/tests:api_compatibility_test: target '//tensorflow:tf_python_api_gen_v2' is not visible from target '//bazel_pip/tensorflow/tools/api/tests:api_compatibility_test'. Check the visibility declaration of the former target if you think the dependency is legitimate
```

Most likely Bazel default python doesn't properly catch the visibility
declaration, so we're trying to use this fix instead.
@googlebot
Copy link

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it!) and we'll verify it.


What to do if you already signed the CLA

Individual signers
Corporate signers

ℹ️ Googlers: Go here for more info.

@alextp
Copy link
Contributor

alextp commented Aug 19, 2019

Please send this pull request to tensorflow/addons; new optimizers go there instead of in core TF

@alextp alextp closed this Aug 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cla: no size:XL CL Change Size:Extra Large

Projects

None yet

Development

Successfully merging this pull request may close these issues.