-
Notifications
You must be signed in to change notification settings - Fork 147
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
Handle failed sdr devices better #19
Comments
one case of this happening has been brought forward in #18 |
That's a good idea |
The latest version in develop has some patches to show a message in the websites' log panel if something goes wrong. it should also prevent the client/server reconnect loop. Of course, when I went to test it, all my sdrs worked like a charm... I'll have to run this for some time to see if there's anything I messed up or missed. |
Roger, I will build a new docker image for test new commit. |
I had builded a new docker image ,and test it about an hour, that' great improve , very stable runing on my nas. |
Here's my quick sum-up of what I gathered on this specific issue in the past few weeks:
|
when an sdr device fails, connected users potentially enter a reconnect loop; the user interface is pretty much unusable, and other sdr devices that may still be functioning are inaccessible.
ideally, openwebrx would remove failed devices from the profiles dialog. if no devices are left, a message should appear that no sdr devices are availalbe.
also, users that are using an sdr at the moment it fails should receive a message about what happened, informing them to switch to another profile.
The text was updated successfully, but these errors were encountered: