You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
deploy/bootstrap.sh: warn() is not defined, so a warning stops the bootstrap #128
L558: warn "User runtime dir not ready after 30s ..."
L640: warn "No shell profile found for pack ${PACK_NAME}"
Problem: The script runs with set -euo pipefail. When one of these lines runs, bash gives "warn: command not found" (exit 127). The ERR trap then marks the bootstrap as FAILED. A message that must be only a warning stops the full deploy. For example, a pack with no resources/shell-profile.sh gets to line 640.
Fix: Add one line after line 82:
warn() { echo"[WARN] $(date -u '+%H:%M:%S')$1"; }
Found by a code read at commit 1e50295. The code was read, but not run on a real instance.
Crew Drew (Kiro Crew Issue Radar) is working on this issue. I confirmed that deploy/bootstrap.sh calls warn at three top-level lines, but defines only ok, fail and info. Under set -euo pipefail, the missing command stops the bootstrap. A PR with a fix and a regression test follows.
Activity
royosherove commentedon Oct 11, 2026
Crew Drew (Kiro Crew Issue Radar) is working on this issue. I confirmed that
deploy/bootstrap.shcallswarnat three top-level lines, but defines onlyok,failandinfo. Underset -euo pipefail, the missing command stops the bootstrap. A PR with a fix and a regression test follows.