| Age | Commit message (Collapse) | Author |
|---|
|
It now requests using the same session that it logs in until the user
arrives at the inbox (denoted by the compose-trigger showing up on the
html in this case)
|
|
|
|
In case a user was being logged out and there's a soledad invalid
auth token error, there might be an inconsistent state where the
user session doesn't exist when this second logout is tried.
This was breaking the login for that user until the next UA restart,
I adapted the code to make logging out an user idempotent to
prevent this corner case
|
|
|
|
I added a new test to check that an existing public key is not being
sent to leap on every login
|
|
We were using an old version of the python's mock library, which lacks
new features such as assert_called() and assert_not_called() that I
found handy to test #778
|
|
We were always sending the public key to nicknym, even if it was
already there. The send_key method purpose is to update the public
key in case a new pair is created and shouldn't be done at every
login
|
|
Register was trying to use LeapConfig and breaking
when trying to register users
|
|
The interstitial was being read at every login
request, that was a blocking read on the main
loop for every user.
That file was also being opened and not closed
at every request, that would aggravate the
'too many open files' problem
|
|
|
|
|
|
|
|
Since we are creating the combined certificates at the beginning
of the UA and using it for multiple users, it makes more sense to
create it in the leap folder instead of on a temporary file
This bundle will be updated on every UA start
|
|
|
|
|
|
|
|
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
|
|
|
|
We had different outputs for inlineCallbacks
and traditional callbacks and the output was
kinda confusing. We normalized the output to
<time> <type>: function <name> (<file>:<line>) in thread <thread_id>
We also changed the earlier type from deferred
to callback (because that is what's being measured)
so now we have two possible types: callback and
inlineCallbacks
|
|
The inlineCallback returnValue has a different logic using
exceptions, the way we measured before, we were getting the
time of the whole deferred chain (including all the callbacks)
instead of exclusively the timing of the last yield up to the
returnValue call.
|
|
This reverts commit 480e7d3bd48f2a7c23a76843750daaa03f2b12b3.
|
|
This reverts commit 8ef8acf8e853fe097c379eed4d65e67f409531d1.
|
|
|
|
|
|
|
|
We did two changes to the twisted patch to be able to
measure the inlineCallbacks correctly:
- Filtered the traditional callbacks timing so that it
doesn't print inlineCallback timings
- Added a measurement for the g.send() method inside
the inlineCallback, to measure the actual execution
time of the call on the main thread, between the
inlineCallback yields
|
|
|
|
|
|
See #761
|
|
SMTP json is a blocking HTTP request that was taking ~1 sec
of the session creation. We moved it to the UA initialization
|
|
|
|
|
|
In some cases, the default home was not expanding
the user part of the path and was causing errors,
now we make sure the path is expanded when setting
the default value
|
|
Soledad json must only be downloaded after we
fetch the api provider certificate, we can't
make the request for it before having this cert
|
|
See: #761
|
|
|
|
|
|
|
|
|
|
|
|
Now we can clock how long a piece of code takes
to execute without being constrained by whole
method like we were with the decorator
|
|
The README explains how to apply the patch so you
can get information about long running methods (longer
than 100ms) on the main thread
|
|
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
|
|
Authentication is now consistently done before
creating the leap session, so I removed the
auth attempt from inside the leap session
factory
|
|
Consolidated authentication to always be
done is a defer to thread and changed the
authenticate_user method name to conform
with what it actually does
|
|
It is already done earlier in the bootstrap and
is not user specific, so shouldn't be done on
user bootstrap
|
|
Reason for the failure: see
https://github.com/karma-runner/karma-phantomjs-launcher/issues/104
|
|
See #751
|
|
at least phantomjs-prebuilt has issues if the node_modules
dir is a symbolic link. Which is the case inside vagrant.
See #751
|
|
The encryption status was being wrongly displayed as
"encrypted encryption-valid" with a green padlock
See: #619
|
