Skip to content

Conversation

@josephjclark
Copy link
Collaborator

This fixes an issue in WCS which comes out of ensure-payload-size

Readable Stream is in flowing mode, data may have been lost. Trying to pause stream.

Claude suggests the problem is the destroy() call after the stream has finished processing. It took a bit of coerscion but I think it's the one before the throw that really does it - I think the throw is interrupting the destroy. Claude suggests the iterator loop in for/await will do any tidy up we need.

AI Usage

Please disclose how you've used AI in this work (it's cool, we just want to know!):

  • Code generation (copilot but not intellisense)
  • Learning or fact checking
  • Strategy / design
  • Optimisation / refactoring
  • Translation / spellchecking / doc gen
  • Other
  • I have not used AI

You can read more details in our Responsible AI Policy

@github-project-automation github-project-automation bot moved this to New Issues in v2 Jan 19, 2026
@josephjclark josephjclark merged commit 4e64191 into main Jan 19, 2026
8 checks passed
@github-project-automation github-project-automation bot moved this from New Issues to Done in v2 Jan 19, 2026
@josephjclark josephjclark deleted the dont-destroy-stream branch January 19, 2026 12:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

2 participants