Wed, 29 Sep 2010 16:46:47 +0200 fix merge, some buffers weren't saved...
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 29 Sep 2010 16:46:47 +0200] rev 6367
fix merge, some buffers weren't saved...
Wed, 29 Sep 2010 16:16:32 +0200 backport stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 29 Sep 2010 16:16:32 +0200] rev 6366
backport stable
Wed, 29 Sep 2010 14:22:12 +0200 [test] must now commit file creation since the later ValidationError trigger a rollback stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 29 Sep 2010 14:22:12 +0200] rev 6365
[test] must now commit file creation since the later ValidationError trigger a rollback
Wed, 29 Sep 2010 12:54:35 +0200 cleanup and micro-optimization stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 29 Sep 2010 12:54:35 +0200] rev 6364
cleanup and micro-optimization
Wed, 29 Sep 2010 12:53:30 +0200 [web action] has_editable_relations should not filter out final relations, fix regression introduced in 6358:22c95c5ef12d stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 29 Sep 2010 12:53:30 +0200] rev 6363
[web action] has_editable_relations should not filter out final relations, fix regression introduced in 6358:22c95c5ef12d
Wed, 29 Sep 2010 12:44:11 +0200 [c-c] fix RuntimeError: 'maximum recursion depth exceeded while calling a Python object' we get when creating/upgrading/shelling an instance: hasattr() call __getattribute__, creating an infinite recursion error catched by the interpretor. Avoid this by testing the method is available on the class instead of the instance stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 29 Sep 2010 12:44:11 +0200] rev 6362
[c-c] fix RuntimeError: 'maximum recursion depth exceeded while calling a Python object' we get when creating/upgrading/shelling an instance: hasattr() call __getattribute__, creating an infinite recursion error catched by the interpretor. Avoid this by testing the method is available on the class instead of the instance
Wed, 29 Sep 2010 12:18:06 +0200 [transaction] to avoid potential db corruption, we should rollback systematically in case of ValidationError stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 29 Sep 2010 12:18:06 +0200] rev 6361
[transaction] to avoid potential db corruption, we should rollback systematically in case of ValidationError
Wed, 29 Sep 2010 12:17:26 +0200 [selector] cleanup stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 29 Sep 2010 12:17:26 +0200] rev 6360
[selector] cleanup
(0) -3000 -1000 -300 -100 -30 -10 -8 +8 +10 +30 +100 +300 +1000 +3000 tip