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.

Sign up for GitHub

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

Jump to bottom

Iterate over Python range instead jnp.arange. #29

Merged

copybara-service merged 1 commit into master from test_399392126

Oct 7, 2021

copybara-service bot commented Sep 28, 2021 •

edited

Loading

Iterate over Python range instead jnp.arange.

google-cla bot commented Sep 28, 2021

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

google-cla bot added the cla: no label

copybara-service bot force-pushed the test_399392126 branch from 7a64680 to 0907041 Compare

September 28, 2021 10:15

copybara-service bot changed the title ~~Iterate over a Python range instead jnp.arange.~~ Iterate over Python range instead jnp.arange.

google-cla bot commented Sep 28, 2021

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

copybara-service bot force-pushed the test_399392126 branch from 0907041 to 59ed279 Compare

October 6, 2021 10:08

google-cla bot commented Oct 6, 2021

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

copybara-service bot force-pushed the test_399392126 branch from 59ed279 to 6673ba1 Compare

October 6, 2021 10:56

google-cla bot commented Oct 6, 2021

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

copybara-service bot force-pushed the test_399392126 branch from 6673ba1 to 8f72691 Compare

October 7, 2021 07:43

google-cla bot commented Oct 7, 2021

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

copybara-service bot force-pushed the test_399392126 branch from 8f72691 to 5aaf35f Compare

October 7, 2021 15:01

google-cla bot added cla: yes and removed cla: no labels


          Iterate over Python range instead jnp.arange.

4ec43c9

PiperOrigin-RevId: 401515158

copybara-service bot force-pushed the test_399392126 branch from 5aaf35f to 4ec43c9 Compare

October 7, 2021 15:11

copybara-service bot merged commit 4ec43c9 into master

copybara-service bot deleted the test_399392126 branch

October 7, 2021 15:11

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels