** Branch linked: lp:~zeitgeist-packagers/zeitgeist/debian
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
https://bugs.launchpad.net/bugs/598666
Title:
Invalid cache access (was: Error when trying to
** Changed in: zeitgeist
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
https://bugs.launchpad.net/bugs/598666
Title:
Invalid cache access (was: Error when
Thanks for the reviews, I addressed them in my last commits to this
branch, I still need to test if the TEMP triggers are working properly.
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
I looked at Markus' branch and I think it makes sense - provided that
we're still confident that the cache gives us a boost :-) And we're
bumpting the schema version anayway...
A quick pre-review of Markus' branch:
- there seems to be missing a commit() after the DELETE statement?
-
Also!
_fix_cache can be a temp table or something right? sqlite has something
akin to a memory backed table that is lost when the process dies. We
might as well use that?
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist
Since Mikkel hasn't commented yet, let's leave this for 0.8.
** Changed in: zeitgeist
Milestone: 0.7.1 = 0.8.0
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
https://bugs.launchpad.net/bugs/598666
** Changed in: zeitgeist
Milestone: 0.8.0 = 0.7.1
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
https://bugs.launchpad.net/bugs/598666
Title:
Invalid cache access (was: Error when trying to fetch
** Branch linked: lp:~thekorn/zeitgeist/fix-598666-remove_cache_entry
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
https://bugs.launchpad.net/bugs/598666
Title:
Invalid cache access (was: Error when
I've added a prototype of my idea as described in my last comment, if we want
to do it this way, we have to bump the sql-schema-version, I guess.
I'm not completely sure if this is the way to go, but given the fact that the
number of entries in the _fix_cache table should be *very* low over time
Hey Markus,
Nice to hear from you again.
What you're proposing sounds better than adding a C binding file for
update_hook (unless we decide we want to start adding more C stuff, but
I can't think of what that'd be right now). I guess it's the best we can
do.
If we're going to do this it should
I don't have any clever solution off the top of my head - I just want
to give Siegfried some props for the cool detective work! Nice job!
Now. To thinking.
___
Mailing list: https://launchpad.net/~zeitgeist
Post to : zeitgeist@lists.launchpad.net
Oh yeah, of course. Indeed, good work Siegfried.
While reading the last few comments one possible fix came into my mind:
Let's maintain a (temporary) helper table called '_fix_cache' with (table_name
VARCHAR, id INTEGER) and create a 'BEFORE DELETE' trigger on each cached table
(interpretation,
I'm re-opening this since I've finally found the cause of this problem!
When events are deleted, interpretations/manifestations/mimetypes/etc.
which are no longer used are automatically removed from the database.
However, the cache isn't informed about this and until Zeitgeist is
restarted it'll
The last release added a workaround for this. Since we currently aren't
able to reproduce this issue, I'm just going to close this bug now.
Please re-open it if you can provide a test case to reproduce the
problem.
** Changed in: zeitgeist
Status: Triaged = Fix Released
** Changed in:
Seif sent me an activity.log which he managed to create by [...]
randomly clicking in GAJ and synapse[...]. This log is broken and
results in the above mentioned KeyError.
The db has a few broken entries: http://paste.ubuntu.com/553188/
--
You received this bug notification because you are a
So I just added a little temporary fix that I would like to see with the next
release.
Instead of zeitgeist returning nothing when requesting a time-period with a
broken event, zeitgeist now can ignore the broken event and return a list with
healthy events. The broken events can be seen in the
** Summary changed:
- Error when trying to fetch items
+ Invalid cache access (was: Error when trying to fetch items)
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
https://bugs.launchpad.net/bugs/598666
** Changed in: zeitgeist
Milestone: None = 0.7.0
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
https://bugs.launchpad.net/bugs/598666
Title:
Invalid cache access (was: Error when trying to fetch
18 matches
Mail list logo
