I suspect that Google is working on improving their models for coding behind the scenes. Hopefully they release something soon to compete with Codex and CC. To be candid, I use CC, but have not tried out Codex.
Yeah, extremely misleading title even if it is technically true semantically. The phrasing gives the impression that a bug was found in `lean-zip` as part of the proof boundary when it was part of the unverified archive-handling code.
The archive-handling code was in lean-zip, it just seems the verifiers forgot to write proofs for it (still a bug).
Thats not the main finding of the article however. The main bug found was actually in the lean runtime, affecting all proofs using scalar arrays where the size of the array is not bounded.
Altman needs to sell off that house and move to an anonymized address. I don’t see these attacks letting up any time soon. Two targeted attacks in three days is nuts.
Having lived on military bases that is a false sense of security. That's one gate guard away from a problem. They make mistakes. There are far better options he can afford.
Honestly that was the cherry on top for me -- the employee confident enough to just decide "this is my work computer, I need it to do work, I can't do work with my hands being irritated, so I will sand down the edge." Pure gold.
reply