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
Part of #716, writing down so the details are not forgotten :)
Context
Embedded js-ipfs in Brave is using chrome-net, http-node, iso-url and some other tricks to convince @hapi/hapi HTTP server that it is running in Node.js 😬
ipfs/js-ipfs#2379 switched ipfs.add to ipfs._addAsyncIterator and it introduced regression in /api/v0/add HTTP API endpoint exposed by embedded js-ipfs in Brave.
Provisional fix
It seems old polyfills are no longer enough. Real fix requires more time to investigate, so for now we switched (2728436) to version of js-ipfs before ipfs/js-ipfs#2379.
How to reproduce
The problem is present only in HTTP API exposed by js-ipfs embedded in ipfs-companion running in Brave.
This switch to js-ipfs before PR-2379
ipfs/js-ipfs#2379 switched ipfs.add
to ipfs._addAsyncIterator and it broke /api/v0/add exposed by embedded
js-ipfs in Brave.
It seems old polyfills are no longer enough. Real fix requires more time
to investigate, so for now we switch to version before js-ipfs/PR-2379.
Used js-ipfs commit is from ipfs/js-ipfs#2304 before it
was rebased on top of master after PR-2379, making it the last safe
version.
Real fix will be tracked in
#757
This switches to async iterator version of ipfs.add
(introduced to js-ipfs in ipfs/js-ipfs#2517)
and ensures Node streams are replaced by deterministic version of readable-stream
Closes#757
* fix: /api/v0/add in Brave
This switches to async iterator version of ipfs.add
(introduced to js-ipfs in ipfs/js-ipfs#2517)
and ensures Node streams are replaced by deterministic version of readable-stream
Closes#757
* fix(cid): fast finish + allow osx to fail
Context
Embedded js-ipfs in Brave is using
chrome-net
,http-node
,iso-url
and some other tricks to convince@hapi/hapi
HTTP server that it is running in Node.js 😬ipfs/js-ipfs#2379 switched
ipfs.add
toipfs._addAsyncIterator
and it introduced regression in/api/v0/add
HTTP API endpoint exposed by embedded js-ipfs in Brave.Provisional fix
It seems old polyfills are no longer enough. Real fix requires more time to investigate, so for now we switched (2728436) to version of js-ipfs before ipfs/js-ipfs#2379.
How to reproduce
The problem is present only in HTTP API exposed by js-ipfs embedded in ipfs-companion running in Brave.
/api/v0/add
before ipfs/js-ipfs#2379 works fine:/api/v0/add
after ipfs/js-ipfs#2379 is missing response body in Brave:However, the same code (
/api/v0/add
after ipfs/js-ipfs#2379) running asjsipfs daemon
works fine!:The text was updated successfully, but these errors were encountered: