84fb3a948d
[server] update entropy-server.pot
2013-12-26 22:54:11 +01:00
d4af59b609
[client] update translations
2013-12-26 22:53:40 +01:00
6048d06fca
[client] update entropy.pot
2013-12-26 22:52:48 +01:00
2a034e4a05
[entropy.client.methods] add an "unlocked" version of get_package_action()
2013-12-26 22:52:13 +01:00
11e6d596b8
[entropy.db.sqlite] do not clear the cache if locks are already acquired
2013-12-26 22:52:13 +01:00
603c96fc05
[entropy.locks] add is_already_acquired()
...
This method returns whether the lock has been already acquired.
It is useful in cases where the reentrancy property is leveraged.
2013-12-26 22:52:13 +01:00
0dcfc0f5bc
[todo] update TODO
2013-12-26 22:52:13 +01:00
d0d4b45e73
[todo] update TODO
2013-12-26 22:52:13 +01:00
528d4ff116
[entropy.client.dep] drop unused imports
2013-12-26 22:52:13 +01:00
6b3e5810fc
[entropy.client.settings] drop repos_installed{_keys,} settings metadata
...
Load the related data ondemand whenever it is needed, save SystemSettings
load time and avoid problems with stale information.
2013-12-26 22:52:13 +01:00
4da9953a71
[entropy.cache] drop EntropyCacher.CACHE_IDS['atom_match']
2013-12-26 22:52:13 +01:00
be311e7045
[entropy.cache] drop EntropyCacher.CACHE_IDS['atom_search']
2013-12-26 22:52:13 +01:00
0f59b909c9
[entropy.cache] drop EntropyCacher.CACHE_IDS['dep_tree']
2013-12-26 22:52:13 +01:00
55faf98b59
[entropy.cache] drop EntropyCacher.CACHE_IDS['check_package_update']
2013-12-26 22:52:13 +01:00
6121ab63bc
[entropy.cache] drop EntropyCacher.CACHE_IDS['depends_tree']
2013-12-26 22:52:13 +01:00
3bb2abc102
[entropy.cache] drop EntropyCacher.CACHE_IDS['library_breakage']
2013-12-26 22:52:13 +01:00
cbe52e67ce
[entropy.cache] drop EntropyCacher.CACHE_IDS['filter_satisfied_deps']
2013-12-26 22:52:12 +01:00
3fb6905387
[entropy.cache] drop EntropyCacher.CACHE_IDS['world_update']
2013-12-26 22:52:12 +01:00
57e2ab5ec8
[entropy.core] when clearing repository cache, don't clear the whole cache
...
This is no longer needed since cache keys are now properly generated
2013-12-26 22:52:12 +01:00
4c0bbd0789
[entropy.client.cache] drop methods used by the dep module only
2013-12-26 22:52:12 +01:00
cd199b0496
[entropy.client.dep] fix format string typo
2013-12-26 22:52:12 +01:00
a8bdb9a4ea
[entropy.cache] drop EntropyCacher.CACHE_IDS['critical_update']
2013-12-26 22:52:12 +01:00
034061620c
[entropy.cache] drop EntropyCacher.CACHE_IDS['world_masked']
2013-12-26 22:52:12 +01:00
01e54a75b9
[entropy.cache] drop EntropyCacher.CACHE_IDS['world_available']
2013-12-26 22:52:12 +01:00
55f5d892aa
[entropy.client.settings] add installed packages repository locking support
2013-12-26 22:52:12 +01:00
e976ea337c
[entropy.client.methods] add installed packages repository locking support
2013-12-26 22:52:12 +01:00
b4f445a61b
[entropy.client.repository] drop entropy_updates_alert argument
...
This is no longer useful for the implemented use cases
2013-12-26 22:52:12 +01:00
cf3305ed43
[entropy.client.repository] do not check the instance type of installed_repository
...
This check is no longer needed
2013-12-26 22:52:12 +01:00
d2c47cc3ba
[entropy.client.db] add installed packages repository locking support
2013-12-26 22:52:12 +01:00
12c34ab8d4
[entropy.client.dep] add installed packages repository locking support
2013-12-26 22:52:12 +01:00
f143614555
[entropy.client.client] add installed packages repository locking support
2013-12-26 22:52:12 +01:00
f5efd44cc2
[RigoDaemon] acquire UpdatesNotificationResourceLock in non blocking mode
...
We cannot sleep with the activity mutex held without affecting
parallelism so badly. Otoh, we cannot wleep on UpdatesNotificationResourceLock
without affecting 3rd party clients in a way that we would starve them
for a while. So, try to acquire the file lock in non blocking mode
and if it fails, reschedule a new call as soon as the same lock is
freed (exclusive acquire succeeds). This assumes that if the lock
is held back, we will just re-do the whole trick again and again.
2013-12-26 22:52:12 +01:00
f1a925c220
[solo.commands.install] acquire the notification lock in shared NB mode
...
This should avoid starvation in the scenario outlined in code comments.
2013-12-26 22:52:12 +01:00
ec198d632b
[RigoDaemon] make sure that the serializer is always released
...
Even in case of exceptions.
2013-12-26 22:52:12 +01:00
bccbce4a34
[RigoDaemon] use UpdatesNotificationResourceLock to avoid signal spam
...
If this resource lock is acquired, block until the lock is released
so that we will not keep sending status updates to the connected clients
2013-12-26 22:52:12 +01:00
00f43b043c
[solo.commands.install] acquire the UpdatesNotificationResourceLock in shared mode
...
This will temporarily disable available updates notifications from
RigoDaemon
2013-12-26 22:52:12 +01:00
6f44f5c40a
[entropy.locks] UpdatesNotificationResourceLock: do not dictate any particular lock mode
2013-12-26 22:52:12 +01:00
934a7ce14b
[RigoDaemon] drop sleep()
...
With the new locking strategy, this is no longer necessary
2013-12-26 22:52:12 +01:00
69d4473249
[entropy.locks] introduce UpdatesNotificationResourceLock
...
This will make possible to stop available updates notifications
from being issued while an install/upgrade is in progress
2013-12-26 22:52:12 +01:00
8049f88c56
[entropy.locks] make sure not to leak fds when using non-blocking calls
2013-12-26 22:52:12 +01:00
ca862463d4
[entropy.locks] make sure not to leak fds when using non-blocking calls
2013-12-26 22:52:12 +01:00
cf8984982a
[entropy.output] sychronize writes to stdout/stderr to avoid garbled output
...
In a multithreaded scenario, text may get garbled if there is no
synchronization between threads wrt the shared resources (std{out,err}).
This happens even when stdio buffering is enabled, of course.
2013-12-26 22:52:12 +01:00
8ed4bff872
Revert "[entropy.client.package] synchronize text output calls to avoid garbled output"
...
This reverts commit e722455432317516235e56fb386a60f05d237804.
2013-12-26 22:52:11 +01:00
a0ec911e68
[entropy.client.package] synchronize text output calls to avoid garbled output
...
Some parts of the package actions code are now multithreaded and some
other will likely become that in the near future.
For this reason, all the TextInterface.output calls are now wrapped and
synchronized by a mutex.
Ideally, this synchronization could have gone directly into entropy.output
but I am reluctant about placing expensive locking so deep into the code at
this time.
2013-12-26 22:52:11 +01:00
ca3b960dca
[entropy.client.sets] make Sets a new-style class
2013-12-26 22:52:11 +01:00
c2d15ddd23
[entropy.client.misc] add sharedinstlock and exclusiveinstlock decorators
2013-12-26 22:52:11 +01:00
0df7092e05
[entropy.locks] drop "_lock", just "acquire" or "release", it's cleaner
2013-12-26 22:52:11 +01:00
1f2575204e
[entropy.locks] make ResourceLock reentrant wrt to individual threads only
2013-12-26 22:52:11 +01:00
3a448a3b19
[entropy.client.package] use atom as part of the unpack directory
...
This greatly reduce the size of the path, mitigating the issue at bug #4078
2013-12-24 15:57:40 +01:00
0cb12a0dae
[entropy.misc] RSS: be more tolerant against xml file corruptions
2013-12-20 13:03:32 +01:00
Fabio Erculiani