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

torrent.ready never becomes true when added after being destroyed #1742

Open
dave-dm opened this issue Dec 3, 2018 · 1 comment
Open

torrent.ready never becomes true when added after being destroyed #1742

dave-dm opened this issue Dec 3, 2018 · 1 comment
Labels
bug

Comments

@dave-dm
Copy link

@dave-dm dave-dm commented Dec 3, 2018

Example:

client.add('08ada5a7a6183aae1e09d831df6748d566095a10')
// wait
torrent = client.torrents[0]
torrent.destroyed // false
torrent.ready // true

// wait

client.remove('08ada5a7a6183aae1e09d831df6748d566095a10')
// wait
torrent.destroyed // true

// wait

client.add('08ada5a7a6183aae1e09d831df6748d566095a10')
// wait
torrent = client.torrents[0]
torrent.destroyed // false
torrent.ready // false

torrent.ready never becomes true when added after being destroyed

What I'm trying to do is destroy the torrent and re-add it multiple times. Sort of like a pause/start.

@feross feross transferred this issue from webtorrent/bittorrent-dht Sep 11, 2019
@feross feross added the bug label Sep 11, 2019
@alxhotel

This comment has been minimized.

Copy link
Member

@alxhotel alxhotel commented Nov 2, 2019

Looks like it's now working correctly in the last version (0.107.16).

Here is an example: https://codepen.io/alxhotel/pen/OJJzpYW

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.