Fixed: Too big eta in qbit api still occurring on official builds

Co-Authored-By: taloth <taloth@users.noreply.github.com>

build.sh

@@ -67,13 +67,6 @@ CleanFolder()
     find $path -depth -empty -type d -exec rm -r "{}" \;
 }
 
-AddJsonNet()
-{
-    rm $outputFolder/Newtonsoft.Json.*
-    cp $sourceFolder/packages/Newtonsoft.Json.*/lib/net45/*.dll $outputFolder
-    cp $sourceFolder/packages/Newtonsoft.Json.*/lib/net45/*.dll $updateFolder
-}
-
 BuildWithMSBuild()
 {
     installationPath=`$vswhere -latest -products \* -requires Microsoft.Component.MSBuild -property installationPath`
@@ -121,8 +114,6 @@ Build()
 
     CleanFolder $outputFolder false
 
-    AddJsonNet
-
     echo "Removing Mono.Posix.dll"
     rm $outputFolder/Mono.Posix.dll
 

src/NzbDrone.Core.Test/Download/DownloadClientTests/QBittorrentTests/QBittorrentFixture.cs

@@ -495,5 +495,13 @@ namespace NzbDrone.Core.Test.Download.DownloadClientTests.QBittorrentTests
             var item = Subject.GetItems().Single();
             item.Category.Should().Be(category);
         }
+
+        [Test]
+        public void should_handle_eta_biginteger()
+        {
+            var json = "{ \"eta\": 18446744073709335000 }";
+            var torrent = Newtonsoft.Json.JsonConvert.DeserializeObject<QBittorrentTorrent>(json);
+            torrent.Eta.ToString().Should().Be("18446744073709335000");
+        }
     }
 }