Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bug(fetch): Reponse.text() hangs if you've cloned the response #520

Open
1 task done
Lioness100 opened this issue Nov 13, 2022 · 1 comment
Open
1 task done

bug(fetch): Reponse.text() hangs if you've cloned the response #520

Lioness100 opened this issue Nov 13, 2022 · 1 comment

Comments

@Lioness100
Copy link
Collaborator

Is there an existing issue for this?

  • I have searched the existing issues

Description of the bug

Basically just node-fetch/node-fetch#1131. The solutions that are offered are using highWaterMark, which might not be possible with cross-fetch, or "to resolve cloned response in parallel", which might not be applicable with cross-fetch? I don't know much about cross-fetch or the technicalities of fetching in general, so help would be appreciated.

Steps To Reproduce

See node-fetch/node-fetch#1131

Expected behavior

See node-fetch/node-fetch#1131

Screenshots

No response

Additional context

No response

@Lioness100 Lioness100 changed the title bug: bug(fetch): Reponse.text() hangs if you've cloned the response Nov 13, 2022
@kyranet
Copy link
Member

kyranet commented Nov 10, 2023

Considering we don't use node-fetch but rather globalThis.fetch, which is undici powered, is this issue still relevant today?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants