Upgrading Tensorflow to 1.15.4 in tf.txt #1341
Comments
|
Idea is cool and good. We have some plans to make TF upgrades down the road for the next year, but not as fast as you might think. However, if you think you could try to work on some of this stuff, well, we'd be thrilled to help! |
|
Yes. I can surely contribute. I will upgrade it to TensorFlow 1.15.4 and check for any compatibility issue. Most likely, there won't be an issue with .4 version. I will update soon. |
|
Sounds fantastic! @ignatov.fedor@gmail.com<mailto:ignatov.fedor@gmail.com> join the discussion if needed! )
Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10
From: Rajmehta123<mailto:notifications@github.com>
Sent: Monday, November 16, 2020 5:15 PM
To: deepmipt/DeepPavlov<mailto:DeepPavlov@noreply.github.com>
Cc: Daniel Kornev<mailto:daniel@zetuniverse.com>; Comment<mailto:comment@noreply.github.com>
Subject: Re: [deepmipt/DeepPavlov] Upgrading Tensorflow to 1.15.4 in tf.txt (#1341)
Yes. I can surely contribute. I will upgrade it to TensorFlow 1.15.4 and check for any compatibility issue. Most likely, there won't be an issue with .4 version. I will update soon.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<#1341 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABIFFK2ZR45PFNTBLNWTT2DSQEXX7ANCNFSM4TVEDZXQ>.
|
|
@Rajmehta123 Hey ) |
|
@moryshka Hey. Yes, I have tested on a few use cases and they don't create any problems. Looking at what TF has changed in 1.15.4, there is nothing with syntax or functionality. The release is for the fixes for bugs. Fixes an undefined behavior causing a segfault in tf.raw_ops.Switch (CVE-2020-15190) |
|
So, this means we can migrate the whole thing to 1.15.4?
Get Outlook for Android<https://aka.ms/ghei36>
…________________________________
From: Rajmehta123 <notifications@github.com>
Sent: Friday, December 11, 2020 7:04:54 PM
To: deepmipt/DeepPavlov <DeepPavlov@noreply.github.com>
Cc: Daniel Kornev <daniel@zetuniverse.com>; Comment <comment@noreply.github.com>
Subject: Re: [deepmipt/DeepPavlov] Upgrading Tensorflow to 1.15.4 in tf.txt (#1341)
@moryshka<https://github.com/moryshka> Hey. Yes, I have tested on a few use cases and they don't create any problems. Looking at what TF has changed in 1.15.4, there is nothing with syntax or functionality. The release is for the fixes for bugs.
Fixes an undefined behavior causing a segfault in tf.raw_ops.Switch (CVE-2020-15190<https://github.com/advisories/GHSA-4g9f-63rx-5cw4>)
Fixes three vulnerabilities in conversion to DLPack format (CVE-2020-15191<https://github.com/advisories/GHSA-q8qj-fc9q-cphr>, CVE-2020-15192<https://github.com/advisories/GHSA-8fxw-76px-3rxv>, CVE-2020-15193<https://github.com/advisories/GHSA-rjjg-hgv6-h69v>)
Fixes two vulnerabilities in SparseFillEmptyRowsGrad (CVE-2020-15194<https://github.com/advisories/GHSA-9mqp-7v2h-2382>, CVE-2020-15195<https://github.com/advisories/GHSA-63xm-rx5p-xvqr>)
Fixes an integer truncation vulnerability in code using the work sharder API (CVE-2020-15202<https://github.com/advisories/GHSA-h6fg-mjxg-hqq4>)
Fixes a format string vulnerability in tf.strings.as_string (CVE-2020-15203<https://github.com/advisories/GHSA-xmq7-7fxm-rr79>)
Fixes segfault raised by calling session-only ops in eager mode (CVE-2020-15204<https://github.com/advisories/GHSA-q8gv-q7wr-9jf8>)
Fixes data leak and potential ASLR violation from tf.raw_ops.StringNGrams (CVE-2020-15205<https://github.com/advisories/GHSA-g7p5-5759-qv46>)
Fixes segfaults caused by incomplete SavedModel validation (CVE-2020-15206<https://github.com/advisories/GHSA-w5gh-2wr2-pm6g>)
Fixes a data corruption due to a bug in negative indexing support in TFLite (CVE-2020-15207<https://github.com/advisories/GHSA-q4qf-3fc6-8x34>)
Fixes a data corruption due to dimension mismatch in TFLite (CVE-2020-15208<https://github.com/advisories/GHSA-mxjj-953w-2c2v>)
Fixes several vulnerabilities in TFLite saved model format (CVE-2020-15209<https://github.com/advisories/GHSA-qh32-6jjc-qprm>, CVE-2020-15210<https://github.com/advisories/GHSA-x9j7-x98r-r4w2>, CVE-2020-15211<https://github.com/advisories/GHSA-cvpc-8phh-8f45>)
Updates sqlite3 to 3.33.00 to handle CVE-2020-9327, CVE-2020-11655, CVE-2020-11656, CVE-2020-13434, CVE-2020-13435, CVE-2020-13630, CVE-2020-13631, CVE-2020-13871, and CVE-2020-15358.
Fixes #41630 by including max_seq_length in CuDNN descriptor cache key
Pins numpy to 1.18.5 to prevent ABI breakage when compiling code that uses both NumPy and TensorFlow headers.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<#1341 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABIFFK6EUZOOOPFDKMZ54ITSUI7KNANCNFSM4TVEDZXQ>.
|
|
@danielkornev Yes we can migrate to 1.15.4 to include security updates |
|
@danielkornev @IgnatovFedor Any update on the upgrade? |
|
We shipped it in 0.14. |
|
Yes just realized. Thanks |
|
Oh, thank you! Your help was instrumental in driving this update!
Get Outlook for Android<https://aka.ms/ghei36>
…________________________________
From: Rajmehta123 <notifications@github.com>
Sent: Friday, January 22, 2021 10:19:50 PM
To: deepmipt/DeepPavlov <DeepPavlov@noreply.github.com>
Cc: Daniel Kornev <daniel@zetuniverse.com>; Mention <mention@noreply.github.com>
Subject: Re: [deepmipt/DeepPavlov] Upgrading Tensorflow to 1.15.4 in tf.txt (#1341)
Yes just realized. Thanks
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#1341 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABIFFK7FTTGSPRAON7LSS5DS3HFVNANCNFSM4TVEDZXQ>.
|
What problem are we trying to solve?:
How can we solve it?:
Are there other issues that block this solution?:
Any important aspect to consider?:
The text was updated successfully, but these errors were encountered: