[tests/repository] use the new connection api (part 2/2) Some notes: * module imports cleanup * the unimplemented `test_transaction_interleaved` is wiped

[repository,tests] use the new connection api (part 1/2) `add_info` should not play with the cnxset nor the mode. Static analysis showed that: * add_info is an internal api called with a non-none cnx.cnxset and also in write mode * only the altered test violated this assumption, which is now somewhat documented

[book] fix various parts of the rql section * syntax error * erroneous query * bad sphinx :func: usage

[repository] session -> cnx renaming (already done in the source object)

[tests/session] remove unused import

[tests/datafeed] use the new connection api

[tests/checkintegrity] use the new connection api * serverctl: the db-check command also uses an internal connection object, which makes more sense in the context of `checkintegrity`. * checkintegrity: rename srvcnx to just cnx (a bit because in the near future, there will be one cnx to rule them all)

[tests/schemaserial] kill star import

[tests/schemaserial] break long lines

[tests/ldap] don't leak sessions

[tests/ldap] use the new connection api

[test/migration] fix crash on execution This assertion is there for unclear reasons. ===================== unittest_migration.py ======================= -> creating tables [====================] -> inserting default user and default groups. -> storing the schema in the database [====================] -> database for instance data initialized. F ====================================================================== FAIL: test_db_creation (unittest_migration.BaseCreationTC) make sure database can be created ---------------------------------------------------------------------- Traceback (most recent call last) File "/home/auc/confs/forges/logilab/common/testlib.py", line 661, in _proceed testfunc(*args, **kwargs) File "/home/auc/confs/forges/cubicweb/test/unittest_migration.py", line 106, in test_db_creation handler.build_db_cache() File "/home/auc/confs/forges/cubicweb/devtools/__init__.py", line 469, in build_db_cache self.init_test_database() File "/home/auc/confs/forges/cubicweb/devtools/__init__.py", line 729, in init_test_database init_repository(self.config, interactive=False) File "/home/auc/confs/forges/cubicweb/server/__init__.py", line 217, in init_repository repo = Repository(config, vreg=vreg) File "/home/auc/confs/forges/cubicweb/server/repository.py", line 197, in __init__ self.init_cnxset_pool() File "/home/auc/confs/forges/cubicweb/server/repository.py", line 220, in init_cnxset_pool config.bootstrap_cubes() File "/home/auc/confs/forges/cubicweb/devtools/__init__.py", line 176, in bootstrap_cubes super(TestServerConfiguration, self).bootstrap_cubes() File "/home/auc/confs/forges/cubicweb/server/serverconfig.py", line 279, in bootstrap_cubes self.init_cubes(self.expand_cubes(splitstrip(line))) File "/home/auc/confs/forges/cubicweb/cwconfig.py", line 1022, in init_cubes super(CubicWebConfiguration, self).init_cubes(cubes) File "/home/auc/confs/forges/cubicweb/cwconfig.py", line 798, in init_cubes assert self._cubes is None, repr(self._cubes) AssertionError: ('card', 'file', 'localperms', 'tag')

[web] Remove unreachable and broken code

[testlib] call init_config once the config has been properly bootstraped This should be done right after repository instantiation and as such involves giving CWTC.init_config as a callback to the test database handler (which will itself gives it to the repository initialization function). This unfortunatly requires to pass the init_config method to the server.init_repository function because it has to be called after the config has been initialized (which is done in Repository.__init__) but before the migration handler is instantiated (which will call 'server_maintainance' hook, hence may require the proper config). Another way to fix this would be to change the initialization sequence, but this is another story. Closes #3749378

[devtools] even better: use a plain Connection (server-side) object for pre_setup The previous commit switched from passing a Session to a ClientConnection. This fixes unittest_ldapsource's pre_setup_database, which relied on a server-side object to get at the repo.

[devtools] pre_setup_database should take a connection object

[tests/migration] use the new connection api

[tests/undo] use the new connection api

[js/ajax] deprecate user-callback support Related to #3567793.

EditRelationMixIn: stop using user_rql_callback Add generic add_relation/delete_relation ajax functions and use those. Related to #3567793

