Fri, 26 Apr 2013 18:21:18 +0200 [pkg] prepare 3.16.4 stable
Pierre-Yves David <pierre-yves.david@logilab.fr> [Fri, 26 Apr 2013 18:21:18 +0200] rev 8948
[pkg] prepare 3.16.4
Fri, 26 Apr 2013 18:06:44 +0200 [repo] straightforward bootstrap sequence. Closes #2841188
Sylvain Thénault <sylvain.thenault@logilab.fr> [Fri, 26 Apr 2013 18:06:44 +0200] rev 8947
[repo] straightforward bootstrap sequence. Closes #2841188 * kill fill_schema method which was doing to much different things, in favor of a deserialize_method which is simply reading schema from the db and returning it * set_schema doesn't bother with cubes This allows to easilly follow what's going on and so to cleanup init_cnxset_pool to get the following boostrap order: 1. load cubes (implies loading site_cubicweb) 2. load schema 3. init data sources 4. init cnx sets
Wed, 24 Apr 2013 14:49:49 +0200 [repo] minor cleanups to bootstrap sequence
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 24 Apr 2013 14:49:49 +0200] rev 8946
[repo] minor cleanups to bootstrap sequence * fix some docstring/comments * move initialization of HooksManager to the __init__.py, this has nothing to do with pool initialization / boostraping
Fri, 26 Apr 2013 17:46:56 +0200 [schemaserial] serialize additional yams parameter for customs type
Vincent Michel <vincent.michel@logilab.fr> [Fri, 26 Apr 2013 17:46:56 +0200] rev 8945
[schemaserial] serialize additional yams parameter for customs type Yams have a new custom type feature. We add support for extra parameter on CWAttribute in schema serialization handling. Closes #2847151
Tue, 23 Apr 2013 14:13:58 +0200 [sql] preprocess_entity uses lgdb helper's SQL converters.
Vincent Michel <vincent.michel@logilab.fr> [Tue, 23 Apr 2013 14:13:58 +0200] rev 8944
[sql] preprocess_entity uses lgdb helper's SQL converters. The preprocess_entity does not yield anymore the conversion logic for different base types, but relies on a new SQL_CONVERTERS dictionary of the db helper. This will allow later inclusion of new base types.
Wed, 24 Apr 2013 14:42:43 +0200 [repo] kill rebuildinfered feature from Repository.set_schema
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 24 Apr 2013 14:42:43 +0200] rev 8943
[repo] kill rebuildinfered feature from Repository.set_schema This clutters thing and is useless in most cases: when schema just have been readen from the database or from the file-system, infered relations have just be calculated. The only use-case where it should be rebuilt is on migration (ie schema modification by editing the meta-model using rql), so move this feature there.
Wed, 24 Apr 2013 14:51:06 +0200 [test] stop deepcopying for nothing
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 24 Apr 2013 14:51:06 +0200] rev 8942
[test] stop deepcopying for nothing
Fri, 26 Apr 2013 12:10:37 +0200 drop xhtml content-type support (closes #2065651)
Aurelien Campeas <aurelien.campeas@logilab.fr> [Fri, 26 Apr 2013 12:10:37 +0200] rev 8941
drop xhtml content-type support (closes #2065651) * HTMLStream does not care about xml any more * reqquest.demote_to_html and .xhtml_browser are deprecated * web config: drop force-html-content-type option * adjust tests
Fri, 26 Apr 2013 11:53:47 +0200 [htmlparser] exclude <script> tag from html source
Pierre-Yves David <pierre-yves.david@logilab.fr> [Fri, 26 Apr 2013 11:53:47 +0200] rev 8940
[htmlparser] exclude <script> tag from html source lxml are confused by them :-(
Fri, 26 Apr 2013 11:52:35 +0200 [htmlparser] store unaltered source in pageinfo.source
Pierre-Yves David <pierre-yves.david@logilab.fr> [Fri, 26 Apr 2013 11:52:35 +0200] rev 8939
[htmlparser] store unaltered source in pageinfo.source Do not store the parser to preserve the source aspect. Store the initial input in the source argument instead. This is very useful when parsing html. In such case we need to drop ``<script>`` tag.
Thu, 25 Apr 2013 18:38:47 +0200 [htmlparser] rename SaxOnlyValidator to XMLValidator
Sylvain Thénault <sylvain.thenault@logilab.fr> [Thu, 25 Apr 2013 18:38:47 +0200] rev 8938
[htmlparser] rename SaxOnlyValidator to XMLValidator
Thu, 25 Apr 2013 17:46:28 +0200 [htmlparser] add missing deprecation message
Sylvain Thénault <sylvain.thenault@logilab.fr> [Thu, 25 Apr 2013 17:46:28 +0200] rev 8937
[htmlparser] add missing deprecation message
Thu, 25 Apr 2013 16:55:12 +0200 [form] remove hard coded id
Pierre-Yves David <pierre-yves.david@logilab.fr> [Thu, 25 Apr 2013 16:55:12 +0200] rev 8936
[form] remove hard coded id html id should be unique. It is clearly not achieved here.
Fri, 26 Apr 2013 11:08:06 +0200 [server/test] use server config in migration
Pierre-Yves David <pierre-yves.david@logilab.fr> [Fri, 26 Apr 2013 11:08:06 +0200] rev 8935
[server/test] use server config in migration This allows a lighter initialisation (no rtag needed). Execution of those test move from 300 secondes to 220 seconds here. A 25% speedup
Mon, 22 Apr 2013 17:57:46 +0200 [session] deprecate `hijack_user` method
Pierre-Yves David <pierre-yves.david@logilab.fr> [Mon, 22 Apr 2013 17:57:46 +0200] rev 8934
[session] deprecate `hijack_user` method The semantic of this method is wicked and lead to very hard violation of sanity. (multiple transaction using the very same cursors). We deprecated the API to be able to drop it as soon as possible. The method was added long ago for some notification trick. It is not needed since we sent notification on ``postcommit_event``. (closes #2781782)
Thu, 25 Apr 2013 12:24:26 +0200 [mail] drop hijack_user usage
Pierre-Yves David <pierre-yves.david@logilab.fr> [Thu, 25 Apr 2013 12:24:26 +0200] rev 8933
[mail] drop hijack_user usage The transaction is now commited before notification. We can create a new session directly and drop `hijack_user` usage. This prepare #2781782
Thu, 25 Apr 2013 13:35:02 +0200 [notification] merge BaseNotificationView and NotificationView
Pierre-Yves David <pierre-yves.david@logilab.fr> [Thu, 25 Apr 2013 13:35:02 +0200] rev 8932
[notification] merge BaseNotificationView and NotificationView They are in the same module now.
Thu, 25 Apr 2013 13:34:48 +0200 [notification] move notification view in ``sobject.notification``
Pierre-Yves David <pierre-yves.david@logilab.fr> [Thu, 25 Apr 2013 13:34:48 +0200] rev 8931
[notification] move notification view in ``sobject.notification`` It has no user outside this module. This enforce serversideness of notification and allow future cleanup. No backward compat is set up to prevent circular import. The class has no other user anyway. (closes 2845144)
Thu, 25 Apr 2013 14:10:55 +0200 remove unused import
Pierre-Yves David <pierre-yves.david@logilab.fr> [Thu, 25 Apr 2013 14:10:55 +0200] rev 8930
remove unused import pyflakes say they are unused. Tests suite confirms.
Thu, 25 Apr 2013 17:30:09 +0200 one more merge
Pierre-Yves David <pierre-yves.david@logilab.fr> [Thu, 25 Apr 2013 17:30:09 +0200] rev 8929
one more merge
Thu, 25 Apr 2013 16:10:56 +0200 [notification] introduce an official `notify_on_commit` function
Sylvain Thénault <sylvain.thenault@logilab.fr> [Thu, 25 Apr 2013 16:10:56 +0200] rev 8928
[notification] introduce an official `notify_on_commit` function It provides a proper notification api instead of replacing it by yet another clumsy one. Closes #2837251
Thu, 25 Apr 2013 10:57:01 +0200 [cubicweb/doc] Replace dc_type() by cw_etype
Vladimir Popescu <vladimir.popescu@logilab.fr> [Thu, 25 Apr 2013 10:57:01 +0200] rev 8927
[cubicweb/doc] Replace dc_type() by cw_etype dc_type() is may be translated. Leading to terrible terrible damage.
Thu, 04 Apr 2013 11:58:41 +0200 [dataimport] backout 6947201033be (related to #2788402)
Vladimir Popescu <vladimir.popescu@logilab.fr> [Thu, 04 Apr 2013 11:58:41 +0200] rev 8926
[dataimport] backout 6947201033be (related to #2788402) (and add a try: except to cache the intended error) The problem actually comes from the ``MassiveObjectStore`` in the ``dataio`` cube, so it should be corrected there. Here, we only protect it with a ``RuntimeWarning`` so that the user can see the problem. ``value`` is set to ``None`` (whence to ``NULL`` from a database standpoint), so that the data can be nevertheless inserted in the database. However, only the keys present in ``row`` are actually non-'``NULL``'. The real solution is to work out the issue in ``MassiveObjectStore`` directly. The current try/except should only be a temporary hack.
Thu, 25 Apr 2013 15:45:38 +0200 merge default heads
Sylvain Thénault <sylvain.thenault@logilab.fr> [Thu, 25 Apr 2013 15:45:38 +0200] rev 8925
merge default heads
Fri, 05 Apr 2013 14:44:03 +0200 [c-c serverctl] import locally to speed up c-c
Sylvain Thénault <sylvain.thenault@logilab.fr> [Fri, 05 Apr 2013 14:44:03 +0200] rev 8924
[c-c serverctl] import locally to speed up c-c
Thu, 25 Apr 2013 12:12:15 +0200 [facet js] minor refactoring and cleanups
Sylvain Thénault <sylvain.thenault@logilab.fr> [Thu, 25 Apr 2013 12:12:15 +0200] rev 8923
[facet js] minor refactoring and cleanups * extract facetCheckBoxSelect and facetCheckBoxUnselect * use $ as prefix for jQuery variable (facet -> $facet) * other minor rephrasing
Wed, 24 Apr 2013 18:11:37 +0200 [ldapfeed] Add support for LDAP groups (closes #2528116)
David Douard <david.douard@logilab.fr> [Wed, 24 Apr 2013 18:11:37 +0200] rev 8922
[ldapfeed] Add support for LDAP groups (closes #2528116) Groups from the LDAP server are imported as CWGourp entities, and in_group relationships are created between existing CWUsers and CWGroups Unit tests have been refactored a bit, especially ti add helper methods to manage LDAP database.
Wed, 24 Apr 2013 17:57:14 +0200 [test/ldap] small improvement to ldapfeed unit tests
Pierre-Yves David <pierre-yves.david@logilab.fr> [Wed, 24 Apr 2013 17:57:14 +0200] rev 8921
[test/ldap] small improvement to ldapfeed unit tests better group testing and further testing of imported user life cycle.
Wed, 24 Apr 2013 17:48:08 +0200 [ldap] prepare import of CWGroup
David Douard <david.douard@logilab.fr> [Wed, 24 Apr 2013 17:48:08 +0200] rev 8920
[ldap] prepare import of CWGroup All CWUser specific code is put in dedicated sections.
Wed, 24 Apr 2013 17:40:49 +0200 [ldap] handle modification date
Pierre-Yves David <pierre-yves.david@logilab.fr> [Wed, 24 Apr 2013 17:40:49 +0200] rev 8919
[ldap] handle modification date We are now able to import modification date from ldap.
Wed, 24 Apr 2013 17:39:10 +0200 [ldap] refactor attributes mapping handling
Pierre-Yves David <pierre-yves.david@logilab.fr> [Wed, 24 Apr 2013 17:39:10 +0200] rev 8918
[ldap] refactor attributes mapping handling * use explicit attributes lists when calling ldap search * direct and reverse attributes maps contains now the same elements.
Wed, 24 Apr 2013 14:00:52 +0200 [ldapfeed] add support for multiple email addresses from ldap
Pierre-Yves David <pierre-yves.david@logilab.fr> [Wed, 24 Apr 2013 14:00:52 +0200] rev 8917
[ldapfeed] add support for multiple email addresses from ldap Multiple emails case was ignored before this change. email test
Wed, 24 Apr 2013 15:37:43 +0200 merge 3.16.x fix in 3.17.x branch
Pierre-Yves David <pierre-yves.david@logilab.fr> [Wed, 24 Apr 2013 15:37:43 +0200] rev 8916
merge 3.16.x fix in 3.17.x branch
Wed, 24 Apr 2013 15:33:49 +0200 [session] fix hooks_control backward compat
Pierre-Yves David <pierre-yves.david@logilab.fr> [Wed, 24 Apr 2013 15:33:49 +0200] rev 8915
[session] fix hooks_control backward compat Session object have no ``hooks_control`` control method. it has ``allow_all_hooks_but`` and ``deny_all_hooks_but`` ones. Regression introduced in bd5b5759c9b3.
Fri, 19 Apr 2013 16:25:45 +0200 [facet js] fix reordering of facet check boxes. Closes #2732947 stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Fri, 19 Apr 2013 16:25:45 +0200] rev 8914
[facet js] fix reordering of facet check boxes. Closes #2732947 Before this patch, when one select an element, it's moved to the top of the select content. Fine. But when it's later deselected, it stays there instead of moving back to its original location. This patch fixes that by introducing a facetCheckBoxReorder function which properly reorder the whole facet, instead of buggy attempt to locally reorder.
Wed, 24 Apr 2013 14:40:09 +0200 [vreg] (re)build entity classes cache after registry initialization. stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 24 Apr 2013 14:40:09 +0200] rev 8913
[vreg] (re)build entity classes cache after registry initialization. This fix potential memory fragmentation issue. Closes #2719113
Wed, 24 Apr 2013 12:10:12 +0200 [task] allow negative intervals for add_looping_task (closes #2818280)
Julien Cristau <julien.cristau@logilab.fr> [Wed, 24 Apr 2013 12:10:12 +0200] rev 8912
[task] allow negative intervals for add_looping_task (closes #2818280) Instead of rejecting values < 0 with a ValueError, we ignore tasks with a negative interval. This introduce a simple way to disable task from configuration.
Wed, 24 Apr 2013 11:58:49 +0200 [task] allow interval=0 for looping tasks
Pierre-Yves David <pierre-yves.david@logilab.fr> [Wed, 24 Apr 2013 11:58:49 +0200] rev 8911
[task] allow interval=0 for looping tasks There is valid usecase for perpetual running task.
Wed, 24 Apr 2013 14:45:13 +0200 [portable dump] skip virtual relations, they have no table associated. Closes #2841199 stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 24 Apr 2013 14:45:13 +0200] rev 8910
[portable dump] skip virtual relations, they have no table associated. Closes #2841199
Wed, 24 Apr 2013 14:37:48 +0200 [test] fix skipIf import, currently failing if unittest2 is not there stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 24 Apr 2013 14:37:48 +0200] rev 8909
[test] fix skipIf import, currently failing if unittest2 is not there
Wed, 24 Apr 2013 14:36:41 +0200 [test] fix bad merge stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 24 Apr 2013 14:36:41 +0200] rev 8908
[test] fix bad merge
Tue, 23 Apr 2013 18:15:10 +0200 merge with other default head
Pierre-Yves David <pierre-yves.david@logilab.fr> [Tue, 23 Apr 2013 18:15:10 +0200] rev 8907
merge with other default head
Tue, 23 Apr 2013 16:07:02 +0200 [ldap] an empty 'user-base-dn' disable the user importation process,
Pierre-Yves David <pierre-yves.david@logilab.fr> [Tue, 23 Apr 2013 16:07:02 +0200] rev 8906
[ldap] an empty 'user-base-dn' disable the user importation process, The same semantic will be used for group. We start by using it for user for the sake of consistency.
Tue, 23 Apr 2013 15:46:09 +0200 drop commented print
Pierre-Yves David <pierre-yves.david@logilab.fr> [Tue, 23 Apr 2013 15:46:09 +0200] rev 8905
drop commented print
Tue, 23 Apr 2013 16:50:18 +0200 [ldap] Major test refactoring
Pierre-Yves David <pierre-yves.david@logilab.fr> [Tue, 23 Apr 2013 16:50:18 +0200] rev 8904
[ldap] Major test refactoring Mostly fix tests (previous refactoring), but also refactor a bit the base class to have better/simpler interaction with the slapd server.
Tue, 23 Apr 2013 17:58:20 +0200 [test/ldap] have RQL2LDAPFilterTC use its own database
Pierre-Yves David <pierre-yves.david@logilab.fr> [Tue, 23 Apr 2013 17:58:20 +0200] rev 8903
[test/ldap] have RQL2LDAPFilterTC use its own database I do not know what RQL2LDAPFilterTC is about and why it does this strange reuse of LDAPUserSourceTC pre_setup_database but it is certainly a good idea to have it use a dedicated database-cache.
Tue, 23 Apr 2013 16:25:56 +0200 [ldap] quieter tests
Pierre-Yves David <pierre-yves.david@logilab.fr> [Tue, 23 Apr 2013 16:25:56 +0200] rev 8902
[ldap] quieter tests Capture slapadd and slapd output if everything goes well.
Wed, 10 Apr 2013 17:50:11 +0200 [test/ldap source] better source naming, some cleanups (prepares #2528116)
Jérôme Roy [Wed, 10 Apr 2013 17:50:11 +0200] rev 8901
[test/ldap source] better source naming, some cleanups (prepares #2528116) ldap uri becomes "ldap" in all cases prepare separation of CONFIGs by source type
(0) -3000 -1000 -300 -100 -48 +48 +100 +300 +1000 +3000 tip