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

[Calendar and Contacts Server] #460: Regression between r7850 and r7985: cannot login anymore
by Calendar and Contacts Server 19 Aug '11

19 Aug '11

#460: Regression between r7850 and r7985: cannot login anymore ----------------------------------+----------------------------------------- Reporter: mail@… | Owner: wsanchez@… Type: Defect | Status: new Priority: 5: Not set | Milestone: Component: Calendar Server | Severity: Other Keywords: | Radar: ----------------------------------+----------------------------------------- I tried to update my calendar server today. But the system totally broke, I cannot login anymore. When visiting the side with firefox I get: {{{ Unauthorized You are not authorized to view the resource at /calendars/. Perhaps you entered a wrong password, or perhaps your browser doesn't support authentication. }}} Downgrading makes it work again. In the logs I have: {{{ 2011-08-13 19:02:30+0200 [-] [caldav-0] [HTTPChannel,4,92.201.116.230] [twext.web2.server#info] GET /calendars/ HTTP/1.1 2011-08-13 19:02:30+0200 [-] [caldav-0] [HTTPChannel,4,92.201.116.230] [twistedcaldav.directory.digest.DigestCredentialsMemcache#debug] Getting Cache Token for '1814181732836391079733155546' 2011-08-13 19:02:30+0200 [-] [caldav-0] [HTTPChannel,4,92.201.116.230] [twistedcaldav.memcachepool.MemCachePool#debug] Busied client: <twistedcaldav.memcachepool.PooledMemCacheProtocol instance at 0x94f702c> 2011-08-13 19:02:30+0200 [-] [caldav-0] [HTTPChannel,4,92.201.116.230] [twistedcaldav.memcachepool.MemCachePool#debug] Clients #free: 0, #busy: 1, #pending: 0, #queued: 0 2011-08-13 19:02:30+0200 [-] [caldav-0] [PooledMemCacheProtocol,client] [twistedcaldav.memcachepool.MemCachePool#debug] Freed client: <twistedcaldav.memcachepool.PooledMemCacheProtocol instance at 0x94f702c> 2011-08-13 19:02:30+0200 [-] [caldav-0] [PooledMemCacheProtocol,client] [twistedcaldav.memcachepool.MemCachePool#debug] Clients #free: 1, #busy: 0, #pending: 0, #queued: 0 2011-08-13 19:02:30+0200 [-] [caldav-0] [PooledMemCacheProtocol,client] [twistedcaldav.extensions#info] Could not find the principal resource for user id: felix }}} I have the following in my accounts.xml: {{{ <!DOCTYPE accounts SYSTEM "accounts.dtd"> <accounts realm="Test Realm"> <user> <uid>felix</uid> <password>****</password> <name>Felix Möller</name> <first-name>Felix</first-name> <last-name>Moeller</last-name> <email-address>*(a)*.de</email-address> </user> }}} -- Ticket URL: <http://trac.calendarserver.org/ticket/460> Calendar and Contacts Server </> HTTP/WebDAV/CalDAV Server

1 4

[CalendarServer] #330: group as no calendar home
by CalendarServer 03 Aug '11

03 Aug '11

#330: group as no calendar home ------------------------------+--------------------------------------------- Reporter: jduffas1@… | Owner: wsanchez@… Type: Defect | Status: new Priority: 5: Not set | Milestone: CalendarServer-2.x Component: Calendar Server | Severity: Serious Keywords: | ------------------------------+--------------------------------------------- I upgraded to the latest version, and all my groups are broken. iCal says that there is no home calendar for group, and when I look in the server terminal, it says : 2009-03-30 17:18:22+0200 [-] [caldav-8009] [PooledMemCacheProtocol,client] [twistedcaldav.static#info] Directory record <XMLDirectoryRecord[groups@21927289-115a-5605-8596-cd1b708d3750(icalconsult Realm)] F2F2B56A-7B0E-498C-816F-1DA30D8A4167(nous_deux) 'nous deux'> is not enabled for calendaring I use the accounts.xml file. -- Ticket URL: <http://trac.calendarserver.org/ticket/330> CalendarServer </> HTTP/WebDAV/CalDAV Server

