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

Cannot read property 'complete' of null #1083

Closed
kim0 opened this issue Mar 24, 2017 · 2 comments
Closed

Cannot read property 'complete' of null #1083

kim0 opened this issue Mar 24, 2017 · 2 comments

Comments

@kim0
Copy link

@kim0 kim0 commented Mar 24, 2017

What version of WebTorrent?
webtorrent 0.98.3
What operating system and Node.js version?
node v7.7.4, darwin x64
What browser and version? (if using WebTorrent in the browser)
n/a
What did you expect to happen?
exit successfully
What actually happened?
Crashed

webtorrent is exiting...

UNEXPECTED ERROR: If this is a bug in WebTorrent, report it!
OPEN AN ISSUE: https://github.com/feross/webtorrent/issues

DEBUG INFO: webtorrent-cli 1.9.0, webtorrent 0.98.3, node v7.7.4, darwin x64, exit 1
/usr/local/lib/node_modules/webtorrent-cli/node_modules/webtorrent/lib/torrent.js:1537
        if (self._checkDone()) self.discovery.complete()
                                             ^

TypeError: Cannot read property 'complete' of null
    at /usr/local/lib/node_modules/webtorrent-cli/node_modules/webtorrent/lib/torrent.js:1537:46
    at /usr/local/lib/node_modules/webtorrent-cli/node_modules/simple-sha1/index.js:6:5
    at _combinedTickCallback (internal/process/next_tick.js:73:7)
    at process._tickCallback (internal/process/next_tick.js:104:9)
@feross

This comment has been minimized.

Copy link
Member

@feross feross commented Mar 24, 2017

You're running an old version of webtorrent. This bug was fixed in 0.98.4. Please upgrade to the latest version.

@feross feross closed this Mar 24, 2017
@lock

This comment has been minimized.

Copy link

@lock lock bot commented May 3, 2018

This thread has been automatically locked because it has not had recent activity. Please open a new issue for related bugs and link to relevant comments in this thread.

@lock lock bot locked as resolved and limited conversation to collaborators May 3, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Linked pull requests

Successfully merging a pull request may close this issue.

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