diff options
| author | drebs <drebs@leap.se> | 2015-06-01 12:32:33 -0300 |
|---|---|---|
| committer | drebs <drebs@leap.se> | 2015-06-01 12:37:24 -0300 |
| commit | 10dd29e09e48ae8c1aab8e38cfcede1d49e190ec (patch) | |
| tree | b2dcf1756285429ba70d830e54ff4d155b9fd410 | |
| parent | 907a864c774cc43fcf0ebff3d6b5082901661e98 (diff) | |
[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.
| -rw-r--r-- | src/leap/bitmask/backend/components.py | 1 |
1 files changed, 0 insertions, 1 deletions
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): """ |