Mon, 29 Apr 2013 12:29:59 +0200 [test/notification] merge related test classe
Pierre-Yves David <pierre-yves.david@logilab.fr> [Mon, 29 Apr 2013 12:29:59 +0200] rev 8955
[test/notification] merge related test classe They have no reason to be distinct.
Mon, 29 Apr 2013 11:43:36 +0200 merge with stable
Pierre-Yves David <pierre-yves.david@logilab.fr> [Mon, 29 Apr 2013 11:43:36 +0200] rev 8954
merge with stable
Tue, 16 Apr 2013 16:51:18 +0200 [server] add a looping task to free unused cnxsets capture by dead pyro stable cubicweb-centos-version-3.16.4-1 cubicweb-debian-version-3.16.4-1 cubicweb-version-3.16.4
Julien Cristau <julien.cristau@logilab.fr> [Tue, 16 Apr 2013 16:51:18 +0200] rev 8953
[server] add a looping task to free unused cnxsets capture by dead pyro When a pyro client disconnects, we're not necessarily notified so they can hang on to their session/cnxset forever. Don't let them do that. The hacky looping task is only installed when pyro is enabled. This optional activation save this very hacky patch from being rejected. closes #2825380
Mon, 29 Apr 2013 11:22:21 +0200 [pkg/debian] update changelog to 3.17.0
Pierre-Yves David <pierre-yves.david@logilab.fr> [Mon, 29 Apr 2013 11:22:21 +0200] rev 8952
[pkg/debian] update changelog to 3.17.0
Mon, 29 Apr 2013 11:06:28 +0200 [devtools] Use XMLValidator instead deprecated SaxOnlyValidator
Pierre-Yves David <pierre-yves.david@logilab.fr> [Mon, 29 Apr 2013 11:06:28 +0200] rev 8951
[devtools] Use XMLValidator instead deprecated SaxOnlyValidator The renaming was introduced in 198fdadafed6.o This prevent a meta class conflict introduced by logilab-common 0fcd2e050621.
Fri, 26 Apr 2013 18:47:36 +0200 [pkg] update changelog
Pierre-Yves David <pierre-yves.david@logilab.fr> [Fri, 26 Apr 2013 18:47:36 +0200] rev 8950
[pkg] update changelog
Fri, 26 Apr 2013 18:37:47 +0200 [pkg] prepare 3.17.0
Pierre-Yves David <pierre-yves.david@logilab.fr> [Fri, 26 Apr 2013 18:37:47 +0200] rev 8949
[pkg] prepare 3.17.0
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.
(0) -3000 -1000 -300 -100 -50 -30 +30 +50 +100 +300 +1000 +3000 tip