OpenCyphal / OpenCyphal/pycyphal
Properly handle global state changes like network interface becoming unavailable
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 142
- Forks
- 110
- PR merge metrics
- No merged PRs in 30d
Description
This is perhaps related to https://github.com/OpenCyphal/pycyphal/issues/224
When the network interface becomes unavailable (e.g., CAN adapter disconnected, IP address changed, Cyphal/serial TCP connection closed), all services dependent on the active transport instance should be notified such that the state change can be adequately processed.
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.
Research direction
Start by reviewing issue 224, then trace how the active transport instance and its dependent services are created and notified. Identify the existing handling for CAN adapter, IP address, and Cyphal/serial TCP connection loss. Done means dependent services receive and process a notification when the active network interface becomes unavailable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100