Clarify Gitea verification failure diagnostics
Verify and publish checkpoint container / container (push) Canceled after 0s
Verify and publish checkpoint container / container (push) Canceled after 0s
This commit is contained in:
1 parent
c414a03a19
commit
0681529e8e
6 files changed
+126
-25
No files matched your search
@@ -17,6 +17,17 @@ open mode gates.
|
||||
|
||||
## Current checkpoint and work
|
||||
|
||||
**Gitea verification diagnostics — 29 October. Partial.** The approved
|
||||
runner network configuration was already applied, and later runs reached the
|
||||
application and published images. Run #85 failed in administrator acceptance
|
||||
when a fetch threw before its response. Its logged 403 was the previous
|
||||
completed request, a possible expected denial, not proof of an authorization
|
||||
failure; the exception's cause was not recorded. Acceptance diagnostics now
|
||||
distinguish request exceptions from the last completed response and report only
|
||||
sanitized details; the security checks are unchanged. Two focused diagnostic
|
||||
cases pass. Run #86 was building its container at the last check; the updated
|
||||
diagnostics still need CI verification.
|
||||
|
||||
**Truthtrance ally funding — 29 October. Prototyped / Partial.**
|
||||
Supported quiet Basic Bidding and Shipment/Movement questions can bind a future
|
||||
funding update to the respondent's current mutual ally. Existing escrow alone
|
||||
|
||||
Reference in new issue
Block a user