Skip to content

docs: explain /tmp fallback in wait_readyz.sh #326

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
smaramwbc merged 2 commits into from
Aug 5, 2026
Merged

docs: explain /tmp fallback in wait_readyz.sh #326

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d6cbc44
docs: explain /tmp fallback in wait_readyz.sh
Vignesh-P-C Aug 5, 2026
809455b
Reword the timing-path comment and restore the trailing newline
smaramwbc Aug 5, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions scripts/wait_readyz.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,6 +16,9 @@ while (( SECONDS < deadline )); do
if [[ "$status" == "ready" ]]; then
elapsed=$((SECONDS - start))
echo "readyz: status=ready in ${elapsed}s"
# Timing lands in /tmp by default, which suits CI and Docker. Set
# STATEWAVE_COLD_TIMING_FILE to write elsewhere — e.g. where /tmp is
# missing or read-only, or to keep the value as a build artifact.
printf '%s\n' "$elapsed" > "${STATEWAVE_COLD_TIMING_FILE:-/tmp/statewave_cold_ready_seconds}"
exit 0
fi
Expand Down