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

[CalendarServer] #302: twistedcaldav.pdmonster.PDClientAddressWrapper#error
by CalendarServer 14 Aug '08

14 Aug '08

#302: twistedcaldav.pdmonster.PDClientAddressWrapper#error -------------------------------------------+-------------------------------- Reporter: aaron.grattafiori(a)microvu.com | Owner: wsanchez(a)apple.com Type: Defect | Status: new Priority: 3: Important | Milestone: Component: Calendar Server | Version: Severity: Other | Keywords: -------------------------------------------+-------------------------------- When connecting with sunbird 0.8 to CalendarServer rev. 2766 I A LOT of the following errors: 2008-08-01 15:31:30+0000 [-] [caldav-8889] [AMP,client] [twistedcaldav.pdmonster.PDClientAddressWrapper#error] Unknown Port: IPv4Address(TCP, 'a.b.c.d', 53427) 2008-08-01 15:31:30+0000 [-] [caldav-8889] [AMP,client] [twistedcaldav.pdmonster.PDClientAddressWrapper#error] Unknown Port: IPv4Address(TCP, 'a.b.c.d', 53427) 2008-08-01 15:31:30+0000 [-] [caldav-8889] [AMP,client] [twistedcaldav.pdmonster.PDClientAddressWrapper#error] Unknown Port: IPv4Address(TCP, 'a.b.c.d', 53427) 2008-08-01 15:31:30+0000 [-] [caldav-8889] [AMP,client] [twistedcaldav.pdmonster.PDClientAddressWrapper#error] Unknown Port: IPv4Address(TCP, 'a.b.c.d', 53427) 2008-08-01 15:31:30+0000 [-] [caldav-8889] [AMP,client] [twistedcaldav.pdmonster.PDClientAddressWrapper#error] Unknown Port: IPv4Address(TCP, 'a.b.c.d', 53427) 2008-08-01 15:31:30+0000 [-] [caldav-8889] [AMP,client] [twistedcaldav.pdmonster.PDClientAddressWrapper#error] Unknown Port: IPv4Address(TCP, 'a.b.c.d', 53427) (where a.b.c.d is my internal IP address) I am running CalendarServer on Debian 4.0 Etch GNU/Linux. Previously several months ago on a testing Ubuntu Linux server this was not happening. These errors do not seem to block functionality of the server but something isn't right. Can these be safely ignored or is there something I need to configure? Thanks, -Aaron -- Ticket URL: <https://trac.calendarserver.org/ticket/302> CalendarServer </> HTTP/WebDAV/CalDAV Server

1 1

[CalendarServer] #287: Breaks with python-vobject 0.6.6
by CalendarServer 14 Aug '08

14 Aug '08

#287: Breaks with python-vobject 0.6.6 -----------------------------+---------------------------------------------- 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: -----------------------------+---------------------------------------------- When replacing python-vobject 0.6.0 by 0.6.6 one gets and exception when trying to add a new appointment. Exception is attached to this report. This is calendarserver 1.2 -- Ticket URL: <http://trac.calendarserver.org/ticket/287> CalendarServer </> HTTP/WebDAV/CalDAV Server

1 10

3 lines of patch to HACKING/schema doc
by Karl Goetz 14 Aug '08

14 Aug '08

Hi all, I have a small patch (should be valid for 72 hrs in pastebin) at [1]. It fixes a typo and removes a redundant "dont't", so its nothing to exciting. I'm still hoping its worth submitting though, Thanks, kk [1] http://paste.debian.net/14213/ -- Karl Goetz <karl(a)kgoetz.id.au>

2 2

Re: [CalendarServer-dev] [CalendarServer] #207: Recurring events do not appear to extend beyond November 2008
by CalendarServer 14 Aug '08

14 Aug '08

#207: Recurring events do not appear to extend beyond November 2008 ------------------------------------+--------------------------------------- Reporter: dekkerdreyer(a)gmail.com | Owner: sagen(a)apple.com Type: Defect | Status: reopened Priority: 1: Blocker | Milestone: 2.x Component: Calendar Server | Version: Severity: Serious | Resolution: Keywords: | ------------------------------------+--------------------------------------- Changes (by wsanchez(a)apple.com) * status: closed => reopened * resolution: fixed => Comment: Whoops, wrong ticket -- Ticket URL: <https://trac.calendarserver.org/ticket/207#comment:9> CalendarServer </> HTTP/WebDAV/CalDAV Server

1 0

Re: [CalendarServer-dev] [CalendarServer] #207: Recurring events do not appear to extend beyond November 2008
by CalendarServer 14 Aug '08

14 Aug '08

#207: Recurring events do not appear to extend beyond November 2008 ------------------------------------+--------------------------------------- Reporter: dekkerdreyer(a)gmail.com | Owner: sagen(a)apple.com Type: Defect | Status: closed Priority: 1: Blocker | Milestone: 2.x Component: Calendar Server | Version: Severity: Serious | Resolution: fixed Keywords: | ------------------------------------+--------------------------------------- Changes (by wsanchez(a)apple.com) * status: new => closed * resolution: => fixed Comment: r2825 -- Ticket URL: <https://trac.calendarserver.org/ticket/207#comment:8> CalendarServer </> HTTP/WebDAV/CalDAV Server

1 0

