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

fix: window.ipfs streaming #465

Merged
merged 1 commit into from
Apr 19, 2018
Merged

Conversation

alanshaw
Copy link
Member

There were two issues at play here:

  1. pull-postmsg-stream was using an old version of postmsg-rpc so wasn't getting the data from a message correctly and caused it to error when pulling over web extension port messaging
  2. Companion was actively disallowing bi-directional messages. For pull streams to work, messages need to flow in both directions

…kground, and upgrade ipfs-postmsg-proxy with fix for pull-postmsg-stream
Copy link
Member

@lidel lidel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

@alanshaw Does it solve issues raised by @olizilla ?
Should we ship a new beta with this fix?

@lidel lidel merged commit 5ffa6d8 into ipfs:master Apr 19, 2018
@olizilla
Copy link
Member

@lidel nope, this fixes it from the window.ipfs side, but there is still an issue with trying to pass streams and pull-streams to js-ipfs-api that @alanshaw is writing up an issue for now.

@alanshaw alanshaw deleted the fix/window.ipfs-streaming branch April 20, 2018 09:35
@alanshaw
Copy link
Member Author

Both js-ipfs-api and (to some extent) js-ipfs have bugs that prevent adding files with pull streams:

ipfs-inactive/js-ipfs-http-client#745
ipfs/js-ipfs#1317

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

Successfully merging this pull request may close these issues.

3 participants