ArduPilot / ArduPilot/MAVProxy
Print module exception by default
- Dominant language
- Python
- Stars
- 595
- Forks
- 773
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 18
Description
At the moment mavproxy does not print module exceptions by default. This is especially annoying if you try a module for the first time and something is not working or there is a bug in an old module. I suggest that mavproxy displays a minimal error message if an exception happens and enables more detailed debugging with the `moddebug` option.
E.g. https://github.com/ArduPilot/MAVProxy/blob/master/MAVProxy/modules/mavproxy_link.py#L908 would need a change.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with MAVProxy/modules/mavproxy_link.py around line 908 and trace how module exceptions are handled, including the existing moddebug option. Confirm the intended default minimal error output and the more detailed output when moddebug is enabled. Done means module exceptions are visible by default without requiring debugging to be enabled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100