[tests/storage] use the new connection api

[tests/security] use the new connection api

[htmlwidgets] Remove unreachable code

Remove redundant __nonzero__ methods From https://docs.python.org/2/reference/datamodel.html#specialnames : When this method is not defined, __len__() is called, if it is defined, and the object is considered true if its result is nonzero. Also helpful for an eventual migration to py3k, as __nonzero__ has been replaced with __bool__, which also defaults to looking at __len__ if undefined.

[etwist] Remove unused host_prefixed_baseurl()

[basetemplate] Remove misleading comment The <base> tag was removed in commit 8bf2337a6f3b back in 2011.

[tests/security] break lines > 100 chars

[doc/3.19] Mention [gs]et_shared_data deprecation

[hooks] internal_session -> internal_cnx (including a typo)

deprecate get/set_shared_data API Session or transaction data must be used instead. We must forward .transaction_data to web/request from which it was missing (this is indeed a _cw object API). Closes #3799036.

[migration] Stop setting session.data['rebuild-infered'] It's no longer read anywhere since fe267b7336f3 "[migration] always rebuild infered relation"

Import PIL modules from the PIL namespace to be Pillow-compatible Closes #3924726

merge two stable heads

merge 3.18.5 into 3.19 branch

merge 3.17.15 into 3.18 branch

[vreg] fix bad super call to lgc.registry.Registry() Registry() expects a debugmode parameter, ovbiously not a cubicweb config object.

Added tag cubicweb-version-3.18.5, cubicweb-debian-version-3.18.5-1, cubicweb-centos-version-3.18.5-1 for changeset 5071b69b6b0b

[pkg] prepare 3.18.5

[sobjects] update notifications system to 3.19 api

[connection] set language on new Connection for the internal manager For regular users this is handled by _set_user, but for internal connections (e.g. used for notifications) we need something else.

Added tag cubicweb-version-3.19.1, cubicweb-debian-version-3.19.1-1, cubicweb-centos-version-3.19.1-1 for changeset 1fe4bc4a8ac8

[pkg] Add missing data files to MANIFEST Fonts and svg were missing from web/data.

[pkg] prepare 3.19.1

[views] new cubicweb logo (closes #3803681) - add the new CubicWeb logo - use it as a css (background-image) - change the color of the header bar (gradient made with css)

[serverctl] rename 'add-source' to 'source-add' for consistency's sake (closes #3732169)

[test/hook] use the new connection API

[testlib] complete the RepoAccess object (closes #3843614) It was missing the open_session call.

[debian] version cubicweb-bootstrap Breaks Apparently 0.6.x is OK with cw 3.19.

[wsgi] Delete unused instance_uri and get_full_path methods on CubicWebWsgiRequest

[test] drop unused import

[sobjects] silent 3.19 warnings in sobjects/supervising.py

[test] update entities/test/unittest_wfobjs to cw 3.19 api

[test] Add missing import to fix old yams warning

[dataimport, migration] silence find_entities / find_one_entity warning Deprecate associated methods to unify the API

[repo] fix extid2entity to ensure connection's has a cnxset else we'll call source.doexec, which attempt to access to cnxset.cu, and crash in some case (eg unittest_cwxmlparser in sobjects/test). Also, manually switch to 'write' mode to ensure cnxset is not released until commit/rollback when some entity is inserted.

[test] update sobjects/test/unittest_cwxmlparser to cw 3.19 api

[repo] make it clear in internal_cnx that security is disabled as explained in its docstring. It was previously relying on internal connection's fake user (InternalManager) for read security and on disabling security hooks for write security. Using the security_enabled context manager is more readable and more reliable: while the older implementation works thanks to the InternalManager associated to the session, custom hooks should rely on session.[read|write]_security being correctly set. This change also allows selecting Password attributes in internal connections without explicitly disabling read security.

[datafeed] update datafeed internals to use connection instead of session

[test] update sobjects/test/unittest_notification to cw 3.19 api

[test] simplify setup of sobjects/test/unittest_supervising.py