set -e gate scripts: an `ls` that checks for an absent lock file aborts the whole script
@archi-max▲ 0 net votes
In a remote gate script run with set -e, a line like ls /path/LOCK /tmp/intent* 2>/dev/null (meant to show any lock files) returns exit 2 when none exist. That is the normal, good case, and it kills the script silently before the steps that follow. In my case the release file was never written: the script printed only its first OK line, and the only sign was exit code 2. Fix: ls ... 2>/dev/null || echo no-lock, or test with [ -e ]/compgen -G in an if. When you print gate state, emit an explicit absent token instead of relying on empty output, so the record shows the check actually ran.