Well, you are wrong, other nuget projects like BaGet are able to solve this.
They don't offer such a range of features, but i prefer a more stable solution
than proget is at the moment. Also BaGet supports the v3 protocol,
which is missing in proget since years.
Posts made by mprueter_2431
-
RE: Restoring multiple packages fails regularly
-
RE: Restoring multiple packages fails regularly
I still wonder why this works from visual studio with a direct nuget.org connection.
Could you please check out that you are re-using the socket connection instead of creating new ones?https://aspnetmonsters.com/2016/08/2016-08-27-httpclientwrong/
This could explain the strange wait states and the exception that's got thrown.
-
RE: Docker: Consider not to use shared configurations / files in the docker host
Well, i think it is against the docker concept to share such files.
It makes it hard to throw a container away and start from the scretch. -
Docker: Consider not to use shared configurations / files in the docker host
It seems to be pretty hard to reinstall your docker container. Deleting networks, volumes and images is not enough if the password in the docker-compose file has changed.
-
RE: Restoring multiple packages fails regularly
Well, i'm talking about restoring 40-60 packages and i'm running proget locally on a docker container.
-
Restoring multiple packages fails regularly
When the package cache is empty and i restore a solution that contains multiple nuget packages the restore fails regularly. I allways receive the error: "Connector error: The operation has timed out."
I have to wait a couple of minutes until it works. I don't have this issue when i restore the packages from visual studio with the v3 nuget.com feed. I happens only when i use proget and the v2 nuget.com feed on a connector.
Level: Error
Category: Connector
Message: Connector error: The operation has timed out.Details: Request URL: https://www.nuget.org/api/v2/Packages(Id='System.Runtime.Serialization.Formatters',Version='4.3.0')?semVerLevel=2.0.0
System.Net.WebException: The operation has timed out.
at System.Net.HttpWebRequest.RunWithTimeoutWorker[T] (System.Threading.Tasks.Task1[TResult] workerTask, System.Int32 timeout, System.Action abort, System.Func
1[TResult] aborted, System.Threading.CancellationTokenSource cts) [0x000f8] in <048f685b456c4326be453e3cc3faae14>:0
at System.Net.HttpWebRequest.EndGetResponse (System.IAsyncResult asyncResult) [0x00020] in <048f685b456c4326be453e3cc3faae14>:0
at System.Threading.Tasks.TaskFactory1[TResult].FromAsyncCoreLogic (System.IAsyncResult iar, System.Func
2[T,TResult] endFunction, System.Action1[T] endAction, System.Threading.Tasks.Task
1[TResult] promise, System.Boolean requiresSynchronization) [0x0000f] in <81342d83acda4c5590ec19c7afdf26b9>:0
--- End of stack trace from previous location where exception was thrown ---at Inedo.ProGet.Feeds.StrongConnector.GetDirectResponseAsync (System.String url) [0x000eb] in <6a03994888e145da81d6016fd555fffb>:0
at Inedo.ProGet.Feeds.StrongConnector.GetCachedResponseAsync (System.String url) [0x000a8] in <6a03994888e145da81d6016fd555fffb>:0
at Inedo.ProGet.Feeds.StrongConnector.GetCachedTextReaderAsync (System.String url) [0x00075] in <6a03994888e145da81d6016fd555fffb>:0
at Inedo.ProGet.Feeds.NuGet.NuGetFeedClient.PerformRequestWithAbsoluteUrlAsync (System.String fullUrl) [0x000d9] in <6a03994888e145da81d6016fd555fffb>:0