| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
When the error happens too quickly, the errback is called before the
assign of the callLater. And in the errback we cancel that call which
gives an error.
- Related: #7451
|
|
- Resolves: #7503
Signed-off-by: Ivan Alejandro <ivanalejandro0@gmail.com>
|
|
NullHandler doesn't have anymore the argument bubble.
https://pythonhosted.org/Logbook/changelog.html#version-0-11-0
|
|
- Related: #7471
|
|
|
|
|
|
- Resolves: #7445
|
|
|
|
there was a bug in plaform that made webapp not serve correctly the smtp
certificates. with this fallback, we try to support platforms < 0.8,
although we should deprecate this behavior in bitmask 0.10
|
|
|
|
|
|
Connecting to the `soledad_bootstrap_finished` signal is not enough
since the password change window is created after the signal is emitted,
that way we were not able to tell when soledad is ready to be used.
- Resolves: #7474
|
|
these methods were returning None, and therefore breaking soledad
password change (since it checks whether mail is enabled before changing
soledad pass after srp pass change).
- Resolves: #7470
|
|
Right after a complete sync we show the unread emails.
- Resolves: #7453
|
|
|
|
Refactor ivan's code (aa4b684d0682ff9faf1577653fa5ceabbc6e0f20) to remove the
time.sleep.
- Resolves: #7414
|
|
the second callback was actually broken, not being called when it was
supposed to be.
the reason is that IncomingMail.startService returns a deferred which
callback is called with the loopingCall instance only when the
loopingCall is stopped.
|
|
logout calls were not being authenticated, so we were receiving 401
return code.
|
|
For our logging we need a new logbook feature that was added on 0.7.0.
- Resolves: #7449
|
|
we need the 'multi' feature all the same, so we'll be depending on
logbook >= 0.7.0.
|
|
This is needed if we use wheels, since the zmq library is not build as
it is when we install from code.
|
|
there's an error in the import
|
|
- Resolves: #7446
|
|
for the version in ubuntu trusty, the call for the zeromq handler
initialization gets one less argument
|
|
|
|
Add scripts to easily test (stable or unstable) debian packages.
- Resolves: #6715
|
|
|
|
I did the previous merge against an outdated version of the PR branch
(leapcode/pr/889). Sorry!
|
|
|
|
- Resolves: #7415
|
|
Look for file defined in the `BITMASK_CREDENTIALS` env variable and load
`provider`, `username` and `password` data.
Trigger login if they were loaded correctly.
The credentials file should look like this:
[Credentials]
username = my-account@my-provider.com
password = secret
- Resolves: #7419
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
If the user wants to register a new account we check whether the
provider allows registration or not right after getting the
provider.json file and show an error msg on the wizard if not allowed.
Also, there is a new signal to handle the error raised by the server if
a registration attempt is made but is rejected with error 403.
- Resolves: #6594
|
|
Is valid for a provider not to provide locations for their gateways.
- Resolves: #7281
|
|
Those files are no longer needed (nor present on the repo).
- Resolves: #7384
|
|
|
|
if __version__ is not properly assigned, provider tests were breaking
when parsing BITMASK_VERSION (which is None, where a string is
expected).
- Resolves: #7322
|
|
on the sumo tarball, the _version file for leap/bitmask submodule wasn't
being frozen, and hence BITMASK_VERSION was None. this was breaking the
provider tests w/o any clear error message.
- Related: #7322
|
