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

Node 18 error with beeDebug.getNodeAddresses() method #840

Closed
IgorShadurin opened this issue Mar 2, 2023 · 0 comments
Closed

Node 18 error with beeDebug.getNodeAddresses() method #840

IgorShadurin opened this issue Mar 2, 2023 · 0 comments

Comments

@IgorShadurin
Copy link
Contributor

IgorShadurin commented Mar 2, 2023

The error occurs when requesting from Node 18 to a bee node (1.11.1) using the beeDebug.getNodeAddresses() method.
It looks like the bee node sends a response with a missing header, or the response is processed incorrectly.

Also, the error disappears if you use the '--no-experimental-fetch' flag for Node 18. Because Node 18 introduced its own fetch, it seems that node-fetch uses this built-in fetch and therefore we get different behavior on different versions of the node.

Tried with bee-js 4.1.1 and 5.1.0

Some information about the issue: nodejs/undici#583
The project affected by the bug: fairDataSociety/fdp-play#92

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