Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement Connection Restoration Mechanism #767

Open
sashacmc opened this issue Oct 29, 2024 · 2 comments · May be fixed by #799
Open

Implement Connection Restoration Mechanism #767

sashacmc opened this issue Oct 29, 2024 · 2 comments · May be fixed by #799
Assignees
Labels
release Part of the next release

Comments

@sashacmc
Copy link
Member

sashacmc commented Oct 29, 2024

Describe the release item

Issue:
When network disruptions occur (e.g., due to network problems or router restarts), zenoh-pico currently loses the connection without any attempt to restore it. Unlike zenoh-c, which includes a mechanism to handle such disruptions and automatically reconnect, zenoh-pico lacks this functionality, potentially causing silent data loss and communication gaps.

Expected Behavior:
zenoh-pico should detect network interruptions and, upon reestablishing connectivity, automatically restore its connection without requiring manual intervention. This would bring zenoh-pico in line with zenoh-c in terms of resilience and reliability.

@sashacmc sashacmc added the release Part of the next release label Oct 29, 2024
@sashacmc sashacmc changed the title Implement connection restarting Implement Connection Restoration Mechanism Oct 29, 2024
@sebglatz
Copy link

sebglatz commented Dec 6, 2024

This feature is a high priority for us.
Could you share an estimated timeline for its completion?
Additionally, is there any way we can assist?

@sashacmc sashacmc self-assigned this Dec 6, 2024
@sashacmc sashacmc linked a pull request Dec 6, 2024 that will close this issue
@sashacmc
Copy link
Member Author

sashacmc commented Dec 6, 2024

Hi @sebglatz, we've already started working on it but there have been a few blockers, I'm hoping we can continue working on it next week and if nothing unexpected comes up by the end of the week I'd like to have it in main.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release Part of the next release
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants