webtorrent / webtorrent/node-bencode
It sorts dictionary entries incorrectly.
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 173
- Forks
- 38
- PR merge metrics
- No merged PRs in 30d
Description
Bug
// fix for issue #13 - sorted dicts
const keys = Object.keys(data).sort()
This is not the correct way of sorting dictionary entries.
When you say “strings” in the context of Bencoding, you mean “binary strings,” or more specifically, “8-bit byte sequences.”
BEP 52 — The BitTorrent protocol specification version 2
Note that, in the context of bencoding, strings, including dictionary keys, are arbitrary byte sequences (
uint8_t[]).
And Array.prototype.sort compares 16-bit units by default.
If
compareFnis not supplied, all non-undefined array elements are sorted by converting them to strings and comparing strings in UTF-16 code units order.
The simple .sort() results in a different order (sorted_in_utf16) than the correct one (sorted_in_utf8). Observe:
const A = String.fromCodePoint(0xFF61);
const B = String.fromCodePoint(0x10002);
const sorted_in_utf8 = [A, B].sort((a, b) => Buffer.compare(Buffer.from(a), Buffer.from(b))); // [A, B]
const sorted_in_utf16 = [A, B].sort(); // [B, A]
Related issues
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in lib/encode.js at the dictionary-key sorting code linked in the issue. Reproduce the difference between UTF-16 sorting and byte-sequence sorting using the provided code points, then inspect the existing encoder tests. Done means dictionary keys are ordered according to their bencoded byte sequences, including the non-ASCII case described here.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 58/100