Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign upAdded test script for multiple file webseed. #397
Closed
Conversation
This comment has been minimized.
This comment has been minimized.
|
@feross this script will not pass w/o https://github.com/feross/bittorrent-swarm/pull/24 |
This comment has been minimized.
This comment has been minimized.
|
When will this be merged? @feross |
Looks like it was forgotten for 'img' and 'iframe'.
See #429 (comment) > This is because a windows system doesn't use the shebang so it might > not know how to execute a js file. Spawning using node and node will > understand how to read this.
This allows Windows to run the tests, as promised in #429 (comment) Note that there are a couple of outstanding failures on Windows: # client.seed: filesystem path to folder with one file, string not ok 8 should be equal --- operator: equal expected: '3a686c32404af0a66913dd5f8d2b40673f8d4490' actual: 'e6887b78d89d995876c7cef3476b6fb32c4c4e3d' ... not ok 9 should be equal --- operator: equal expected: |- 'magnet:?xt=urn:btih:3a686c32404af0a66913dd5f8d2b40673f8d4490&dn=folder&tr=udp%3A%2F%2Ftracker.webtorrent.io%3A80' actual: |- 'magnet:?xt=urn:btih:e6887b78d89d995876c7cef3476b6fb32c4c4e3d&dn=folder&tr=udp%3A%2F%2Ftracker.webtorrent.io%3A80'
The specs say that the second Blob constructor argument is optional (http://www.w3.org/TR/FileAPI/#constructorParams), however Chrome and FF implement that differently. FF checks if the second arg is not undefined, while Chrome checks "arguments.length". As a result, if the second argument is undefined, Chrome will throw an error (https://chromium.googlesource.com/chromium/blink/+/72fef91ac1ef679207f51def8133b336a6f6588f/LayoutTests/fast/files/blob-constructor.html#55), while FF will just ignore it. This change makes it so that the second arg is not passed at all when it's undefined, and Chrome is happy as a result.
This forces Windows checkouts to keep LF line endings for test files. https://help.github.com/articles/dealing-with-line-endings/#example resolves #429
…ithub.com/solderzzc/webtorrent into add-test-script-for-multiple-file-webseed
This comment has been minimized.
This comment has been minimized.
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. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
solderzzc commentedAug 9, 2015
Added test script for multiple file webseed.