Visual Studio Code 1.7 overloaded npmjs.org, release reverted

Re:Visual Studio Code 1.7 overloaded npmjs.org, release reve... by BenjaminCoe on Wednesday November 02, 2016 @10:44PM (#12861232)

As one of the folks on the front-lines helping patch this, I certainly have no hard feelings; and I'm excited to be able to support this feature properly

... also ... not going to lie, this was the first time we've gotten to test several of the checks and balances we have in the npm registry which I was jazzed about :)

[ Parent | on HN ]

Re:Visual Studio Code 1.7 overloaded npmjs.org, release reve... by raisedadead on Thursday November 03, 2016 @02:01AM (#12861898)

Thanks, Benjamin, Laurie and everyone else for mitigating this, it feels great to know when the community chimes in together for such highly unanticipated scenarios.

On that note, however, respectfully I believe that features which have the potential of hitting the registry so bad should first be beta tested on a private registry and moved on to the high traffic serving CDNs of npm.

And 10% of the daily traffic is from India??? Whoa, every day is a school day.

[ Parent | on HN ]

Re:Visual Studio Code 1.7 overloaded npmjs.org, release reve... by poizan42 on Thursday November 03, 2016 @06:43AM (#12862796)

> And 10% of the daily traffic is from India??? Whoa, every day is a school day.

Well, 17% of the world's population lives in India, so doesn't seems surprising.

[ Parent | on HN ]

Re:Visual Studio Code 1.7 overloaded npmjs.org, release reve... by raisedadead on Friday November 04, 2016 @02:12PM (#12874642)

lol. agreed.

[ Parent | on HN ]