[querier] test and fix potential bug in insertion query with multiple relations inside, caused by a name conflict. Also fix another bug non reproduced by using a set instead of a list (list may leads to compare entity instances which isn't allowed).

[form] avoid spurious warning subsequent for form's action refactoring w/ autoforms

backport stable

[web test] Add a CubicWebServerTC class to run test with a cw web serveur available.

[web server] vregistry may now be passed as named argument in CubicWebRootResource constructor This will be needed to start an http server for testing purpose. Also, server run command has now a debug name argument to set debug mode explicitly

[etwist] twisted won't install signal handler outside the main thread. This patch avoid some warning about this issue.

[vreg] ensure you can register an object from module not known yet. This ease registration of arbitrary objects during testing.

[web] cleanup use of config in web application initialisation

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

cleanup the no_sqlite_wrap attribute after this test is executed

merge back on-site fixes

various brown paper bag fixes

merge

fix create_eid for sqlite (and bring back tests)

backport improved on-site change

TimedCache now only accepts values expressed in seconds updated ldapuser.py and pyrorql.py to that new interface.

backported to stable some changes made on site for a customer

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)

[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.

log the user name on session opening for easier debugging

more robust handling of looping task configuration in ldap source * use minimum times * updated documentation and help strings * fix the minutes vs. seconds confusion

backport stable

[rql2sql] fix scope computation of variable from temporary table

stop being dumb please