News for hackers. Stuff that matters.
Re:NPM proxy users receiving ERR 418 I'm a teapot by iends on Monday May 28, 2018 @11:29PM (#17176256)
2 hours after the incident was responded to by an npm employee and the status is still green: https://status.npmjs.org/

I love fake status pages!

Re:NPM proxy users receiving ERR 418 I'm a teapot by tannhaeuser on Tuesday May 29, 2018 @02:11AM (#17176858)
The entire traffic light metaphor of status pages and dashboards is questionable IMHO.
Re:NPM proxy users receiving ERR 418 I'm a teapot by unixhero on Tuesday May 29, 2018 @02:14AM (#17176869)
Ahh. The RAG status.

Professional truth-massaging

Re:NPM proxy users receiving ERR 418 I'm a teapot by wxuan on Monday May 28, 2018 @11:58PM (#17176373)
Overall, the system is up and running. I believe, the issue only affects a subset of users behind proxies.
Re:NPM proxy users receiving ERR 418 I'm a teapot by sitepodmatt on Tuesday May 29, 2018 @02:19AM (#17176882)
This is why I make clients drop/replace SaaSs. When SaaS don't update status page, or in a transparent and prompt way, because it's not 100% outage it rages me, especially if the reports are found elsewhere - twitter/reddit/hn.
Re:NPM proxy users receiving ERR 418 I'm a teapot by mattmanser on Tuesday May 29, 2018 @04:10AM (#17177264)
You force your clients to do things for trivial reasons that send you info a rage?
Re:NPM proxy users receiving ERR 418 I'm a teapot by sitepodmatt on Tuesday May 29, 2018 @06:40AM (#17177924)
I don't consider a non working status page trivial. Yes, if a SaaSs send me into a rage then there probably dozens of red flags already, yes I will work with clients to drop or replace such SaaS with one that can communicate, absolutely as it usually falls under my devop remit. This doesn't apply to npm as not a paid Iaas/SaaS, but more to point out the number of shit SaaS that don't manage their status updates probably. Imgix in the past for example, Linode when Ddos - absolutely shambolic communication, and so on
Re:NPM proxy users receiving ERR 418 I'm a teapot by nonconvergent on Tuesday May 29, 2018 @08:45AM (#17178596)
Wouldn't that be more of an issue of not having an SLA between SaaS and client?

If the silly non-automated dashboard is part of the SLA, then it costs someone money/liability/trust to not maintain it, otherwise "who cares as long the issue gets resolved, people who care about the issue are tracking the bug report?"

Re:NPM proxy users receiving ERR 418 I'm a teapot by abritinthebay on Tuesday May 29, 2018 @11:48AM (#17180207)
Except this IS a working status page.
Re:NPM proxy users receiving ERR 418 I'm a teapot by sitepodmatt on Tuesday May 29, 2018 @11:52AM (#17180240)
I wasn't curl'ing and greping for 200... I think that was obvious. Things aren't working for a number of users, what's going on, if I found out here or twitter first then you've failed. At least tell me via your status page you're aware of reports (you can even use the bullshit phrase - a 'minority of our users') and investigating... Operating a status page ain't rocket science although hmmm...
Re:NPM proxy users receiving ERR 418 I'm a teapot by iends on Tuesday May 29, 2018 @12:39AM (#17176543)
This is exactly what a status page should communicate.
Re:NPM proxy users receiving ERR 418 I'm a teapot by gpvos on Tuesday May 29, 2018 @01:16AM (#17176684)
Then put it on yellow or something.
Re:NPM proxy users receiving ERR 418 I'm a teapot by TeMPOraL on Tuesday May 29, 2018 @05:15AM (#17177597)
And ruin the marketing value of long history of status page showing green?

I feel some companies have the following meaning for the lights: yellow is when servers are literally on fire. Red is when the CEO is bleeding out somewhere on the floor, and the Feds are about to bust in and close the shop.

