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

Fix missing icalendar_component #339

Merged
merged 2 commits into from
Oct 5, 2023
Merged

Conversation

e-katkov
Copy link
Contributor

@e-katkov e-katkov commented Oct 5, 2023

We faced the problem that icalendar_component missing in some cases. Added checks if the event has the icalendar_component attribute.

@tobixen
Copy link
Member

tobixen commented Oct 5, 2023

That means the server hasn't returned valid data. Does it work as intended for you with this patch? Ideally I'd like to have a test case and some credentials to the server for testing, if possible.

In any case, my intention is for the caldav library to be pragmatic and work over as many caldav servers as possible, even when they are breaking the standards, so I will eventually merge this request.

@tobixen
Copy link
Member

tobixen commented Oct 5, 2023

(test failures for 3.7 and 3.8 are due to a known problem with the testing framework itself - I haven't gotten around to look into it yet).

@e-katkov
Copy link
Contributor Author

e-katkov commented Oct 5, 2023

That means the server hasn't returned valid data.

We have had "empty" events received in some cases. Such events had VERSION, PRODID, TZID, DTSTART, TZNAME and similar fields. In addition, they did not contain the UID, SUMMARY, DESCRIPTION, ORGANIZER, ATTENDEE, LAST-MODIFIED, RRULE and similar fields.

Does it work as intended for you with this patch?

Yeah. That's what made it work.

Ideally I'd like to have a test case and some credentials to the server for testing, if possible.

Unfortunately, that's not possible. We have only gotten this for one user so far. It is not clear how "empty" events are created.

@tobixen
Copy link
Member

tobixen commented Oct 5, 2023

That saves me from spending time doing research on this at least :-) (may I ask what calendar server it is?)

@tobixen tobixen added this pull request to the merge queue Oct 5, 2023
Merged via the queue into python-caldav:master with commit ce4004d Oct 5, 2023
5 of 7 checks passed
@e-katkov
Copy link
Contributor Author

e-katkov commented Oct 5, 2023

Google calendar)

@e-katkov
Copy link
Contributor Author

e-katkov commented Oct 5, 2023

May I ask when you plan to update version that will have these changes?

@tobixen
Copy link
Member

tobixen commented Oct 5, 2023

Right, other users have had similar problems with Google Calendar, just at some other place in the code.

I should do a patch-level release relatively soon as there are other unreleased bugfixes in the master branch ... but I should do a lot of testing before doing a release, I need to find some time for that. I'd say best case in some few days, worst case during this month.

@tobixen
Copy link
Member

tobixen commented Nov 7, 2023

sorry that the "worst case" has slipped a bit, hope to get it out soon.

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

Successfully merging this pull request may close these issues.

3 participants