-
Notifications
You must be signed in to change notification settings - Fork 97
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
Test fails against radicale #439
Comments
I'd like to write up a "caldav server compatibility checker"-tool, it's currently a pain that no caldav servers are perfect enough to not break the tests. Try this
|
I did that too. |
That's strange, Hm. When I try, with the master branch, and
I will see if I get time to look more into it during the day ... but this is not the same errors as you observe? |
Don't worry, I see those two too. :-/ |
I'm a bit swamped those days, but I will try to look into those two during the day at least. |
It's weird, because I don't think it's that long since last I ran the test towards Radicale. Perhaps a new version is out with degraded compatibility. So the The Possible workarounds/solutions:
I don't like the second option, as it may cause subtle changes in how the library works in production environments, breaking backward-compatibility. The third option is possibly the best, but requires most work - and it should be well thought through. I think the last option will be too bloated. |
So I'll go for the first option as a temp workaround just to get the tests working (again), and the third option will be for a later release. |
Could you test my new branch? |
Disclaimer, I didn't yet update radicale to its current master branch. I'll do that sometime soon(ish).
|
Oh ... the scheduling test ... docstring says it all:
This one ended up deep down in my todo-stack. I think I was quite demotivated by the apparent lack of support for this standard in the calendar servers that I expected to support it. Radicale is for sure not one of them. Those tests are only run if adding multiple principals in the conf_private, in the I regret a bit creating |
conf_private.py:
Radicale versions tested: 3.1.8, 3.2.3
The text was updated successfully, but these errors were encountered: