Closed opiechow closed 2 years ago
Are you on the latest version of etesync-dav? It was definitely fixed recently, though maybe only for etesync 2.0. Need to check after you respond.
pip freeze says I'm on version: etesync-dav==0.32.0
In the meantime I recreated a venv for python3.8.12 and this is from this venv, didn't help, gets stuck with a similar issue.
OK, I have applied the changes https://github.com/etesync/etesync-dav/commit/88cb99b9420ce8729b0d93708437285a1bcd7d4f to storage.py also and now it seems to work just fine, do you want me to submit a PR with this? :)
Thanks a lot for the PR! I made a comment.
Hi,
I suspect this issue started to occur after I have updated python. At first my venv setup wouldn't run at all, so I decided to configure a new one. The problem occurs also after doing a fresh installation (after clearing .config) of etesync-dav via venv method.
Attaching debug log from the crashing thread (with Etesync and Linux username replaced with 'xyzzy'):
If this is relevant, I still haven't migrated to Etesync 2.0 and I am connecting to a self-hosted instance.