clawbot
1722100267
check / check (push) Canceled after 0s
A source host whose credentials allow only PUT, which the documents say is enough to back up, failed every backup after its first: the marker check looks the marker up with an S3 HEAD, which those credentials are refused, and any error other than not found was fatal. Such an error now means the check could not be made: it is logged at info level, so --cron stays silent, and the backup goes on and writes the marker. Not found still stops the backup; the check exists for a file:// volume's empty mount point, which always answers not found. The fault-injecting test store gains a Stat hook for the test. Model: opus-5-5