Our builders build a debian package 4 times (not using the provided builder because we need it to follow FHS, master:i386, stable:i386, master:amd64, stable:amd64) and every time in the last few days we hit the 3rd build we get an error (which is ironic because the status is always 200 OK) because of rate limiting (I can only assume, but even then it’s just a guess) but your rate limiting kicks in (if it is that) and we get:
npm ERR! registry error parsing json npm ERR! SyntaxError: Unexpected token < npm ERR! npm ERR! <?xml version="1.0" encoding="utf-8"?> npm ERR! <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" npm ERR! "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> npm ERR! <html> npm ERR! <head> npm ERR! <title>200 OK</title> npm ERR! </head> npm ERR! <body> npm ERR! <h1>Error 200 OK</h1> npm ERR! <p>OK</p> npm ERR! <h3>Guru Meditation:</h3> npm ERR! <p>XID: 724789816</p> npm ERR! <hr> npm ERR! <p>Varnish cache server</p> npm ERR! </body> npm ERR! </html>
I could be wrong here and this could be an actual npm.org error but considering it always happens when it is installing an atom package, I can only assume that it’s an atom.io error. I am fine with the error and how it crashes, I am not, however, fine with the status 200 Can you please fix that bad status code?