Zope-Dev July 2004

zope-dev@zope.dev

51 participants
54 discussions

Re: [Zope-dev] Re: "hasattr" geddon
by Shane Hathaway 18 Aug '04

18 Aug '04

On Saturday 10 July 2004 20:54 pm, Casey Duncan wrote: > Shane Hathaway <shane(a)hathawaymix.org> wrote: > > Why are > > we fixing hasattr and bare excepts when the real problem is ZODB? > > Well, the real problem is *probably* people, but I digress... http://c2.com/cgi/wiki?TheProcessIsTheProblem ;-) > Still, swallowing read conflicts can lead to bugs, even in read-only > tranactions. Consider the following function: > > def getStuffFrom(ob, default): > if hasattr(ob, 'stuff'): > return ob.stuff > return default > > I have seen this idiom about in some zope application/framework code. If > the hasattr results in a read conflict, then it returns false and > default is returned by the function even if ob does have the attribute. > In the example I saw (in DCWorkflow) this would result in the wrong UI > elements being displayed for ob mysteriously. Reloading the page would > likely fix the problem, baffling both the user and app developer, who > now both think Zope is playing with their minds. The change to ZODB that I'm suggesting would fix this. The suppressed conflict error would still mark the transaction as uncommitable. When the publisher calls commit() (which it does on every request even if nothing changed), it would result in a ConflictError, then the publisher would call abort() and the transaction would be retried. Users would never see results from a transaction that had any conflict. Shane

3 2

KeyError in GlobalTranslationService.py
by Russ Ferriday 11 Aug '04

11 Aug '04

I just submitted a patch for Plone 2.0.3 http://plone.org/collector/3329 that stops a KeyError from being triggered in GlobalTranslationService.py when a msgid contains a "$" I think that passing a translation key containing $ should not cause an Error page. So here's a patch for Zope that at least prevents the problem. Translation Service dudes will probably pick big holes in it. Oh, and traceback attached below. The msgid was Ca$hville, the title of a doc. --r. diff GlobalTranslationService.py.orig GlobalTranslationService.py 28,31c28,35 < def repl(m, mapping=mapping): < return ustr(mapping[m.group(m.lastindex)]) < cre = re.compile(r'\$(?:(%s)|\{(%s)\})' % (NAME_RE, NAME_RE)) < return cre.sub(repl, default or msgid) --- > try: > def repl(m, mapping=mapping): > return ustr(mapping[m.group(m.lastindex)]) > cre = re.compile(r'\$(?:(%s)|\{(%s)\})' % (NAME_RE, NAME_RE)) > return cre.sub(repl, default or msgid) > except KeyError: > return msgid Traceback: Site Error An error was encountered while publishing this resource. KeyError Sorry, a site error occurred. Traceback (innermost last): * Module ZPublisher.Publish, line 163, in publish_module_standard * Module ZPublisher.Publish, line 127, in publish * Module Zope.App.startup, line 203, in zpublisher_exception_hook * Module ZPublisher.Publish, line 100, in publish * Module ZPublisher.mapply, line 88, in mapply * Module ZPublisher.Publish, line 40, in call_object * Module Shared.DC.Scripts.Bindings, line 306, in __call__ * Module Shared.DC.Scripts.Bindings, line 343, in _bindAndExec * Module Products.CMFCore.FSPageTemplate, line 191, in _exec * Module Products.CMFCore.FSPageTemplate, line 124, in pt_render * Module Products.PageTemplates.PageTemplate, line 96, in pt_render <FSPageTemplate at /testdollarproblem/document_view used for /testdollarproblem/foo> * Module TAL.TALInterpreter, line 189, in __call__ * Module TAL.TALInterpreter, line 233, in interpret * Module TAL.TALInterpreter, line 663, in do_useMacro * Module TAL.TALInterpreter, line 233, in interpret * Module TAL.TALInterpreter, line 408, in do_optTag_tal * Module TAL.TALInterpreter, line 393, in do_optTag * Module TAL.TALInterpreter, line 388, in no_tag * Module TAL.TALInterpreter, line 233, in interpret * Module TAL.TALInterpreter, line 663, in do_useMacro * Module TAL.TALInterpreter, line 233, in interpret * Module TAL.TALInterpreter, line 605, in do_loop_tal * Module TAL.TALInterpreter, line 233, in interpret * Module TAL.TALInterpreter, line 408, in do_optTag_tal * Module TAL.TALInterpreter, line 393, in do_optTag * Module TAL.TALInterpreter, line 388, in no_tag * Module TAL.TALInterpreter, line 233, in interpret * Module TAL.TALInterpreter, line 629, in do_condition * Module TAL.TALInterpreter, line 233, in interpret * Module TAL.TALInterpreter, line 552, in do_insertTranslation * Module TAL.TALInterpreter, line 615, in translate * Module Products.PageTemplates.TALES, line 263, in translate * Module Products.PageTemplates.GlobalTranslationService, line 31, in translate * Module Products.PageTemplates.GlobalTranslationService, line 29, in repl KeyError: 'hville' (Also, an error occurred while attempting to render the standard error message.) ————————————————————— Russ Ferriday Solution Workshops for Plone (+44) (0) 7789 338868 http://www.solutionworkshops.com