Re: [CalendarServer-dev] [CalendarServer] #207: Recurring events do not appear to extend beyond November 2008
by CalendarServer 13 Aug '08

13 Aug '08

#207: Recurring events do not appear to extend beyond November 2008 ------------------------------------+--------------------------------------- Reporter: dekkerdreyer(a)gmail.com | Owner: sagen(a)apple.com Type: Defect | Status: new Priority: 1: Blocker | Milestone: 2.x Component: Calendar Server | Version: Severity: Serious | Resolution: Keywords: | ------------------------------------+--------------------------------------- Comment (by apm(a)one.com) Suggestion for solution posted to -dev list. Please comment. -- Ticket URL: <http://trac.calendarserver.org/ticket/207#comment:7> CalendarServer </> HTTP/WebDAV/CalDAV Server

1 0

Re: [CalendarServer-dev] [CalendarServer] #161: CalendarServer doesn't delete stray sockets on startup
by CalendarServer 05 Aug '08

05 Aug '08

#161: CalendarServer doesn't delete stray sockets on startup --------------------------------+------------------------------------------- Reporter: wsanchez(a)apple.com | Owner: wsanchez(a)apple.com Type: Defect | Status: new Priority: 1: Blocker | Milestone: 2.x Component: Calendar Server | Version: Severity: Crash/data loss | Resolution: Keywords: | --------------------------------+------------------------------------------- Comment (by wsanchez(a)apple.com) As I said, no good reason for the logs dir; we should fix that. You don't need an apple.com email address to submit patches. We all have our priorities; if this is important to you, the best thing you can do to make progress on it is to submit a patch. -- Ticket URL: <http://trac.calendarserver.org/ticket/161#comment:8> CalendarServer </> HTTP/WebDAV/CalDAV Server

1 0

Re: [CalendarServer-dev] [CalendarServer] #161: CalendarServer doesn't delete stray sockets on startup
by CalendarServer 04 Aug '08

04 Aug '08

#161: CalendarServer doesn't delete stray sockets on startup --------------------------------+------------------------------------------- Reporter: wsanchez(a)apple.com | Owner: wsanchez(a)apple.com Type: Defect | Status: new Priority: 1: Blocker | Milestone: 2.x Component: Calendar Server | Version: Severity: Crash/data loss | Resolution: Keywords: | --------------------------------+------------------------------------------- Comment (by aaron.grattafiori(a)microvu.com) Replying to [comment:6 wsanchez(a)apple.com] > "Why are the sockets in the logs directory?" > > No good reason there; should be in /var/run. > Changing the default path in the config file fixed the pid and sockets being in the wrong place. (They are now in {{{/var/run/caldavd}}}) [[BR]] I fail to see why the "logs" directory was chosen for anything other than logs or remains the default[[BR]] > "Why hasn't this been fixed a long time ago?" > > Might be because you haven't submitted a patch fixing this yet.[[BR]] Is this a problem with Twisted or CalendarServer? Seems like they are cleaning up sockets here: http://twistedmatrix.com/trac/browser/trunk/twisted/internet/unix.py?rev=24… [[BR]] Has the year been spent waiting for someone to submit a patch? My email address doesn't end in apple.com -- Ticket URL: <http://trac.calendarserver.org/ticket/161#comment:7> CalendarServer </> HTTP/WebDAV/CalDAV Server

1 0

Re: [CalendarServer-dev] [CalendarServer] #161: CalendarServer doesn't delete stray sockets on startup
by CalendarServer 03 Aug '08

03 Aug '08

#161: CalendarServer doesn't delete stray sockets on startup --------------------------------+------------------------------------------- Reporter: wsanchez(a)apple.com | Owner: wsanchez(a)apple.com Type: Defect | Status: new Priority: 1: Blocker | Milestone: 2.x Component: Calendar Server | Version: Severity: Crash/data loss | Resolution: Keywords: | --------------------------------+------------------------------------------- Changes (by wsanchez(a)apple.com) * owner: dreid(a)apple.com => wsanchez(a)apple.com Comment: "Why are the sockets in the logs directory?" No good reason there; should be in /var/run. "Why hasn't this been fixed a long time ago?" Might be because you haven't submitted a patch fixing this yet. -- Ticket URL: <https://trac.calendarserver.org/ticket/161#comment:6> CalendarServer </> HTTP/WebDAV/CalDAV Server

1 0

Re: [CalendarServer-dev] [CalendarServer] #161: CalendarServer doesn't delete stray sockets on startup
by CalendarServer 01 Aug '08

01 Aug '08

#161: CalendarServer doesn't delete stray sockets on startup --------------------------------+------------------------------------------- Reporter: wsanchez(a)apple.com | Owner: dreid(a)apple.com Type: Defect | Status: new Priority: 1: Blocker | Milestone: 2.x Component: Calendar Server | Version: Severity: Crash/data loss | Resolution: Keywords: | --------------------------------+------------------------------------------- Comment (by aaron.grattafiori(a)microvu.com) "If all of the stray socket files in the logs directory are deleted, then and only then does CalendarServer start up correctly." Why are the sockets in the logs directory? Why hasn't this been fixed a long time ago? -- Ticket URL: <http://trac.calendarserver.org/ticket/161#comment:5> CalendarServer </> HTTP/WebDAV/CalDAV Server

1 0