An error occurred fetching the project authors.
- 02 Jan, 2004 2 commits
-
-
Jeremy Hylton authored
-
Jeremy Hylton authored
The last tid is already set as a result of the invalidate() calls made in _update_cache().
-
- 30 Dec, 2003 2 commits
-
-
Jeremy Hylton authored
Move setLastTid() call into block where lock is held.
-
Jeremy Hylton authored
-
- 26 Dec, 2003 1 commit
-
-
Jeremy Hylton authored
This eliminates a bunch of checks that weren't exercised by the test suite. Not sure if they were superstition or not, but I'm willing to risk it.
-
- 24 Dec, 2003 1 commit
-
-
Jeremy Hylton authored
-
- 28 Nov, 2003 1 commit
-
-
Jim Fulton authored
-
- 03 Oct, 2003 1 commit
-
-
Jeremy Hylton authored
Synchronous is what matters for the tests.
-
- 02 Oct, 2003 1 commit
-
-
Jeremy Hylton authored
-
- 15 Sep, 2003 1 commit
-
-
Jeremy Hylton authored
Please make all future changes on the Zope-2_7-branch instead.
-
- 06 Aug, 2003 1 commit
-
-
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).
-
- 09 Jul, 2003 1 commit
-
-
Fred Drake authored
from Python 2.3. These warnings are displayed when running the unit tests. This patch fixes the occurrances that are triggered by the unit tests; there are probably others.
-
- 16 Jun, 2003 3 commits
-
-
Jeremy Hylton authored
-
Jeremy Hylton authored
It was lost backporting changes from the 3.1 branch, which doesn't have the last tid feature.
-
Tim Peters authored
-
- 13 Jun, 2003 1 commit
-
-
Jeremy Hylton authored
-
- 10 Jun, 2003 1 commit
-
-
Jeremy Hylton authored
-
- 05 Jun, 2003 1 commit
-
-
Jeremy Hylton authored
-
- 30 May, 2003 3 commits
-
-
Jeremy Hylton authored
After the merge, I made several Python 2.1 compatibility changes for the auth code.
-
Jeremy Hylton authored
Disable test for ZEO + MappingStorage, since it doesn't support undo.
-
Toby Dickenson authored
Check whether a registered extension method already exists before creating the marshaller attribute. This allows for a smooth migration should a former extension method be promoted to the normal storage interface.
-
- 23 May, 2003 1 commit
-
-
Jeremy Hylton authored
-
- 30 Apr, 2003 1 commit
-
-
Jeremy Hylton authored
-
- 29 Apr, 2003 2 commits
-
-
John Dahlin authored
-
Jeremy Hylton authored
If asyncore is not running in a separate thread, the client needs to call poll() to perform the IO necessary for cache verification to finish. This allows us to eliminate several calls to sync() in the test suite.
-
- 22 Apr, 2003 1 commit
-
-
Jeremy Hylton authored
-
- 09 Apr, 2003 3 commits
-
-
Jeremy Hylton authored
Don't know what happened, but the tests started running very slowly with Python2.3. Fixed by checking _ready at the start of the loop in _wait() instead of at the bottom. Most of the time _ready is set by the time we start, and no more I/O is going to occur until the client connects; as a result, the tests always sat in pending() until it timed out at 30 seconds.
-
Jeremy Hylton authored
There's a race between closing the storage and shutting down the ConnectThread. If we return here, the ConnectThread does no harm.
-
Jeremy Hylton authored
-
- 04 Mar, 2003 1 commit
-
-
Jeremy Hylton authored
-
- 29 Jan, 2003 1 commit
-
-
Barry Warsaw authored
-
- 27 Jan, 2003 1 commit
-
-
Barry Warsaw authored
so we're consistent with the cleanup that tpc_abort() does.
-
- 20 Jan, 2003 1 commit
-
-
Barry Warsaw authored
intent according to the comment.
-
- 17 Jan, 2003 1 commit
-
-
Jeremy Hylton authored
Fix likely bug where calling tpc_abort() after a client disconnected did not properly clear the client's internal state about the transaction. The change means that tpc_abort() will never raise a ClientDisconnected error, even when disconnected. Added a new test that sort-of covers this case and deleted another that was testing, in part, that you did get a ClientDisconnected error.
-
- 15 Jan, 2003 1 commit
-
-
Jeremy Hylton authored
ZEO.Exceptions.ClientDisconnected will always be raised when a client is disconnected. There's also a subclass of this exception in ZEO.zrpc.error so that it's possible to distinguish whether the error occurred in the RPC layer or at the storage layer.
-
- 14 Jan, 2003 1 commit
-
-
Jeremy Hylton authored
XXX Maybe there should be an option to allow this. A ZEO client can run in disconnected mode, using data from its cache, or in connected mode. Several instance variables are related to whether the client is connected. _server: All method calls are invoked through the server stub. When not connect, set to disconnected_stub an object that raises ClientDisconnected errors. _ready: A threading Event that is set only if _server is set to a real stub. _connection: The current zrpc connection or None. _connection is set as soon as a connection is established, but _server is set only after cache verification has finished and clients can safely use the server. _pending_server holds a server stub while it is being verified. Before this change, a client could start using a connection before verification finished. If verification took a long time, it could even commit a new transaction using a mixing of old and new data.
-
- 07 Jan, 2003 1 commit
-
-
Guido van Rossum authored
variables. Updated docstrings/comments.
-
- 03 Jan, 2003 1 commit
-
-
Jeremy Hylton authored
-
- 20 Dec, 2002 1 commit
-
-
Guido van Rossum authored
self._tbuf was unexpectedly None. The only way this can happen is when the storage is closed (probably by a different thread); close() sets _tbuf to None. It turns out that a TransactionBuffer instance can safely be closed more than once, so there's no need to set _tbuf to None in the close() method.
-
- 13 Dec, 2002 1 commit
-
-
Jeremy Hylton authored
tpc_begin() doesn't return anything anyway. Rename transaction to txn to make lines shorter.
-