1. 08 Oct, 2003 2 commits
  2. 07 Oct, 2003 3 commits
  3. 06 Oct, 2003 3 commits
  4. 05 Oct, 2003 3 commits
  5. 03 Oct, 2003 7 commits
  6. 02 Oct, 2003 10 commits
  7. 30 Sep, 2003 1 commit
  8. 25 Sep, 2003 2 commits
  9. 15 Sep, 2003 1 commit
  10. 03 Sep, 2003 1 commit
  11. 06 Aug, 2003 2 commits
    • Tim Peters's avatar
      checkTimeoutAfterVote, · 3ac7c1e7
      Tim Peters authored
      checkTimeoutProvokingConflicts:  These shouldn't start a server; setup
      already did.  Starting two servers caused intermittent failures on
      Windows, due to lockfile contention.
      3ac7c1e7
    • Tim Peters's avatar
      Forward-porting critical ZEO client fixes from ZODB3-3_1-boston-branch. · e2c28914
      Tim Peters authored
      + If a storage times out between the vote and the finish, the ZEO cache
        could get populated with objects that don't make it to the storage
        server.
      
        A new flag self._midtxn_disconnect gets reset in tpc_begin() and set
        in notifyDisconnected().  If tpc_finish() discovers this flag set, it
        raises a ClientDisconnected error before calling tpc_finish() on the
        server.
      
      + In tpc_finish() we re-order the calls so that the server's tpc_finish()
        is called (and must succeed) before we update the ZEO client cache.
      
      + The storage name is now prepended to the sort key, to ensure a
        unique global sort order if storages are named uniquely.
      
      + Added new tests for the above (checkTimeoutAfterVote,
        checkTimeoutProvokingConflicts, checkSortKey).
      e2c28914
  12. 02 Aug, 2003 2 commits
    • Chris McDonough's avatar
      Refactor start_zope function and add tests for its functionality. · c219b65a
      Chris McDonough authored
      Changes:
      
       - startup log handler now pays attention to the logging levels of
         the handlers defined within the config file and uses the "lowest"
         level to log messages to stdout during startup.
      
       - entirely removed warning when the starting user's umask is "too
         permissive".  it wasn't clear that it added any value under normal
         operations.
      
       - replaced ancient setuid code with code stolen from zdaemon that
         works the same but looks nicer.
      c219b65a
    • Chris McDonough's avatar
      Don't try to optimize by checking for disabled and effective levels within the... · 3d5726eb
      Chris McDonough authored
      Don't try to optimize by checking for disabled and effective levels within the log method.  The logger's level may not be meaningful if this logger is configured with handlers that accept messages at a lower level than that of the logger itself.
      
      3d5726eb
  13. 30 Jul, 2003 1 commit
  14. 28 Jul, 2003 2 commits