runpod: try multiple log routes (the tail= param returned HTTP 400)
Live run showed get_pod_logs hitting HTTP 400 on {rest}/pods/{id}/logs?tail=N, so a
failed boot fell back to the console link with no output. Now tries the plausible
routes in order (no params, ?limit=, containerLogs) and keeps the first that
answers, reporting the collected errors otherwise. The console deep-link remains
the always-available path.
Co-Authored-By:
Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01R6iugoNeEgt9PkajKrFyq4
Showing
Please
register
or
sign in
to comment