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.

Sign up for GitHub

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

Jump to bottom

SynchronizerMonitor should not throw if no devices report heartbeats #172

Open
glopesdev opened this issue Oct 26, 2023 · 0 comments · May be fixed by #224
Open

SynchronizerMonitor should not throw if no devices report heartbeats #172

glopesdev opened this issue Oct 26, 2023 · 0 comments · May be fixed by #224
Labels
bug Something isn't working

Comments

@glopesdev
Copy link
Contributor

Currently the conversion inside the SynchronizerMonitor workflow throws if the list of heartbeat messages is empty. While empty heartbeat lists are indeed a serious concern, we wouldn't want a monitoring / alert system to bring the entire workflow down since it might be solved by replugging a cable.
@glopesdev glopesdev added the bug Something isn't working label Oct 26, 2023
@aspaNeuro aspaNeuro linked a pull request Oct 17, 2024 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
1 participant
@glopesdev