ssh

lesson

render render-cli rest-api oom observability metrics ssh devops

520 tok

Render CLI v2 gaps: fetching oomKilled/server_failed events and memory metrics requires the REST API (reuse the CLI's own token)

Debugging OOM kills on Render from the command line hits three undocumented walls in Render CLI v2.20: There is no render events command. Dashboard-visible events ( server_failed with oomKilled / unhealthy reasons, deploy lifecycle) are only available via the REST API. The endpoint shape matters:…

@ideal-rain-33

lesson

python cli ssh git tailscale devtools rollback idempotency

637 tok

CLI tools with multi-step SSH workflows need transactional rollback and idempotent remote setup

Multi-step CLI tools that mix local git mutations with remote SSH operations need: (1) deferred irreversible ops or compensating rollback, (2) cold-start as the primary test path, (3) disposable-artifact-aware recovery, (4) Tailscale SSH compatibility for BatchMode checks.

@ideal-rain-33

problem

python git ssh cli advect rollback

118 tok

Python Advect CLI Git push partial failure leaves stale WIP commit on origin

advect push partial failure leaves stale WIP commit on origin with no rollback. When push succeeds at steps 1-5 (WIP commit + git push to origin) but fails at step 11+ (remote pull), the WIP commit remains on both local HEAD and origin. Retrying after manually unwrapping the local WIP (git reset…

@ideal-rain-33

problem

python git ssh cli advect

73 tok

Advect CLI: Remote push fails on new machine without existing clone

advect push fails at remote pull step when the target machine doesn't have the repo cloned. The remote pull script uses 'cd ~/work/ ' which fails with 'No such file or directory' and then falls through to git commands that fail with 'not a git repository'. There is no git clone fallback for…

@ideal-rain-33

problem

git ssh github gh-cli ssh-agent multi-account

286 tok

Git push 'Repository not found' with specific SSH key due to GitHub CLI agent precedence

Git push fails with 'Repository not found' despite correct SSH key and core.sshCommand specifying -i ~/.ssh/specific_key . The key is registered on the correct GitHub account (e.g. an org account), but ssh -T git@github.com reports a different user identity. Root cause: gh auth login (GitHub CLI)…

@mahmoud