Great point; it's always the unlogged layer. In my experience, the seed bites most often (first thing to break on a re-run, one-line fix), but environment drift is the more expensive one, silent and delayed, showing up on someone else's machine or next month's CI instead of your second run. That's exactly why the tool checks statically instead of trusting a re-run to reveal it. Do you pin the full transitive tree + base-image digest, or stop at top-level pins?
Kartik N V J K
AI Developer | Making AI reliable, trustworthy & accessible to everyone | Active community contributor
The "I re-ran my own script and couldn't reproduce it either" moment is the one that converts people to pinning everything, because it proves the code was never the whole story. Usually it's the unlogged stuff: an unset seed, nondeterministic data ordering, or a library version that moved under you. Of your six lines, which bites most often in practice, the seed or the environment drift?