1. 21 Jun, 2016 1 commit
  2. 19 Jun, 2016 3 commits
  3. 18 Jun, 2016 2 commits
  4. 16 Jun, 2016 1 commit
  5. 13 Jun, 2016 2 commits
  6. 11 Jun, 2016 2 commits
    • Julien Muchembled's avatar
    • Julien Muchembled's avatar
      windows: fix failures due to low-precision of time.time() · f08b40e1
      Julien Muchembled authored
      This fixes the following random failure:
      
      Failure in test checkBaseHistory (ZODB.tests.testDemoStorage.DemoStorageTests)
      Traceback (most recent call last):
        File "unittest\case.py", line 384, in _executeTestPart
          function()
        File "ZODB\tests\testDemoStorage.py", line 96, in checkBaseHistory
          self._checkHistory(base_only())
        File "ZODB\tests\HistoryStorage.py", line 46, in _checkHistory
          self.assertLess(a, b)
        File "unittest\case.py", line 1026, in assertLess
          self.fail(self._formatMessage(msg, standardMsg))
        File "unittest\case.py", line 508, in fail
          raise self.failureException(msg)
      AssertionError: 1465433823.260304 not less than 1465433823.260304
      f08b40e1
  7. 06 Jun, 2016 6 commits
  8. 05 Jun, 2016 1 commit
  9. 31 May, 2016 3 commits
  10. 30 May, 2016 1 commit
  11. 17 May, 2016 1 commit
  12. 12 May, 2016 1 commit
  13. 09 May, 2016 3 commits
  14. 05 May, 2016 3 commits
  15. 04 May, 2016 1 commit
  16. 29 Apr, 2016 2 commits
  17. 28 Apr, 2016 2 commits
  18. 27 Apr, 2016 4 commits
    • Julien Muchembled's avatar
      Changelog for PR #52 · 06df0eba
      Julien Muchembled authored
      06df0eba
    • Julien Muchembled's avatar
      Fix possible data corruption after FileStorage is truncated to roll back a transaction · 028b1922
      Julien Muchembled authored
      Multi-threaded IO support, which is new to ZODB 3.10, allows clients to read
      data (load & loadBefore) even after tpc_vote has started to write a new
      transaction to disk. This is done by using different 'file' objects.
      
      Issues start when a transaction is rolled back after data has been appended
      (using the writing file object). Truncating is not enough because the FilePool
      may have been used concurrently to read the end of the last transaction:
      file objects have their own read buffers which, in this case, may also contain
      the beginning of the aborted transaction.
      
      So a solution is to invalidate read buffers whenever they may contain wrong
      data. This patch does it on truncation, which happens rarely enough to not
      affect performance.
      
      We discovered this bug in the following conditions:
      - ZODB splitted in several FileStorage
      - many conflicts in the first committed DB, but always resolved
      - unresolved conflict in another DB
      If the transaction is replayed with success (no more conflict in the other DB),
      a subsequent load of the object that could be resolved in the first DB may, for
      example, return a wrong serial (tid of the aborted transaction) if the layout
      of the committed transaction matches that of the aborted one.
      
      The bug usually manifests with POSKeyError & CorruptedDataError exceptions in
      ZEO logs, for example while trying to resolve a conflict (and restarting the
      transaction does not help, causing Site Errors in Zope). But theorically,
      this could also cause silent corruption or unpickling errors at client side.
      028b1922
    • Julien Muchembled's avatar
      Changelog for PR #54 · b83ac1c2
      Julien Muchembled authored
      b83ac1c2
    • Julien Muchembled's avatar
      Merge pull request #54 from zopefoundation/deps-cleanup · eebae5a2
      Julien Muchembled authored
      Cleanup dependencies, remove ZEO leftovers
      eebae5a2
  19. 25 Apr, 2016 1 commit