[ZODB-Dev] POSKeyError when transaction.commit after savepoint.rollback and connection.readCurrent

[Marius Gedminas]

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
> http://rpatterson.net/blog/poskeyerror-during-commit
> 
> The test is now pushed to the 3.10 branch on github :
> 
> https://github.com/zopefoundation/ZODB/commit/49919d31cfa73410cede0af969d80527a9fd852c
> 
> The fix is pushed as well.
> 
> https://github.com/zopefoundation/ZODB/commit/9ce470f70acc9655aaf915e5a74678b43f6312da
...
> - As the test above depends on Acquisition (which is not ported to
> Python 3), what should be the strategy to include my work in master
> ? Pull the fix only ? Pull the fix and do some magic with the test
> so that it runs only in Python 2 ? Other suggestion ?

Could you tell us why that test depends on Acquisition?  Is it possible
to replicate the bug using pure Python code?

Marius Gedminas
-- 
Q: A good ninja is hard to find.
A: Well, yes, actually, being hard to find is the whole point with them.
        -- http://tinyurl.com/5tnrwr
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: Digital signature
URL: <http://mail.zope.org/pipermail/zodb-dev/attachments/20140203/968f2b48/attachment.sig>