From 10dd29e09e48ae8c1aab8e38cfcede1d49e190ec Mon Sep 17 00:00:00 2001 From: drebs Date: Mon, 1 Jun 2015 12:32:33 -0300 Subject: [bug] do not unset soledad proxy object too early The backend was unsetting the soledad proxied object before actually calling the soledad close() method and this was causing the application to hang when exitting. As the local soledad component's cancel_bootstrap() method is called before the close() method, we'd better not unset the proxied object there, and let only the close method do it. This commit fixes this by just removing the line that unsets the proxied object in the wrong place. --- src/leap/bitmask/backend/components.py | 1 - 1 file changed, 1 deletion(-) (limited to 'src/leap/bitmask/backend') diff --git a/src/leap/bitmask/backend/components.py b/src/leap/bitmask/backend/components.py index 0a2f1029..d602156d 100644 --- a/src/leap/bitmask/backend/components.py +++ b/src/leap/bitmask/backend/components.py @@ -829,7 +829,6 @@ class Soledad(object): logger.debug("Cancelling soledad defer.") self._soledad_defer.cancel() self._soledad_defer = None - zope.proxy.setProxiedObject(self._soledad_proxy, None) def close(self): """ -- cgit v1.2.3