{"version":"2.1.239","anchor":"empty-api-streams-get-their-own-error","canonical_anchor":"empty-api-streams-get-their-own-error","heading":"Empty API streams get their own error","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/empty-api-streams-get-their-own-error","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Empty API streams get their own error\n\nA stream that ends with no events now reports that specifically rather than a vague error.\n\n**What**\n\nA response stream that closes without delivering a single event now fails with a specific error, `StreamNoEventsError`, reading \"Stream ended without receiving any events\", rather than surfacing as generic stream trouble.\n\n**Details**\n\n- Unconditional; applies to any API stream.\n\n**Evidence**\n\n`Stream ended without receiving any events`\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}