2 1

Collector Status Meanings
by Chris Withers 10 Aug '04

10 Aug '04

Hi All, Apologies for the cross-posting, but I think this is relevent to all these lists. I've summarised the meaning of the various collector states here: http://dev.zope.org/CVS/CollectorStatuses Please let me know if you disagre with any of that, although I'm pretty sure they're right and will argue with anyone who thinks otherwise ;-) The only real change is that Deferred now means "we asked the user for more information and we'll reject the issue unless they give it to us within a month" I went through all the issues which WERE deferred and "dealt" with them. I'm trying to avoid having states where issues end up that aren't definitive and so get forgotten about. The "wontfix" stuff now has a definitve meaning, but it may still be good to go through them all once a year or so to check that none of them have been solved in other ways. I found quite a few of the "deferred" ones that really should have been "wontfix" had been addressed and could now be marked as resolved :-) cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk

8 9

Making a ZSQL.DA fully multi-threaded?
by Brad Clements 08 Aug '04

08 Aug '04

I am using ZsapdbDA with SAPDB (now MaxDB) and have run into problems when Zope has more than one thread. The folks at SAP suggest that there should be one database connection per thread, rather than sharing one connection across threads. I haven't yet looked at the Zsapdb source, but I think it has only one connection for all threads. Is there a document somewhere that explains how to make variables "thread private" in Zope? I vaguely recall something about one cache per thread, or that variables are read- only shared unless updated by a thread, and then they're copied.. This is probably quite wrong, but obviously I just don't understand how data and threading works in Zope. So, I'm looking for a document that explains this clearly. How to have data that is not shared between threads (perhaps a kind of connection pool thingy). Also, I have other projects where I really want to have just one object of it's kind no matter how many threads. For example, gvibDA uses Thunked_TM for this, but that doesn't really work with ZSQLDA because I've seen that multiple connect calls are made, even with the THUNKED_TM. Is there a "Zen Of" document about this somewhere? Thanks -- Brad Clements, bkc(a)murkworks.com (315)268-1000 http://www.murkworks.com (315)268-9812 Fax http://www.wecanstopspam.org/ AOL-IM: BKClements

7 26

July Bug Day Roundup
by Chris Withers 31 Jul '04

31 Jul '04

