PATHS_BLOCKED not sent when it should be
Open
Nobody has claimed this yet.
multipath
- Dominant language
- Rust
- Stars
- 413
- Forks
- 63
- Avg merge
- 4d 14m
- Merged PRs (30d)
- 4
Description
When trying to open a new path, we will never send PATHS_BLOCKED because of a logic error in Connection::open_path.
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 at Connection::open_path and trace the logic used when opening a new path, focusing on the condition that should send PATHS_BLOCKED. Done means correcting the logic so PATHS_BLOCKED is sent when the path-opening situation requires it, while preserving the existing behavior in other cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100