May 2009 - calendarserver-dev - lists.macosforge.org

[CalendarServer] #305: Apache directory service types broken?
by CalendarServer 25 Feb '10

25 Feb '10

#305: Apache directory service types broken? ------------------------------------+--------------------------------------- Reporter: msantos(a)santosland.com | Owner: wsanchez(a)apple.com Type: Defect | Status: new Priority: 5: Not set | Milestone: Component: Calendar Server | Version: trunk Severity: Crash/data loss | Keywords: ------------------------------------+--------------------------------------- It appears that the Apache directory service types are broken. Code in udpateDirectoryService() in config.py seems to be trying to validate the directory service parameters from the config file against the known keywords, but there is no entry for them in serviceDefaultParams[], so the code takes a KeyError exception at this line: if param not in serviceDefaultParams[dsType]: because dsType is twistedcaldav.directory.apache.DigestDirectoryService, but the list in config.py only has entries for: twistedcaldav.directory.xmlfile.XMLDirectoryService twistedcaldav.directory.appleopendirectory.OpenDirectoryService Maybe that list is supposed to be updated somewhere else (from apache.py?), but I couldn't find any such place. -- Ticket URL: <http://trac.calendarserver.org/ticket/305> CalendarServer </> HTTP/WebDAV/CalDAV Server

2 7

[CalendarServer] #285: Uses deprecated twisted interfaces
by CalendarServer 25 Feb '10

25 Feb '10

#285: Uses deprecated twisted interfaces -----------------------------+---------------------------------------------- Reporter: agx(a)sigxcpu.org | Owner: wsanchez(a)apple.com Type: Defect | Status: new Priority: 5: Not set | Milestone: Component: Calendar Server | Version: Severity: Other | Keywords: -----------------------------+---------------------------------------------- In Debian we splitted out things enough (so we don't have to ship our own twisted). We only ship the patched web2 plugin + twistedcaldav. With recent twisted we're seeing: /usr/lib/python2.5/site-packages/twisted/plugins/twisted_web2.py:22: DeprecationWarning: mktap and related support modules are deprecated as of Twisted 8.0. Use Twisted Application Plugins with the 'twistd' command directly, as described in 'Writing a Twisted Application Plugin for twistd' chapter of the Developer Guide. from twisted.scripts.mktap import _tapHelper This is 1.2 but the code in 1.3 looks pretty much the same. I assume you guys will want switch to newer twisted sooner or later. Any hints on how to fix this in a way that can go into your SVN. -- Ticket URL: <http://trac.calendarserver.org/ticket/285> CalendarServer </> HTTP/WebDAV/CalDAV Server

2 10

[CalendarServer] #308: Minor doc nit: only one <Directory> source is legal at a time.
by CalendarServer 25 Feb '10

25 Feb '10

#308: Minor doc nit: only one <Directory> source is legal at a time. -----------------------------+---------------------------------------------- Reporter: ggm(a)apnic.net | Owner: wsanchez(a)apple.com Type: Defect | Status: new Priority: 5: Not set | Milestone: Component: Calendar Server | Severity: Other Keywords: | -----------------------------+---------------------------------------------- Please can you clarify in the documentation that only one form of Directory can be live at a time. Open/Apple Directory also allows multiple back-end information bindings which needs to be clarified. Can you also explain if with htpasswd/group form, you can perform all calendar operations, and how the __uuid__ value mappings for another directory source are handled, if you change directory (risk of information lossage) -- Ticket URL: <http://trac.calendarserver.org/ticket/308> CalendarServer </> HTTP/WebDAV/CalDAV Server

2 2

[CalendarServer] #318: Startup Error on Suse
by CalendarServer 26 Oct '09

26 Oct '09

