| Age | Commit message (Collapse) | Author |
|---|
|
|
|
the should_redownload function was only called if the pemfile was not
present of the fs.
- Resolves: #7869
|
|
|
|
This includes getting the token for the imap authentication, and
displaying it on the help window.
- Resolves: #4469
- Releases: 0.10.0
|
|
Adapt to users emitting the userid/uuid too.
- Resolves: #7656
- Releases: 0.10.0
|
|
|
|
- Related: #7583
|
|
- Resolves: #7585
|
|
|
|
- Related: #7552
|
|
- Resolves: #7568
|
|
|
|
|
|
Add a UI message for the user to know where to go next.
This message goes away after 60 seconds or right after a MUA logs in.
- Resolves: #7552
|
|
|
|
from debian stretch on, gpg will be a symlink to gpg2.
this is currently failing if one uses dpkg-divert to make gpg2 provide
/usr/bin/gpg.
this solution just attempts to use gpg2 binary if the search for gpg
binary fails.
- Resolves: #7563
- Releases: 0.9.1
|
|
|
|
|
|
- Resolves: #7542
|
|
|
|
|
|
|
|
|
|
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
|
|
|
|
|
|
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.
|
|
- 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
|
|
Register to Soledad's sync (send and receive) events and display the
progress in the UI.
- Resolves: #7353
|
|
apply_updates.py applies the already downloaded files from the updates
folder and removes all the obsolete files from the bundle. It's meant
to be use by the pyinstaller bundle.
- Resolves: #7342
- Related: #5876
|
|
The tests where using deferToThread to run without need, I remove it
and now it's easier to debug when one test fails.
- Resolves: #7343
|
|
The new pyinstaller method will rule out the launcher, we need the
updater working inside bitmask client.
- Closes: #7291
|
|
Fix:
If the logbook controller is not started the stop call will fail.
Trying to start it twice fails.
|
|
|
|
|
|
Prevent locks caused by the zmq log handler reaching the zmq's HWM (High
water mark / buffer limit) and causing some components to block until
the buffer is empty (running the zmq handler for instance).
We run the zmq handler in the background all the time to prevent this.
- Resolves: #7222
|
|
Due to #7139 (the logbook log centralizer) logs from 3rd party libs are
included in the centralized logs with lots of debug information and we
don't want that.
We use the existing silencer to exclude logs that are not from leap
modules.
- Resolves: #7185
|
