Re: [Zope-dev] Preliminary findings: Zope 2.7 leakage caused by errors

2004-05-20 Thread Dieter Maurer
[EMAIL PROTECTED] wrote at 2004-5-19 14:44 -0400: ... In following to the discussions regarding the leakage zope.org and my site suffer from, I've done some testing, and here's what I've found. First of all, the leak does seem to occur when errors occur. Unlike what Chris suggested, I still

Re: [Zope-dev] Preliminary findings: Zope 2.7 leakage caused by errors

2004-05-20 Thread Dieter Maurer
[EMAIL PROTECTED] wrote at 2004-5-19 14:44 -0400: ... Right now I've focused on finding out why the Requests are still around. Using the gc module, I've found that all leaked requests are being held by a dictionary. If I look at said dictionaries, this is what they might look like: {'REQUEST':

Re: [Zope-dev] Preliminary findings: Zope 2.7 leakage caused by errors

2004-05-20 Thread Andreas Jung
I have not followed the discussion but is this leak as serious as it should be resolved before the next 2.7.1 beta1 release? Andreas --On Donnerstag, 20. Mai 2004 9:52 Uhr +0200 Dieter Maurer [EMAIL PROTECTED] wrote: [EMAIL PROTECTED] wrote at 2004-5-19 14:44 -0400: ... Right now I've focused

[Zope-dev] Re: [ZPT] RFC: TALES adapters and TAL/Tales variable namespaces

2004-05-20 Thread Jim Fulton
Evan Simpson wrote: Jim Fulton wrote: I've posted two proposals: http://dev.zope.org/Zope3/TALESPathExpressionAdapters Proposes a mechanism for easily using adapters in TALES expressions. I'm not at all clear on how the proposed mechanism is superior to the implementation of path segment

Re: [Zope-dev] Read-only root database doesn't work ... bug or feature?

2004-05-20 Thread robert rottermann
Paul Winkler wrote: I'm trying to figure out how to mount my main storage read-only with zope 2.7.0. I'm starting to suspect that it's impossible. I tried a few things below - ATTEMPT #1. I find this in the zope.conf examples: # Directive:

RE: [Zope-dev] Preliminary findings: Zope 2.7 leakage caused by e rrors

2004-05-20 Thread Jean-Francois . Doyon
Dieter, Thanks yet again for all the valuable input. I've started tracking down/running into the whole ExtensionClasses instances/issues. As you suggest, the dict is probably help by BaseRequest.RequestContainer, which I've seen grow in parallel to the HTTPRequest refcounts ... Which seems to

RE: [Zope-dev] Re: Preliminary findings: Zope 2.7 leakage caused by errors

2004-05-20 Thread Jean-Francois . Doyon
Juan David, I'm using 1.0.1 ... I'm just abotu to try and test with 1.1.0a3 ... BTW, does that mean it's alpha software or something? is 1.1.0 stable? If the problem comes from Localizer I suspect this patch might be the cause: def new_publish(request, module_name, after_list, debug=0):

Re: [Zope-dev] Re: Preliminary findings: Zope 2.7 leakage caused by errors

2004-05-20 Thread J. David Ibáñez
The a in 1.1.0a3 means alpha. If the problem is in Localizer 1.0.1 I think it will be in 1.1.0a3 too. Yes, I have a site with a similar behaviour, unfortunately today the network connection is too slooow, so I can't test that site. I'm going to do some local tests, though. Yes, the problem might

Re: [Zope-dev] Read-only root database doesn't work ... bug or feature?

2004-05-20 Thread Paul Winkler
On Thu, May 20, 2004 at 10:53:35AM +0200, robert rottermann wrote: Paul Winkler wrote: I'm trying to figure out how to mount my main storage read-only with zope 2.7.0. I'm starting to suspect that it's impossible. (snip) we had a simmilar problem. Eventually we spved it by patching zope.

RE: [Zope-dev] Re: Preliminary findings: Zope 2.7 leakage caused by errors

2004-05-20 Thread Jean-Francois . Doyon
Juan David, OK, 1.1.0a3 indeed suffers from the same problem, I'm going to take a closer look the the publishing mechanism to see if I can find anything relevant. Thanks, J.F. -Original Message- From: J. David Ibáñez [mailto:[EMAIL PROTECTED] Sent: May 20, 2004 10:17 AM To: [EMAIL

[Zope-dev] Re: [ZPT] RFC: TALES adapters and TAL/Tales variable namespaces

2004-05-20 Thread Evan Simpson
Jim Fulton wrote: I thought you had proposed this, but I couldn't find a proposal or documentation. You say this is implemented in Zope 2? Where is it documented? Actually, it's only implemented on evan-pathprefix-branch. It has been quite a while since I had a chance to work on it, so I had

[Zope-dev] Re: [ZPT] RFC: TALES adapters and TAL/Tales variable namespaces

2004-05-20 Thread Jim Fulton
Evan Simpson wrote: Jim Fulton wrote: I thought you had proposed this, but I couldn't find a proposal or documentation. You say this is implemented in Zope 2? Where is it documented? Actually, it's only implemented on evan-pathprefix-branch. It has been quite a while since I had a chance to

[Zope-dev] Re: [ZPT] RFC: TALES adapters and TAL/Tales variable namespaces

2004-05-20 Thread Evan Simpson
Jim Fulton wrote: I don't inderstand what motivated the special expression types for this namespace. For example, to get at file-system based code, couldn't you have used the modules variable? I started there, but went with the special expression types because the set of things that are valid

RE: [Zope-dev] Re: Preliminary findings: Zope 2.7 leakage caused by errors

2004-05-20 Thread Dieter Maurer
[EMAIL PROTECTED] wrote at 2004-5-20 09:58 -0400: ... def new_publish(request, module_name, after_list, debug=0): id = get_ident() print Localizer got thread id: + str(id) Publish._requests[id] = request print Request dict is now: + str(Publish._requests) x =

Re: [Zope-dev] Preliminary findings: Zope 2.7 leakage caused by errors

2004-05-20 Thread Dieter Maurer
Andreas Jung wrote at 2004-5-20 10:02 +0200: I have not followed the discussion but is this leak as serious as it should be resolved before the next 2.7.1 beta1 release? I doubt that it is a Zope bug... I am unable to reproduce any leak in connection with error handling. Otherwise, we can only

RE: [Zope-dev] Re: Preliminary findings: Zope 2.7 leakage caused by errors

2004-05-20 Thread Jean-Francois . Doyon
Indeed, I was hoping the ref in the dictionary there was getting in the way when old_publish was raising an exception, but I tried using a weakref.proxy() instead and that didn't help. I managed to test without Localizer (It dawned on me that since I'm looking at errors, it really doesn't matter