| 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
|
|
|
|
|
|
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
|
|
if the lsb_release utility is present on system, log part of its output
so we can have more information about the platform bitmask is running
on.
- Resolves: #7162
- Releases: 0.9.0
|
|
- Related: #7139
- Related: #7140
- Related: #7141
- Related: #7142
- Related: #7143
- Related: #7144
- Related: #7180
- Related: #7184
|
|
We don't need to run the event server on the backend if we are running
from the standalone bundle since the launcher takes care of that.
- Related: #7126
|
|
due to remaining bits that had not been changed after a refactor.
- Resolves: #7093
|
|
- Related: #6359
|
|
* Instead of checking if soledad is still syncing for the timeuot cancel
the delayed call.
* Count retries properly.
* Now soledad sync only returns SoledadError (#6981).
|
|
Before this commit, the backend used plain pyzmq bindings for communicating
with the frontend. This implements the txzmq twisted-powered bindings instead.
Closes: #6360
|
|
Change the 'ip' command location to support Fedora/RHEL distros.
/bin/ip is pressent on Debian/Ubuntu but not on Fedora.
/sbin/ip is a symlink to /bin/ip on Debian/Ubuntu and a binary on Fedora.
- Resolves: #6894
|
|
- Related: #6876
|
|
On 64bit Fedora/RHEL systems the python path is /usr/lib64 instead of
/usr/lib like on Ubuntu systems. This fix allows those users to use the
bootstrap_develop.sh script.
|
|
If the quit() call is triggered by the system logout we should not
disable the autostart. Otherwise bitmask won't autostart on the next
session start.
- Resolves: #6424
|
|
Catch the keyring.errors.InitError exception.
The automatic login sequence now stops correctly instead of freezing if
the user cancel the keyring open operation.
- Resolves: #6682
|
|
Replace the hardcoded port '1194' for the port specified in
eip-service.json.
Choose the best port to use according which one is enabled in the
eip-service.json file
Resolves: #6541
|
|
After a provider fails to pass the checks, the providers combo box is
not enabled when it should, we just took care of the provider line edit.
- Resolves: #6418
|
|
Also set text to 'bold' so it's easier to find at a first sight.
- Resolves: #5526
|
|
Resolves: #6713
|
|
|
|
|
|
|
|
|
|
FIX: Login attempt is made against previously selected provider.
Closes #6654.
Cherry-picked from release/0.8.x since it's a very annoying bug for the
testing cycles for the next release (0.9.0) -- kali.
|
|
FIX: Login attempt is made against previously selected provider.
Closes #6654.
|
|
Use global flag for ZMQ_HAS_CURVE.
Closes #6646
|
