Julien Jehannet <julien.jehannet@logilab.fr> [Tue, 01 Jun 2010 17:03:28 +0200] rev 5650
[web] cleanup use of config in web application initialisation
Alexandre Fayolle <alexandre.fayolle@logilab.fr> [Thu, 03 Jun 2010 09:41:41 +0200] rev 5649
fix unit tests by not using the new create_eid implementation with sqlite
Actually, fix a couple of issues with a previous attempt:
* do not use double underscores as method patching will fail with these
* old method must always be used with sqlite regardless of the no_sqlite_wrap attribute
Alexandre Fayolle <alexandre.fayolle@logilab.fr> [Thu, 03 Jun 2010 09:24:41 +0200] rev 5648
cleanup the no_sqlite_wrap attribute after this test is executed
Alexandre Fayolle <alexandre.fayolle@logilab.fr> [Wed, 02 Jun 2010 23:06:38 +0200] rev 5647
merge back on-site fixes
Alexandre Fayolle <alexandre.fayolle@logilab.fr> [Wed, 02 Jun 2010 23:03:35 +0000] rev 5646
various brown paper bag fixes
Alexandre Fayolle <alexandre.fayolle@logilab.fr> [Wed, 02 Jun 2010 18:12:47 +0200] rev 5645
merge
Alexandre Fayolle <alexandre.fayolle@logilab.fr> [Wed, 02 Jun 2010 18:12:27 +0200] rev 5644
fix create_eid for sqlite (and bring back tests)
Alexandre Fayolle <alexandre.fayolle@logilab.fr> [Wed, 02 Jun 2010 17:26:26 +0200] rev 5643
backport improved on-site change
Alexandre Fayolle <alexandre.fayolle@logilab.fr> [Wed, 02 Jun 2010 17:23:42 +0000] rev 5642
TimedCache now only accepts values expressed in seconds
updated ldapuser.py and pyrorql.py to that new interface.
Alexandre Fayolle <alexandre.fayolle@logilab.fr> [Wed, 02 Jun 2010 16:30:36 +0200] rev 5641
backported to stable some changes made on site for a customer
Alexandre Fayolle <alexandre.fayolle@logilab.fr> [Wed, 02 Jun 2010 16:25:12 +0000] rev 5640
logging settings
* document helpful log format when dealing with MT issues
* on Win32, use a logrotate equivalent so that logs get a bit lighter (requires updates logilab.common)
Alexandre Fayolle <alexandre.fayolle@logilab.fr> [Wed, 02 Jun 2010 16:12:18 +0000] rev 5639
[win32] fix deadlock occuring on the sequence tables with SQLServer
actually, this deadlock would occur with any db backend other that PostgreSQL
as the previous code was heavily relying on PG's SEQUENCE facility, not available
elsewhere.
Deadlock description:
Thread1 starts creating entities (and therefore calls create_eid):
-> this creates a DB-level lock on the entities_id_seq table, which
will last until end of transaction
Thread2 calls create_eid, which acquires the Python lock object, but
updating the entities_id_seq is held by the DB lock
Thread1 wants to create a new entity, calls create_eid, and is stuck by
the Python lock object held by Thread2.
Solution:
use a separate connection to read and write the entities_id_seq table.
Alexandre Fayolle <alexandre.fayolle@logilab.fr> [Wed, 02 Jun 2010 16:05:40 +0000] rev 5638
log the user name on session opening for easier debugging
Alexandre Fayolle <alexandre.fayolle@logilab.fr> [Wed, 02 Jun 2010 15:55:58 +0000] rev 5637
more robust handling of looping task configuration in ldap source
* use minimum times
* updated documentation and help strings
* fix the minutes vs. seconds confusion