Make delivery and integration failures explicit
Persist reminder presentations and retry state, atomically complete collapsed deliveries, fall back across away reaches, and block permanent failures visibly (V-715, V-678). Fail closed when enabled integrations lack credentials and keep remote arms explicitly dark (V-691). Give mavweb one sanitized, request-correlated error contract (V-689). Owner explicitly requested direct commits to master.
This commit is contained in:
@@ -75,8 +75,13 @@ func TestEventsPageReportsAReadFailure(t *testing.T) {
|
||||
t.Fatalf("status = %d, want 200 with the error rendered", w.Code)
|
||||
}
|
||||
body := w.Body.String()
|
||||
if !strings.Contains(body, "journal unavailable") || !strings.Contains(body, "core is down") {
|
||||
t.Errorf("page did not report the read failure: %s", body)
|
||||
if !strings.Contains(body, "intake journal unavailable") ||
|
||||
!strings.Contains(body, string(problemCoreReadFailed)) ||
|
||||
!strings.Contains(body, "request ") {
|
||||
t.Errorf("page did not report a traceable, sanitized read failure: %s", body)
|
||||
}
|
||||
if strings.Contains(body, "core is down") {
|
||||
t.Errorf("page disclosed the internal read error: %s", body)
|
||||
}
|
||||
if strings.Contains(body, "nothing has arrived yet") {
|
||||
t.Error("a failed read rendered as an empty journal")
|
||||
|
||||
Reference in New Issue
Block a user