mutable variable and alive objects
Bug #553334 reported by
Jürgen Kartnaller
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Storm |
Fix Released
|
Medium
|
Thomas Herve |
Bug Description
When using objects containing mutable variables (Pickle, List) these objects don't detect changes if the object is in the alive list after a commit.
The attached file demonstrates this behavior. In line 88 I do a commit which doesn't update the object in the database.
The problem is that the variable for the pickle is not checkpointed if the object comes from the alive cache and is read using store.find(). If store.get() is used it works fine.
The mutable variable needs to be checkpointed in order to emit a "changed" event.
Related branches
lp:~therve/storm/mutable-alive-check-553334
- Guilherme Salgado (community): Approve
- Jamu Kakar (community): Approve
- Gustavo Niemeyer: Needs Information
-
Diff: 122 lines (+43/-10)2 files modifiedstorm/store.py (+4/-10)
tests/store/base.py (+39/-0)
Changed in storm: | |
assignee: | nobody → Thomas Herve (therve) |
importance: | Undecided → Medium |
status: | New → In Progress |
Changed in storm: | |
status: | In Progress → Fix Committed |
Changed in storm: | |
milestone: | none → 0.17 |
Changed in storm: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
It seem it has been introduced with bug #334084. I'm trying to figure out what's going on. Thanks for the bug report!