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

[NEW FEATURE] Gate survive to its exclusion. #463

Open
nicolas-rabault opened this issue Jan 8, 2024 · 0 comments
Open

[NEW FEATURE] Gate survive to its exclusion. #463

nicolas-rabault opened this issue Jan 8, 2024 · 0 comments
Assignees

Comments

@nicolas-rabault
Copy link
Member

Details

The Gate is not only used to test firmware, some users use it in production to drive a device through Python.
If some services lose connection to the gate they are excluded from the network, but when they come back they don't always receive the information about their exclusion, so they can still send information to the Gate.
Because Gate excluded this service, it's rejecting the message, and by doing that the service will exclude the Gate.
The Gate receiving its exclusion will isolate itself from any other service, including the Pipe needed to interact with Pyluos.

After that, you don't get any data from the gate and you can't send anything to the Gate. The Gate looks like crashed, and you have to reboot it to get it back.

What feature would you like to be included in Luos?

To avoid this reboot we should make the Gate perform a detection again to allow it to go back to work.

@nicolas-rabault nicolas-rabault self-assigned this Jan 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant