ArduPilot / ArduPilot/MAVProxy
MAVProxy doesn't attempt tcp reconnect when source dropped
Open
- Dominant language
- Python
- Stars
- 595
- Forks
- 773
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 18
Description
If MAVProxy is connected to a tcp source (eg. SITL) and the source restarts or connection interrupted, MAVProxy does not attempt to restart the connection. It should, in a fluffy rainbow world.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating MAVProxy's TCP source connection handling and the disconnect path for a dropped or restarted source. Reproduce the SITL interruption scenario, then verify that the source connection is attempted again and remains usable after the source returns.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100