sotashimozono_obsidian-remo.../plugin/scripts
Souta c9d465d1d0 fix(test): integration sshd healthcheck (install iproute2 + dump logs on fail)
CI on PR #56 first run came back "sshd entered unhealthy state:
unhealthy". Two issues compounded:

1. The compose healthcheck shells `ss -lnt | grep ':22 '`, but
   `ss` isn't shipped in the minimal `ubuntu:22.04` base — the
   command exited non-zero every interval, so health stayed
   unhealthy past the retry budget. Adding `iproute2` to the
   apt-get install line gives us `ss` (~600 KB add).

2. When the start script gave up, it printed the timeout message
   and exited. We had no visibility into *why* sshd was unhealthy
   because docker logs weren't captured. Added `dumpContainerLogs`
   which calls `docker logs --tail 200` and `docker inspect
   --format '{{json .State.Health}}'` on every failure path so
   the next CI run (or local run) shows the actual sshd output
   and the healthcheck output history without manual digging.
2026-04-27 14:23:59 +09:00
..
build-server.mjs feat(plugin): auto-deploy obsidian-remote-server over SSH 2026-04-25 17:40:45 +09:00
bump-version.mjs chore(ci): version-check workflow + auto-release-on-merge + 0.3.0 bump 2026-04-27 11:00:04 +09:00
cdp-tail.mjs chore: monorepo restructure (plugin/ + server/ + proto/) 2026-04-25 10:52:52 +09:00
dev-install.mjs chore(security): replace personal info with generic placeholders (0.3.2) 2026-04-27 11:30:25 +09:00
start-test-sshd.mjs fix(test): integration sshd healthcheck (install iproute2 + dump logs on fail) 2026-04-27 14:23:59 +09:00
stop-test-sshd.mjs feat(test): docker sshd integration test environment (Tier B-1+B-3, 0.4.0) 2026-04-27 14:05:55 +09:00