4 30

Re: [CalendarServer-dev] [Calendar and Contacts Server] #153: Validate iCalendar data from clients
by Calendar and Contacts Server 02 Aug '11

02 Aug '11

#153: Validate iCalendar data from clients --------------------------------+------------------------------------------- Reporter: wsanchez@… | Owner: cdaboo@… Type: Defect | Status: new Priority: 2: Expected | Milestone: CalendarServer-3.x Component: Calendar Server | Severity: Other Keywords: | Radar: --------------------------------+------------------------------------------- Comment(by mail@…): I think pycalendar takes care of this now. -- Ticket URL: <http://trac.calendarserver.org/ticket/153#comment:5> Calendar and Contacts Server </> HTTP/WebDAV/CalDAV Server

1 0

[Calendar and Contacts Server] #443: Bad assertion in sendmsg_sendmsg()
by Calendar and Contacts Server 01 Aug '11

01 Aug '11

#443: Bad assertion in sendmsg_sendmsg() -------------------------------------------+-------------------------------- Reporter: narge-macosforge@… | Owner: wsanchez@… Type: Defect | Status: new Priority: 5: Not set | Milestone: Component: Calendar Server | Severity: Crash/data loss Keywords: | Radar: -------------------------------------------+-------------------------------- I recently upgraded caldavd from 2.4 to trunk on a ppc linux machine. After the upgrade, caldavd dies on the first incoming connection, with an assertion failure at twext/python/sendmsg.c line 213. This assertion states that CMSG_NXTHDR() returns non-NULL. However, it will only return non-NULL if there is space for another control message. Thus, the assertion always fails after copying the last control message; it should be moved to the beginning of the loop, before CMSG_NXTHDR(). -- Ticket URL: <http://trac.calendarserver.org/ticket/443> Calendar and Contacts Server </> HTTP/WebDAV/CalDAV Server

1 3

[Calendar and Contacts Server] #432: Python2.7 ism in bootstrapdatabase.py
by Calendar and Contacts Server 01 Aug '11

01 Aug '11

#432: Python2.7 ism in bootstrapdatabase.py -------------------------------+-------------------------------------------- Reporter: roland@… | Owner: wsanchez@… Type: Defect | Status: new Priority: 5: Not set | Milestone: CalendarServer-3.0 Component: Calendar Server | Severity: Crash/data loss Keywords: | Radar: -------------------------------+-------------------------------------------- bootstrapdatabase.py uses subprocess.check_output which is new in python2.7. It is possible to use subprocess.check_call. Only the output isn't preserved. -- Ticket URL: <http://trac.calendarserver.org/ticket/432> Calendar and Contacts Server </> HTTP/WebDAV/CalDAV Server

1 4

[Calendar and Contacts Server] #371: better parsing of returned properties would help
by Calendar and Contacts Server 01 Aug '11

01 Aug '11

#371: better parsing of returned properties would help ----------------------------+----------------------------------------------- Reporter: douglm@… | Owner: cdaboo@… Type: Defect | Status: new Priority: 5: Not set | Milestone: Component: CalDAV Tester | Severity: Other Keywords: | ----------------------------+----------------------------------------------- Tests fail with messages like: {{{ Failed Verifier: propfindItems Items not returned in report (OK) for /ucaldav/user/user01/Inbox/: ('urn:ietf:params:xml:ns:caldavschedule-default-calendar-URL', '<href xmlns="DAV:">/ucaldav/user/user01/calendar</href>') Unexpected items returned in report (OK) for /ucaldav/user/user01/Inbox/: (u'urn:ietf:params:xml:ns:caldavschedule- default-calendar-URL', u'<href>/ucaldav/user/user01/calendar/</href>') }}} because of unexpected formats to the response, e.g. {{{ <?xml version="1.0" encoding="UTF-8" ?> <multistatus xmlns="DAV:" xmlns:ns1="urn:ietf:params:xml:ns:caldav" xmlns:ns2="http://www.w3.org/2002/12/cal/ical#"> <response> <href>/ucaldav/user/user01/Inbox/</href> <propstat> <prop> <ns1:schedule-default-calendar-URL> <href>/ucaldav/user/user01/calendar/</href> </ns1:schedule-default-calendar-URL> </prop> <status>HTTP/1.1 200 ok</status> </propstat> </response> </multistatus> }}} -- Ticket URL: <http://trac.calendarserver.org/ticket/371> Calendar and Contacts Server </> HTTP/WebDAV/CalDAV Server

