Age | Commit message (Collapse) | Author |
|
I was surprised this test was not working correctly.
|
|
the old events if they were not cleaned up after previous errors
|
|
|
|
|
|
with @tayanefernandes
|
|
We were trying to setup services even after closing the session. We fixed it
and added unit test.
Related with: #815
|
|
When the upload of the user key fails (i.e. Timeout), the session was being held
in memory, preventing the user from trying again.
Related with: #815, #889
|
|
with @thaissiqueira."
This reverts commit ebdeec4ad6d0f91bc60fd34a580fc02787026692.
|
|
@thaissiqueira.
|
|
|
|
|
|
|
|
using the cache
Issue #773
|
|
With this change we don't have to create the combined_ca_bundle
for every user at every login.
To support this change, we started migrating away from the
LeapCertificate class that was making the LeapProvider setup
more brittle
|
|
Started adapting get_leap_session to deferreds
Soledad and keymanager setup calls will now
happen in deferreds and leap session creation
itself is a deferred with callbacks
This is a start in breaking the big blocking
calls we were doing on the main thread, this
was done without changing code inside the
leap libraries yet so things can be further
optimized
This breaks the ~4 seconds get_leap_session
piece into smaller 1 seconds one, that can be
further optimized and deferred to even smaller
calls
There are requests calls happening on the main
thread that should get this number even further
down
Also moved some pieces from bitmask libraries
to our bootstrap, because they are not bitmask
libraries anymore and that was causing confusion
|