Signals judge 25 items every 5 minutes instead of going straight through the queue #260

Closed
opened 2026-10-16 11:14:55 -07:00 by rays · 1 comment
Owner

Found 2026-10-16 watching the re-judge after #259: each pass had entries=25 and the next came 5 minutes later. unjudged() limits rows, one per item per Signal, to 50; with two Signals that is 25 items. The pass decides whether more is waiting by comparing the number of items, 25, with 50, so it always thinks the queue is empty and sleeps until the next wake or 5 minutes.

Found 2026-10-16 watching the re-judge after #259: each pass had entries=25 and the next came 5 minutes later. unjudged() limits rows, one per item per Signal, to 50; with two Signals that is 25 items. The pass decides whether more is waiting by comparing the number of items, 25, with 50, so it always thinks the queue is empty and sleeps until the next wake or 5 minutes.
rays added the bug label 2026-10-16 11:14:55 -07:00
Author
Owner

Fixed in 9e5dcbb, deployed: the re-judge then went straight through, AI Development settling at 48 items over the 30 days and Apple 272, with no refusals.

Fixed in 9e5dcbb, deployed: the re-judge then went straight through, AI Development settling at 48 items over the 30 days and Apple 272, with no refusals.
rays closed this issue 2026-10-16 11:27:08 -07:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: rays/ipx#260