fix: call await body.text() to avoid undici SocketError: other side closed error #337
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR solves the following error that occurs intermittently (but frequently).
There is a massive Undici issue thread thats related nodejs/undici#583 with an unsatisfactory result that concludes that you need to call
await body.text();
to avoid the issue which is what this PR does at the expense of essentially buffering up the fetch body before chunking it up again and streaming it as usual.This is one (sub optimal) way to fix the issue but it does seem reliable. Perhaps there are better ways to fix it? @trygve-lie