[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

backport stable

[tableview / facets] to work properly with facet, initial table should handle case where actualrql isn't specified

[test] generated html differs w/ pygments version

[storage] source's callback has a new prototype, update usage

grmbl

grmbl

backport stable

cleanup

[external storage] refactor to give session to storage's callback (needed by vcsfile storage)

[navigation] use pageContent instead of paginated-content as default div id, paginated-content doesn't seems used anymore

[test] update test to follow recent navigation/facets fixes

[tableview] use pageContent instead of paginated-content as default div id, paginated-content doesn't seems used anymore

[sparql] improve error reporting and fix one bug

[test] add missing __main__ as expected by apycot pyunit checker

[tableview] don't fail with AttributeError when paginated as main content view

[facet] we must add type restriction for attribute facets as well

[tableview] support for json-paginated table if paginable

[navigation] view may implements page_navigation_url to handle them self url generated for pagination

[navigation] when there are to much results, use a <select> based page navigation

[primary] add missing version number to deprecation warnings

[sparql] fix type inference (test_dctitle_both_project_cwuser) and support for <http://www.w3.org/1999/02/22-rdf-syntax-ns#type tag (test_base_rdftype)

[form] remove double property call

cleanups

[sparql] add failing test for two entities with dc:title

[sparql] adding test for "rdf:type -> is"

proof read documentation some clarifications, some typo fixes, and a couple of other strings fixed on the way

skip flymake junk when reloading this avoids nasty ex aequo scores in selectors in dev. mode

merge back to stable some changes made on site for a customer.

[win32 SQLServer] connection lost detection The pyodbc driver when connected to SQLServer 2005 reports lost connections in a quite strange way, raising a pyodbc.Error exception with a specific exc.args value. This patch catches these and reconnect properly.

ldap: reset cache when a user is deleted When a user is deleted from ldap, reset both caches used by the source otherwise the search is not performed again and exceptions such as UnknownEid: No entity with eid 74078 in the repository will occur

ldap source logging Added some extra logging statement to understand what happens in the ldap source.

forbid looping tasks with an interval of 0 This severly harm the server, and generally are the result of a baaad configuration file. We want to stop the server asap when this is detected to give people a chance to fix the configuration.

/siteinfo page: display information about the names of the running threads

[win32 service] activate logging to the configured file as soon as possible since we don't always have access to the system events of the computer running CW it is important to get as much information as possible in the log file, especially startup failure messages.

[bfss] Rename filenames according to their metadata on entity update.

[form] missing return...

[adapters] fix NameError introduced by adapters refactoring

[security] fix security insertion on DISTINCT queries

[adapters] fix bad copy and past....

backport stable

[rql2sql] properly compute scope for variable from temporary tables

[form] fix bw compat issue introduced by 5588:377c9adfe81e

[web] update to 3.9 Entity api