Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.
If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!
Constant timeouts doing NuGet restore
-
If I can venture a guess as to what's happening, I think that the ThreadPool is being completely saturated.
Kestrel will use the ThreadPool to service a request. That request is then using a parallel query, which will also use the ThreadPool. At some point, every thread in the pool is blocked, waiting for a task to complete, but the task can't complete because it needs to be scheduled onto the ThreadPool, but every thread in the pool is blocked.
I'd be curious to see what happens if the ParallelEnumerable query is replaced with a standard Enumerable query.
-
@brett-polivka thanks again for all the help and insights!
I talked this over with the engineering team, and we just decided to remove the
ParallelEnumerablequery.Would you be able to try a pre-release container?
inedo/proget:5.3.23-ci.4 -
I'm still seeing the same problem and the stack traces. Can you confirm that the 5.3.23-ci.4 release is the right version, because it still contains the parallel query.
-
Hi @brett-polivka,
It looks like there was a mix-up in one of our branches. I just pushed an updated image with the ParallelEnumerable removed. Can you please give the
proget.inedo.com/productimages/inedo/proget:5.3.23-ci.5image a try?Thanks,
Rich -
Hi Rich,
This seems to have done the trick! I've been running constant restores against it for an hour with no timeouts.
Thanks!!
-
Thanks to @atripp as well. Appreciate your patience dealing with this (and me).
-
Whoops, my bad!
@brett-polivka thanks so much for the help, this was a baffling .NET5 issue, but so glad we could identify and fix it. This will definitely go in the maintence release as well, of course.
-
@atripp This is probably related with the same issue i kept mentioning which you were saying it was possibly due to an overloaded network stack or other type of configurations. I still have the problem even after setting up a completely new server so it also shows that any timeout is related with proget application code. Looking forward to try out this fix. This apparently was happening to other users as well. :)
-
@nuno-guerreiro-rosa_9280 very glad we could fix it! It's definitely a .NET5 bug, and in a totally unexpected place
-
I also confirm I didn't get any more timeouts on the latest version. Very good!
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login