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

TypeError: Cannot read property 'complete' of null #1029

Closed
mrbernnz opened this issue Jan 27, 2017 · 3 comments
Closed

TypeError: Cannot read property 'complete' of null #1029

mrbernnz opened this issue Jan 27, 2017 · 3 comments

Comments

@mrbernnz
Copy link

@mrbernnz mrbernnz commented Jan 27, 2017

What version of WebTorrent?
1.9.0 (0.98.3)
What operating system and Node.js version?
macOS Sierra (10.12.2)
7.4.0 (node)
What browser and version? (if using WebTorrent in the browser)
N/A
What did you expect to happen?
Just a completion print to screen
What actually happened?

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.4.0, 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:67:7)
    at process._tickCallback (internal/process/next_tick.js:98:9)
@mrbernnz

This comment has been minimized.

Copy link
Author

@mrbernnz mrbernnz commented Jan 27, 2017

Sorry just made an identical issue to #1022

@feross

This comment has been minimized.

Copy link
Member

@feross feross commented Jan 27, 2017

No worries, thanks for the report.

@feross feross closed this Jan 27, 2017
@lock

This comment has been minimized.

Copy link

@lock lock bot commented May 4, 2018

This thread has been automatically locked because it has not had recent activity. To discuss futher, please open a new issue.

@lock lock bot locked as resolved and limited conversation to collaborators May 4, 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.