Seif Lotfy has proposed merging lp:~seif/zeitgeist/fix-643303 into lp:zeitgeist.
Requested reviews:
Zeitgeist Framework Team (zeitgeist)
Related bugs:
#643303 Upgrade of the db schema strategy for version jumps
https://bugs.launchpad.net/bugs/643303
I tried to fix the bug by simple
RainCT, can u look at thekorn's
https://code.edge.launchpad.net/~thekorn/zeitgeist/fix-660415-improve-zeitgeist-daemon/+merge/38914
so we can get it in
its very very simple
RainCT, please
seif_: it's already approved
by me
can u approve it to
?
and mikkel
and my comment also suggests tha
The proposal to merge lp:~thekorn/zeitgeist/fix-660415-improve-zeitgeist-daemon
into lp:zeitgeist has been updated.
Status: Needs review => Approved
--
https://code.launchpad.net/~thekorn/zeitgeist/fix-660415-improve-zeitgeist-daemon/+merge/38914
Your team Zeitgeist Framework Team is request
Do we want them to be backwards compatible ? Why would someone downgrade
zeitgeist ?
--
DB upgrades not backwards compatible (even when their are)
https://bugs.launchpad.net/bugs/665607
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to
Oh... this means we need 2_1 scripts for example... right?
On Sat, Oct 23, 2010 at 8:05 PM, Siegfried Gevatter
wrote:
> Because of using a system-wide Zeitgeist installation but testing a
> Zeitgeist running from trunk.
>
> --
> DB upgrades not backwards compatible (even when their are)
> https:/
ah ok :) +1 for ur fix then
On Sat, Oct 23, 2010 at 8:28 PM, Siegfried Gevatter
wrote:
> 2010/10/23 Seif Lotfy <665...@bugs.launchpad.net>:
> > Oh... this means we need 2_1 scripts for example... right?
>
> No, that's too much of a mess. But for database example
** Changed in: zeitgeist
Assignee: (unassigned) => Mohamed Amine IL Idrissi (ilidrissi.amine)
--
Using logging output for debugging purposes
https://bugs.launchpad.net/bugs/660440
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to
** Changed in: zeitgeist
Status: Triaged => In Progress
--
Upgrade of the db schema strategy for version jumps
https://bugs.launchpad.net/bugs/643303
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Status
** Changed in: zeitgeist
Status: Confirmed => In Progress
--
Using logging output for debugging purposes
https://bugs.launchpad.net/bugs/660440
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Status in Ze
** Changed in: zeitgeist
Milestone: 0.6 => 0.7
--
Implement storage monitor (devices and connectivity)
https://bugs.launchpad.net/bugs/489194
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Status in Unity F
Seif Lotfy has proposed merging lp:~seif/zeitgeist/fix-665607-and-643303 into
lp:zeitgeist.
Requested reviews:
Zeitgeist Framework Team (zeitgeist)
I tried to fix the bug by simple detecting the current core schema and "i" and
then iterating through all update scripts in form o
** Branch unlinked: lp:~seif/zeitgeist/fix-643303
--
Upgrade of the db schema strategy for version jumps
https://bugs.launchpad.net/bugs/643303
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Status in Zeitgeist
** Changed in: zeitgeist
Status: Confirmed => Fix Committed
--
DB upgrades not backwards compatible (even when their are)
https://bugs.launchpad.net/bugs/665607
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framewo
** Changed in: zeitgeist
Status: In Progress => Fix Committed
--
Upgrade of the db schema strategy for version jumps
https://bugs.launchpad.net/bugs/643303
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
with only a week left and no decision on the development method and API
I postponed the bug to 0.7
** Changed in: zeitgeist
Milestone: 0.6 => 0.7
--
Blacklist API sucks
https://bugs.launchpad.net/bugs/612344
You received this bug notification because you are a member of Zeitgeist
Framework T
** Also affects: zeitgeist
Importance: Undecided
Status: New
--
zeitgeist fails to run if its database structure is not complete
https://bugs.launchpad.net/bugs/660307
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgei
** Changed in: zeitgeist
Milestone: 0.6 => 0.7
--
Improve insertion times
https://bugs.launchpad.net/bugs/639737
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Status in Zeitgeist Framework: In Progress
Bu
Ok I don't think this issue will be tackled for 0.6 now so postponing
for 0.7
** Changed in: zeitgeist
Milestone: 0.6 => 0.7
--
Large requests increase memory usage considerably
https://bugs.launchpad.net/bugs/624310
You received this bug notification because you are a member of Zeitgeist
Fr
Blueprint changed by Seif Lotfy:
Approver: (none) => Zeitgeist Framework Team
Whiteboard set to:
Lets discuss this idea.
Do we want it as a supported extension or do we want to have in the engine. Or
do we want it as a community extension? How relevant is that to our current
work?
I am on it :)
On Fri, Oct 29, 2010 at 7:05 PM, mad-kow <601...@bugs.launchpad.net>
wrote:
> Why would Firefox disable my extensions when being in private mode?
> I still want adds to be blocked and protection against malicious JavaScript
> code, don't I?
>
> It's really your job to disable loggin
** Changed in: zeitgeist
Milestone: 0.3.3 => 0.6
** Changed in: zeitgeist
Milestone: 0.6 => 0.3.3
** Changed in: zeitgeist
Status: Fix Committed => Fix Released
--
Activity Journal's Right-Click Delete Functionality Broken
https://bugs.launchpad.net/bugs/561860
You received this
** Changed in: zeitgeist
Assignee: Michal Hruby (mhr3) => (unassigned)
** Changed in: zeitgeist-datahub
Assignee: (unassigned) => S. Sickert (s-sickert)
--
Monitoring for new files
https://bugs.launchpad.net/bugs/602211
You received this bug notification because you are a member of Zei
Public bug reported:
With some work being done from the taskview side we will be able to tracker
files move/renamed/copied
Currently I suggest adding event interpretations for these events. However I am
interested in figuring out how we want to make it reflect on the developers.
If a file has be
Public bug reported:
The telepathy logger works just fine and I think it should get an
installer script to be merged with trunk for later packaging :)
** Affects: zeitgeist-dataproviders
Importance: Undecided
Status: New
--
get telepathy logger into the main branch
https://bugs.la
Public bug reported:
When wanting to use a new extension one has to restart zeitgeist. Problem with
that is that all monitors are then gone.
My suggestion would be to be able to dynamically load extension by monitoring
the extensions directories and pulling in the new extension on runtime.
** A
Public bug reported:
Zeitgeist API can give us vague information but not statistics over the API
Use case:
- Give me counts of every subject_text from actor = Unity
Currently to do that one will need to either:
Request all events with Unity as an Actor and count the subject_text
This can be done m
My current suggestion based on Michal Hruby's requirements would be a
method called
def get_events_count(timerange, event_templates):
...
return dict
where dict = {event_template_1: count1,
event_template_2: count2,
...
}
--
I started working on a wiki with user stories and use cases to allow us to
triage the requirements better
http://wiki.zeitgeist-project.com/index.php?title=Aggregation_API
On Thu, Nov 4, 2010 at 3:39 PM, Markus Korn wrote:
> I suggest something like:
>
> def find_events_and_data(*find_event_argu
** Changed in: zeitgeist
Importance: Undecided => Wishlist
** Changed in: zeitgeist
Status: New => Confirmed
** Changed in: zeitgeist
Milestone: None => 0.7
--
Add new aggregate API
https://bugs.launchpad.net/bugs/670358
You received this bug notification because you are a member
The problem is more difficult than that. If a table is not there it gets
created with the next starting of zeitgeist. So there should be another
explanation why the update failed... We need more info about the
issue... I will mark it as incomplete until we can actually reproduce
this bug.
** Chang
I don't think we will have this done for the 0.7 release thus it won't
be assigned any milestone for now
** Changed in: zeitgeist
Milestone: 0.7.0 => None
--
Implement storage monitor (devices and connectivity)
https://bugs.launchpad.net/bugs/489194
You received this bug notification because
an extension added might be rare but lets say someone installs gnome-
activity-journal via software-center. He will never be able to get it to
work unless he restarts the session or zeitgeist. IMHO this is not
inviting to users and especially non-techies. Either we restart
Zeitgeist upon installati
I found an issue...
The tables are generated if not existent on each startup
However if the table exists but is damaged or incomplete it wont overwrite
it
We can fix that by getting the columns for each table and replacing if
incomplete
Does that sound sane?
On Fri, Nov 5, 2010 at 4:49 AM, Rocko
OK I gave it more thought and I think Markus's idea makes a lot of sense.
This will allow us to even later work with more "data_types", so if for example
geo-location extension becomes officially supported we can shoot out the
locations as a results. having a an array of dicts in data will allow
Do you mind attaching the broken activity.sql file for us to test with?
--
zeitgeist fails to run if its database structure is not complete
https://bugs.launchpad.net/bugs/660307
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitge
** Summary changed:
- Monitoring for new files
+ Monitoring Create/Move/Copy Files events
--
Monitoring Create/Move/Copy Files events
https://bugs.launchpad.net/bugs/602211
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist F
** Description changed:
- I was thinking on how tracker monitors new files to index. Turns out they
monitor directories using inotify. Recurse XDG dirs and single iterate $HOME
- Does this make sense to us?
+ An issue we are facing at the moment is that ppl lose track of there files in
a timeli
That is why i proposed solution 2 which in my opinion covers everything
:)
On Sun, Nov 7, 2010 at 2:36 PM, Siegfried Gevatter
wrote:
> 1) Modify the uris in the uris table
> -1, events are immutable by definition, they aren't supposed to change
>
> --
> Monitoring Create/Move/Copy Files events
>
Nautilus can tell us when a file is being renamed or moved from whithin
nautilus.
On Sun, Nov 7, 2010 at 7:27 PM, S. Sickert wrote:
> Reading through all the comments - it seems to me that there are two
> problems to tackle:
>
> 1) Determine which files are interesting for the user - this can be
awesome :)
On Sun, Nov 7, 2010 at 9:15 PM, S. Sickert wrote:
> I agree that 95% of the user never use the commandline, so that's not a
> big problem.
>
> AFAIK renaming in nautilus is just moving the file.
>
> --
> Monitoring Create/Move/Copy Files events
> https://bugs.launchpad.net/bugs/602211
the problem we have with both methods is that we can only handle 1
event_template
and the result types MostRecentEvents and LeastRecentEvent can not be used
since it will always return a count of 1
--
Add new aggregate API
https://bugs.launchpad.net/bugs/670358
You received this bug notificati
Let me elaborate on my last comment...
If we set result_type to MostRecentSubject we will return the most recent event
of each unique subject and the count how many times the subject occurred.
However if we ask for MostRecentEvent we will return most recent event and
count how many times the ev
** Description changed:
An issue we are facing at the moment is that ppl lose track of there files in
a timeline if the file was moved around or renamed. I would propose using
taskview or patch nautilus to actually grab those events and either:
1) Modify the uris in the uris table
2) Creat
OK I think we can just add 1 column that links to the new uri in the uri
table so it becomes
id | uri | new_id
so i i have a uri xxx
1 | xxx | 1
if its moved or renamed from xxx to yyy we have
1 | xxx | 2
2 | yyy | 2
OR we can do it the other way round by having the new column reference
to it
ok since we already have 3* -1 I am changing the bug to "won' fix"
** Changed in: zeitgeist
Status: New => Won't Fix
--
dynamic loading of extensions
https://bugs.launchpad.net/bugs/670355
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is su
** Changed in: zeitgeist
Assignee: (unassigned) => Mikkel Kamstrup Erlandsen (kamstrup)
** Changed in: zeitgeist
Status: New => In Progress
** Changed in: zeitgeist
Milestone: None => 0.7.0
--
Log rar and zip files as archives
https://bugs.launchpad.net/bugs/626492
You received
Public bug reported:
When for some reason zeitgeist restarts all monitors are then gone
Quoting kamstrup:
"And fwiw - libzeitgeist detects when the daemon comes and goes and reinstates
any monitors it has running - so restarting the daemon is not an issue for
libzeitgeist customers"
We should l
** Project changed: zeitgeist => zeitgeist-dataproviders
--
zeitgeist-datasources PPA only for amd64
https://bugs.launchpad.net/bugs/672315
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Data-Sources.
Status in Zeitgeist
*** This bug is a duplicate of bug 602211 ***
https://bugs.launchpad.net/bugs/602211
** This bug has been marked a duplicate of bug 602211
Monitoring Create/Move/Copy Files events
* You can subscribe to bug 602211 by following this link:
https://bugs.launchpad.net/zeitgeist/+bug/602211/+s
** Also affects: zeitgeist/0.7
Importance: Low
Assignee: Markus Korn (thekorn)
Status: In Progress
--
find_event() queries with timerange other than TimeRange.always() are slow
https://bugs.launchpad.net/bugs/672965
You received this bug notification because you are a member of Zei
** Changed in: zeitgeist
Status: In Progress => Fix Committed
--
Log rar and zip files as archives
https://bugs.launchpad.net/bugs/626492
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Status in Zeitgeis
** Changed in: zeitgeist
Assignee: (unassigned) => Seif Lotfy (seif)
** Changed in: zeitgeist-datahub
Status: Incomplete => New
--
Monitoring Create/Move/Copy Files events
https://bugs.launchpad.net/bugs/602211
You received this bug notification because you are a member of Zei
to foo.txt since the old foo.txt is its origin.
This will allow me to search bar.txt and get foo.txt as a result (which is
not good for feature events) but foo.txt is not linked to bar.txt
We need more time for that issue
On Tue, Nov 9, 2010 at 2:39 PM, Siegfried Gevatter wrote:
> 20
** Also affects: unity
Importance: Undecided
Status: New
--
Monitoring Create/Move/Copy Files events
https://bugs.launchpad.net/bugs/602211
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Status in Uni
** Changed in: zeitgeist-datahub
Status: New => Confirmed
--
Monitoring Create/Move/Copy Files events
https://bugs.launchpad.net/bugs/602211
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Status in Unity
OK what would happen if we use our uri table as our lookup table and add
the above table as the uri_tracking_table
Another though would be actually to have the normal uri_table and a new
update_uri_table
where we link and id to its new id
so moving foo to bar will give us
===
At some point people will need to blacklist over Unity. I think that should be
taken in consideration in the new design and development cycle.
Example: What if I don't want my .py files to show up in Unity
** Also affects: unity
Importance: Undecided
Status: New
--
Blacklist API sucks
** Changed in: zeitgeist
Status: New => Fix Committed
--
'iso_strptime.py' is mentioned in COPYRIGHT files although we don't ship this
file anymore
https://bugs.launchpad.net/bugs/673386
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subs
Seif Lotfy has proposed merging lp:~seif/zeitgeist/clean-up-get-events into
lp:zeitgeist.
Requested reviews:
Zeitgeist Framework Team (zeitgeist)
I cleaned up and shortend the code
I am not sure how much performance increase we get out of that but I think its
much more compact now.
All
** Changed in: zeitgeist
Status: New => Triaged
--
Using the subj_origin column of event_view is slower than it should be
https://bugs.launchpad.net/bugs/673452
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framewo
** Changed in: zeitgeist
Status: New => Confirmed
--
Queries for subj_uri and subj_origin are using no index
https://bugs.launchpad.net/bugs/673394
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Status i
I dont understand the soltuion tbh
However looking at your table i got an idea
Scenario:
* foo.txt gets renamed to nice.txt
* nice.txt gets renamed to stuff.txt
* create new foo.txt,
* stuff.txt gets renamed to omg!!
uri
=
id | value
---
1 | foo.txt
2 | nice.txt
3 | stuff.txt
TBH I am not fond of the idea of having the file monitor inside Zeitgeist.
Zeitgeist is about events first. Also this means we will need to reside on
inotify and this is a BIG NO from me again. Unless we have fanotify I dont
even think we should look at the solution being inside Zeitgeist TBH.
I ho
Review: Approve
Good work! Works fine here. Very elegantly done
--
https://code.launchpad.net/~zeitgeist/zeitgeist/fix-673916-GetEvent-duplicate-id/+merge/40655
Your team Zeitgeist Framework Team is subscribed to branch
lp:~zeitgeist/zeitgeist/fix-673916-GetEvent-duplicate-id.
__
Since we are not using it I suggest removing it... What do you think?
--
ZeitgeistEngine.get_events(rows=x) is broken
https://bugs.launchpad.net/bugs/673922
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Status
** Changed in: zeitgeist
Assignee: (unassigned) => Seif Lotfy (seif)
** Changed in: zeitgeist
Status: New => Confirmed
** Changed in: zeitgeist
Milestone: None => 0.7.0
--
ZeitgeistEngine.get_events(rows=x) is broken
https://bugs.launchpad.net/bugs/673922
You received
Seif Lotfy has proposed merging lp:~seif/zeitgeist/fix-673922 into lp:zeitgeist.
Requested reviews:
Zeitgeist Framework Team (zeitgeist)
Related bugs:
#673922 ZeitgeistEngine.get_events(rows=x) is broken
https://bugs.launchpad.net/bugs/673922
I removed rows from get_events since it is not
I manged to replicate this manually creating an invalid structure. Thank
you for the bug. We are on it.
** Changed in: zeitgeist
Status: Incomplete => Confirmed
** Changed in: zeitgeist
Assignee: (unassigned) => Seif Lotfy (seif)
** Changed in: zeitgeist
Milestone: None =&
To replicate this
1) Backup the activity.sqlite DB
2) restart the daemon
3) while its saying "DEBUG:zeitgeist.sql:Updating sql schema" kill the
daemon
On Fri, Nov 12, 2010 at 8:13 PM, Seif Lotfy
<660...@bugs.launchpad.net>wrote:
> I manged to replicate this manually creating a
http://paste.ubuntu.com/530852/ is a start of the fix
On Fri, Nov 12, 2010 at 8:42 PM, Seif Lotfy wrote:
> To replicate this
> 1) Backup the activity.sqlite DB
> 2) restart the daemon
> 3) while its saying "DEBUG:zeitgeist.sql:Updating sql schema" kill the
> daemon
>
So my take on this would be to check every table upon startup for validity.
This requires however that we know what current scheme the db is on how how the
structure would look like.
This means we need to store the table structures and compare them on startup.
We will be confronted with two scenar
** Changed in: zeitgeist (Ubuntu)
Status: Incomplete => Invalid
--
zeitgeist-datahub crash when opening activity journal
https://bugs.launchpad.net/bugs/626056
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framewor
Again to sum it up. My new suggestion is:
* change the event table to include current_subject_uri
* add a logic that handles MOVE/COPY/RENAME events
* listen to MOVE/COPY/RENAME events from outside sources such as nautilus
(by patching, ssickert has a patch)
--
Monitoring Create/Move/Copy Files e
I think it easy for clients to determine subjects that have been deleted
by calling exists on the uri. Of course we can detect delete events from
nautilus too and thusly change the "current_uri" for it.
But again to the solution for solving "moved" files. The solution proposed by
Mikkel (modified
I completely agree that current_uri as a new parameter however once u use it
u will need to use the the logic i described before:
So lets say I have a file that has been moved from /home/seif/foo to
/home/seif/bar. This means I query for all events where subject_uri =
/home/seif/foo so I get all r
** Changed in: zeitgeist
Milestone: None => 0.7.0
--
Using the subj_origin column of event_view is slower than it should be
https://bugs.launchpad.net/bugs/673452
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framewor
** Changed in: zeitgeist
Milestone: None => 0.7.0
--
Queries for subj_uri and subj_origin are using no index
https://bugs.launchpad.net/bugs/673394
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Status in Z
OK I think the only way we can actually get the insertion time improved
ATM is by using WAL for journaling. However it requires sqlite 3.7 and
once its set to WAL sqlite 3.6 wont be able to access it.
This breaks compatibility with older zeitgeist DBs:
However I think this should be doable if we s
** Changed in: zeitgeist
Milestone: None => 0.7.0
** Changed in: zeitgeist
Assignee: (unassigned) => Seif Lotfy (seif)
--
'iso_strptime.py' is mentioned in COPYRIGHT files although we don't ship this
file anymore
https://bugs.launchpad.net/bugs/673386
Blueprint changed by Seif Lotfy:
Whiteboard changed:
--- seif 2010-10-27 10:28pm ---
Lets discuss this idea.
Do we want it as a supported extension or do we want to have in the engine.
Or do we want it as a community extension? How relevant is that to our current
work? How could it help
m> wrote:
> On 15 November 2010 21:07, Seif Lotfy <602...@bugs.launchpad.net> wrote:
> > SNIP
> > So lets say I have a file that has been moved from /home/seif/foo to
> > /home/seif/bar. This means I query for all events where subject_uri =
> > /home/seif/foo so I
Blueprint changed by Seif Lotfy:
Whiteboard changed:
--- seif 2010-10-27 10:28pm ---
Lets discuss this idea.
Do we want it as a supported extension or do we want to have in the engine.
Or do we want it as a community extension? How relevant is that to our current
work? How could it help
Blueprint changed by Seif Lotfy:
Whiteboard changed:
--- seif 2010-10-27 10:28pm ---
Lets discuss this idea.
Do we want it as a supported extension or do we want to have in the engine.
Or do we want it as a community extension? How relevant is that to our current
work? How could it help
Blueprint changed by Seif Lotfy:
Whiteboard changed:
--- seif 2010-10-27 10:28pm ---
Lets discuss this idea.
Do we want it as a supported extension or do we want to have in the engine.
Or do we want it as a community extension? How relevant is that to our current
work? How could it help
** Changed in: zeitgeist
Milestone: 0.7.0 => None
--
Improve insertion times
https://bugs.launchpad.net/bugs/639737
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Status in Zeitgeist Framework: In Progress
OK I think we can start by always backing up while doing an upgrade from n ->
n+1.
I don't know what a gzipped ttl file is so why not just copy the
activity.sqlite to another back_activity.sqlite?
After upgrade is done we need to check the DB if its properly built. If not we
try to recover from
either you install libsoob from synaptic or do
rm -r /home/nvsbl/.local/share/zeitgeist/extensions/desktopcouch_gateway.py
this bug is not a zeitgeist bug. You have some extension that uses soup
in the zeitgeist directories.
** Changed in: zeitgeist
Status: New => Invalid
** Changed in: g
OK I think I need to spam this bug a bit.
While I agree that use cases and user stories are the way to go. There is no
such thing as a simple use case for some features. Developers want to rank
their stuff so they need COUNTS. And currently we have no simple way of
exposing COUNTS.
The use case
** Changed in: zeitgeist
Importance: Undecided => Low
** Changed in: zeitgeist
Status: New => Confirmed
** Changed in: zeitgeist
Milestone: None => 0.7.0
--
Zeitgeist builds man page for zeitgeist-datahub
https://bugs.launchpad.net/bugs/680360
You received this bug notification be
I opened this bug again since after considering extending the event table with
one more column "current_uri" I see it as an opportunity to actually create
another event_origin column.
The reasoning behind that is that it will allow us to trace origins of events
like "which website got me to this
The proposal to merge lp:~seif/zeitgeist/fix-redundant-statement into
lp:zeitgeist has been updated.
Description changed to:
Basically I found this statement. For me we could get rid of one of them. Right
now using only one statement of both works for all our test cases.
if return_mode == 0:
Seif Lotfy has proposed merging lp:~seif/zeitgeist/fix-redundant-statement into
lp:zeitgeist.
Requested reviews:
Zeitgeist Framework Team (zeitgeist)
Basically I found this statement. For me we could get rid of one of them. Right
now using only one statement of both works for all our test
Again the use case is not visible to the user. It is all about sorting and
ranking.
I want to use it in Synapse. For that I need to have "starred subjects" which
are all subject that have been ACCESSED or MODIFIED more than 10 times within
the last 24h. These are usually things that are stamped
** Changed in: zeitgeist
Assignee: (unassigned) => Seif Lotfy (seif)
** Changed in: zeitgeist-sharp
Assignee: (unassigned) => Manish Sinha (manishsinha)
** Changed in: zeitgeist
Milestone: None => 0.7.0
--
Reinstall monitors upon startup
https://bugs.launchpad.net/bugs/6
** Changed in: zeitgeist
Milestone: 0.7.0 => None
--
Add new aggregate API
https://bugs.launchpad.net/bugs/670358
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Status in Zeitgeist Framework: Confirmed
Bug
** Changed in: zeitgeist
Milestone: 0.7.0 => None
--
Large requests increase memory usage considerably
https://bugs.launchpad.net/bugs/624310
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Status in Zeitgei
** Changed in: zeitgeist
Milestone: 0.7.0 => None
--
Blacklist API sucks
https://bugs.launchpad.net/bugs/612344
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Status in Unity: Triaged
Status in Unity Files
** Changed in: zeitgeist
Milestone: 0.7.0 => None
--
Monitoring Create/Move/Copy Files events
https://bugs.launchpad.net/bugs/602211
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Status in Unity: Triaged
S
I am very very pleased with the API proposal. GREAT GREAT WORK thekorn. You
rock big time :)
+1 from me
On Sat, Nov 27, 2010 at 1:48 PM, Michal Hruby
wrote:
> > @Markus: I basically like your proposal, but since I was told that
> event ids are not unique, isn't there a huge flaw in that API?
>
>
Morten we should not break our current clients to satisfy upcoming
clients...
I know it seems weird but I think they can live with it since it just a
freaking namespace. I could call it org.hunannyyumyum.Zeitgeist and it
should not matter :)
On Sun, Nov 28, 2010 at 4:10 PM, Morten Mjelva
<681...@b
101 - 200 of 999 matches
Mail list logo
