-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Update to .NET 5 #10346
Update to .NET 5 #10346
Conversation
.NET 5 brings many performance (especially regex) improvements https://devblogs.microsoft.com/dotnet/announcing-net-5-0/ Can look at bringing the packages upto date and using a single file executable in a future PR if the maintainers are interested
Run out of time for now, will try and have another look this weekend (unless some one else is keen!) |
@garfield69 @ilike2burnthing I have a lot of work lately. I can only spend time on this project on the weekend. I will go over all the important assignments on Saturday or Sunday. If something can't wait that long, you don't have to wait for me. |
Fixed the issue with Mono, really great work from the maintainers having those integration tests, pretty unusual in OSS |
As far as I'm aware, all praise goes to @ngosang (at least of late) for those |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am extremely confused.
Ran my win10 VirtualBox and started ubuntu 18.04, downloaded the amd package from this PR, extracted it and ran the systemd installer
and the Jackett log shows:
2020-12-04 16:34:21 Info Using HTTP Client: HttpWebClient
2020-12-04 16:34:21 Info Using proxy: Disabled
2020-12-04 16:34:21 Info App config/log directory: /home/garfield69/.config/Jackett
2020-12-04 16:34:21 Info ThreadPool MaxThreads: 32767 workerThreads, 1000 completionPortThreads
2020-12-04 16:34:21 Info Running in Docker: No
2020-12-04 16:34:21 Info File /etc/issue: Ubuntu 18.04.5 LTS \n \l
2020-12-04 16:34:21 Info Jackett variant: Mono
2020-12-04 16:34:21 Info OS version: Unix 4.15.0.126 (64bit OS) (64bit process)
2020-12-04 16:34:21 Info Environment version: 5.0.0 (/home/garfield69/Downloads/Jackett.Binaries.LinuxAMDx64/Jackett/)
2020-12-04 16:34:18 Info Starting Jackett v0.16.2296.0
- Was expecting Jackett variant CoreLinuxAmdx64 not Mono
downloaded the win package, installed and the Jackett log shows:
2020-12-04 16:47:02 Info Using HTTP Client: HttpWebClient
2020-12-04 16:47:02 Info Using proxy: Disabled
2020-12-04 16:47:02 Info App config/log directory: C:\ProgramData\Jackett
2020-12-04 16:47:02 Info ThreadPool MaxThreads: 682 workerThreads, 1000 completionPortThreads
2020-12-04 16:47:02 Info Running in Docker: No
2020-12-04 16:47:02 Info Jackett variant: FullFrameworkWindows
2020-12-04 16:47:02 Info OS version: Microsoft Windows NT 10.0.19042.0 (64bit OS)
2020-12-04 16:47:02 Info Environment version: 5.0.0 (C:\ProgramData\Jackett\)
2020-12-04 16:47:01 Info Starting Jackett v0.16.2296.0
- Was expecting Jackett variant CoreWindows not FullFrameworkWindows
Ran win10 VirtualBox and started BigSur, downloaded the mac package, installed and the Jackett log shows:
2020-12-04 21:32:28 Info Using HTTP Client: HttpWebClient
2020-12-04 21:32:28 Info Using proxy: Disabled
2020-12-04 21:32:28 Info App config/log directory: /Users/garfield69/.config/Jackett
2020-12-04 21:32:28 Info ThreadPool MaxThreads: 32767 workerThreads, 1000 completionPortThreads
2020-12-04 21:32:28 Info Running in Docker: No
2020-12-04 21:32:28 Info Jackett variant: Mono
2020-12-04 21:32:28 Info OS version: Unix 11.0.0 (64bit OS) (64bit process)
2020-12-04 21:32:28 Info Environment version: 5.0.0 (/Users/garfield69/Downloads/Jackett/)
2020-12-04 21:31:58 Info Starting Jackett v0.16.2296.0
- Was expecting Jackett variant CoreMacOs not Mono
looks like it is failing this conditional
|
so this
no longer contains core when .net 5 is activehttps://docs.microsoft.com/en-us/dotnet/api/system.runtime.interopservices.runtimeinformation.frameworkdescription?view=net-5.0 |
Good pickup @garfield69 , sorry my bad Also, I'd suggest bumping the minorVersion to 17 for this, but will leave that to you to decide |
@airhawk777 Thank you! This is an important change and I want to be sure everything is right. It can take some time.
@garfield69 @ilike2burnthing I will need help with Windows, MacOS tests |
Compile warnings are not blocking this issue. They can be fixed later.
@airhawk777 do you have some info to share? can it be related to the new dependencies included in this pr? memory usage in windows is similar? |
LegendWS- Working Set 221 indexers, of which 31 failed. 21 failed when using proxy/VPN, with little to no difference in memory. All are expected to fail (i.e. this isn't causing indexers to fail which weren't already). Multiple runs (restarting the Jackett in between) had some variance, figures above show a rough average. Log traces:
Manual updates from 3.1>5.0, 5.0>3.1, and 5.0>5.0 all worked fine without error. |
I did all test in Linux / Mono / Docker and everything is fine. |
tested OK on my win10 VirtualBox macOS Big Sur image. |
If needed, you can extract the VHD from the XP Mode installer - https://www.microsoft.com/en-us/download/details.aspx?id=8002 Got it up and running using Hyper-V, but couldn't get internet access for whatever reason. |
found my winXP sp4 installer cd, installing into VirtualBox image as I type this. Should be done in the next couple hours ;-) |
Will have a look at the compile warnings when I get some spare time. Looks like a new warning with .net 5 so will follow this issue dotnet/sdk#14502 it shouldn’t cause any issues since it’s been doing this all along Doubt jackett even with current release will work on xp since .NET core requires win7. Jackett read me also specifies a minimum of win7 as well |
WinXP is unsupported as pointed out by airhawk777 Will bump the minorversion to 17 on this PR and then publish as a pre-release |
testing check-for-updates upgrading from 0.16.2374 to 0.17.3 pre-release on win10, win7sp1, ubuntu18,04 and BigSur |
Nice job! Thank you very much to all. |
@airhawk777 Sorry if this is the wrong place to ask, but I'm getting errors that I'm unfamiliar with. Everything was fine until I updated my Visual Studio 2019 to version 16.9. I am now getting these errors:
I eventually found the fix, which is to add Can someone tell me why I needed to do this now and not before the VS update? Am I doing something wrong or have they changed the way you're supposed to add frameworks? Is this something we should add to this change or am I the only one experiencing this error? And if we were to add this to master, would this have an effect on other platforms (because it's targeting Windows, which I'm developing on)? |
@XYZJR I don't know much about your particular issue, but whenever my VS upgrades and I get a problem I just access the tools->nuGet packet manager->packet manager console, and when the prompt is ready and type |
@garfield69 I re-installed .NET 5 SDK and Visual Studio, then re-cloned the project. |
@XYZJR that's unfortunate. |
@XYZJR here's a fix from @JigSawFr: After cloning your fork, execute these commands:
And it will work as expected otherwise server project building will fail. :) |
.NET 5 brings many performance (especially regex) improvements
https://devblogs.microsoft.com/dotnet/announcing-net-5-0/
Can look at bringing the packages upto date and using a single file executable in a future PR if the maintainers are interested