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

Lack of a way to recover from connection issues - Softlock #44

Open
Void2258 opened this issue Nov 18, 2023 · 1 comment
Open

Lack of a way to recover from connection issues - Softlock #44

Void2258 opened this issue Nov 18, 2023 · 1 comment

Comments

@Void2258
Copy link

Void2258 commented Nov 18, 2023

If the connection fails (information entry mistake) or stalls (says it connects, but then circles forever "connecting" in the device area), there is no way to retry. Everything is entirely stuck without a way to abort or retry. Even end-tasking as many processes as can be found does not fix the problem. The program remains in a locked state until the entire computer is rebooted. This is a large issue, as rebooting may not always be trivial or even possible to do. The program needs to be able to abort and retry or retry in place or at least have a way to force a full kill without touching the rest of the system; it must not irrecoverably softlock.

@Frontesque
Copy link
Owner

I haven't experienced this. No data is being stored that should be persistent through a reboot, so I'm inclined to say that this is something with your setup.

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

2 participants