Re:NPM proxy users receiving ERR 418 I'm a teapot by ReidZB on Tuesday May 29, 2018 @11:25AM (#17179978)
AWS certainly operates that way, but even with a third level: green check mark with an info note box. I think I've only seen a "red" AWS status once or twice in the past few years.

Before AWS updated their status page to be a little more usable, I used a Chrome extension to remove green status services from the page. Funny enough, that extension also incremented every status (info check box became warning, warning became red), which was far more accurate in my experience.

Re:NPM proxy users receiving ERR 418 I'm a teapot by noir_lord on Tuesday May 29, 2018 @12:33PM (#17180677)
For red can we just call that a Cambridge Analytica?
Re:NPM proxy users receiving ERR 418 I'm a teapot by abritinthebay on Tuesday May 29, 2018 @11:50AM (#17180226)
Why? It appears to affect a tiny subset of a tiny subset of users.

If it’s not significant (and it’s not) then it shouldn’t change to a medium grade outage status (amber).

At best a notes portion of a status page could mention it.

Re:NPM proxy users receiving ERR 418 I'm a teapot by jwandborg on Tuesday May 29, 2018 @03:38AM (#17177157)
The status page is telling the truth if this is a client side issue.
Re:NPM proxy users receiving ERR 418 I'm a teapot by codefined on Tuesday May 29, 2018 @08:48AM (#17178621)
Yes, that status page is only for the registry.

This error was in how clients were appending ports to the HOST header.

Re:NPM proxy users receiving ERR 418 I'm a teapot by iends on Tuesday May 29, 2018 @08:54AM (#17178669)
This seems like playing semantics rather than focusing on what your customers care about...especially since the issue was fixed on the server.
Re:NPM proxy users receiving ERR 418 I'm a teapot by askmike on Tuesday May 29, 2018 @09:22AM (#17178883)
The status page doesn't display what customers care about. It displays whether the servers are up and reachable. If this effected everyone I see your point, but it didn't. Note that most NPM "customers" don't pay a dime.
Re:NPM proxy users receiving ERR 418 I'm a teapot by ricardobeat on Tuesday May 29, 2018 @01:29PM (#17181210)
First, the HTTP spec _mandates_ that a port number be appended when it is not the default, so a server has to accept it. Not a client issue at all. It was fixed on their service, not the clients.

Second, the service should respond with 400, not a funny 418 when it fails to parse the host field. This is also a bug on their end.

Finally, where does payment come into play? Does anybody expect bugs in homebrew / yum / aptitude / rubygems to go unfixed because those are not paid services?

Re:NPM proxy users receiving ERR 418 I'm a teapot by askmike on Tuesday May 29, 2018 @01:44PM (#17181348)
> Finally, where does payment come into play?

Merely commenting on the word customers: npm has few customers but a lot of users.

> Second, the service should respond with 400, not a funny 418 when it fails to parse the host field. This is also a bug on their end.

Is it a bug that on error youtube serves a 200OK page that says that "A team of highly trained monkeys has been dispatched" when their is an actual error? [EDIT: they are since returning 500 errors now, not 200 anymore, though they did do this in the past]. Note that 418 is an actual HTTP status code, for all we know the server was actually a tea pot . If this is the case is it not a bug anymore?

> First, the HTTP spec _mandates_ that a port number be appended when it is not the default, so a server has to accept it. Not a client issue at all. It was fixed on their service, not the clients.

This has little to do with the status page. Yes it's not formal against the HTTP spec if NPM does this but if you want to cover that you need tests of the sort that will validate output against a spec, NOT a status page that is meant for an entirely different purpose (to indicate whether your service is down or not).

Re:NPM proxy users receiving ERR 418 I'm a teapot by iends on Tuesday May 29, 2018 @04:28PM (#17182671)
The status page should be used for conveying more than just "whether the servers are up and reachable" and it's obvious that npm thinks so too. At the top of their page they list an issue about certain packages that "are currently unable to be viewed or installed."

If you're using your status page just to talk about sever availability and not about all types of service interruptions then you're not taking advantage of arguably the most important communication channel your customers care about.

In the end, you'll break their trust and you'll have to work impossibly hard to get it back.