[SciPy-Dev] few patches for your consideration

Warren Weckesser warren.weckesser@enthought....
Mon Apr 5 14:42:44 CDT 2010


Yaroslav Halchenko wrote:
> Dear all,
>
> since my humble attempt to provide patches via mailing list has
> failed (noone followed) I've tried to open  a ticket on trac but got:
>
> Oops…
> Trac detected an internal error:
>
> OperationalError: database is locked
>   


I've been getting that error a lot lately.  I've reported it to our IT 
guy, Aaron, but I don't know if he's had time to look at it or what 
conclusion he's reached if he has looked at it.

I usually just try again--eventually it works.

Warren

> There was an internal error in Trac. It is recommended that you inform your local Trac administrator and give him all the information he needs to reproduce the issue.
>
> To that end, you could ==== How to Reproduce ==== While doing a POST operation on `/newticket`, Trac issued an internal error. ''(please provide additional details here)'' Request parameters: {{{ {'__FORM_TOKEN': u'ac193bbb6eeef1400267b402', 'attachment': u'on', 'field_cc': u'', 'field_component': u'Other', 'field_description': u"String formatting is errorneous while raising exceptions in those files. Also those messages better be more informative. Thus I am providing a bugfix patch + enhancement patch for those.\r\n\r\nThey are also available from my git clone:\r\n\r\nhttp://github.com/yarikoptic/scipy3/commit/0cef22c0342faf8e70d84dd4008dc5ee44f365d4\r\nBUG: use correct string formatting in raising depending on info from lapack\r\n\r\nhttp://github.com/yarikoptic/scipy3/commit/4feb14edcb9d6efdb307fc14c351aab41bad69f4\r\nENH: a bit more of information upon failure in LinAlgError's from lapack\r\n", 'field_keywords': u'', 'field_milestone': u'0.8.0', 'field_priority': u'normal', 'field_status': u'new', 'field_summary': u'fix "unsupported format character" while raising exceptions in scipy/linalg/basic.py scipy/linalg/decomp.py', 'field_type': u'defect', 'field_version': u'0.7.0', 'submit': u'Create ticket'} }}} User Agent was: `Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.8) Gecko/20100308 Iceweasel/3.5.8 (like Firefox/3.5.8)` ==== System Information ==== || '''Trac''' || `0.11.3` || || '''Python''' || `2.4.3 (#1, Jan 21 2009, 01:11:33) ` [[br]] `[GCC 4.1.2 20071124 (Red Hat 4.1.2-42)]` || || '''setuptools''' || `0.6c7` || || '''SQLite''' || `3.3.6` || || '''pysqlite''' || `2.3.3` || || '''Genshi''' || `0.5.1` || || '''Subversion''' || `1.4.6 (r28521)` || || '''jQuery:''' || `1.2.6` || ==== Python Traceback ==== {{{ Traceback (most recent call last): File "/srv/scipy/python-packages/lib/python2.4/site-packages/Trac-0.11.3-py2.4.egg/trac/web/main.py", line 435, in _dispatch_request dispatcher.dispatch(req) File "/srv/scipy/python-packages/lib/python2.4/site-packages/Trac-0.11.3-py2.4.egg/trac/web/main.py", line 205, in dispatch resp = chosen_handler.process_request(req) File "/srv/scipy/python-packages/lib/python2.4/site-packages/Trac-0.11.3-py2.4.egg/trac/ticket/web_ui.py", line 183, in process_request return self._process_newticket_request(req) File "/srv/scipy/python-packages/lib/python2.4/site-packages/Trac-0.11.3-py2.4.egg/trac/ticket/web_ui.py", line 394, in _process_newticket_request self._do_create(req, ticket) # (redirected if successful) File "/srv/scipy/python-packages/lib/python2.4/site-packages/Trac-0.11.3-py2.4.egg/trac/ticket/web_ui.py", line 981, in _do_create ticket.insert() File "/srv/scipy/python-packages/lib/python2.4/site-packages/Trac-0.11.3-py2.4.egg/trac/ticket/model.py", line 204, in insert db.commit() OperationalError: database is locked }}} a ticket.
>
> The action that triggered the error was:
>
> POST: /newticket
>
> Obviously I couldnt' file a bug report against this issue for the same reason.
>
> is there possibly a 3rd way to submit patches (mail be via snail mail)?
>
> Cheers,
> Yarik
> On Fri, 12 Mar 2010, Yaroslav Halchenko wrote:
>
>   
>> Hi Everyone,
>>     
>
>   
>> Being lazy and git spoiled I am exposing tentative BUG: and  ENH:
>> commits upon your consideration:
>>     
>
>   
>> http://github.com/yarikoptic/scipy3/commit/0cef22c0342faf8e70d84dd4008dc5ee44f365d4
>> BUG: use correct string formatting in raising depending on info from lapack
>>     
>
>   
>> http://github.com/yarikoptic/scipy3/commit/4feb14edcb9d6efdb307fc14c351aab41bad69f4
>> ENH: a bit more of information upon failure in LinAlgError's from lapack
>>     
>
>   
>> P.S. If I get a RW commit to SVN I would be happy to dcommit, or if you
>> instruct so I could file 'Pull request' into David's github clone, but since it
>> is just git-svned, not sure if it wouldn't create more problems than would
>> provide benefits.
>>     




More information about the SciPy-Dev mailing list