[Zope-dev] Bad Marshal Data

2002-03-27 Thread seb bacon
I've asked this before, about a year ago, but got no response. Does anyone else ever see 'bad marshal data' errors sometimes? What are they a symptom of? It sometimes happens in my products, other times in Zope. It always occurs on import statements. I usually manage to fix it by playing

Re: [Fwd: [Zope-dev] Re: more on the segfault saga]

2002-03-27 Thread Matthew T. Kromer
Martijn Jacobs wrote: Hello Leo! Tell us if your segfaults go away and whether Zope performance is impacted by it. The segfault is AWAY! I have an uptime of 2 hours now, it has never been so long since it's in use! I don't notice any performance differences, but I also have to say that I

Re: [Zope-dev] OpenSSH configuration between ZEO clients storage server

2002-03-27 Thread Shane Hathaway
Itamar Shtull-Trauring wrote: Toby Dickenson wrote: but ssh port forwarding is only one layer of TCP. ssh port forwarding is good. I'mp pretty sure it's TCP over TCP (ssh protocol does multiplexing). SSL OTOH is not TCP over TCP. I think you are mistaken. :-) The site you referred

Re: [Zope-dev] OpenSSH configuration between ZEO clients storageserver

2002-03-27 Thread Itamar Shtull-Trauring
Shane Hathaway wrote: But you don't need reliability compensation to multiplex. SSH assumes the transport layer is reliable. So an SSH tunnel and an SSL tunnel are virtually synonymous. They're not really, but yeah, I was wrong :) A SSL forwarder takes a packet, and then sends over

Re: [Zope-dev] ZClass Constructor Cleanup for 2.6

2002-03-27 Thread Matt Behrens
Casey Duncan wrote: Does anyone see a problem with changing the default generated constructor method for ZClasses to a python script in Zope 2.6? I think we are encouraging really bad style by keeping this in DTML, since it is purely business logic. Thoughts? I will, of course,

Re: [Zope-dev] ZClass Constructor Cleanup for 2.6

2002-03-27 Thread Leonardo Rochael Almeida
On Wed, 2002-03-27 at 17:31, Casey Duncan wrote: I don't think this is a big enough change to warrant a real proposal, so I'll shoot this out here: Does anyone see a problem with changing the default generated constructor method for ZClasses to a python script in Zope 2.6? I think we

Re: [Zope-dev] Bad Marshal Data

2002-03-27 Thread Leonardo Rochael Almeida
I haven't seen anything like that. What I have seen, an which scares the heck out of me everytime I see it is UnpicklingErrror, which, in my case, usually happens when the _p_jar dictionary doesn't have an object that other parts of zope swear they exist. The solution to that usually involves

Re: [Zope-dev] ZClass Constructor Cleanup for 2.6

2002-03-27 Thread Casey Duncan
Good point, I'll add that to my list. -Casey Leonardo Rochael Almeida wrote: On Wed, 2002-03-27 at 17:31, Casey Duncan wrote: I don't think this is a big enough change to warrant a real proposal, so I'll shoot this out here: Does anyone see a problem with changing the default generated

ZCatalogPathAware (was Re: [Zope-dev] ZClass Constructor Cleanup for 2.6)

2002-03-27 Thread Matt Behrens
Leonardo Rochael Almeida wrote: ZClasses have been overlooked enough. Nobody has even bothered putting a ZCatalogPathAware available for them... I tried do to this quickly for someone on IRC once. The problem is that the mixin is identically named for CatalogAwareness and

[Zope-dev] Crashing problem? Python workaround?!

2002-03-27 Thread Matthew T. Kromer
Hey fellow Zopistas: If you're still experiencing crashing problems with Python 2.1.2, and Zope, please consider trying the following test: From a clean Python build tree, modify Include/object.h line 587. #define PyTrash_UNWIND_LEVEL 50 make this read #define PyTrash_UNWIND_LEVEL 500

re: [Zope-dev] Crashing problem? Python workaround?!

2002-03-27 Thread Martijn Jacobs
Hi Matt, Leo Pythonlabs found this today after much assistance from the folks on #zope on the irc.openprojects.net system; particularly, Leonardo Rochael Almeida's assistance has been extremely valuable in isolating this problem. And jus to say it again : thank you all again!! You've