4 ms·
"If I understand correctly, " You don't. You are missing the part where the LLM had a token which blocked access as expected. Then the LLM searched the sourc
by hunterpayne 6mo ago
"If I understand correctly, "
You don't. You are missing the part where the LLM had a token which blocked access as expected. Then the LLM searched the source base, found a different token with the delete privs and then used that.
PS That warning happens in staging envs too, the LLM doesn't know which env is which by design.
- throwdbaaway 6mo agoHuh that's not what I gathered from the tweet at all. If I am going to write a five why's analysis, the immediate cause is the LLM wrongly decided to delete a volume, while the root cause is the bad design to co-locate staging and production data in the same volume. The writing was quite vague though, let's wait for a response from railway.