ML researcher @kalomaze says a KV cache bug caused transformer inference routing errors that exposed model outputs to other users
The failure mode resembles OpenAI's 2023 routing errors
The failure mode resembles OpenAI's 2023 routing errors
The failure mode resembles OpenAI's 2023 routing errors
The failure mode resembles OpenAI's 2023 routing errors
The downside of serving batches of customers on the same device is that you're one indexing error away from accessing other's output tokens In the end, people will want private personal compute for inference. Lower latency and more power efficient. https://twitter.com/MoritzW42/status/2062930461802811720
OpenAI employees from 2023 know the pain of this. It’s not leaking customer data, but it’s likely there is some issue with inference - which looks like getting someone else’s response. https://twitter.com/MoritzW42/status/2062930461802811720
Incredible how often this happens even to "serious" labs Seen it with DeepSeek (long ago tbh, they're very good at cache now), Grok, and now Claude? https://twitter.com/MoritzW42/status/2062930461802811720
ahahaha oh man this is the scariest kind of kv cache bug https://twitter.com/moritzw42/status/2062930461802811720
Maybe they didn't tell it not to make any mistakes 🤷♀️ https://twitter.com/MoritzW42/status/2062930461802811720
Should I make http://willclaudequotareset.com? https://twitter.com/MoritzW42/status/2062930461802811720
@kalomaze dang cant believe mythos let this one slip through
Ask a question below.
Published answers will appear here.