Appearance family writes can time out and lose assignments under contention #552

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

A real-server adversarial round on 2026-09-30 against merged origin/dev (e96a8bf2a) sent 16 concurrent writes to distinct Appearance family/scheme assignments. The probe used a 10-second request timeout. Eight requests had no response before timeout; the final read returned 200 but ten requested family/scheme assignments were missing. The server process remained alive at the end of the round.

This happened during a broad API campaign on a busy shared build host, so the probe does not isolate whether load or write concurrency caused the loss. Please reproduce on an isolated host and preserve the expected no-loss check.

A real-server adversarial round on 2026-09-30 against merged `origin/dev` (`e96a8bf2a`) sent 16 concurrent writes to distinct Appearance family/scheme assignments. The probe used a 10-second request timeout. Eight requests had no response before timeout; the final read returned 200 but ten requested family/scheme assignments were missing. The server process remained alive at the end of the round. This happened during a broad API campaign on a busy shared build host, so the probe does not isolate whether load or write concurrency caused the loss. Please reproduce on an isolated host and preserve the expected no-loss check.
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#552
No description provided.