Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Paket gets stuck while resolving packages from Sonatype Nexus 3

See original GitHub issue

Description

Paket.exe gets stuck under certain conditions. It seems to getting into an infinite loop consuming more and more memory:

Repro steps

I have set up own repository just to make sure I can reproduce the problem I’m having in a production environment. To reproduce it:

Download version 5.0.0 of paket.exe into e.g. c:\temp\nexus-bug
Create paket.dependencies with the following contents

source http://91.121.154.55:8081/repository/nuget-hosted/

nuget Small.ExeFile1
nuget Small.ExeFile2
nuget Small.ExeFile3
nuget Small.ExeFile4
nuget Small.ExeFile5
nuget Small.ExeFile6
nuget Small.ExeFile7
nuget Small.ExeFile8
#nuget Small.ExeFile9
#nuget Small.ExeFile10
#nuget Small.ExeFile11
#nuget Small.ExeFile12

nuget Big.ExeFile1
#nuget Big.ExeFile2
#nuget Big.ExeFile3

Run paket install like this:

Expected behavior

Paket should resolve and install all the packages.

Actual behavior

Package resolution gets stuck at Small.ExeFile7 and never finishes.

It looks like when there is at least one big package and a group of other (small) packages with lots of versions of each package, then paket only handles eight (8) items at most. If there is more than eight, it gets stuck.

Known workarounds

None.

Issue Analytics

State:
Created 6 years ago
Comments:24 (14 by maintainers)

Top GitHub Comments

1reaction

matthidcommented, Jun 17, 2017

Yes I’m seeing it now:

http://91.121.154.55:8081/repository/nuget-hosted/Packages()?$filter=tolower%28Id%29+eq+%27small.exefile8%27&semVerLevel=2.0.0&amp

Yields all versions and

<link rel="next" href="http://91.121.154.55:8081/repository/nuget-hosted/Packages()?$skip=40&amp;$filter=tolower%28Id%29+eq+%27small.exefile8%27&amp;amp;semVerLevel=2.0.0&amp;amp="/>

But if you request that uri it will return the exact same versions, but:

<link rel="next" href="http://91.121.154.55:8081/repository/nuget-hosted/Packages()?$skip=80&amp;amp;amp;semVerLevel=2.0.0&amp;amp;$filter=tolower%28Id%29+eq+%27small.exefile8%27&amp;amp;amp="/>

As you can see the server is returning always the same result but increments the skip parameter by 40. Looks pretty broken to me…

0reactions

nikoudelcommented, Jan 2, 2018

No updates from my side. I’ve updated the Jira ticket.

Top Results From Across the Web

Solving NuGet Performance Problems in Nexus Repository 3

The performance issue described in this article only occurs when OrientDb database is used in Nexus Repo 3. So migration to Postgres ...

Stuck on "Resolving Packages"

trying to get everything upgraded to 20182.2 before we start a new project. This is a pervasive issue that we have not been...

Stuck on resolving packages in 2020.3 LTS? Try this!

This solution only works when Unity keeps resolving packages again and again after the project is loaded. If you can't load the project, ......

Nexus3 stuck on initializing and not properly resolving ...

First thing to do is to make sure nginx has been configured to send in the headers Nexus Repo needs. Examples can be...

Nexus OSS not starting after adding the R repository plug-in

On a quick search in the Maven public repository, I didn't find any artifacts ... by: Unable to resolve org.sonatype.nexus.plugins.nexus-repository-r/1.0.1: ...