chore(docker): the two review items of #822

A comment says why the wait after the kill keeps its 2>/dev/null (bash 3.2
prints a Terminated job line there, bash 5.2 does not, so CI would not
notice its removal), and the two probe tests use the file's own imports.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Codeman maintainer committed 2026-11-20 04:03:18 +01:00
1 parent 507116f019
commit 6a5b818f65
2 files changed
+4 -4

No files matched your search

+2
View File
@@ -168,6 +168,8 @@ port_answers() {
while kill -0 "$pid" 2>/dev/null; do
if ((tries >= 20)); then
kill "$pid" 2>/dev/null
# The 2>/dev/null keeps bash 3.2 from printing a "Terminated" job line on
# the first-run path; bash 5.2 prints nothing without it, so CI won't notice.
wait "$pid" 2>/dev/null
return 1
fi