Hi All, A pretty frenetic bug day saw a LOT of cruft ejected from the collector. It also saw a good few bugs resolved, and a lot more marked as resolved that had been fixed along the way. Also, there's now documentation of what the various collector states mean at: http://dev.zope.org/CVS/CollectorStatuses Some points of it are still up for discussion, so please join in at zope-coders(a)zope.org if you have a view! All in all, a massive 64 issues were dealt with! Many thanks to all who helped out, look forward to seeing as many of you as possible for the next one at the end of August... cheers, Chris Here's what got dealt with (there are "player stats" at the bottom ;-) Resolved: #13 - Undo with multiple ZEO´s mounted #248 - refresh does not work for products initialized in the old style #290 - Usage of trry: except: in Zope source #515 - Collecor.__init__ stores new brains class in volatile attribute #552 - Import obj w/ Proxy roles into Zope w/o role fails #578 - ImplicitAcquisitionWrapper claim to be callable() #691 - KeywordIndex and callable #692 - DateTime fails to pass european dates #740 - _tzoffset returns wrong offset #891 - Enable locking of RESPONSE.setStatus and RESPONSE.setBody #1156 - getObject fails to return objects which redefine __len__ #1233 - ZOPE_CONFIG environment var for app=Zope.app() #1252 - VIRTUAL_URL #1279 - --config-file support for test.py #1295 - 2.7.0 tutorial Lesson 6 #1370 - customDefaultZPTReport.dtml Creates Invalid HTML #1416 - DateTime class doesn't initialize off DateTime instance #1421 - DateTime doesn't always raise a SyntaxError for bad dates #1439 - Zope 2.7.2 for Windows uses Python 2.3.3 #1440 - Zope 2.7.2 lists as "unreleased version" #1441 - Silly Borg Headers tempt MS Office #1442 - Example cache sizes in zope.conf, using MB or kB #1445 - test.py problems with -p and -v(v) Rejected: #18 - sequence-last inducts error when used in nested dtml-in #37 - Z ODBC Database with DB2 TIMESTAMP# #50 - DCO2 based ZOracle Adapter does not use bind variables #154 - Zope crashes on external method loading dll #229 - Paste object without view permission on management screen #237 - Version editing via FTP/WebDAV #247 - permission strings in ZMI aren't consistently capitalized #418 - DTML anonymizes exceptions #522 - "Owned" assumes access to the ObjectManagerItem Interface #717 - support selection:{type} in manage_propertiesForm #746 - dtml-sendmail expected string, unicode found #775 - manage_changeProperties can't set boolean properties to false #1223 - Problem with meta_type #1308 - (duplicate) Need "actual URL" method #1361 - (duplicate) etag header obliterated no matter what #1378 - ExtensionClass Bug: unbound C method... #1391 - tal: namspace attributes dropped before i18n processing #1404 - envirnoment and cgi_environment don't appear to work #1419 - Transience should return True|False, not 1|0 #1424 - Zope returns 400 to report an internal error #1427 - Accept config file from stdin #1444 - (duplicate) ZODB Error from Historical Compare #1446 - TAL parse error on tags inside script #1449 - DateTime wrong when 12:00:00AM #1448 - "cache picture and css mixing" Wontfix: #15 - sqlgroup.py enhancements - set, noparens, and comma tags #127 - css files defines absolut sizes #136 - FTP Upload raises Unauthorized after file upload #371 - DTML and Python security function APIs are different #553 - ZMI "find" doesnt find in File with text #564 - Content-length of HEAD responses should be based on *parsed* #729 - Edit page title tag should show the object title or id #872 - Numbers in STX Tables #1277 - manage_FTPget of Image is sad. #1428 - Serve xml as application/xml instead of text/xml Deferred: (meaning act on these or they get rejected next month) #428 - FTP and large file uploads #526 - anonymous users can sometimes view historical revisions #804 - "make clean" doesn't run #1398 - BTree raise SystemError on FreeBSD #1401 - SystemError in SessionDataManager And here's the "player stats" ;-) Resolved Rejected Wontfixed Deferred Assists chrisw 16 19 7 2 ajung 6 6 2 2 ctheune 1 1 2 arnarl 5 shh 2 casey 2 jim 1 evan 1 mcdonc 1 stevea 1 brian 1 -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk

2 1

Are input streams seekable in Zope?
by Ames Andreas (MPA/DF) 30 Jul '04

30 Jul '04

