-
Notifications
You must be signed in to change notification settings - Fork 166
"Error: no such option: --max-workers" and "Exception in thread Thread-1" #166
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
Comments
Vdirsyncer is very strict with argument order:
but this won't:
Check out |
Regarding the threading exceptions, I can't see how they're related to your issue. Vdirsyncer should raise completely different exceptions if there is something wrong with the response provided by the server. Are you sure there are even events in your |
Thanks for your response.
and this one for the sync command:
There are at least 4 events on the server but none is written to the local calendar directory. |
Are you able to do anything with other clients? There are in fact no problems in the interaction with the server (the threading exception is due to a broken worker cleanup), it's just that the server reports the collections as empty. |
Also, is it correct that you only have the |
DAVdroid and even Outlook via z-push can access the SabreDAV server. There are also contacts on the server. But "privat" is the only calendar. As it seems to be an server issue I'll try to install Radicale in parallel to the SabreDAV and check with this one. Is there anything I can do to solve the threading exception? |
I'll have to fix that myself. That you get that one regularly is kinda irritating. Another idea: Maybe you forgot to provide vdirsyncer with username and password, which is why sabredav says the calendars are empty? |
No,unfortunately not. This is the part of the config:
|
@evert Would you know of any behavior in SabreDAV that would cause it to show empty collections? |
It looks like this is due to the I do think this is a bug on our end, but I will want to fix this by just throwing an exception and include a proper HTTP status code for this. |
What do you recommend? Removing the header or setting it to a particular value? |
Also I am not sure if a |
also ownCloud deals with my "infinity" requests just fine -- has this been introduced with 2.0? |
Best to set it to |
The relevant line from 1.8 is here: https://github.com/fruux/sabre-dav/blob/1.8/lib/Sabre/CalDAV/Plugin.php#L589 A single equals sign was used, instead of The same line in 2.0: https://github.com/fruux/sabre-dav/blob/2.0/lib/CalDAV/Plugin.php#L636 So it only really worked in the first place, due to a bug. |
What adds to the confusion is the fact that the default for calendar-queries is |
Yea, I noticed other clients having issues with that as well, and I even considered adding some extra xml element to the output that specifically tells client developers : 'you are not getting any results due to the depth header you specified'. |
ISTM any value |
Where did you get that? Infinity is never mentioned, there's no concept of a depth higher than 1 in caldav calendars, and all of the examples use depth: 1. |
Infinity is mentioned in WebDAV:
http://tools.ietf.org/html/rfc4918#section-10.2 I am not sure either way... you certainly have more experience with the spec, and I didn't intend to phrase this statement in such a definitive way. |
I changed it now. @flart Could you try the following:
|
I think an argument could also be made that infinity should also work and just behave the same as |
FWIW I percieved |
e.g. iCloud returns the collection href with contenttype |
|
@untitaker Sorry for my late reply. I reinstalled as you told me.
and the last:
It seems to be working and now there are elements in the local directory. Thank you very much. |
Thanks, I raised #167 for this. |
First of all - I think you have done a great piece of work and vdirsyncer is exactly what I was looking for to sync a remote with a local caldav-server.
In your Changelog there is written for version 0.3.1 "There is now a --max-workers option on the CLI..."
I tried the option but got "Error: no such option: --max-workers":
Is this option still available in v4.1?
But the many problem is the "Exception in thread Thread-1 (most likely raised during interpreter shutdown)".
vdirsyncer was installed in virtualenv as described in the Tutorial - Manual installation without any errors. The test config is local filesystem with local SabreDAV-server.
When I try "vdirsyncer discover" or "vdirsyncer sync" the sync process seems to start but always ends up with the above-mentioned exception and the local calendar directory remains empty.
Although I'm not a programmer I took a look on the code and searched the web. This seems to be a problem of daemon threads so I tried to reduce the workers to one with the --max-workers option. But this gave me the "Error: no such option: --max-workers".
I would be glad if you could give me some hints on how to get vdirsyncer working for me.
The system is a Raspberry Pi with Arch Linux ARM and Python 2.7.9.
The text was updated successfully, but these errors were encountered: