i''lddlZddlZddlZddlZddlZddlmZdadZGddZ d dZ dZ dS) N) to_normal_strc*t|}|ds|dz}tjdd|}tjdd|}tjdd|}tjdd |}d |vrbd |vsJtjtjj d }tjdd |d|}d tt| ddz}||krtdz ad}tjd}|tr|j}n|j}ddddtdg} ddl}t)|| d| dd } n #d|d|g} YnxYw|d || z|S)aThis function receives some ical as it's given from the server, checks for breakages with the standard, and attempts to fix up known issues: 1) COMPLETED MUST be a datetime in UTC according to the RFC, but sometimes a date is given. (Google Calendar?) SOGo! Ref https://github.com/home-assistant/core/issues/106671 2) The RFC does not specify any range restrictions on the dates, but clearly it doesn't make sense with a CREATED-timestamp that is centuries or decades before RFC2445 was published in 1998. Apparently some calendar servers generate nonsensical CREATED timestamps while other calendar servers can't handle CREATED timestamps prior to 1970. Probably it would make more sense to drop the CREATED line completely rather than moving it from the end of year 0AD to the beginning of year 1970. (Google Calendar) 3) iCloud apparently duplicates the DTSTAMP property sometimes - keep the first DTSTAMP encountered (arguably the DTSTAMP with earliest value should be kept). 4) ref https://github.com/python-caldav/caldav/issues/37, X-APPLE-STRUCTURED-EVENT attribute sometimes comes with trailing white space. I've decided to remove all trailing spaces, since they seem to cause a traceback with vobject and those lines are simply ignored by icalendar. 5) Zimbra can apparently create events with both dtstart, dtend and duration set - which is forbidden according to the RFC. We should probably verify that the data is consistent. As for now, we'll just drop DURATION or DTEND (whatever comes last). 6) On FOSSDEM I was presented with icalendar data missing the DTSTAMP field. This is mandatory according to the RFC. All logic here is done with on the ical string, and not on icalendar objects. There are two reasons for it, originally optimization (not having to parse the icalendar data and create an object, if it's to be tossed away again shortly afterwards), but also because broken icalendar data may cause the instantiation of an icalendar object to break. TODO: this should probably be moved out from the library.  z!COMPLETED(?:;VALUE=DATE)?:(\d+)\szCOMPLETED:\g<1>T120000ZzCREATED:00001231T000000ZzCREATED:19700101T000000Zz\\+('\")z\1z *$z DTSTAMP:z ENDtzz%Y%m%dT%H%M%SZz( END:(VTODO|VEVENT|VJOURNAL))c||dz z S)Nr )ns J/root/projects/butler/venv/lib/python3.11/site-packages/caldav/lib/vcal.pyzfix..msa!e$5caldavz4Ical data was modified to avoid compatibility issuesz4(Your calendar server breaks the icalendar standard)zFThis is probably harmless, particularly if not editing events or tasksz(error count: z - this error is ratelimited)rN)linetermz Original: z Modified: )rendswithresubdatetimenowtimezoneutcstrftimejoinfilterLineFilterDiscardingDuplicatesstripsplitfixup_error_loggingslogging getLoggerwarningdebugdiffliblist unified_diff) eventfixeddtstampfixed2is_power_of_twologgerlog log_messager$diffs r fixr0s3X % E >>$    F79SUZ [ [E F-/I5 Q QE F;u - -E F5"e $ $E5  %#''8+<+@'AAJJK[\\8:Sw:S:S:SUZ[[ YYv<>> @S@STX@Y@YZZ [ [^b bF  !55"8,, ?/ 0 0 .CC,C C B T P1 P P P   ? NNN,,U[[->-> T@R@R]_,``aaDD ? %v>DDD DIIkD( ) )*** Ms AG%%G/c eZdZdZddZdZdS)rzNeeds to be a class because it keeps track of whether a certain group of date line was already encountered within a vobject. This must be called line by line in order on the complete text, at least comprising the complete vobject. returnNc"d|_d|_dSNr)stampedended)selfs r __init__z'LineFilterDiscardingDuplicates.__init__s  rc|drd|_d|_n]tjd|r|jrdS|xjdz c_n.tjd|r|jrdS|xjdz c_dS)NzBEGIN:Vrz(DURATION|DTEND|DUE)[:;]Fr z DTSTAMP[:;]T) startswithr5r6rmatch)r7lines r __call__z'LineFilterDiscardingDuplicates.__call__s ??9 % % DLDJJ X0$ 7 7 z u JJ!OJJJ XmT * * | u LLA LLtr)r2N)__name__ __module__ __qualname____doc__r8r=r rr rrsA rren_DKc <t|}d|vr|d|d<|r tjd|tjst j}|d} t jj|}n7#t jj |}YnxYw| || dsd|pdvr |d krd |d<n|| d s'd t| zd z}t j|}|jd}d}| ds|dd|z| ds|dd| dsX| dsC|dt"jt"jj| ds<| ds'|dt+ji}|D] }||t/||t"jr:||js-||t"jj||<|dvrF||D]<}|dt5|d|id=| dr||||dd<||d|||| |rt9||t|} |rL| r8tjd| dz| tjd } | S)!aCreates some icalendar based on properties given as parameters. It basically creates an icalendar object with all the boilerplate, some sensible defaults, the properties given and returns it as a string. TODO: timezones not supported so far class_classz^BEGIN:VNVEVENTstatusz STATUS:rVTODOz NEEDS-ACTIONzBEGIN:VCALENDARzBEGIN:VCALENDAR z END:VCALENDAR rprodidz-//python-caldav//caldav//versionz2.0r)ruid)childparentz related-toreltypeT) parametersencodealarm_z^END:Vz END:Vr )flagscount)rpoprsearch MULTILINE icalendarCalendarcalcomponent_factoryComponentFactory add_componentgetrr: from_ical subcomponentsaddrrrruuiduuid1 isinstancetzinfo astimezonestrupper add_alarmto_icalr) ical_fragmentobjtypelanguageprops my_instance componentalarmpropvaluerets r create_icalrus"-00M58,,g  *mR\ R R(** ?G V! 7@BBII V! 7HHJJ7SUUIII!!),,,  (## -M$7R887"",E(O""$$//0ABB #mM4G4G4I4I&J&JJM``  (22=AA -a0   ??8 $ $K">"IJJJ ??9 % %* 5))) == # #REIIi,@,@R i!2!6!6(:K:O!6!P!PQQQ ==  + %(8(8+ eTZ\\*** E11 ; "%+x'899 L%+BT L#Dk44X5F5JKKd ***"4[EMM$E $-tzz||#<# "** 1"'+d122h dD))) dE$K000 &+u%%%  ++-- . .C ,,.. f     ! !I - ,     Js &B2B9ctj}|D]}|||||jd||Sr4)rXAlarmrar`r])icalrqiarrs r ririsZ   B"" tU4[!!!!q''+++ Kr)NNrB) rr rrbrXcaldav.lib.python_utilitiesrrr0rrurir rr r{s 555555$fffR