Live data from Hacker News

NPM: 429 Too Many Requests

github.com

161–170 of 171 posts

Re: NPM: 429 Too Many Requests

#161
post #136

Earlier quoted context omitted.

How?

It helps focus the culture on the business over other social queues and aspects, it removes the anxiety that different social groups will have with that workplace. https://hackernoon.com/for-inclusive-culture-maybe-less-is-m...

If that makes the office more diverse, than the real issue is in the hiring bias, not in how you dress. For sure if you only hire people like you, which can happen both in a business environment or a social one, you will have an office less diverse, that's by definition.

I disagree entirely that we can't be social with people different as us. I also disagree that business shouldn't be social, but that's mostly an opinion.

Re: NPM: 429 Too Many Requests

#162

Earlier quoted context omitted.

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

It's not about employment status. Injecting noise into a channel that is currently being used to diagnose a severe bug affecting many people disrespects the time of those working to fix the issue. Other, more appropriate venues are available for people who want to blow off some steam.

so who died and made you king of npm issues?

Re: NPM: 429 Too Many Requests

#163

Earlier quoted context omitted.

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).

The problem, specifically, is that folks use humor to mask the fact that they don't know or understand what's going on.

Do the jokes count towards the 10X ?

Re: NPM: 429 Too Many Requests

#164
post #52

Earlier quoted context omitted.

> vendors our dependencies Is that like a local cache?

Vendoring is checking in your dependencies with the source. You can def consider that a local cache. The next step up is to run your own proxy server (pretty much a package server / mirror). Next is to use a service like artifacory that does similar.

We should call it a backup. Calling it a cache puts people in mind of size/hit ratio tradeoffs; what's needed is zero tolerance for loss of mission critical code.

Re: NPM: 429 Too Many Requests

#165
Here's an explanation from CloudFlare as to the root cause. [0]

> I am the engineering manager for the DDoS protection team and this morning at 11:06 UTC we tweaked a rule that affected one of our signals. The signal relates to the HTTP referer header, and we have a piece of code that looks at invalid referer headers. In this case we tweaked it to include not just "obvious garbage" but "anything that does not conform to the HTTP specification"... i.e. is the referer a URI? If not then it contributes to knowledge about bad traffic.

> So... why did this impact npmjs.org? It turns out that a lot of NPM traffic sends the referer as "install" which is invalid according to the HTTP specification. As NPM is also a heavily trafficked site this resulted in the DDoS systems picking this up and treating the traffic as a HTTP flood and determining that a rate-limit should be applied.

> When we noticed that NPM was seeing an increase in HTTP 429s (as seen on Twitter) we contacted NPM and started an internal investigation. As soon as we identified the root cause we reverted the change, which was at 13:00 UTC.

> We'll note that NPM and 1 other site use the referer for purposes outside the HTTP spec and we'll update our systems to ensure that this does not happen again. Additionally we'll improve our monitoring around changes of this nature so that we can discover impact sooner and roll back automatically.

[0] https://github.com/npm/cli/issues/836#issuecomment-587019096

Re: NPM: 429 Too Many Requests

#166
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 it's just that writing is seen as the primary mean of communication.

if something goes bad at work, someone (orally) always makes a joke to defuse the situation. This is the same thing happening here.

Re: NPM: 429 Too Many Requests

#167
post #44
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)

In my observation, this demographic is most densely concentrated in the JavaScript community. Not sure what that says about the language itself, but there’s definitely a glut of unprofessional JS devs out there.

Ooh back in my coding days it was PHP. And before that in my undergrad years was Vb6 ... which provided me and several other programmers with lots of frustration and consulting hours to fix the mess the owners' kid made while "programming" their new CRUD system.

There will always be a "cool new" language attracting newcomers and kids.

Re: NPM: 429 Too Many Requests

#168
post #155
post #115

Earlier quoted context omitted.

> conditioning by society. There is a limit. I'm sure you have one too if you really think about it. Is it tattoos all over the face? What about sandals? Or shorts? Or going bare-feet around the office. I don't know... It's about people giving me money for work. I don't feel like I can go to work dressed like any given Sunday.

Tattoos, someone's skin color or moles on people's facing at work doesn't bother me. Someone complaining about it would. Sandals/shorts/barefeet? It's winter here but in those brief moments of summer please do that. Wearing a three piece suit means you won't be able to work as hard during the heat wave.

Its an interesting discussion no doubt. Sometimes easier to have a "dress code/standard" in an office as it sets an (externalised) baseline.

I think the key thing is balance, not everyone is comfortable to wear a 3-piece suit but also few people are comfortable working with people who ave poor hygiene (e.g. dont shower after the lunchtime gym)

I think as long as someone is clean and presentable (context dependent) then there shouldnt be an issue.

Re: NPM: 429 Too Many Requests

#169
post #149
post #115

Earlier quoted context omitted.

> conditioning by society. There is a limit. I'm sure you have one too if you really think about it. Is it tattoos all over the face? What about sandals? Or shorts? Or going bare-feet around the office. I don't know... It's about people giving me money for work. I don't feel like I can go to work dressed like any given Sunday.

> I don't feel like I can go to work dressed like any given Sunday. And why not? As you said: they are giving us money... for work. Not for playing dressing up. If they expect otherwise, they should be clear about it up front and give a good reason to give up on that freedom while we work for them.

> And why not?

To me (and of course, it's a personal opinion) it shows that someone cares. It's like when you do your resume, you want it clean and presentable, without typos, to show that you care.

We all like good user interfaces and experiences in our programs. To me, the look is like the presentation layer of our own UX. Is it required for our work? Most of the times it is not, because our work depends on the logic layers, but it doesn't hurt to have a nice presentation layer.

And I'm not telling about going to work in a D&G suit.

EDIT: and I'm not telling that I would discriminate or think right away that someone doesn't care! I don't do that. My attitude about good looking is mono-directional; from me towards others.

Re: NPM: 429 Too Many Requests

#170
post #169
post #149

Earlier quoted context omitted.

> I don't feel like I can go to work dressed like any given Sunday. And why not? As you said: they are giving us money... for work. Not for playing dressing up. If they expect otherwise, they should be clear about it up front and give a good reason to give up on that freedom while we work for them.

> And why not? To me (and of course, it's a personal opinion) it shows that someone cares. It's like when you do your resume, you want it clean and presentable, without typos, to show that you care. We all like good user interfaces and experiences in our programs. To me, the look is like the presentation layer of our own UX. Is it required for our work? Most of the times it is not, because our work depends on the log…

Well, to me, people care by showing up on time.

They care by solving problems.

They care by being there when the team needs them.

They care by being honest, authentic and candid.

They care by making things simpler and smoother for themselves and those around them.

They care by striving to avoid office politics and back stabbing.

They care by being the team mate we all wish we had and strive to be.

They care making our common working space a place we are all eager to come to in the morning.

And I would pick a reliable, self-aware, well-rounded, face tattooed, green haired and barefoot colleague that's comfortable in their own skin any day, over any well-dressed, high maintenance, drama king / queen.

What's interesting though, is that even knowing, and thinking that, I couldn't help but be spontaneously biased towards he or she who made the so-called effort of dressing to look the part. And that's a problem.

Also, I am nowhere near being that ideal team mate. More like a work in progress >.<'

Post reply on HN