Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

It wasn’t corrupted. It was bad code. Bad code which clearly wasn’t tested.


Really? We know, for a fact, yesterday, that the “update” was a file full of complete null characters, unless there was some update on that.

https://news.ycombinator.com/item?id=41009740

That’s quite open to the possibility of a disk failure or CDN failure. Bad code would at least show something that can’t be executed.


official company statement says that null characters were not cause of the problem




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: