December 2011 - calendarserver-dev - lists.macosforge.org

[Calendar and Contacts Server] #470: Auto-schedule doesn't work
by Calendar and Contacts Server 01 Dec '11

01 Dec '11

#470: Auto-schedule doesn't work ---------------------------------+------------------------------------------ Reporter: brent@… | Owner: wsanchez@… Type: Defect | Status: new Priority: 2: Expected | Milestone: CalendarServer-3.1 Component: Calendar Server | Severity: Other Keywords: | Radar: ---------------------------------+------------------------------------------ Auto-schedule for principals doesn't appear to be working. I am using the release tagged 3.1. I have the XML file augment service configured: {{{  <key>AugmentService</key> <dict> <key>type</key> <string>twistedcaldav.directory.augment.AugmentXMLDB</string> <key>params</key> <dict> <key>xmlFiles</key> <array> <string>augments.xml</string> </array> </dict> </dict> }}} Augments.xml contains: {{{ <augments> <record> <uid>boardroom</uid> <enable>true</enable> <enable-calendar>true</enable-calendar> <enable-addressbook>true</enable-addressbook> <auto-schedule>true</auto-schedule> </record> </augments> }}} The boardroom calendar still needs to have events manually accepted. There appears to be no information in the logs regarding this, even set to debug. -- Ticket URL: <http://trac.calendarserver.org/ticket/470> Calendar and Contacts Server </> HTTP/WebDAV/CalDAV Server

1 4

[Calendar and Contacts Server] #469: incompatible with python-sqlparse 0.1.3 (Debian Testing)
by Calendar and Contacts Server 01 Dec '11

01 Dec '11

#469: incompatible with python-sqlparse 0.1.3 (Debian Testing) ---------------------------------+------------------------------------------ Reporter: patrick.ohly@… | Owner: wsanchez@… Type: Enhancement | Status: new Priority: 5: Not set | Milestone: Component: Calendar Server | Severity: Other Keywords: | Radar: ---------------------------------+------------------------------------------ When starting the server with the system's python-sqlparse 0.1.3 instead of the version 0.1.2 that it would use as fallback, the server fails with: ... File "/home/pohly/src/CalendarServer/CalendarServer/twext/enterprise/dal/parseschema.py", line 232, in nextColumn return self.parseColumn(maybeIdent.value) File "/home/pohly/src/CalendarServer/CalendarServer/twext/enterprise/dal/parseschema.py", line 307, in parseColumn theType = SQLType(typeName.value.encode("utf-8"), typeLength) AttributeError: 'NoneType' object has no attribute 'encode' Adding some print statements showed that it fails for varchar entries: txdav/common/datastore/sql_schema/current.sql create table CALENDAR_HOME ( RESOURCE_ID integer primary key default nextval('RESOURCE_ID_SEQ'), => OWNER_UID varchar(255) not null unique ); In python-sqlparse, typeName.value was "varchar", same as the string representation of typeName itself. Based on that observation here's a crude patch which uses str(typeName) as default. Works for me, no idea whether it is the right fix... diff --git a/CalendarServer/twext/enterprise/dal/parseschema.py b/CalendarServer/twext/enterprise/dal/parseschema.py index 0978b5f..4e3fcb1 100644 --- a/CalendarServer/twext/enterprise/dal/parseschema.py +++ b/CalendarServer/twext/enterprise/dal/parseschema.py @@ -304,7 +304,7 @@ class _ColumnParser(object): # something else typeLength = None self.pushback(maybeTypeArgs) - theType = SQLType(typeName.value.encode("utf-8"), typeLength) + theType = SQLType((typeName.value or str(typeName)).encode("utf-8"), typeLength) theColumn = self.table.addColumn( name=name.encode("utf-8"), type=theType ) -- Ticket URL: <http://trac.calendarserver.org/ticket/469> Calendar and Contacts Server </> HTTP/WebDAV/CalDAV Server

1 4

[Calendar and Contacts Server] #465: Sharing invites are not propagated across partitioning
by Calendar and Contacts Server 01 Dec '11

01 Dec '11

#465: Sharing invites are not propagated across partitioning -----------------------------+---------------------------------------------- Reporter: apm@… | Owner: wsanchez@… Type: Defect | Status: new Priority: 5: Not set | Milestone: Component: Calendar Server | Severity: Other Keywords: | Radar: -----------------------------+---------------------------------------------- Looking at the CalendarServer-3.0 code, it seems notification of invites are not implemented for a DirectoryReverseProxyResource which means that you can share a calendar with a user on another host (partition). CalendarServer throws an exception: 2011-09-28 08:42:52+0000 [-] [caldav-0] notifications = notificationResource._newStoreNotifications 2011-09-28 08:42:52+0000 [-] [caldav-0] exceptions.AttributeError: 'DirectoryReverseProxyResource' object has no attribute '_newStoreNotifications' -- Ticket URL: <http://trac.calendarserver.org/ticket/465> Calendar and Contacts Server </> HTTP/WebDAV/CalDAV Server

1 1

[Calendar and Contacts Server] #463: calendarserver/tools/bootstrapdatabase.py assumes wrong location for current.sql
by Calendar and Contacts Server 01 Dec '11

01 Dec '11

#463: calendarserver/tools/bootstrapdatabase.py assumes wrong location for current.sql ----------------------------------+----------------------------------------- Reporter: mail@… | Owner: wsanchez@… Type: Defect | Status: new Priority: 5: Not set | Milestone: Component: Calendar Server | Severity: Other Keywords: | Radar: ----------------------------------+----------------------------------------- In bootstrapdatabase.py the schema is assumed to be at /usr/share/caldavd/lib/python/txdav/common/datastore/sql_schema/current.sql. However just doing a python setup.py install places it for me at /usr/lib64/python2.7/site- packages/txdav/common/datastore/sql_schema/current.sql -- Ticket URL: <http://trac.calendarserver.org/ticket/463> Calendar and Contacts Server </> HTTP/WebDAV/CalDAV Server

1 1

[Calendar and Contacts Server] #462: Hypervisjon adresseliste
by Calendar and Contacts Server 01 Dec '11

01 Dec '11

#462: Hypervisjon adresseliste -----------------------------------+---------------------------------------- Reporter: martin@… | Owner: wsanchez@… Type: Defect | Status: new Priority: 3: Important | Milestone: CalendarServer-4.x Component: Calendar Server | Severity: Performance Keywords: | Radar: -----------------------------------+---------------------------------------- fellesadresser -- Ticket URL: <http://trac.calendarserver.org/ticket/462> Calendar and Contacts Server </> HTTP/WebDAV/CalDAV Server

1 2

[Calendar and Contacts Server] #454: LDAP cacheTimeout clarification
by Calendar and Contacts Server 01 Dec '11

01 Dec '11

#454: LDAP cacheTimeout clarification -----------------------------+---------------------------------------------- Reporter: rob@… | Owner: wsanchez@… Type: Enhancement | Status: new Priority: 4: Nice to have | Milestone: CalendarServer-3.x Component: Calendar Server | Severity: Other Keywords: ldap linux | Radar: -----------------------------+---------------------------------------------- Can there be more clarification on the units for the LDAP cacheTimeout attribute? Is it seconds or milliseconds? Please add a comment to relevant .plist files and the ldapdirectory.py file. -- Ticket URL: <http://trac.calendarserver.org/ticket/454> Calendar and Contacts Server </> HTTP/WebDAV/CalDAV Server

1 3

[Calendar and Contacts Server] #451: Bad response leads to String index out of range in propfindItems
by Calendar and Contacts Server 01 Dec '11

01 Dec '11

#451: Bad response leads to String index out of range in propfindItems -----------------------------+---------------------------------------------- Reporter: douglm@… | Owner: wsanchez@… Type: Defect | Status: new Priority: 5: Not set | Milestone: Component: Calendar Server | Severity: Other Keywords: | Radar: -----------------------------+---------------------------------------------- A missing header leads to an okprop of the form urn:ietf:params:xml:ns:caldavschedule-tag$$schedule-tag-organizer: This in turn leads to a string index error in propfindItems when normalizeXML is called after splitting on "$" -- Ticket URL: <http://trac.calendarserver.org/ticket/451> Calendar and Contacts Server </> HTTP/WebDAV/CalDAV Server

1 2

[Calendar and Contacts Server] #441: Postgres is crashing on first request
by Calendar and Contacts Server 01 Dec '11

01 Dec '11

#441: Postgres is crashing on first request ----------------------------------------+----------------------------------- Reporter: ian@… | Owner: wsanchez@… Type: Defect | Status: new Priority: 3: Important | Milestone: Linux Port Component: Calendar Server | Severity: Serious Keywords: | Radar: ----------------------------------------+----------------------------------- I've been trying to get this running as a production server on the standard ports. When I try to start the installed caldavd everything seems to be working until I actually send it a request, at which point I can see that postgres process has crashed and there is an error in the log. Any help would be appreciated. -- Ticket URL: <http://trac.calendarserver.org/ticket/441> Calendar and Contacts Server </> HTTP/WebDAV/CalDAV Server

1 3

[Calendar and Contacts Server] #431: Support IPv6
by Calendar and Contacts Server 01 Dec '11

01 Dec '11

#431: Support IPv6 --------------------------------+------------------------------------------- Reporter: wsanchez@… | Owner: glyph@… Type: Defect | Status: new Priority: 2: Expected | Milestone: CalendarServer-3.x Component: Calendar Server | Severity: Other Keywords: | Radar: --------------------------------+------------------------------------------- We currently only bind to IPv4, and we should support IPv6 before the world comes to an end. -- Ticket URL: <http://trac.calendarserver.org/ticket/431> Calendar and Contacts Server </> HTTP/WebDAV/CalDAV Server

1 1

[Calendar and Contacts Server] #421: Create PostgreSQL DB on run CalendarServer - could not create shared memory segment
by Calendar and Contacts Server 01 Dec '11

01 Dec '11

#421: Create PostgreSQL DB on run CalendarServer - could not create shared memory segment ----------------------------------+----------------------------------------- Reporter: donaldinos@… | Owner: wsanchez@… Type: Defect | Status: new Priority: 5: Not set | Milestone: CalendarServer-3.x Component: Calendar Server | Severity: Crash/data loss Keywords: | Radar: ----------------------------------+----------------------------------------- This issue occurs on execute ./run from command line on FreeBSD 8 2011-03-14 16:37:37+0100 [-] Unhandled Error Traceback (most recent call last): File "/usr/local/lib/python2.6/site- packages/twisted/internet/_baseprocess.py", line 60, in maybeCallProcessEnded proto.processEnded(Failure(reason)) File "/usr/local/src/AppleCalendarServer/CalendarServer/txdav/base/datastore/subpostgres.py", line 153, in processEnded self.deferred.callback(''.join(self.output)) File "/usr/local/lib/python2.6/site- packages/twisted/internet/defer.py", line 318, in callback self._startRunCallbacks(result) File "/usr/local/lib/python2.6/site- packages/twisted/internet/defer.py", line 424, in _startRunCallbacks self._runCallbacks() --- <exception caught here> --- File "/usr/local/lib/python2.6/site- packages/twisted/internet/defer.py", line 441, in _runCallbacks self.result = callback(self.result, *args, **kw) File "/usr/local/src/AppleCalendarServer/CalendarServer/txdav/base/datastore/subpostgres.py", line 407, in doCreate raise RuntimeError("Unable to initialize postgres database: %s" % (result,)) exceptions.RuntimeError: Unable to initialize postgres database: The files belonging to this database system will be owned by user "XXXXXX". This user must also own the server process. The database cluster will be initialized with locale C. creating directory /usr/local/src/AppleCalendarServer/CalendarServer/data/Data/Database/cluster ... ok creating subdirectories ... ok selecting default max_connections ... 10 selecting default shared_buffers/max_fsm_pages ... 400kB/20000 creating configuration files ... ok creating template1 database in /usr/local/src/AppleCalendarServer/CalendarServer/data/Data/Database/cluster/base/1 ... FATAL: could not create shared memory segment: Cannot allocate memory DETAIL: Failed system call was shmget(key=1, size=1818624, 03600). HINT: This error usually means that PostgreSQL's request for a shared memory segment exceeded available memory or swap space. To reduce the request size (currently 1818624 bytes), reduce PostgreSQL's shared_buffers parameter (currently 50) and/or its max_connections parameter (currently 10). The PostgreSQL documentation contains more information about shared memory configuration. child process exited with exit code 1 initdb: removing data directory "/usr/local/src/AppleCalendarServer/CalendarServer/data/Data/Database/cluster" -- Ticket URL: <http://trac.calendarserver.org/ticket/421> Calendar and Contacts Server </> HTTP/WebDAV/CalDAV Server

1 5