You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,6 +25,7 @@ If you send us a PR, whether for documentation, examples, or library code, we re
25
25
***DO** refer to any relevant issues, and include [keywords](https://help.github.com/articles/closing-issues-via-commit-messages/) that automatically close issues when the PR is merged.
26
26
***DO** tag any users that should know about and/or review the change.
27
27
***DO** ensure each commit successfully builds. The entire PR must pass all tests in the Continuous Integration (CI) system before it'll be merged.
28
+
***DO** add a brief description to the RELEASENOTES.md file at the top under the heading of the upcoming release.
28
29
***DO** address PR feedback in an additional commit(s) rather than amending the existing commits, and only rebase/squash them when necessary. This makes it easier for reviewers to track changes.
29
30
***DO** assume that ["Squash and Merge"](https://github.com/blog/2141-squash-your-commits) will be used to merge your commit unless you request otherwise in the PR.
30
31
***DO NOT** fix merge conflicts using a merge commit. Prefer `git rebase`.
Copy file name to clipboardExpand all lines: DEVGUIDE.md
+10-7Lines changed: 10 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -70,23 +70,26 @@ To change the TorchSharp package version update this [file](https://github.com/d
70
70
The TorchSharp package is pushed to nuget.org via Azure DevOps CI release pipeline. Assuming you're not building or updating the LibTorch packages
71
71
(`BuildLibTorchPackages` is `false` in [azure-pipelines.yml](azure-pipelines.yml)) this is pretty simple once you have the permissions:
72
72
73
-
1. Integrate code to main and wait for CI to process
74
-
2. Go to [releases](https://donsyme.visualstudio.com/TorchSharp/_release) and choose "Create Release" (top right)
75
-
3. Under "Artifacts-->Version" choose the pipeline build corresponding to the thing you want to release. It should be a successful build on main
76
-
4. Press "Create"
73
+
1. Update the version number in [./build/BranchInfo.props](./build/BranchInfo.props) and in the [Release Notes](./RELEASENOTES.md) file and then submit a PR.
77
74
78
-
The package version is currently taken from the CI build version.
75
+
Updating the major or minor version number should only be done after a discussion with repo admins. The patch number should be incremented by one each release and set to zero after a change to the major or minor version.
76
+
2. Integrate code to main and wait for CI to process
77
+
3. Go to [releases](https://donsyme.visualstudio.com/TorchSharp/_release) and choose "Create Release" (top right)
78
+
4. Under "Artifacts-->Version" choose the pipeline build corresponding to the thing you want to release. It should be a successful build on main
79
+
5. Press "Create"
80
+
81
+
6. Once the package has been successfully pushed and is available in the NuGet gallery, create a GitHub tag in the 'main' branch with the version as the name of the tag.
79
82
80
83
# The libtorch packages
81
84
82
85
The libtorch packages are huge (~3GB compressed combined for CUDA Windows) and cause a
83
-
lot of problems to make and deliver due to nuget package size restrictions.
86
+
lot of problems to make and deliver due to NuGet package size restrictions.
84
87
85
88
These problems include:
86
89
87
90
1. A massive 2GB binary in the linux CUDA package and multiple 1.0GB binaries in Windows CUDA package
88
91
89
-
2. Size limitations of about ~500MB on nuget packages on the Azure DevOps CI system and about ~250MB on `nuget.org`
92
+
2. Size limitations of about ~500MB on NuGet packages on the Azure DevOps CI system and about ~250MB on `nuget.org`
90
93
91
94
4. Regular download/upload failures on these systems due to network interruptions for packages of this size
Copy file name to clipboardExpand all lines: RELEASENOTES.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,6 +11,10 @@ __Fixed Bugs:__
11
11
Fixed incorrectly implemented Module APIs related to parameter / module registration.
12
12
#353 Missing torch.minimum (with an alternative raising exception)
13
13
14
+
__API Changes:__
15
+
16
+
Removed the type-named tensor factories, such as 'Int32Tensor.rand(),' etc.
17
+
14
18
### NuGet Version 0.92.52220
15
19
16
20
This was the first release since moving TorchSharp to the .NET Foundation organization. Most of the new functionality is related to continuing the API changes that were started in the previous release, and fixing some bugs.
Copy file name to clipboardExpand all lines: src/TorchSharp/Tensor/Tensor.cs
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -1243,7 +1243,7 @@ public Tensor take_along_dim(Tensor indices)
1243
1243
/// <param name="indices">The indices into input. Must have long dtype.</param>
1244
1244
/// <returns></returns>
1245
1245
/// <remarks>Functions that return indices along a dimension, like torch.argmax() and torch.argsort(), are designed to work with this function.</remarks>
/// Selects values from input at the 1-dimensional indices from indices along the given dim.
@@ -1267,7 +1267,7 @@ public Tensor take_along_dim(Tensor indices, long dimension)
1267
1267
/// <param name="dim">Dimension to select along.</param>
1268
1268
/// <returns></returns>
1269
1269
/// <remarks>Functions that return indices along a dimension, like torch.argmax() and torch.argsort(), are designed to work with this function.</remarks>
0 commit comments