#318: Startup Error on Suse -----------------------------+---------------------------------------------- Reporter: roland@… | Owner: wsanchez@… Type: Feature | Status: new Priority: 5: Not set | Milestone: CalendarServer-2.x Component: Calendar Server | Severity: Other Keywords: | -----------------------------+---------------------------------------------- Traceback (most recent call last): File "/root/server/Twisted/bin/twistd", line 21, in <module> run() File "/root/server/Twisted/twisted/scripts/twistd.py", line 27, in run app.run(runApp, ServerOptions) File "/root/server/Twisted/twisted/application/app.py", line 374, in run config.parseOptions() File "/root/server/Twisted/twisted/application/app.py", line 354, in parseOptions usage.Options.parseOptions(self, options) File "/root/server/Twisted/twisted/python/usage.py", line 184, in parseOptions for (cmd, short, parser, doc) in self.subCommands: File "/root/server/Twisted/twisted/application/app.py", line 365, in subCommands self.loadedPlugins[plug.tapname] = plug File "/root/server/CalendarServer/twisted/plugins/caldav.py", line 9, in getProperty return getattr(reflect.namedClass(self.serviceMakerClass), propname) File "/root/server/Twisted/twisted/python/reflect.py", line 347, in namedObject module = namedModule(string.join(classSplit[:-1], '.')) File "/root/server/Twisted/twisted/python/reflect.py", line 335, in namedModule topLevel = __import__(name) File "/root/server/CalendarServer/twistedcaldav/mail.py", line 45, in <module> from twistedcaldav.scheduling.scheduler import IMIPScheduler File "/root/server/CalendarServer/twistedcaldav/scheduling/scheduler.py", line 34, in <module> from twistedcaldav.scheduling import addressmapping File "/root/server/CalendarServer/twistedcaldav/scheduling/addressmapping.py", line 20, in <module> from twistedcaldav.scheduling.caldav import ScheduleViaCalDAV File "/root/server/CalendarServer/twistedcaldav/scheduling/caldav.py", line 39, in <module> from twistedcaldav.resource import isCalendarCollectionResource File "/root/server/CalendarServer/twistedcaldav/resource.py", line 54, in <module> from twistedcaldav.extensions import DAVResource, DAVPrincipalResource File "/root/server/CalendarServer/twistedcaldav/extensions.py", line 52, in <module> from twisted.web2.dav.xattrprops import xattrPropertyStore File "/root/server/Twisted/twisted/web2/dav/xattrprops.py", line 43, in <module> import xattr File "/root/server/xattr/build/lib.linux-i686-2.5/xattr/__init__.py", line 12, in <module> import _xattr ImportError: No module named _xattr -- Ticket URL: <http://trac.calendarserver.org/ticket/318> CalendarServer </> HTTP/WebDAV/CalDAV Server

1 2

[CalendarServer] #304: digest service requires undocumented realm parameter
by CalendarServer 26 Oct '09

26 Oct '09

#304: digest service requires undocumented realm parameter ------------------------------------+--------------------------------------- Reporter: msantos(a)santosland.com | Owner: wsanchez(a)apple.com Type: Defect | Status: new Priority: 5: Not set | Milestone: Component: Calendar Server | Version: trunk Severity: Other | Keywords: ------------------------------------+--------------------------------------- The Apache digest directory service requires the undocumented realmName parameter. This parameter should be added to the docs, and to the sample configuration file provided in the distribution. -- Ticket URL: <http://trac.calendarserver.org/ticket/304> CalendarServer </> HTTP/WebDAV/CalDAV Server

1 2

[CalendarServer] #303: Support 'component'(=VEVENT, VTODO) parameter in getcontenttype properties of PROPFIND results
by CalendarServer 26 Oct '09

26 Oct '09

#303: Support 'component'(=VEVENT,VTODO) parameter in getcontenttype properties of PROPFIND results -------------------------------+-------------------------------------------- Reporter: helge(a)zideone.com | Owner: wsanchez(a)apple.com Type: Enhancement | Status: new Priority: 5: Not set | Milestone: Component: Calendar Server | Version: Severity: Other | Keywords: -------------------------------+-------------------------------------------- Small wish: could iCalServer set the 'component' property in resource content-types? This would make in-place filtering of PROPFIND results easier: {{{ http://www.faqs.org/rfcs/rfc2447.html }}} Sample: {{{ Content-Type:text/calendar; charset=UTF-8; component=vevent }}} Rational: In Outlook we need to map a single calendar collection to two (or three) Outlook folders, eg "Calendar (Events)" and "Calendar (Tasks)". In Outlook each folder has a distinct type (its either tasks or events, never both). So when we do a PROPFIND on a CalDAV calendar which supports both (calendar-component-set: VEVENT+VTODO), tasks and events (and journals ...), we currently just get the generic text/calendar type. We need to fetch the content to decide whether the item is relevant or not for a specific Outlook folder type. If the server would report the contained component-type, we could avoid that annoyingly hard work ;-) Thanks PS: obviously the client can't (and shouldn't) rely on that parameter, but its a relevant optimization. -- Ticket URL: <http://trac.calendarserver.org/ticket/303> CalendarServer </> HTTP/WebDAV/CalDAV Server

