Error getting a hash
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 63
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
This is what I did
$ dhtkv put "nicola"
e8da214959c50a0a9e62528c6109501d85943588
$ dhtkv get e8da214959c50a0a9e62528c6109501d85943588
/usr/local/lib/node_modules/dhtkv/index.js:20
console.log(res.v.toString())
^
TypeError: Cannot read property 'v' of null
at /usr/local/lib/node_modules/dhtkv/index.js:20:22
at done (/usr/local/lib/node_modules/dhtkv/node_modules/bittorrent-dht/client.js:227:5)
at done (/usr/local/lib/node_modules/dhtkv/node_modules/bittorrent-dht/client.js:511:5)
at done (/usr/local/lib/node_modules/dhtkv/node_modules/k-rpc/index.js:240:5)
at doNTCallback0 (node.js:430:9)
at process._tickCallback (node.js:359:13)
Ideas?
Contributor guide
No contributing guide indexed for this repository
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 with index.js at line 20 and reproduce the issue using the shown dhtkv put and get commands. Trace why the get callback receives null before accessing res.v; done means the command handles this lookup result without crashing and reports an appropriate outcome.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- cli, distributed-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100