Add demand and cancellation semantics #16

Closed
opened 2026-10-16 10:12:47 +00:00 by mmacia · 0 comments
Owner

Objective

Bound item delivery and define cancellation, failure, and cleanup behavior for event streams.

Scope

Add a demand-driven single-consumer producer with one-item and max_queue_bytes bounds. Handle consumer cancellation, downstream exceptions, consumer-process death, parser errors, and temporary resource cleanup.

Acceptance Criteria

  • Pending events never exceed the configured byte budget.
  • Parser work stops promptly when demand is absent or the consumer cancels.
  • Parser errors are delivered once and terminate the stream.
  • Downstream failures and owner death release resources.
  • Read-ahead and cancellation behavior are covered by tests.
## Objective Bound item delivery and define cancellation, failure, and cleanup behavior for event streams. ## Scope Add a demand-driven single-consumer producer with one-item and `max_queue_bytes` bounds. Handle consumer cancellation, downstream exceptions, consumer-process death, parser errors, and temporary resource cleanup. ## Acceptance Criteria - Pending events never exceed the configured byte budget. - Parser work stops promptly when demand is absent or the consumer cancels. - Parser errors are delivered once and terminate the stream. - Downstream failures and owner death release resources. - Read-ahead and cancellation behavior are covered by tests.
mmacia self-assigned this 2026-10-16 10:12:47 +00:00
Sign in to join this conversation.
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: mmacia/feed_reader#16