NPM: 429 Too Many Requests • Hacker News Board

Re: NPM: 429 Too Many Requests

#21

Post by vsareto » Mon, Feb 17, 2020, 1:20 PM UTC

matsemann wrote: post #14

lm28469 wrote: post #10

Earlier quoted context omitted.

Some people getting in the workforce in the last few years have troubles making the distinction between work and play contexts. It's extremely visible on github, slack, &c. which are more and more looking like discord / reddit (gifs, memes, random jokes in the middle of serious discussions)

You say it like it's a bad thing? It's possible to be both professional and have some fun (not talking about the linked GH).

It should get quarantined into a different channel or server. If not, and you don't like a bunch of shitty meme spam, it's difficult to filter out while keeping your coworkers unblocked.

Re: NPM: 429 Too Many Requests

#22

Post by avinassh » Mon, Feb 17, 2020, 1:20 PM UTC

zaphar wrote: post #12

gmemstr wrote: post #6

This seems to be slowly clearing up. Regardless, can we talk about the conduct in this GitHub thread? I know every community is different but is it common to have memes and jokes posted this quickly and often in a GitHub issue? It makes it really hard to follow and discourages genuinely useful discussion of workarounds or progress.

I think this is partly a result of two things. 1. GitHub presents an interface that encourages Reddit style behaviour. 2. NPM outages are essentially a meme in themselves at this point. Both of them together create a perfect storm.

I don't work with JS or related ecosystems, but how common are NPM outages?

Re: NPM: 429 Too Many Requests

#23

Post by empath75 » Mon, Feb 17, 2020, 1:20 PM UTC

Philomath wrote: post #8

If this is causing production CI/CD pipelines to fail, this might be a bigger issue than it seems. Has this already happened in the past with npm?

You should always run a local mirror/cache of artifact repositories if you’re doing builds at any kind of scale at all.

Re: NPM: 429 Too Many Requests

#24

Post by sethammons » Mon, Feb 17, 2020, 1:21 PM UTC

This is one of the reasons why, in Go, my team vendors our dependencies. For any service that seeks stability and the ability to deploy any time, removing networked build dependencies is important.

Re: NPM: 429 Too Many Requests

#25

Post by scoutt » Mon, Feb 17, 2020, 1:21 PM UTC

matsemann wrote: post #14

lm28469 wrote: post #10

Earlier quoted context omitted.

Some people getting in the workforce in the last few years have troubles making the distinction between work and play contexts. It's extremely visible on github, slack, &c. which are more and more looking like discord / reddit (gifs, memes, random jokes in the middle of serious discussions)

You say it like it's a bad thing? It's possible to be both professional and have some fun (not talking about the linked GH).

I think it's fine to joke, but even if I try, I really have to make an effort to not get angry when someone at work or an external replies with something written like this:

"yeah, u know, i could do it better, lol".

Edit: to add that I agree with the idea there is a problem with people making a distinction between work and play contexts.

Re: NPM: 429 Too Many Requests

#26

Post by avereveard » Mon, Feb 17, 2020, 1:22 PM UTC

lm28469 wrote: post #10

gmemstr wrote: post #6

This seems to be slowly clearing up. Regardless, can we talk about the conduct in this GitHub thread? I know every community is different but is it common to have memes and jokes posted this quickly and often in a GitHub issue? It makes it really hard to follow and discourages genuinely useful discussion of workarounds or progress.

Some people getting in the workforce in the last few years have troubles making the distinction between work and play contexts. It's extremely visible on github, slack, &c. which are more and more looking like discord / reddit (gifs, memes, random jokes in the middle of serious discussions)

there's also quite some personal contributors in github, for these it's not a work context to begin with

Re: NPM: 429 Too Many Requests

#27

Post by hans1729 » Mon, Feb 17, 2020, 1:22 PM UTC

matsemann wrote: post #14

lm28469 wrote: post #10

Earlier quoted context omitted.

Some people getting in the workforce in the last few years have troubles making the distinction between work and play contexts. It's extremely visible on github, slack, &c. which are more and more looking like discord / reddit (gifs, memes, random jokes in the middle of serious discussions)

You say it like it's a bad thing? It's possible to be both professional and have some fun (not talking about the linked GH).

Having fun is not whats discouraged.

Rather: if I'm looking for the solution for some problem, I don't want to scroll through memes, because I want to be productive, getting things done. Spam/fog in the resolution-thread obviously doesn't help with that; the opposite is the case.

Re: NPM: 429 Too Many Requests

#28

Post by VBprogrammer » Mon, Feb 17, 2020, 1:23 PM UTC

gmemstr wrote: post #11

Philomath wrote: post #8

If this is causing production CI/CD pipelines to fail, this might be a bigger issue than it seems. Has this already happened in the past with npm?

> if It 100% is, unfortunately. I don't recall this happening in recent history, but it has been the case that 3rd party services have broken CI/CD pipelines and production pushes (e.g pip broke a few weeks ago, and their own pipeline for deploying changes was blocked by the bug).

It's very easy for these kind of dependancies to creep into the build process. If the worst case cost of not being able to create a new build out-weights the cost of rearchitecting your build process then it's something you should seriously consider. On the plus side it also brings additional benefits like faster builds and resilience against packages being unilaterally removed.

Re: NPM: 429 Too Many Requests

#29

Post by merb » Mon, Feb 17, 2020, 1:23 PM UTC

imtringued wrote: post #18

Honestly, don't depend on central repositories for daily availability. Especially if you are doing CI that redownloads everything from scratch. Use something like artifactory to cache the repository you are using: https://www.jfrog.com/confluence/display/RTF/npm+Registry

there is also sonatype nexus: https://www.sonatype.com/product-nexus-repository

Re: NPM: 429 Too Many Requests

#30

Post by aequitas » Mon, Feb 17, 2020, 1:23 PM UTC

gmemstr wrote: post #6

This seems to be slowly clearing up. Regardless, can we talk about the conduct in this GitHub thread? I know every community is different but is it common to have memes and jokes posted this quickly and often in a GitHub issue? It makes it really hard to follow and discourages genuinely useful discussion of workarounds or progress.

The countless +1 and "Same here" comments without additonal info are a huge problem as well on Github. A simple click on a +1 button would suffice instead of a full comment. It's especially irritating when you follow a lot of issues hoping to get notified when there is a resolution but instead you get spammed by people making these pointless comments.