- Zope-Dev - Zope lists

Proposal: Eliminating Globals as an import façade
by Tres Seaver 29 Dec '08

29 Dec '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have just checked in work on a separate branch which removes all use of 'Globals' as an indirection for imports within the Zope2 core, restoring the module to its original purpose, which was to hold shared data (e.g., the opened database, etc.). My rationale was that the current usage leads to a confusion of the actual dependencies, as well as oddball anti-patterns based around import cycles, etc. I got started on the task while trying to track down whatever import-time side effect it is which causes the current functional test failures on the trunk. I didn't actually *find* that issue, of course ;(, but I did get back to the staus quo ante. I am more comfortable now that finding those side-effects will be possible. I do restore the importable names in the module for benefit of 3rd party code, but that happens only at Zope2 startup time (for now). I would prefer that folks change that code, but want to leave such products workable indefinitely: at the moment, for instance, the CMF produccts work at appserver startup, although their tests fail (because the BBB is added too late). The branch is here: svn+ssh://svn.zope.org/repos/main/Zope/branches/tseaver-no_globals_imports I would like to merge the branch soon, because it touches lots of files and is likely to hit conflicts if I let it go too long. I am still pondering whether to have the BBB imports done earlier: I really don't want to spew warnings about them, which is why I didn't use the "deferred import" mechanism initially. Thoughts? Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver(a)palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJVmF++gerLs4ltQ4RAlWXAKCi4QDmGsXNG0mVz09DUpCGF2Z9rQCgkcKc 8z9rLwRRaKljOGyXiQTbYdg= =0oTI -----END PGP SIGNATURE-----

3 4

Zope Tests: 4 OK, 2 Failed
by Zope Tests Summarizer 29 Dec '08

29 Dec '08

Summary of messages to the zope-tests list. Period Sun Dec 28 12:00:00 2008 UTC to Mon Dec 29 12:00:00 2008 UTC. There were 6 messages: 6 from Zope Tests. Test failures ------------- Subject: FAILED (failures=1) : Zope-trunk Python-2.4.5 : Linux From: Zope Tests Date: Sun Dec 28 20:36:55 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-December/010739.html Subject: FAILED (failures=1) : Zope-trunk Python-2.5.2 : Linux From: Zope Tests Date: Sun Dec 28 20:38:25 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-December/010740.html Tests passed OK --------------- Subject: OK : Zope-2.8 Python-2.3.7 : Linux From: Zope Tests Date: Sun Dec 28 20:30:51 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-December/010735.html Subject: OK : Zope-2.9 Python-2.4.5 : Linux From: Zope Tests Date: Sun Dec 28 20:32:22 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-December/010736.html Subject: OK : Zope-2.10 Python-2.4.5 : Linux From: Zope Tests Date: Sun Dec 28 20:33:54 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-December/010737.html Subject: OK : Zope-2.11 Python-2.4.5 : Linux From: Zope Tests Date: Sun Dec 28 20:35:25 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-December/010738.html

1 0

Re: [Zope-dev] Sorting for zope.index
by Dan Korostelev 28 Dec '08

28 Dec '08

2008/12/28 Chris McDonough <chrism(a)plope.com>: > BTW, one optimization for fieldindex sorting that I'm fooling around with now > (based on profiling data from a real-world application) is to: > > - Keep around a list of docids in forward value-sorted order. > > - Keey around a list of docids in reverse value-sorted order. > > - Iterate over these lists within a generator when it's an ascending sort with a > limit or when it's a reverse sort; yield back the docids we're passed in the > order implied by the list. > > When I say "list" above, I actually mean some ZODB-friendly data structure that > isn't just a plain Python list (that's actually what I'm fooling around with > creating now). > > FTR, doing this would let us get the KeyError-when-docid-isnt-there behavior > back, and it would make the reverse-sort case (where we use sorted(docids, > key=rev_index.get, reverse=reverse) far less sucky. > > I'll let you know how this goes. I also thought about that. But I'm not sure if we should add it to FieldIndex. It could be a subclass like SortingFieldIndex or something. Because fieldindexes are used wide and zope.index can't depend on something like zope.app.generations for nice migrating. It might be a bit overload when sorting is not needed. Also, the KeyError thing is matter of interface. Even if we create a fieldindex that can efficiently check and raise KeyError, others may not, so I'd leave the interface as it is now. BTW, you might be interested in zc.blist package for the ZODB-friendly balanced lists structure. -- WBR, Dan Korostelev

2 1

Re: [Zope-dev] Sorting for zope.index
by Dan Korostelev 28 Dec '08

28 Dec '08

2008/12/28 Chris McDonough <chrism(a)plope.com>: > IMO, the cognitive cost of maintaining the write-on-read and > by-default-normalize code (imagine someone looking at this code three years from > now) is pretty high. For example, it took me about two or three hours to figure > out that the keyword index case normalization code was added by someone who > didn't really understand what the kw index was actually used for; I thought I > was just missing something. I'm not sure what I'd think if I came across the > write-on-read code; it'll be there forever if we don't take it out now. > Given that we *know* that the kw index and topic index filtered set can't have > been used except for anything but very special-purpose things (they could have > only been used outside the catalog), I think it'd be fine to tell the folks who > used them to how do the one-time upgrade in CHANGES.txt. IMO, of course. I'm generally fine with that. So if there won't be objections until tommorow, I'll make that refactorings and merge that code to trunk. -- WBR, Dan Korostelev

1 0

Zope Tests: 4 OK, 2 Failed
by Zope Tests Summarizer 28 Dec '08

28 Dec '08

Summary of messages to the zope-tests list. Period Sat Dec 27 12:00:00 2008 UTC to Sun Dec 28 12:00:00 2008 UTC. There were 6 messages: 6 from Zope Tests. Test failures ------------- Subject: FAILED (failures=1) : Zope-trunk Python-2.4.5 : Linux From: Zope Tests Date: Sat Dec 27 20:38:05 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-December/010733.html Subject: FAILED (failures=1) : Zope-trunk Python-2.5.2 : Linux From: Zope Tests Date: Sat Dec 27 20:39:35 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-December/010734.html Tests passed OK --------------- Subject: OK : Zope-2.8 Python-2.3.7 : Linux From: Zope Tests Date: Sat Dec 27 20:32:03 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-December/010729.html Subject: OK : Zope-2.9 Python-2.4.5 : Linux From: Zope Tests Date: Sat Dec 27 20:33:34 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-December/010730.html Subject: OK : Zope-2.10 Python-2.4.5 : Linux From: Zope Tests Date: Sat Dec 27 20:35:04 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-December/010731.html Subject: OK : Zope-2.11 Python-2.4.5 : Linux From: Zope Tests Date: Sat Dec 27 20:36:34 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-December/010732.html

1 0

Zope Tests: 4 OK, 2 Failed
by Zope Tests Summarizer 27 Dec '08

27 Dec '08

Summary of messages to the zope-tests list. Period Fri Dec 26 12:00:00 2008 UTC to Sat Dec 27 12:00:00 2008 UTC. There were 6 messages: 6 from Zope Tests. Test failures ------------- Subject: FAILED (failures=1) : Zope-trunk Python-2.4.5 : Linux From: Zope Tests Date: Fri Dec 26 20:39:08 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-December/010727.html Subject: FAILED (failures=1) : Zope-trunk Python-2.5.2 : Linux From: Zope Tests Date: Fri Dec 26 20:40:38 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-December/010728.html Tests passed OK --------------- Subject: OK : Zope-2.8 Python-2.3.7 : Linux From: Zope Tests Date: Fri Dec 26 20:33:07 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-December/010723.html Subject: OK : Zope-2.9 Python-2.4.5 : Linux From: Zope Tests Date: Fri Dec 26 20:34:37 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-December/010724.html Subject: OK : Zope-2.10 Python-2.4.5 : Linux From: Zope Tests Date: Fri Dec 26 20:36:07 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-December/010725.html Subject: OK : Zope-2.11 Python-2.4.5 : Linux From: Zope Tests Date: Fri Dec 26 20:37:37 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-December/010726.html

1 0

Zope Tests: 4 OK, 2 Failed
by Zope Tests Summarizer 26 Dec '08

26 Dec '08

Summary of messages to the zope-tests list. Period Thu Dec 25 12:00:00 2008 UTC to Fri Dec 26 12:00:00 2008 UTC. There were 6 messages: 6 from Zope Tests. Test failures ------------- Subject: FAILED (failures=2) : Zope-trunk Python-2.4.5 : Linux From: Zope Tests Date: Thu Dec 25 20:39:10 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-December/010721.html Subject: FAILED (failures=2) : Zope-trunk Python-2.5.2 : Linux From: Zope Tests Date: Thu Dec 25 20:40:40 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-December/010722.html Tests passed OK --------------- Subject: OK : Zope-2.8 Python-2.3.7 : Linux From: Zope Tests Date: Thu Dec 25 20:33:08 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-December/010717.html Subject: OK : Zope-2.9 Python-2.4.5 : Linux From: Zope Tests Date: Thu Dec 25 20:34:39 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-December/010718.html Subject: OK : Zope-2.10 Python-2.4.5 : Linux From: Zope Tests Date: Thu Dec 25 20:36:10 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-December/010719.html Subject: OK : Zope-2.11 Python-2.4.5 : Linux From: Zope Tests Date: Thu Dec 25 20:37:40 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-December/010720.html

1 0

Zope Tests: 4 OK, 2 Failed
by Zope Tests Summarizer 25 Dec '08

25 Dec '08

Summary of messages to the zope-tests list. Period Wed Dec 24 12:00:00 2008 UTC to Thu Dec 25 12:00:00 2008 UTC. There were 6 messages: 6 from Zope Tests. Test failures ------------- Subject: FAILED (failures=2) : Zope-trunk Python-2.4.5 : Linux From: Zope Tests Date: Wed Dec 24 20:34:48 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-December/010715.html Subject: FAILED (failures=2) : Zope-trunk Python-2.5.2 : Linux From: Zope Tests Date: Wed Dec 24 20:36:18 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-December/010716.html Tests passed OK --------------- Subject: OK : Zope-2.8 Python-2.3.7 : Linux From: Zope Tests Date: Wed Dec 24 20:28:47 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-December/010711.html Subject: OK : Zope-2.9 Python-2.4.5 : Linux From: Zope Tests Date: Wed Dec 24 20:30:17 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-December/010712.html Subject: OK : Zope-2.10 Python-2.4.5 : Linux From: Zope Tests Date: Wed Dec 24 20:31:47 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-December/010713.html Subject: OK : Zope-2.11 Python-2.4.5 : Linux From: Zope Tests Date: Wed Dec 24 20:33:17 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-December/010714.html

1 0

running out of available tcp ports on a zeo cluster
by sathya 25 Dec '08

25 Dec '08

Hello folks, We are testing a zeo cluster in a vmware environment (zeo clients are running on multiple windows 2003 server guest vms). We are using Apache as a load balancer using mod_rewrite (on a separate windows 2003 guest vm ). We are using load runner to generate load After hitting about 40 concurrent users we are getting tcp errors on apache indicating that there are no available ports for accepting connections. It seems like the connections are hanging on for a longer period of time causing the available ports to get exhausted. The errors get worse on increasing the concurrent users. It seems as though there is a problem recycling ports for new connections. Has anybody seen this problem before ? Is there an issue with connections between apache and zope not closing down ? We have run similar tests on linux before and have not faced this problem ( I know, but the client wants windows :( ) Any feedback will be greatly appreciated. Regards sathya -- ZeOmega LLC Integrated Care Management software Frisco Tx 214-618-9880 www.zeomega.com --

1 0

force-connection-close ? what is this used for
by sathya 25 Dec '08

25 Dec '08

Hello folks I have seen this parameter force-connection-close in the http-server section of zope.conf file I cannot grep for this in the source. Does anybody know what this parameter does ? The examples seem to indicate that the default for http-server is "on" whereas for a webdav it is "off". I was curious to know why this was and its effect on tcp connections. Regards sathya -- ZeOmega LLC Integrated Care Management software Frisco Tx 214-618-9880

2 1