On Fri, Jul 17, 2026 at 08:31:09PM -0700, Carlos Bilbao wrote: > Historically, one of the biggest criticisms of coco, especially around > device hardening, was that there were too many values that a > malicious/buggy device could misreport, making it a losing battle. That is > no longer the case with LLMs, and we have the advantage (and challenge) of > open-source dev, which allows us to receive many of these fixes "for free". > If others want to burn their tokens, let them :)
I have lots of tokens to burn :) So along those lines, any suggestions on how best to fuzz these code paths? Any workloads you all use for testing that I can take advantage of? thanks, greg k-h
