rclc_executor_spin_some returns RCL_RET_ERROR when using a custom transport
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- embedded-iot
Research direction
Start by tracing rclc_executor_spin_some and the custom read function to find where RCL_RET_ERROR is produced. Reproduce the failure on the FreeRTOS/MicroBlaze transport and inspect the return path and available diagnostics. Done means the failing layer is identified and the issue has a documented correction or debugging path.
Written by the indexing model from the issue text.
Description
I am implementing a custom transport on FreeRTOS using the MicroBlaze processor. The transport is straightforward—it continuously polls memory, waiting for new data in the custom read function. I have already verified that the custom read function returns the correct number of bytes.
However, I am encountering the generic error "RCL_RET_ERROR". How can I effectively debug this issue? What does this generic error typically indicate?
- Dominant language
- Shell
- Stars
- 6
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
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.
Similar issues
-
good-start
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
VilnaCRM-Org/user-service#497 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
conda-forge/spacy-feedstock#177 ·
-
area:jail bug security severity:low track:open-source
Difficulty 1/5 Under an hour Newbie friendliness 75/100