zopefoundation / ZODB / 1016

76%

master: 84%

push

travis-ci

<a href="https://github.com/zopefoundation/ZODB/commit/<a class=hub.com/zopefoundation/ZODB/commit/8d20f20440ff116cbf72b074df0538f9a5b0b8d6">8d20f2044<a href="https://github.com/zopefoundation/ZODB/commit/8d20f20440ff116cbf72b074df0538f9a5b0b8d6">&quot;&gt;mvccadapter: check if the last TID changed without invalidation

Since commit </a><a class="double-link" href="https://github.com/zopefoundation/ZODB/commit/<a class="double-link" href="https://github.com/zopefoundation/ZODB/commit/b5895a5c23309ff2dfe8fd853b838a0c5e349210">b5895a5c2</a>">b5895a5c2</a><a href="https://github.com/zopefoundation/ZODB/commit/8d20f20440ff116cbf72b074df0538f9a5b0b8d6"> (&quot;mvccadapter:
fix race with invalidations when starting a new transaction&quot;),
a ZEO test fails as follows:

    File &quot;src/ZEO/tests/drop_cache_rather_than_verify.txt&quot;, line 114, in drop_cache_rather_than_verify.txt
    Failed example:
        conn.root()[1].x
    Expected:
        6
    Got:
        1

Earlier in the test, the ZEO server is restarted and then another
client commits. When disconnected, the first client does not receive
invalidations anymore and the connection gets stuck in the past until
there&#39;s a new commit after it reconnected. It was possible to make the
test pass with the following patch:

--- a/src/ZEO/ClientStorage.py
+++ b/src/ZEO/ClientStorage.py
@@ -357,6 +357,7 @@ def notify_connected(self, conn, info):

         # invalidate our db cache
         if self._db is not None:
+            self._db.invalidate(self.lastTransaction(), ())
             self._db.invalidateCache()

         logger.info(&quot;%s %s to storage: %s&quot;,

Other implementations like NEO are probably affected the same way.

Rather than changing interfaces in a backward-incompatible way,
this commit revert to the original behaviour, and all the changes
that were done in existing tests are reverted.

6387 of 8572 relevant lines covered (74.51%)

0.75 hits per line