-
Notifications
You must be signed in to change notification settings - Fork 525
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Prerelease package range causes stack overflow in PackageResolver #1432
Comments
sounds like a duplicate of #1392 - is there a way for me to reproduce? (something like giving me temporary access?) |
i'll need to get back to you with a reduced test case... |
This is a small reproducible testcase Running setup_packages.sh with Paket 2.39.10 it will yield:
Later versions will yield:
so it seems to happen when one package defines a prerelease dependency and the other one a release dependency. Earlier this would resolve to the release dependency being picked. |
Please test version 2.50.3 and see discussion in #1470 |
Now the second fix is perfectly matching the discussion in #1392 but boy I would never have guessed that reason without a proper repro |
Glad I could help :) So far it looks good. Thanks for the fix. |
We've been using a paket based package system internally to manage nuget packages within our organisation. In recent versions we've noticed a recurring error which forces us to pin to a lower version (we are using 2.39.10, but more investigation is needed to check whether more recent versions are stable)
When using the latest (2.47.2 release and also current master d0846c4 ) we get error when attempting to run
paket update
. From a brief look it appears that the error is due to recent changes in the prerelease handling code.We have two situations in our build, one stable version where we wish to pull in only stable releases, and a prerelease version, where all dependencies are pulled in on the latest development/prerelease version.
the paket.dependencies file for a prerelease looks similar to
In this situation it looks like
getCompatibleVersions
is only returning non prerelease versions and so the resolver gets stuck in a loop when it recurses on step.Attached is a sample stack trace
stacktrace.txt
The text was updated successfully, but these errors were encountered: