Skip to content

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

Closed
DartBot opened this issue Apr 30, 2015 · 8 comments
Closed

pub upgrade hanging #23347

DartBot opened this issue Apr 30, 2015 · 8 comments
Labels
closed-duplicate Closed in favor of an existing report

Comments

@DartBot
Copy link

DartBot commented Apr 30, 2015

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

@DartBot
Copy link
Author

DartBot commented Apr 30, 2015

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.

@floitschG
Copy link
Contributor

Added Area-Pub, Triaged labels.

@nex3
Copy link
Member

nex3 commented May 4, 2015

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.


Added Duplicate label.
Marked as being merged into #16961.

@DartBot
Copy link
Author

DartBot commented May 4, 2015

This comment was originally written by @rbishop-bah


name: xxx_webapp
environment:
  sdk: '>=1.9.0 <2.0.0'
dependencies:
  browser: any
  core_elements: "^0.7.0"
  intl: any
  logging: any
  paper_elements: "^0.7.0"
  polymer: "^0.16.0"
  bwu_fontawesome_iconset_svg: "^0.1.1"

  ... + some locally hosted packages that i don't want to share publicly....
dev_dependencies:
  unittest: "^0.11.0" ----> hangs when any
dependency_overrides:
  # to get polymer, core_elements paper_elements to coexist with bwu_fontawesome_iconset_svg
  core_elements: "^0.7.0"
  paper_elements: "^0.7.0"
  polymer: "^0.16.0"
transformers:

  • polymer:
        entry_points: [web/index.html]

@nex3
Copy link
Member

nex3 commented May 4, 2015

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:

  • quiver 0.21.3 depends on version >=0.10.0 <0.12.0
  • test 0.12.0 depends on version >=0.12.0 <0.12.1

...although I'm not sure why adding a looser constraint produces the error.

@DartBot
Copy link
Author

DartBot commented May 4, 2015

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"
  color_picker: "^1.1.4"
  collection: "^1.1.0"
  intl: "^0.12.1"
  logging: ">=0.9.3 <0.11.0"
  meta: "^0.8.8"
dev_dependencies:
  benchmark_harness: "^1.0.4"
  browser: "^0.10.0"

@nex3
Copy link
Member

nex3 commented May 4, 2015

It still fails quickly for me.

Don't worry about it too much, we've got other pathological pubspecs we can look at.

@DartBot
Copy link
Author

DartBot commented Jun 4, 2015

This issue has been moved to dart-lang/pub#14.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed-duplicate Closed in favor of an existing report
Projects
None yet
Development

No branches or pull requests

4 participants