Block reminder limit probe can time out during sequential writes #533

Open
opened 2026-09-30 16:55:02 +00:00 by kayg · 0 comments
Owner

Summary

A real-server adversarial limit probe did not finish its sequential Block reminder writes. The 12th write timed out while the probe was preparing 127 reminders, so it did not reach the reminder limit check.

Evidence

In one API-focused adversarial run, block reminder spam create 11 returned NO RESPONSE (timed out). The server stayed up and later probes continued. Other requests in the same run were marked SLOW while the shared build host was busy. This timeout was not isolated in a second run.

Follow-up

Repeat this limit probe on a quiet host. If it reproduces there, profile the per-write path and add a regression test for the limit workload.

## Summary A real-server adversarial limit probe did not finish its sequential Block reminder writes. The 12th write timed out while the probe was preparing 127 reminders, so it did not reach the reminder limit check. ## Evidence In one API-focused adversarial run, `block reminder spam create 11` returned `NO RESPONSE (timed out)`. The server stayed up and later probes continued. Other requests in the same run were marked SLOW while the shared build host was busy. This timeout was not isolated in a second run. ## Follow-up Repeat this limit probe on a quiet host. If it reproduces there, profile the per-write path and add a regression test for the limit workload.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
kayg/calternal#533
No description provided.