OpenSlides/openslides/users
Oskar Hahn dd4754d045 Disable the future-lock when updating the restircted data cache
Before this commit, there where two different locks when updating the restricted
data cache. A future lock, what is faster but only works in the same thread. The
other lock is in redis, it is not so fast, but also works in many threads.

The future lock was buggy, because on a second call of update_restricted_data
the same future was reused. So on the second run, the future was already done.

I don't see any way to delete. The last client would have to delete it, but there
is no way to find out which client the last one is.
2019-03-04 21:37:00 +01:00
..
management Run black 2019-01-08 21:51:52 +01:00
migrations delete wrong file 2019-01-19 14:48:01 +01:00
__init__.py Run black 2019-01-08 21:51:52 +01:00
access_permissions.py Added gender field for users. 2019-01-18 19:47:00 +01:00
apps.py Projector V 2019-01-28 23:18:27 +01:00
config_variables.py Fixes 2019-02-25 18:26:27 +01:00
models.py Disable the future-lock when updating the restircted data cache 2019-03-04 21:37:00 +01:00
projector.py (Current) list of speaker slide 2019-02-22 10:40:28 +01:00
serializers.py Disable the future-lock when updating the restircted data cache 2019-03-04 21:37:00 +01:00
signals.py Disable the future-lock when updating the restircted data cache 2019-03-04 21:37:00 +01:00
urls.py Run black 2019-01-08 21:51:52 +01:00
views.py Disable the future-lock when updating the restircted data cache 2019-03-04 21:37:00 +01:00