Error sending 'b'findValue' to/from own ip/port
Open
Nobody has claimed this yet.
area: DHT
- Dominant language
- Python
- Stars
- 7.2k
- Forks
- 493
- PR merge metrics
- No merged PRs in 30d
Description
The Issue
Args: [b'L0Yi\xd0\nMk\x1d\xa3\xbc\x96\xf8j\x93\x9b\x91b^\x9fE\x7f\x04e\xb0\xd9\xf7\\\x1fT\xc0X\xbc\x97\xb0zy\xfe~\xc8y\x86\x92z\xde\x1e\xd0\x08', {b'protocolVersion': 1}]
Raised: <class 'AssertionError'>(('012bd010', '012bd010'))
2019-05-16 14:34:49,144 WARNING lbrynet.dht.protocol.protocol:518: Error sending 'b'findValue'' to 24.184.108.248:4400
Args: [b'H\xed\xd1\xec\x85>\r+\xaa\xee\x9c\xb4\xa9\xee\n6\x14V\x8b\x88SsO\xc0~\xa8s\x80\xf8&\xb9\xe1C\xff\xc1HA\xc5%\xc7\xe7F\tL\x17\xe2\xac\x9c', {b'protocolVersion': 1}]
Raised: <class 'AssertionError'>(('012bd010', '012bd010'))
2019-05-16 14:34:49,144 ERROR lbrynet.dht.protocol.protocol:653: Unexpected error while storing blob_hash
Traceback (most recent call last):
File "c:\users\thoma\documents\lbry\lbrynet\dht\protocol\protocol.py", line 640, in store_to_peer
return await __store()
File "c:\users\thoma\documents\lbry\lbrynet\dht\protocol\protocol.py", line 633, in __store
res = await self.get_rpc_peer(peer).store(hash_value)
File "c:\users\thoma\documents\lbry\lbrynet\dht\protocol\protocol.py", line 151, in store
find_value_resp = await self.find_value(blob_hash)
File "c:\users\thoma\documents\lbry\lbrynet\dht\protocol\protocol.py", line 180, in find_value
self.peer, RequestDatagram.make_find_value(self.protocol.node_id, key)
File "c:\users\thoma\documents\lbry\lbrynet\dht\protocol\protocol.py", line 553, in send_request
response = await asyncio.wait_for(response_fut, self.rpc_timeout)
File "C:\Users\thoma\AppData\Local\Programs\Python\Python37-32\lib\asyncio\tasks.py", line 416, in wait_for
return fut.result()
lbrynet.dht.error.RemoteException: <class 'AssertionError'>(('012bd010', '012bd010'))
2019-05-16 14:34:49,148 ERROR lbrynet.dht.protocol.protocol:653: Unexpected error while storing blob_hash
Traceback (most recent call last):
File "c:\users\thoma\documents\lbry\lbrynet\dht\protocol\protocol.py", line 640, in store_to_peer
return await __store()
File "c:\users\thoma\documents\lbry\lbrynet\dht\protocol\protocol.py", line 633, in __store
res = await self.get_rpc_peer(peer).store(hash_value)
File "c:\users\thoma\documents\lbry\lbrynet\dht\protocol\protocol.py", line 151, in store
find_value_resp = await self.find_value(blob_hash)
File "c:\users\thoma\documents\lbry\lbrynet\dht\protocol\protocol.py", line 180, in find_value
self.peer, RequestDatagram.make_find_value(self.protocol.node_id, key)
File "c:\users\thoma\documents\lbry\lbrynet\dht\protocol\protocol.py", line 553, in send_request
response = await asyncio.wait_for(response_fut, self.rpc_timeout)
File "C:\Users\thoma\AppData\Local\Programs\Python\Python37-32\lib\asyncio\tasks.py", line 416, in wait_for
return fut.result()
lbrynet.dht.error.RemoteException: <class 'AssertionError'>(('012bd010', '012bd010'))
System Configuration
- LBRY Daemon version:
- LBRY App version:
- LBRY Installation ID:
- Operating system:
Anything Else
Screenshots
Internal Use
Acceptance Criteria
Definition of Done
- Tested against acceptance criteria
- Tested against the assumptions of user story
- The project builds without errors
- Unit tests are written and passing
- Tests on devices/browsers listed in the issue have passed
- QA performed & issues resolved
- Refactoring completed
- Any configuration or build changes documented
- Documentation updated
- Peer Code Review performed
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 with lbrynet/dht/protocol/protocol.py around find_value (line 180), send_request (line 553), and store_to_peer (line 640), using the reported AssertionError and self-address details as the starting case. Reproduce the failure if possible, trace why the request reaches the own IP/port, and add focused tests showing the corrected behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- distributed-systems, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100