lp:~phablet-team/history-service/single_instance_using_lock_file

Branch merges

Propose for merging

No branches dependent on this one.

Merged into lp:history-service/staging at revision 262

Tiago Salem Herrmann (community): Approve on 2017-03-22

Diff: 47 lines (+16/-5)

2 files modified

cmake/modules/GenerateTest.cmake (+1/-0)
daemon/main.cpp (+15/-5)

api

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

277. By Gustavo Pichorim Boiko on 2017-03-09

History-daemon is not a system service, so store a lock somewhere in the user's home
directory to allow running one instance per user.

276. By Tiago Salem Herrmann on 2017-03-09

merge parent branch

275. By Tiago Salem Herrmann on 2017-03-08

merge parent branch

274. By Gustavo Pichorim Boiko on 2017-03-08

Make sure tests use different lock files so that they can run simultaneously

273. By Gustavo Pichorim Boiko on 2017-03-03

Use a QLockFile to ensure there will be only one instance of the daemon per user.
As we now delay the registration on dbus, sometimes we ended up having two
instances of the daemon running (because of dbus activation). This change makes
sure that won't happen.

272. By Gustavo Pichorim Boiko on 2017-03-03

When threads are removed, make sure the events models get refreshed accordingly.

271. By Gustavo Pichorim Boiko on 2017-03-02

Update tests

270. By Gustavo Pichorim Boiko on 2017-03-02

Optimize thread removal by deleting the events using a sqlite trigger instead
of manually removing and notifying them.
Also make the thread and event removal asynchronous calls on dbus level as the
result will be notified back to us as signals.

269. By Gustavo Pichorim Boiko on 2017-03-02

Stop using the telepathy pending message status to mark messages as read as
that causes performance problems when dealing with a large number of messages.

268. By Tiago Salem Herrmann on 2017-02-23

fix build