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

Exception when running tests #118

Closed
feross opened this issue Sep 21, 2014 · 3 comments
Closed

Exception when running tests #118

feross opened this issue Sep 21, 2014 · 3 comments

Comments

@feross
Copy link
Member

@feross feross commented Sep 21, 2014

Issue by jhiesey
Thursday Jun 05, 2014 at 04:10 GMT
Originally opened as https://github.com/feross/bittorrent-client/issues/22


When I run node test/strategy.js I sometimes get:

/Users/jhiesey/Desktop/webtorrent/bittorrent-client/node_modules/tape/index.js:75
        throw err
              ^
RangeError: length > kMaxLength
    at new Buffer (buffer.js:194:21)
    at ut_metadata._requestPieces (/Users/jhiesey/Desktop/webtorrent/bittorrent-client/node_modules/ut_metadata/index.js:201:21)
    at ut_metadata.onExtendedHandshake (/Users/jhiesey/Desktop/webtorrent/bittorrent-client/node_modules/ut_metadata/index.js:58:12)
    at Wire._onExtended (/Users/jhiesey/Desktop/webtorrent/bittorrent-client/node_modules/bittorrent-swarm/node_modules/bittorrent-protocol/index.js:430:25)
    at Wire._onmessage (/Users/jhiesey/Desktop/webtorrent/bittorrent-client/node_modules/bittorrent-swarm/node_modules/bittorrent-protocol/index.js:583:19)
    at Wire._write (/Users/jhiesey/Desktop/webtorrent/bittorrent-client/node_modules/bittorrent-swarm/node_modules/bittorrent-protocol/index.js:482:10)
    at doWrite (_stream_writable.js:226:10)
    at writeOrBuffer (_stream_writable.js:216:5)
    at Wire.Writable.write (_stream_writable.js:183:11)
    at write (_stream_readable.js:582:24)
@feross

This comment has been minimized.

Copy link
Member Author

@feross feross commented Sep 21, 2014

Comment by fisch0920
Thursday Jun 12, 2014 at 01:52 GMT


@feross, I've seen this once as well, and I think it was caused by a peer sending an invalid metadata size that was something like MAXINT.

@feross feross added the bug label Sep 21, 2014
@feross

This comment has been minimized.

Copy link
Member Author

@feross feross commented Sep 21, 2014

Comment by feross
Thursday Jun 12, 2014 at 01:53 GMT


Yep, I've seen this twice as well.

@feross

This comment has been minimized.

Copy link
Member Author

@feross feross commented Sep 21, 2014

I haven't seen this error in a long time. Closing.

@feross feross closed this Sep 21, 2014
@lock lock bot locked as resolved and limited conversation to collaborators May 7, 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
1 participant
You can’t perform that action at this time.