Hi, I've stumbled over some code in Zope 2.7.0 that seems to suggest that input streams are meant to be seekable. In an extension I wrote for ZServer, i.e. AJPServer, I throw an exception when this is tried and I'm quite sure the call to seek wasn't there in 2.6.x. I found the call to seek in ZPublisher.HTTPRequest.py, line 128, in method "retry". Does this mean that only seekable streams are allowed in ZPublisher (i.e. not stdin) or is this a bug? TIA, andreas

3 2

Re: [ZC] 1223/ 8 Reject "Problem with meta_type"
by Chris Withers 30 Jul '04

30 Jul '04

Gareth Bult wrote: > > Out here in the real world, in this specific case, apparently it doesn't > make things worse .. I go from not working at all, to working apparently > 100% .. without having to scrap my DB or write code to scan for items > with missing meta_types and create them... In your real world maybe ;-) Where there are hundreds to thousands of hits per second, it starts making a difference... >>*shrugs* I'd personally prefer to make the one line patch in the product >>that's missing a meta type in it's class definition ;-) > > And what about all the pre-existing objects with no meta-type ??? If the meta_type is added as a class variable, as they usually are, all your pre-existing object will have that attribute as soon as you restart Zope. Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk

1 0

Re: [ZC] 1223/ 8 Reject "Problem with meta_type"
by Chris Withers 30 Jul '04

30 Jul '04

Gareth Bult wrote: >>Actually, this should be rejected. A Zope object without a meta_type has some pretty serious issues ;-) > > Interesting statement - not that I disagree .. but my question is - does > a Zope that crashes when it could (with a one-line change) be made not > to crash have *more* serious issues ? > (I guess developers are going to say "no", but I'm a user - I say > "yes" !) your suggested one line change could have implications such as reduced data integrity and other unexpected behaviour. So, I'd say "yes" too, except your one-line change makes things worse ;-) > fyi; Not that I'm saying it's a proper solution or one that should be > implemented, but I've seen no ill effects in 5 months and around 3 > million hits re; the suggested patch. > (which for me is one up on repeated nasty site crashes .. ) *shrugs* I'd personally prefer to make the one line patch in the product that's missing a meta type in it's class definition ;-) Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk

1 0

ZClass to FS Class conversion magic?
by Taylor, Monty 28 Jul '04

28 Jul '04

Hi all, So I'm working a project with a bunch of ZClasses. (It's got a _bunch_ of DTML, too, but that's a whole different story) I'd like to replace the ZClasses with Python Filesystem based classes. The problem comes with the instantiated objects of the ZClasses. I have tried making a fake ZClass, instantiating it, and the replacing the ZClass with a Python class, but I can seem to get the object to associate with the new class. I've used the same class names and meta_type type stuff. Is there a magic __something variable I need to set somewhere, or some other magic I can do to register a class to replace the ZClass. (I would obviously have to delete the ZClass) Any ideas? I don't ever screw with ZClasses, prefering emacs and cvs, so I don't have too much zen with them. Thanks! Monty "Bringing people together to advance their lives." NOTICE: The information contained in this electronic mail transmission is intended by TMP Interactive Inc. d/b/a Monster or one of its subsidiaries for the use of the named individual or entity to which it is addressed and may contain information that is privileged or otherwise confidential. It is not intended for transmission to, or receipt by, any individual or entity other than the named addressee (or a person authorized to deliver it to the named addressee) except as otherwise expressly permitted in this electronic mail transmission. If you have received this electronic transmission in error, please delete it without copying or forwarding it, and notify the sender of the error by reply email or by calling Monster at 1-800-MONSTER.

1 0

svn checkins failing?
by Chris McDonough 28 Jul '04

28 Jul '04

When I attempt to commit any change to the head of the Zope2 repo in SVN, I get the following: svn: Commit failed (details follow): svn: Berkeley DB error while opening 'uuids' table for filesystem /svn/repos/main/db: Cannot allocate memory svn: Your commit message was left in a temporary file: svn: '/home/chrism/software/Trunk/svn-commit.tmp' Is anyone else having problems?

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

Zope-Dev July 2004