8000 Cherry pick openssl fix and R fix and update release notes. by aselle · Pull Request #25125 · tensorflow/tensorflow · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Cherry pick openssl fix and R fix and update release notes. #25125

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
Merged
merged 3 commits into from
Jan 23, 2019
Merged

Cherry pick openssl fix and R fix and update release notes. #25125

merged 3 commits into from
Jan 23, 2019

Conversation

aselle
Copy link
Contributor
@aselle aselle commented Jan 23, 2019

No description provided.

perfinion and others added 3 commits January 23, 2019 01:01
@perfinion @aselle
cloud oauth_client: update for OpenSSL 1.1.0 compatibility
23cd023 
EVP_MD_CTX_cleanup was removed in OpenSSL 1.1.0. There is a call to
EVP_MD_CTX_destroy right after and _destroy will call _cleanup if
required. EVP_MD_CTX_destroy exists in OpenSSL 1.0, 1.1 and BoringSSL so
removing the call to _cleanup works everywhere.

Signed-off-by: Jason Zaman <jason@perfinion.com>
@jtkeeling @aselle
Add bounds checking when looking at the stack in deprecation messages.
91e69ff 
This was breaking integration with R, fixes tensorflow#25067.

PiperOrigin-RevId: 230431304
@aselle
Updated release notes to additional 2 herry-picks
4057b2b
@googlebot
Copy link

So there's good news and bad news.

👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there.

😕 The bad news is that it appears that 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 here in the pull request.

Note to project maintainer: This is a terminal state, meaning the cla/google commit status will not change from this state. It's up to you to confirm consent of all the commit author(s), set the cla label to yes (if enabled on your project), and then merge this pull request when appropriate.

@aselle aselle added cla: yes and removed cla: no labels Jan 23, 2019
@googlebot
Copy link

A Googler has manually verified that the CLAs look good.

(Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.)

@aselle aselle requested a review from annarev January 23, 2019 09:15
@aselle aselle merged commit a8e5c41 into tensorflow:r1.13 Jan 23, 2019
@aselle aselle mentioned this pull request Feb 4, 2019
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@annarev annarev annarev approved these changes

Assignees
No one assigned
Labels
cla: yes
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
5 participants
@aselle @googlebot @annarev @perfinion @jtkeeling
0