Re:Cybersecurity researchers aren't happy about the guardrai...
by buildbot on Wednesday June 10, 2026 @09:43PM
(#48485281)
It honestly explains so many issues I have been having, as I used it primarily for ML research (on my personal account, doing things not related to my job I should note). It would literally typo package names and spend huge amounts of time failing to setup simple environments…then do stupid things like set the learning rate to 1e-7, and use the eval set as training data.
[ Parent
| on HN ]
Re:Cybersecurity researchers aren't happy about the guardrai...
by sterlind on Thursday June 11, 2026 @12:15AM
(#48486122)
just imagine if they made it sneaky. get things just subtly wrong enough that your training runs just never quite go as well as you think they should.
Re:Cybersecurity researchers aren't happy about the guardrai...
by peyton on Wednesday June 10, 2026 @10:56PM
(#48485729)
That’s insane. I hope they fix it.
Re:Cybersecurity researchers aren't happy about the guardrai...
by baq on Thursday June 11, 2026 @12:41AM
(#48486294)
Nothing to fix. This is working as designed.
Using codex for this use case is the fix.
Re:Cybersecurity researchers aren't happy about the guardrai...
by peyton on Friday June 12, 2026 @10:28PM
(#48512057)
They fixed it.
Re:Cybersecurity researchers aren't happy about the guardrai...
by notrealyme123 on Thursday June 11, 2026 @01:08AM
(#48486451)
It burned through all of my tokens in a very short time. I wonder if it their ML mitigations leads to model into deadlocks.