Pub upgrade failing often -- 1.9.3

[DartBot]

Originally opened as dart-lang/sdk#23214

This issue was originally filed by [email protected]

---

What steps will reproduce the problem?

1. Any pub upgrade on an existing project

Pub upgrade failed, [69] Resolving dependencies...
Got socket error trying to find package XXXXX at https://pub.dartlang.org.

The actual package in the error varies. The pub upgrade fails almost all the time, but not always. Having local path dependencies seems to make the chances of failure higher, and commenting them out temporarily can sometimes buy a successful upgrade (but only sometimes).

My projects have all "any" (plus some local) dependencies and were resolving before upgrading to 1.9.3 without any problems.

What version of the product are you using?
1.9.3 Dart Editor

On what operating system?
Win x64

[DartBot]

<img src="https://avatars.githubusercontent.com/u/8631949?v=3" align="left" width="48" height="48"hspace="10"> Comment by floitschG

---

Added Area-Pub, Triaged labels.

[DartBot]

<img src="https://avatars.githubusercontent.com/u/188?v=3" align="left" width="48" height="48"hspace="10"> Comment by nex3

---

Can you include the output of running with "--verbose"?

This looks like a network error of some sort. If you're still seeing it, that suggests it's something to do with your local network rather than pub.dartlang.org itself. Do you have any unusual network configuration like proxies or firewalls?

---

Added NeedsInfo label.

[DartBot]

This comment was originally written by [email protected]

---

It cleared up after a couple of days, gradually. It'd be good if pub could give some kind of feedback in these situations to help understand what the issue is. Nothing unusual about the network configuration that I'm aware of.

[DartBot]

<img src="https://avatars.githubusercontent.com/u/188?v=3" align="left" width="48" height="48"hspace="10"> Comment by nex3

---

Unfortunately there's not much more pub can tell you about the failure than it already is. All it sees is the socket error... it has no insight into what the underlying cause is, so presenting the raw information is the best it can do.

---

Added CannotReproduce label.