Open matteocrippa opened 5 years ago
Hmm I'll look into it, thanks for the report. I'm surprised this would happen because afaik there aren't any long running connections.
I can't reproduce the issue on my machine with the latest revision of sncli. Could you let us know which version of sncli you are running, the versions of the dependencies (especially simperium-python). If you're running in a virtual env, an easy way to find this is with pip freeze
.
Also would be interested in seeing the full log, annotated with when the internet connection changes state.
I was using the AUR package https://aur.archlinux.org/packages/sncli-git
But I noticed that requests
with pip was not latest, tried for now to upgrade that and now monitoring that.
Here's the new pip freeze: freeze.log
Just experimented again the same issue, here a quick snapshot of the log
If I run in terminal sncli
and open a new instance I see that is perfectly connected.
Was wondering if not worth to add an extra key to force reconnect manually in this scenario.
ps. reopening the app I see that it syncs and logs shows
Was wondering if not worth to add an extra key to force reconnect manually in this scenario.
sncli doesn't keep any long running connections. Any action does a plain requests.post
or requests.get
. That's why I can't understand why this is happening.
I'm facing this issue, once the device go suspend and later I wake it up, or if the wifi goes down and then up (so internet is back working) sncli stays disconnected.
Even forcing sync with
S
doesn't helpIs there a way to force it connect back? Last time, sadly, I lost the note written in the meanwhile and not synced :(