1 3

[CalendarServer] #297: Incorrect treatment of Depth on REPORTs
by CalendarServer 26 Oct '09

26 Oct '09

#297: Incorrect treatment of Depth on REPORTs ---------------------------------+------------------------------------------ Reporter: navara(a)emclient.com | Owner: cdaboo(a)apple.com Type: Defect | Status: new Priority: 5: Not set | Milestone: Component: CalDAV Tester | Version: Severity: Other | Keywords: ---------------------------------+------------------------------------------ CalDAVTester incorrectly sends calendar-query REPORTs with no Depth header and expect it to match on the contents of the collection. No Depth header is equivalent to Depth: 0 as per RFC 4791 and RFC 3253 (section 3.6), so no matching on child resources should be performed by the server. This results in the failure of reports.xml tests and possibly others. -- Ticket URL: <https://trac.calendarserver.org/ticket/297> CalendarServer </> HTTP/WebDAV/CalDAV Server

1 2

[CalendarServer] #277: Set process name
by CalendarServer 26 Oct '09

26 Oct '09

#277: Set process name --------------------------------+------------------------------------------- Reporter: wsanchez(a)apple.com | Owner: wsanchez(a)apple.com Type: Defect | Status: new Priority: 3: Important | Milestone: 2.x Component: Calendar Server | Version: Severity: Other | Keywords: --------------------------------+------------------------------------------- Server should do `setproctitle` or whatever to set the process name so that it isn't `python`, which makes it harder to distinguish from other python programs. I think this would require a C extension, since Python doesn't provide API for it. -- Ticket URL: <https://trac.calendarserver.org/ticket/277> CalendarServer </> HTTP/WebDAV/CalDAV Server

1 2

[CalendarServer] #274: caldavd does not properly quote parameters
by CalendarServer 26 Oct '09

26 Oct '09

#274: caldavd does not properly quote parameters ---------------------------------+------------------------------------------ Reporter: kmdurbrow(a)gmail.com | Owner: wsanchez(a)apple.com Type: Defect | Status: new Priority: 5: Not set | Milestone: Component: Calendar Server | Version: Severity: Other | Keywords: ---------------------------------+------------------------------------------ Last line of caldavd {{{ ${configfile} }}} should be quoted -- Ticket URL: <https://trac.calendarserver.org/ticket/274> CalendarServer </> HTTP/WebDAV/CalDAV Server

1 2

[CalendarServer] #319: A solution is needed when max_allowed_instances is exceeded.
by CalendarServer 26 Oct '09

26 Oct '09

#319: A solution is needed when max_allowed_instances is exceeded. -----------------------------+---------------------------------------------- Reporter: apm@… | Owner: wsanchez@… Type: Defect | Status: new Priority: 5: Not set | Milestone: Component: Calendar Server | Severity: Serious Keywords: | -----------------------------+---------------------------------------------- With the ability to create events longer into the future the possibility that a user will create an event with more than "max_allowed_instances" (currently 1000) increases. From instance.py: # The maximum number of instances we will ezpand out to. # Raise a TooManyInstancesError exception if we exceed this. max_allowed_instances = 1000 ... which will make events disappear from instance 1000 or not get created at all if you place the mother event sufficiently far back in the past. If - say - your default_future_expansion_duration is 2 years, you currently cannot create a daily recurring event with a motherevent before ~ april 2008. Or if you create a daily recurring event today, it will no longer work after 1000 days. I see no good solution to this without some mechanism for the user to clean up old calendars, so the don't unnecessarily contain - say - 5 year old daily events. -- Ticket URL: <http://trac.calendarserver.org/ticket/319> CalendarServer </> HTTP/WebDAV/CalDAV Server

1 2