I want to install a nuget package from our BaGet server (https://github.com/ai-traders/BaGet). This fails with an InvalidOperationException: Timeouts werden in diesem Datenstrom nicht unterstützt (german windows, the error message says timeouts are not supported for this data stream). It works with the previous stable version (5.181.1)
This behaviour was observed on Windows 10 with both the full dotnet framework and the dotnet core sdk installed (latest-ish versions - let me know if the precicse versions help)
Please provide the steps required to reproduce the problem
Create a new f# console application, add the paket bootstrapper
Use this as paket.dependencies
storage: none
source https://api.nuget.org/v3/index.json
framework: auto-detect
nuget FSharp.Core
source https://baget.cloud.douglasconnect.com/v3/index.json
nuget DouglasConnect
The package should be downloaded and installed
An exception occurs:
Paket failed with
-> Could not download DouglasConnect 6.0.6 from https://baget.cloud.douglasconnect.com/v3/package/douglasconnect/6.0.6/douglasconnect.6.0.6.nupkg.
StackTrace:
bei [email protected](Exception _arg12)
bei [email protected](AsyncParams`1 args)
--- Ende der Stapelüberwachung vom vorhergehenden Ort, an dem die Ausnahme ausgelöst wurde ---
bei System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
bei Microsoft.FSharp.Control.AsyncBuilderImpl.commit[a](AsyncImplResult`1 res)
bei Microsoft.FSharp.Control.CancellationTokenOps.RunSynchronouslyInCurrentThread[a](CancellationToken token, FSharpAsync`1 computation)
bei Microsoft.FSharp.Control.CancellationTokenOps.RunSynchronously[a](CancellationToken token, FSharpAsync`1 computation, FSharpOption`1 timeout)
bei Microsoft.FSharp.Control.FSharpAsync.RunSynchronously[T](FSharpAsync`1 computation, FSharpOption`1 timeout, FSharpOption`1 cancellationToken)
bei Microsoft.FSharp.Collections.Internal.IEnumerator.map@74.DoMoveNext(b& curr)
bei Microsoft.FSharp.Collections.Internal.IEnumerator.MapEnumerator`1.System-Collections-IEnumerator-MoveNext()
bei Microsoft.FSharp.Core.CompilerServices.RuntimeHelpers.takeOuter@274[T,TResult](ConcatEnumerator`2 x, Unit unitVar0)
bei Microsoft.FSharp.Core.CompilerServices.RuntimeHelpers.takeOuter@274[T,TResult](ConcatEnumerator`2 x, Unit unitVar0)
bei System.Collections.Generic.List`1..ctor(IEnumerable`1 collection)
bei Microsoft.FSharp.Collections.SeqModule.ToArray[T](IEnumerable`1 source)
bei Paket.InstallProcess.InstallIntoProjects[a](InstallerOptions options, Boolean forceTouch, DependenciesFile dependenciesFile, LockFile lockFile, FSharpList`1 projectsAndReferences, FSharpMap`2 updatedGroups)
bei Paket.UpdateProcess.SmartInstall(DependenciesFile dependenciesFile, UpdateMode updateMode, UpdaterOptions options)
bei <StartupCode$Paket-Core>[email protected](Unit unitVar0)
bei Paket.Utils.RunInLockedAccessMode[a](String lockedFolder, FSharpFunc`2 action)
bei [email protected](ParseResults`1 results)
bei Paket.Program.processWithValidationEx$cont@42[a](Boolean silent, FSharpFunc`2 commandF, a result, Unit unitVar)
bei Paket.Program.processWithValidation[T](Boolean silent, FSharpFunc`2 validateF, FSharpFunc`2 commandF, ParseResults`1 result)
bei Paket.Program.handleCommand(Boolean silent, Command command)
bei Paket.Program.main()
-> InvalidOperationException: Timeouts werden in diesem Datenstrom nicht unterstützt.
Switch from using paket in magic mode to using the last stable version.
Looks related to https://github.com/fsprojects/Paket/pull/3383
+1 Can reproduce.
We are experiencing the same error, InvalidOperationException: Timeouts are not supported on this stream. when using paket 5.183.0. The version 5.181.1 works fine.
ok I'm reverting
I can confirm this issue also occurs for ProGet feeds.
Latest version should work again. Can anyone confirm?
Raphael Schweizer notifications@github.com schrieb am Mi., 31. Okt. 2018,
08:41:
I can confirm this issue also occurs for ProGet feeds.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/fsprojects/Paket/issues/3407#issuecomment-434590430,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADgNKJ5z09aN6rOKNCQpU0T2WTor10aks5uqVRCgaJpZM4YCZm9
.
@forki Yes, latest (5.184.0) does work. Sorry, should have mentioned this as well.
Ok good.
If someone finds a way to reapply the PR in a way that is non-breaking then
it would be appropriated.
Raphael Schweizer notifications@github.com schrieb am Mi., 31. Okt. 2018,
09:06:
@forki https://github.com/forki Yes, latest (5.184.0) does work. Sorry,
should have mentioned this as well.—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/fsprojects/Paket/issues/3407#issuecomment-434595325,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADgNIzhVGyU8-8y2KO9qZMAPaPkAaW1ks5uqVl6gaJpZM4YCZm9
.
@forki - Just following up - 5.184.0 is working for me as well. Thanks!
Thanks to the feed provided i think that i was able to solve the problem and will make a PR tomorrow.
One remaining question to be answered would be if the default timeouts set are ok like they are now.
They could just be set to never timeout as default.
Here is the pull request for the problem.
https://github.com/fsprojects/Paket/pull/3424
Can this issue be closed then?
Thanks
Most helpful comment
ok I'm reverting