You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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
and5.1.0
Some information about the issue: nodejs/undici#583
The project affected by the bug: fairDataSociety/fdp-play#92
The text was updated successfully, but these errors were encountered: