4 ms·
It wasn’t corrupted. It was bad code. Bad code which clearly wasn’t tested.
by qeternity 2y ago
It wasn’t corrupted. It was bad code. Bad code which clearly wasn’t tested.
- gjsman-1000 2y agoReally? 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 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.
- kiicia 2y agoofficial company statement says that null characters were not cause of the problem