Investigate server abort during tag adversarial probe #560

Open
opened 2026-09-30 23:43:21 +00:00 by kayg · 0 comments
Owner

The time-boxed adversarial API round caused the server process to abort during tag-related probes. Before the failure, the probe reported mkdir storm: 200 created, 0 errors and rename race: 1 succeeded, 0 errors; then tag rename across sources received no response because the remote end closed the connection, and later requests received Connection refused. The harness reported the server process as Aborted. The run script cleaned its temporary directory on exit, so no server backtrace was retained. The root cause is not yet known. Please reproduce with server output retained and fix any crash found. This was observed in tests/adversarial/run.sh API round; the round was not repeated.

The time-boxed adversarial API round caused the server process to abort during tag-related probes. Before the failure, the probe reported `mkdir storm: 200 created, 0 errors` and `rename race: 1 succeeded, 0 errors`; then `tag rename across sources` received no response because the remote end closed the connection, and later requests received `Connection refused`. The harness reported the server process as `Aborted`. The run script cleaned its temporary directory on exit, so no server backtrace was retained. The root cause is not yet known. Please reproduce with server output retained and fix any crash found. This was observed in `tests/adversarial/run.sh` API round; the round was not repeated.
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#560
No description provided.