1 3

[Calendar and Contacts Server] #450: Uninformative FATAL ERROR
by Calendar and Contacts Server 01 Aug '11

01 Aug '11

#450: Uninformative FATAL ERROR ----------------------------+----------------------------------------------- Reporter: douglm@… | Owner: cdaboo@… Type: Enhancement | Status: new Priority: 5: Not set | Milestone: Component: CalDAV Tester | Severity: Other Keywords: | Radar: ----------------------------+----------------------------------------------- Some server 'feature' kills the tester with FATAL ERROR: string index out of range Added a traceback print to caldavtest.py except Exception, e: print traceback.format_exc() self.manager.log(manager.LOG_ERROR, "FATAL ERROR: %s" % (e,), before=2) return 0, 1, 0 -- Ticket URL: <http://trac.calendarserver.org/ticket/450> Calendar and Contacts Server </> HTTP/WebDAV/CalDAV Server

1 1

[Calendar and Contacts Server] #440: Release on PyPi
by Calendar and Contacts Server 01 Aug '11

01 Aug '11

#440: Release on PyPi -------------------------------+-------------------------------------------- Reporter: roland@… | Owner: wsanchez@… Type: Enhancement | Status: new Priority: 5: Not set | Milestone: Component: PyKerberos | Severity: Other Keywords: | Radar: -------------------------------+-------------------------------------------- Please release PyKerberos on PyPi. That way it become's easy_install-able. -- Ticket URL: <http://trac.calendarserver.org/ticket/440> Calendar and Contacts Server </> HTTP/WebDAV/CalDAV Server

1 4

[Calendar and Contacts Server] #392: Provide a more descriptive error when log directory is missing
by Calendar and Contacts Server 01 Aug '11

01 Aug '11

#392: Provide a more descriptive error when log directory is missing ---------------------------------+------------------------------------------ Reporter: s.adam@… | Owner: wsanchez@… Type: Enhancement | Status: new Priority: 5: Not set | Milestone: Component: Calendar Server | Severity: Other Keywords: | ---------------------------------+------------------------------------------ CalendarServer 2.4 outputs a long, slightly confusing/misleading error if the log directory is missing: <...> File "/opt/CalendarServer/usr/lib64/python2.6/site- packages/twisted/python/logfile.py", line 32, in __init__ assert os.path.isdir(self.directory) It would be probably be good to have something a bit more clear. -- Ticket URL: <http://trac.calendarserver.org/ticket/392> Calendar and Contacts Server </> HTTP/WebDAV/CalDAV Server

1 1

[Calendar and Contacts Server] #374: Do GET to allow auto-provision?
by Calendar and Contacts Server 01 Aug '11

01 Aug '11

#374: Do GET to allow auto-provision? ----------------------------+----------------------------------------------- Reporter: douglm@… | Owner: cdaboo@… Type: Enhancement | Status: new Priority: 5: Not set | Milestone: Component: CalDAV Tester | Severity: Other Keywords: | ----------------------------+----------------------------------------------- CalDAV/implicitauto1.xml failed during startup until the following get was added after request #4 {{{ <request user="$resourceid1:" pswd="$pswd1:"> <method>GET</method> <ruri>$rcalendarpath1:/</ruri> </request> }}} This allowed the system to auto-provision the resource account -- Ticket URL: <http://trac.calendarserver.org/ticket/374> Calendar and Contacts Server </> HTTP/WebDAV/CalDAV Server

1 1