Hi all,
It needed time and obstinacy to find how to write a test that triggers
the same POSKeyError during commit as triggered by some Plone 3 to 4
migrations.
For more details about the error, see
http://rpatterson.net/blog/poskeyerror-during-commit
The test is now pushed to the 3.10
On Mon, Feb 03, 2014 at 02:50:42PM +0100, Godefroid Chapelle wrote:
It needed time and obstinacy to find how to write a test that
triggers the same POSKeyError during commit as triggered by some
Plone 3 to 4 migrations.
For more details about the error, see
Le 03/02/14 15:12, Marius Gedminas a écrit :
Could you tell us why that test depends on Acquisition? Is it possible
to replicate the bug using pure Python code?
Marius Gedminas
I have not been able to replicate the bug with pure Python code. Reason
why it took me so much time.
IIRC, the
On Mon, Feb 03, 2014 at 03:33:13PM +0100, Godefroid Chapelle wrote:
Le 03/02/14 15:12, Marius Gedminas a écrit :
Could you tell us why that test depends on Acquisition? Is it possible
to replicate the bug using pure Python code?
I have not been able to replicate the bug with pure Python
Le 17/09/13 10:44, Godefroid Chapelle a écrit :
Hi,
Plone 3 to 4 migration occasionally triggers a POSKeyError during
transaction commit. See
http://rpatterson.net/blog/poskeyerror-during-commit
I encountered the issue yesterday.
I committed a test and a fix in branch 3.10.
