Micro Ros Agent if not configured properly or left with default value, code execution will stop without much debug info.
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 42/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- c
- Domain
- embedded-iot, networking
Research direction
Start by reproducing the issue in the Int32_publisher example with idf.py build flash monitor after skipping menuconfig. Inspect the abort path and the network and micro-ROS agent configuration handling. Done means the example reports its configuration context and clearly identifies network initialization or configuration failures instead of stopping with only a line reference.
Written by the indexing model from the issue text.
Description
- Hardware description: Doit ESP32 Dev Kit
- RTOS: Simple publisher int32 example.
- Installation type: micro_ros_setup
- Version or commit hash: jazzy
Steps to reproduce the issue
- Clone this repo.
- Source the terminal using export.sh and then go to the Int32_publisher example.
- Do idf.py build flash monitor.(Make sure esp32 is connected while doing so).
- I delibrately left the idf.py menuconfig step.
- Once, flashed, you'll see notice that program gets aborted indicating the line at which issue occured without additional info.
Expected behavior
The program should atleast output the default config such as ssid, password, micro-ros-agent config. Giving more context and ensuring network is intialized properly and any issue with configuration could be easily debugged.
Actual behavior
The program stops indicating the line where issue occured.
Proposed Changes:
Adding network intialization check and logging default configuration in the code.
- Dominant language
- C
- Stars
- 419
- Forks
- 124
- Avg merge
- 21h 35m
- Merged PRs (30d)
- 3
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.
More from micro-ROS/micro_ros_espidf_component
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
micro-ROS/micro_ros_espidf_component#336 · 3 comments ·
-
micro-ROS/micro_ros_espidf_component#314 · 3 comments · 1 assignee ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
micro-ROS/micro_ros_espidf_component#310 · 2 comments ·
All issues in micro-ROS/micro_ros_espidf_component
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
BasedHardware/omi#15662 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
level/task module/gcp type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
Difficulty 1/5 Under an hour Newbie friendliness 86/100
hapostgres/pg_auto_failover#1190 ·