nervosnetwork / nervosnetwork/fiber
[send_payment] no path found after UnknownNextPeer err
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 59
- Forks
- 31
- Avg merge
- 3d 5h
- Merged PRs (30d)
- 18
Description
commit: 80ddb35e
Sending a payment failed before the channel was ready, resulting in an UnknownNextPeer error, which subsequently causes all send payment attempts to report "no path found."
1. self.open_channel(self.fiber1, self.fiber2, 1000 * 100000000, 1000 * 100000000)
2. self.open_channel(self.fiber2, self.fiber3, 1000 * 100000000, 1000 * 100000000)
3. self.open_channel(self.fiber3, self.fiber1, 1000 * 100000000, 1000 * 100000000)
4. self.fiber3.stop()
5. self.fiber3.start()
6. time.sleep(2)
7. self.send_payment(self.fiber1,self.fiber1,1)
return no path found
8. time.sleep(1 min)
9. self.send_payment(self.fiber1,self.fiber1,1)
return no path found
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
Reproduce the open-channel, node restart, and send_payment sequence described in the issue, then inspect node.log from commit 80ddb35e. Start at the send_payment handling of UnknownNextPeer and follow the state after the channel becomes ready. Done means later payment attempts no longer incorrectly return "no path found."
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- blockchain, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100