-
Notifications
You must be signed in to change notification settings - Fork 1.7k
pub upgrade hanging #23347
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
Comments
This comment was originally written by @rbishop-bah Actually, pinning unittest: "^0.11.0" gets things working again so it appears pub upgrade is getting confused by having unittest 0.12.0 as an option. |
This is a duplicate of issue #16961. Pub's version solving algorithm can run into cases where it goes exponential, and it looks like you've found one of those cases. If you can provide the pubspec that caused this issue, it may help us add more heuristics to avoid it in the future. |
This comment was originally written by @rbishop-bah name: xxx_webapp ... + some locally hosted packages that i don't want to share publicly....
|
Your locally-hosted packages may be relevant here. Without them (and changing the "unittest" dependency to "any"), I get the following error quickly: Incompatible version constraints on matcher:
...although I'm not sure why adding a looser constraint produces the error. |
This comment was originally written by @rbishop-bah I believe the additional transitive dependencies from the local packages would be: browser_detect: "^1.0.3" |
It still fails quickly for me. Don't worry about it too much, we've got other pathological pubspecs we can look at. |
This issue has been moved to dart-lang/pub#14. |
This issue was originally filed by @rbishop-bah
Build that was working until this morning now hanging on pub upgrade, presumably due to just-released polymer, web_components, smoke, observe, etc. packages.
pub upgrade --verbose shows the pub solver churning endlessly.
What version of the product are you using?
1.10.0
On what operating system?
Win 7 x64
The text was updated successfully, but these errors were encountered: