On it!

All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter.

We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only @googlebot I consent. in this pull request.

Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the cla label to yes (if enabled on your project).

ℹ️ Googlers: Go here for more info.

@saudet , I've rebased the PR and it looks like you need to reconsent now.

Also, I've noticed that there are a lot of changes in the .bazelrc file of TensorFlow that we did not import in our copy, I'm not sure if we should copy it/merge it at each upgrade, wdyt?

@googlebot I consent.

All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter.

We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only @googlebot I consent. in this pull request.

Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the cla label to yes (if enabled on your project).

ℹ️ Googlers: Go here for more info.

@saudet , I've rebased the PR and it looks like you need to reconsent now.

Also, I've noticed that there are a lot of changes in the .bazelrc file of TensorFlow that we did not import in our copy, I'm not sure if we should copy it/merge it at each upgrade, wdyt?

Not sure what to say, this Bazel stuff is all really annoying.

All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter.

We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only @googlebot I consent. in this pull request.

Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the cla label to yes (if enabled on your project).

ℹ️ Googlers: Go here for more info.

All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter.

We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only @googlebot I consent. in this pull request.

Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the cla label to yes (if enabled on your project).

ℹ️ Googlers: Go here for more info.

@googlebot I consent.

@saudet , I've rebased the PR and it looks like you need to reconsent now.
Also, I've noticed that there are a lot of changes in the .bazelrc file of TensorFlow that we did not import in our copy, I'm not sure if we should copy it/merge it at each upgrade, wdyt?

Not sure what to say, this Bazel stuff is all really annoying.

Yeah same here, it's hard to say what are the real impact of updating/not-updating this file... Ok let's merge it as is and we can update it later if we think we need to. Thanks @saudet!