Investigate Calendar Event from Log timeout under shared load

kayg commented

2026-09-27 17:18:35 +00:00

Owner

Observed behavior

A bounded adversarial API round on 2026-09-27 recorded Calendar Event from Log: NO RESPONSE (b'timed out') after the 30-second client timeout.

At the same time, the shared host was under concurrent job load. Routed Photos uploads took 5.2–10.9 seconds, and duplicate-account requests returned the expected 409 status in 5.4–5.5 seconds. The server had no reported 5xx response at this point.

Follow-up

Reproduce this request under quiet-host conditions. If it returns successfully when the host is quiet, classify the observation as shared-host load. If it still times out, trace the Calendar-to-Log write path and add a regression test.

The probe ran on job/flat-layout; the observed request is outside the flat-layout change.

## Observed behavior A bounded adversarial API round on 2026-09-27 recorded `Calendar Event from Log: NO RESPONSE (b'timed out')` after the 30-second client timeout. At the same time, the shared host was under concurrent job load. Routed Photos uploads took 5.2–10.9 seconds, and duplicate-account requests returned the expected 409 status in 5.4–5.5 seconds. The server had no reported 5xx response at this point. ## Follow-up Reproduce this request under quiet-host conditions. If it returns successfully when the host is quiet, classify the observation as shared-host load. If it still times out, trace the Calendar-to-Log write path and add a regression test. The probe ran on `job/flat-layout`; the observed request is outside the flat-layout change.

kayg referenced this issue

2026-09-27 17:28:10 +00:00

Flat Home layout: Notes/ flat (tasks and Daily notes included), attachments by type, no folder-derived meaning (DESIGN §40) #165

kayg referenced this issue

2026-09-27 21:10:55 +00:00

BUG: menus inside Settings/overlays have no blur (nested backdrop root); two rows highlighted #246

kayg referenced this issue

2026-09-27 22:14:07 +00:00

BUG: menus inside Settings/overlays have no blur (nested backdrop root); two rows highlighted #246

kayg commented

2026-09-27 22:45:31 +00:00

Author

Owner

Reproduced the Calendar Event-from-Log no-response during Forgejo #191's adversarial round on 2026-09-28: the request hit the probe's 30-second timeout while several concurrent jobs were building or probing on the shared host. The server remained alive, and later Calendar/Journal requests succeeded, mostly taking 7–15 seconds. This does not establish behavior on an idle host; recording it here as further loaded-host evidence for the requested quiet-host follow-up.

kayg referenced this issue

2026-09-27 23:12:19 +00:00

Block actions: hover controls, make-note (→), block reminders with quiet hours, phone capsule bar (DESIGN §42) #191

kayg commented

2026-09-30 22:48:56 +00:00

Author

Owner

The round-3 API-only adversarial run repeated this timeout: Calendar Event from Note returned 201 after 12.9 s, then Calendar Event from Log reached the probe's 30-second client timeout with no response. The server was still alive at the end of the round. Local load average during the round was 23.46 / 26.74 / 27.64, and many unrelated API responses were marked SLOW. This was one run only; I did not repeat the probe.

The round-3 API-only adversarial run repeated this timeout: `Calendar Event from Note` returned 201 after 12.9 s, then `Calendar Event from Log` reached the probe's 30-second client timeout with no response. The server was still alive at the end of the round. Local load average during the round was 23.46 / 26.74 / 27.64, and many unrelated API responses were marked SLOW. This was one run only; I did not repeat the probe.

kayg referenced this issue

2026-09-30 23:05:18 +00:00

Log attachments: deleted file still shown, attachments not live, batch send not live, Log order, raw camera names #427

kayg commented

2026-10-02 17:35:52 +00:00

Author

Owner

Partial duplicate symptom: #205, #264, #265, #267 and #269 also report Calendar Event-from-Log creation timing out at the 30-second client deadline during shared-host adversarial runs. Their other route and data findings differ. Recommend keeping #250 as the focused issue for this operation and linking the repeated timeout evidence from those runs; retain each report's unrelated findings.