Hello Kristoffer, The problem you reported should be fixed as of r15350: http://trac.calendarserver.org/changeset/15350/CalendarServer/trunk My latest client sim runs show none of the 'unicode value for key not allowed' tracebacks like the ones you mentioned. Cheers, -dre
On Nov 30, 2015, at 1:26 PM, Andre LaBranche <dre@apple.com> wrote:
Hello,
Thanks for this report. I see the same thing when using a remote postgres DB. It appears to be a problem with how the DBAPI driver is initialized.
This also reveals a problem with our client simulator, which does not throw a red flag if it's configured for push, the server supports push, and the client sims never get any pushes. This is why we missed the other bug.
Stay tuned :)
-dre
On Nov 25, 2015, at 7:53 AM, Kristoffer Møllerhøj <kmo@one.com> wrote:
Hi,
I observed a problem when running the development build of CalendarServer-7.0 using an external PostgreSQL database. Errors like the following shows up:
2015-11-11 14:25:59+0100 [-] [caldav-0] [-] [twext.enterprise.jobs.jobitem#error] JobItem: 72, WorkItem: 72 failed: [Failure instance: Traceback: <type 'exceptions.TypeError'>: Unicode value for key 'id' not allowed: u'/CalDAV/localhost/10000000-0000-0000-0000-000000000001/calendar/'
When running the same setup with internal PostgreSQL database everything seems to work fine. Have anybody else observed this problem?
I also created a bugreport: http://trac.calendarserver.org/ticket/923
Best regards, Kristoffer Møllerhøj.
_______________________________________________ calendarserver-users mailing list calendarserver-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/calendarserver-users
_______________________________________________ calendarserver-users mailing list calendarserver-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/calendarserver-users