TIMEOUT_SECONDS = 90 and the default of GiteaClient are in this file. Since 292a057 the Solution names the file next to the change.
This file only carries the version 0.60.1 (Version: patch). Since 292a057 the Solution says so.
The tests are here: ErrorTextTest checks Scenario#131.01 and #131.02. Since 292a057 the Solution names this file and its test class.
cc56fc4c58
PR document: reviews wait longer for a slow Gitea, and hs-review names the cause of a failure
Answer to the review of deb0b3f: Codex has no findings; the Jev hint on docs/werkrevisor.werkbaum is answered without a change, see the thread. Left to the human: the risky paths and the size.…
No change: the Werkbaum file is the plan, not the implementation. Its node tools/rotate-secret points to the code of this PR, tools/rotate-secret, tools/host_secret.py and `werkrevisor/secret…
bc4ed87e44
Review round 4: unreadable backups stop purge; fetch brings a missing old value into secrets.env; local errors exit with 2
Answer to the review of 4a7f720, fixed in deb0b3f:
- Merge conflict: rebased onto 0.59.1 of PR#127; the version stays 0.60.0.
- Codex finding on the exit code after six refused connections:…
Fixed in deb0b3f: retrying names the six refused connections and returns 2. test_an_unreachable_host_is_an_error_with_2 failed without the fix (1 != 2) and passes with it.
f2b69fd4f6
Review round 4: unreadable backups stop purge; fetch brings a missing old value into secrets.env; local errors exit with 2
ec02e8a240
Review round 1: Gitea probe checks the write scopes; purge only by backup names; unreadable configs are errors
Fixed in 855ff55, as in the same finding 6996 of werkrevisor: the marker comes only with the last edit, and a failed upload or edit deletes the comment again, so a retry is not refused.…
Fixed in 855ff55: the draft line and the warning of different commits count only as lines of the header, before the first ###. test_a_finding_that_quotes_the_draft_line_is_no_refusal.
Fixed in 855ff55: attach_draft holds a lock file next to the draft (fcntl.flock), so a second run of --attach for the same PR stops with a message. Two humans on two workstations remain…