-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Daemon dies with segfaults and Bus error: 10 (also unequal MACs earlier) #878
Comments
Ok a small dir of three empty .txt files works. Is it possible to serve a large JS bundle? Shouldn't I be able to do this from command line? Appreciate the help. |
Hi @JohnAllen, thanks for reporting this bug! I believe I know what is the bug, it is not related with adding files but with using WebRTC. I've been noticing that the WRTC module is now more unstable (than ever) and since we added WebRTC as a default transport in Node.js (and browser), it is crashing the jsipfs daemon. I believe I will disable WebRTC as default in Node.js in the next version, although it makes me incredibly sad as I wanted the users to be able to use it out of the box. wrtc: https://www.npmjs.com/package/wrtc The simple solution for your issue is to remove the |
Thanks for the help solving this! Can I ask what are the benefits of use WRTC over other alternatives? Are there not other real-time communications transports? Just curious and want to learn more. |
I can report that this does prevent the daemon from crashing but it seems the files are not added to IPFS (but can confirm adding on smaller directories does work). I will look for some more JS bundle app examples. Perhaps we can build our app in a way that is more suitable to JS-IPFS |
WRTC is the WebRTC implementation available for Node.js, we use multiple transports in IPFS to support it working in different environments (i.e desktop, browser, etc) when you are adding large directories, does the process end or does it get stale? It might be the case that it is still adding, js-ipfs currently doesn't have progress bar support. If you would like to take a stab at it, see: ipfs-inactive/js-ipfs-unixfs-engine#123 |
Yeah actually started working on progress bar support earlier. So will take
a stab :)
…On Jun 10, 2017 1:48 PM, "David Dias" ***@***.***> wrote:
WRTC is the WebRTC implementation available for Node.js, we use multiple
transports in IPFS to support it working in different environments (i.e
desktop, browser, etc)
when you are adding large directories, does the process end or does it get
stale? It might be the case that it is still adding, js-ipfs currently
doesn't have progress bar support. If you would like to take a stab at it,
see: ipfs-inactive/js-ipfs-unixfs-engine#123
<ipfs-inactive/js-ipfs-unixfs-engine#123>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#878 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ACq8Ab6pRvBBRmZTenGBqXji-V4YMIU5ks5sCp64gaJpZM4N19V3>
.
|
I got the above errors when running
jsipfs add -r .
(add single file works). Prior seemingly alljsipfs
command responded with nothing or worked improperly.I'll try to help if possible.
Let me know how I can help fix this!
The directory is somewhat large, MBs. It's a large js repo. I tried
.
andcd ..; jsipfs add -r dirName
with same behavior.The text was updated successfully, but these errors were encountered: