pub upgrade times out with this pubspec

[DartBot]

This issue was originally filed by pruj...@gmail.com

---

What steps will reproduce the problem?

1. Use this pubspec:
   name: test
   version: 0.0.1
   description: pub upgrade churn
   dependencies:
     core_elements: '>=0.2.0+1'
     game_loop: '>=0.9.4'
     logging: '>=0.9.2'
     paper_elements: '>=0.1.1+2'
     polymer: '>=0.13.0+3'
     query_string: '>=1.0.4'
     redstone: '>=0.5.15'
     redstone_mapper: '>=0.1.6'
     yaml: '>=2.0.0'
2. run pub get (works)
3. run pub upgrade (times out)

What is the expected output? What do you see instead?
This was working until I upgrade dart to 1.7.2 today. Though I can't say this is directly related, since package dependencies may have changed since the last time I ran pub upgrade.

pub upgrade now returns after about 5 minutes with:
Connection closed before full header was received

What version of the product are you using?
1.7.2 stable

On what operating system?
linux/windows: tried on both

What browser (if applicable)?
n/a

Please provide any additional information below.
I feel like I'm running into some upper bound of what pub can do before timing out. For example, when I start to remove some of these packages and reduce it down to lets say:
  polymer: '>=0.13.0+3'
  redstone: '>=0.5.15'
  redstone_mapper: '>=0.1.6'

Then the upgrade process will complete in at just under 5 minutes. But as I start adding packages back in, pub upgrade gives up with the connection closed timeout.

Any suggestions? Or is there a way to increase the timeout?

[lrhn]

Added Area-Pub, Triaged labels.

[nex3]

The best solution here at the moment is probably to run with --verbosity=solver, try to figure out where the conflicting version constraint is, and update your version constraints to avoid it (or submit pull requests to the dependencies if necessary).

---

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

[DartBot]

This comment was originally written by pruj...@gmail.com

---

I suppose that works, if I had any idea what I'm looking for. I suppose I could upgrade things manually with constraints in the pubspec until I bump into a problem.

[DartBot]

This comment was originally written by prujo...@gmail.com

---

I fixed it by manually upgrading the versions of the projects in the pubspec.yaml. I guess I was confused, because I thought 'pub upgrade' would do this for me implicitly.

[nex3]

It will, but it can get into a situation where the latest versions of every package don't work together and it's not clear which packages to roll back to what version to solve the issue.

[DartBot]

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