Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
W
wendelin.core
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
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Joshua
wendelin.core
Commits
eb53b7aa
Commit
eb53b7aa
authored
Dec 10, 2019
by
Kirill Smelkov
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
.
parent
a02f19de
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
32 additions
and
26 deletions
+32
-26
zrace.py
zrace.py
+32
-26
No files found.
zrace.py
View file @
eb53b7aa
#!/usr/bin/env python
# XXX doc
#
#newTransaction
# ._storage.sync()
# invalidated = ._storage.poll_invalidations():
#
# ._storage._start = ._storage._storage.lastTrasaction() + 1:
# s = ._storage._storage
# s._lock.acquire()
# head = s._ltid
# s._lock.release()
# return head
# XXX T2 commits here: objX
#
# ._storage._lock.acquire()
# r = _storage._invalidations ; T1 receives invalidations for some transactions after head
# ._storage._lock.release()
# return r
#
# # T1 processes invalidates for [... head] _and_ some next transactions.
# # T1 thus will _not_ process invalidations for those next transactions when
# # opening zconn _next_ time. The next opened zconn will thus see _stale_ data.
# ._cache.invalidate(invalidated)
"""Program zopenrace.py demonstrates race-condition bug in ZODB
Connection.open() that leads to stale live cache and wrong data provided by
database to users.
newTransaction
._storage.sync()
invalidated = ._storage.poll_invalidations():
._storage._start = ._storage._storage.lastTrasaction() + 1:
s = ._storage._storage
s._lock.acquire()
head = s._ltid
s._lock.release()
return head
XXX T2 commits here: objX
._storage._lock.acquire()
r = _storage._invalidations ; T1 receives invalidations for some transactions after head
._storage._lock.release()
return r
# T1 processes invalidates for [... head] _and_ some next transactions.
# T1 thus will _not_ process invalidations for those next transactions when
# opening zconn _next_ time. The next opened zconn will thus see _stale_ data.
._cache.invalidate(invalidated)
"""
from
ZODB
import
DB
from
ZODB.MappingStorage
import
MappingStorage
...
...
@@ -39,8 +43,7 @@ def go(f, *argv, **kw):
return
t
# PInt is persistent integer:
# PInt is persistent integer.
class
PInt
(
Persistent
):
def
__init__
(
self
,
i
):
self
.
i
=
i
...
...
@@ -51,6 +54,7 @@ def main():
db
=
DB
(
zstor
)
# init initializes the database with two integer objects - obj1/obj2 that are set to 0.
def
init
():
transaction
.
begin
()
zconn
=
db
.
open
()
...
...
@@ -119,9 +123,11 @@ def main():
okv
[
1
]
=
True
N
=
1000
# run T1 and T2 concurrently. As of 20191210, due to race condition in
# Connection.open, it triggers the bug where T1 sees stale obj2 with obj1.i != obj2.i
init
()
N
=
1000
t1
=
go
(
T1
,
N
)
t2
=
go
(
T2
,
N
)
t1
.
join
()
...
...
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