-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Updated Tensorflow.Net to 0.70.2 with Tensorflow 2.7.0. #7472
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.
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
base: main
Are you sure you want to change the base?
Changes from 3 commits
82e3275
16782f6
85f7ad4
02419b8
17bf4cc
7e5d791
1da1a6f
82e8a64
f350740
bb5c00c
eada7a0
734b8d1
3a4df1e
1089633
7562205
822e26a
e99dcc1
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -67,9 +67,9 @@ | |
<ParquetDotNetVersion>2.1.3</ParquetDotNetVersion> | ||
<PlotlyNETCSharpVersion>0.11.1</PlotlyNETCSharpVersion> | ||
<SharpZipLibVersion>1.4.2</SharpZipLibVersion> | ||
<TensorflowDotNETVersion>0.20.1</TensorflowDotNETVersion> | ||
<TensorflowDotNETVersion>0.70.2</TensorflowDotNETVersion> | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Why this version and not latest ( There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. It was a time critical update and we needed to get to a version that could be deployed without requiring WSL support to enable full use of the GPU. I believe that 0.100.x releases still works without WSL but it seemed quite a big jump to go from 0.70.x and to jump Tensorflow from 2.7 to 2.10. We could investigate though to see if there are any breaking changes involved? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Ideally we should be on the latest supported so that we ensure we can take any future updates. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I ran into issues going all the way to the latest TensorFlow.NET. I was able to absorb the breaking API changes, but they removal of strong name signing as well as taking on a dependency without a strong name will break consumption on .NETFramework. I filed SciSharp/TensorFlow.NET#1296 to track those. I rolled back to a version without those breaks, hit one other break around disposal of status, and rolled back further to 0.100.2. I think this is the latest version that will still work and it's just one release ahead of what you were using 🙃 |
||
<TensorFlowMajorVersion>2</TensorFlowMajorVersion> | ||
<TensorFlowVersion>2.3.1</TensorFlowVersion> | ||
<TensorFlowVersion>2.7.0</TensorFlowVersion> | ||
ericstj marked this conversation as resolved.
Show resolved
Hide resolved
|
||
<TorchSharpPyBridgeVersion>1.4.1</TorchSharpPyBridgeVersion> | ||
<AutoGenVersion>0.2.3</AutoGenVersion> | ||
<SemanticKernelVersion>1.48.0</SemanticKernelVersion> | ||
|
@@ -90,6 +90,7 @@ | |
<BenchmarkDotNetVersion>0.13.12</BenchmarkDotNetVersion> | ||
<DotNetRuntime60Version>6.0.36</DotNetRuntime60Version> | ||
<DotNetRuntime80Version>8.0.16</DotNetRuntime80Version> | ||
<DotNetRuntime90Version>9.0.5</DotNetRuntime90Version> | ||
ericstj marked this conversation as resolved.
Show resolved
Hide resolved
|
||
<AwesomeAssertionsVersion>8.1.0</AwesomeAssertionsVersion> | ||
<MicrosoftCodeAnalysisTestingVersion>1.1.2</MicrosoftCodeAnalysisTestingVersion> | ||
<MicrosoftDotNetBuildTasksTemplatingVersion>9.0.0-beta.24212.4</MicrosoftDotNetBuildTasksTemplatingVersion> | ||
|
Uh oh!
There was an error while loading. Please reload this page.