-
slinkp committed patchset 229 of module ZSyncer to the ZSyncer CVS repository, changing 1 files.
2009-10-23 16:32:11 UTC in ZSyncer
-
slinkp committed patchset 228 of module ZSyncer to the ZSyncer CVS repository, changing 1 files.
2008-06-11 13:39:51 UTC in ZSyncer
-
slinkp committed patchset 227 of module ZSyncer to the ZSyncer CVS repository, changing 1 files.
2007-09-13 14:58:36 UTC in ZSyncer
-
Some questions:
What ZSyncer version are you using? Are you using the same version on both zope instances?
From the traceback it looks like you're pulling from the remote server to the local one.
(where "local" just means the one that you're viewing the UI on.)
Can you confirm that?
Which instance is running out of memory - "local" or "remote"? Or both?
Are you using the ZMI or...
2007-09-13 14:23:27 UTC in ZSyncer
-
See also http://tech.groups.yahoo.com/group/xml-rpc/message/6652
"I have just looked at the Redstone Bas64 decoder and it's obviously
broken. The code correctly ignores whitespace characters but then
complains that the data is too short."
See also http://effbot.org/zone/xmlrpc-errata.htm : "It's okay to split base64-data over multiple lines.".
2007-07-16 15:40:23 UTC in Redstone XML-RPC Library
-
I just posted a relevant message to the xmlrpc mailing list... we'll see what they have to say, if anything. http://tech.groups.yahoo.com/group/xml-rpc/message/6650.
2007-07-13 22:48:19 UTC in Redstone XML-RPC Library
-
Redstone apparently expects base64 data to have no newlines, as per RFC 4648 (http://tools.ietf.org/html/rfc4648#section-3.1 ) or 3548 ( http://tools.ietf.org/html/rfc3548#section-2.1 ).
However, when the xmlrpc spec was written (1999), those RFCs did not exist. The common specification for base64 at the time was MIME (see http://tools.ietf.org/html/rfc2045#section-6.8 ), which specifies a...
2007-07-13 22:40:03 UTC in Redstone XML-RPC Library
-
slinkp committed patchset 226 of module ZSyncer to the ZSyncer CVS repository, changing 3 files.
2007-05-12 18:25:30 UTC in ZSyncer
-
slinkp committed patchset 225 of module ZSyncer to the ZSyncer CVS repository, changing 2 files.
2007-05-12 18:02:26 UTC in ZSyncer
-
Can you try again with current CVS code?
(Just committed now; it might take a while to show up in anonymous checkouts... to verify, check the $Id$ tag in ZSyncer.py, it should be at least "$Id: ZSyncer.py,v 1.101 2007/04/30 04:43:35 slinkp Exp $" ... if you don't see an $Id tag at all, it's too old)
I've written some a test case that should reproduce this bug, and another for
bug 1161733...
2007-04-30 04:49:53 UTC in ZSyncer
