Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Z
ZEO
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
nexedi
ZEO
Commits
7b5188f3
Commit
7b5188f3
authored
Oct 05, 2005
by
Tim Peters
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Merge rev 38770 from 3.4 branch.
tpc_abort(): Release the commit lock no matter what.
parent
ad54eedd
Changes
2
Show whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
9 additions
and
1 deletion
+9
-1
NEWS.txt
NEWS.txt
+8
-0
src/ZODB/BaseStorage.py
src/ZODB/BaseStorage.py
+1
-1
No files found.
NEWS.txt
View file @
7b5188f3
...
...
@@ -38,6 +38,14 @@ ZEO
erroneous ``AttributeError`` exception. Thanks to Tres Seaver for the
diagnosis.
BaseStorage
-----------
- (3.6a4) Nothing done by ``tpc_abort()`` should raise an exception.
However, if something does (an error case), ``BaseStorage.tpc_abort()``
left the commit lock in the acquired state, causing any later attempt
to commit changes hang.
PersistentMapping
-----------------
...
...
src/ZODB/BaseStorage.py
View file @
7b5188f3
...
...
@@ -192,8 +192,8 @@ class BaseStorage(UndoLogCompatible):
self
.
_abort
()
self
.
_clear_temp
()
self
.
_transaction
=
None
self
.
_commit_lock_release
()
finally
:
self
.
_commit_lock_release
()
self
.
_lock_release
()
def
_abort
(
self
):
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment