[CLOSED] Path option not working

[feross]

Issue by Fr3aKkK
Friday Aug 22, 2014 at 06:00 GMT
Originally opened as https://github.com/feross/bittorrent-client/issues/41

---

Hello guys,
I wanted to use bittorrent client, but upon adding torrent, the CPU usage goes crazy, but this is already reported. The problem for me is that something is being downloaded, but I can't find it anywhere and after a minute or two I am getting "Wire not speaking BitTorrent protocol" a lot of it, until I just stop the script.

[feross]

Comment by feross
Friday Aug 22, 2014 at 07:01 GMT

---

Thanks for the report. Can you share the code you're using? Also, can you check which version of bittorrent-client you're using? There were a lot of improvements recently.

[feross]

Comment by Fr3aKkK
Friday Aug 22, 2014 at 08:14 GMT

---

The version is 0.8.0
As for the code I wanted to start with something simpler to test before moving on.

var client = BitTorrentClient({
path: '/var/www/public/movies'
})
client.add('super-long-magnet')
client.on('torrent', function (torrent) {
console.log(torrent.name)
torrent.files.forEach(function (file) {
console.log(file.name)
var stream = file.createReadStream()
})
})

[feross]

Comment by feross
Friday Aug 22, 2014 at 08:48 GMT

---

Can you share the magnet uri you're using? Email works: feross@gmail.com

[feross]

Comment by Fr3aKkK
Friday Aug 22, 2014 at 09:00 GMT

---

Yea of course.

[feross]

Comment by feross
Friday Aug 22, 2014 at 09:09 GMT

---

So, the issue is that the path option is not supported (and actually never was). You need to save the files to disk for yourself using fs. Here's how:

var BitTorrentClient = require('./')
var fs = require('fs')

var client = BitTorrentClient({})
client.add('<magnet>')
client.on('torrent', function (torrent) {
  console.log(torrent.name)
  torrent.files.forEach(function (file) {
    console.log(file.name)
    file.createReadStream().pipe(fs.createWriteStream('/path/to/folder/that/exists/' + file.name))
  })
})

Let me know if that code works for you.

[feross]

Comment by Fr3aKkK
Friday Aug 22, 2014 at 09:36 GMT

---

Yes, now the files are there, although I am still getting this error multiple times in the console.

[feross]

Comment by feross
Friday Aug 22, 2014 at 09:38 GMT

---

The message about "Wire not speaking BitTorrent protocol" is not really an error. It just means that one of the peers the client tried to connect to didn't send the expected handshake and so the connection with this peer was closed. I updated the underlying module to not spew this debugging message onto the console. If you run npm update the message should disappear :)

[feross]

Comment by feross
Friday Aug 22, 2014 at 09:39 GMT

---

Closing this issue for now, but let me know (via a new issue) if you have any more issues!