| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
- Resolves: #8910
|
|
|
|
|
|
- remove premature optimization for fast-notifies. blobs will cover
that, no point in maintaning the optimization at the price of creeping
complexity.
|
|
- Create the 'Sent folder' ourselves to avoid pixelated hitting a bug in
mailbox creation.
- I believe there's still a problem with bitmask desing for the adaptor
(in get-or-create mailbox). This needs further tests.
- Case manipualation to avoid having a 'Sent' and 'SENT' folder when
Thunderbird and Pixelated write to those.
- Further hacks to monkeypatch the leap-mail-adapter that Pixelated
uses (make them reuse the account instance!). This is getting insane,
I am really looking forward to the fork.
- Duly note our technical debt in the area of Pixelated integration.
Keeping the Pixelated codebase untouched for a long time will
backfire. As far as I've noticed, we have a basic violation of the
assumptions about a single-instance writes and notifications to all
listeners. As commented in the commit, this should go either for a
guarantee that only one account object is created per user (creating
it in the bootstrapping process in bitmask), or for the opposite
direction in which the listeners are communicated in some other way
(zmq events, for instance).
- In any case, it's strongly recommended to deduplicate the Pixelated
libraries as soon as possible and make Pixelated use a better defined
set of Bitmask's public apis.
- Modify the wrapper create methods so that they return the modified
wrapper itself.
- Resolves: #8903, #8904
|
|
|
|
|
|
this commit is porting the polkit launcher from the legacy bitmask
client. if no polkit authentication agent is running, it will try to run
one that is found in the system.
- Resolves: #8836
|
|
no need to setup LD_LIBRARY_PATH anymore, we're shipping a static
binary.
|
|
|
|
|
|
|
|
Allows to upload a key to providers that use a different api uri than
api.provider.net
- Resolves: #8868
|
|
|
|
If we do fast-notifies with pixelated running, the poll notifications
for new mail on inbox break on pixelated side, because the email is not
ready.
- Related: #8798
|
|
When setting the listeners in the IMAP Folder, we avoid setting more
than one listener for the same imap mailbox (because in some situations
we were registering way too many listeners).
this was making the pixelated inbox registering the notification and
therefore the imap mailbox not being registered.
this MR also refactors the way pixelated is initialized, so that it
avoid creating a second Account instance. In this way, we make sure that
the pixelated mua and the imap server share the same collections for a
given mailbox, and therefore any of the two is able to get a
notification whenever the other adds a message to the mailbox.
- Resolves: #8846, #8798
|
|
|
|
- Resolves: #8884
|
|
|
|
- Resolves: #8886
|
|
- Resolves: #8887
|
|
|
|
In the previous commit 73fe341 the autoconf param for authentication
calls was changed to 'True', so the cli has to send the right
representation.
|
|
This fixes two bugs with handling the autoconf parameter:
- It looks for "True" instead of "true" in the dispatching code to
account for json.dumps() converting true into a boolean and str()
returning the python-style capitalized version "True".
- It moves the initial definitions of offirst_bootstrap,
ongoing_bootstrap, and stuck_bootstrap into the class instantiation
method so they don't get shared between instances of the
class. Previously, this caused one instance being bootstrapped to
causes other instances to think they were also actively being
bootstrapped.
Resolves #8843
|
|
|
|
The bundled version of bitmask is unable to find the bitmask_helpers
binary. Let's include it as part of the frozen binary generated by
pyinstaller.
- Resolves: #8862
|
|
- Resolves: #8873
|
|
None is recognized as not-default and gives an error if the
searched config value is not present in the config file. This was
provoking an error with manhole not being configured.
|
|
- Resolves: #8870
|
|
|
|
|
|
|
|
|
|
I changed most of the logger statements to use a class attribute, in
this way it's easier to identify which class it's logging them.
in some cases I leave a module-level logger, when we're either using
functions or when the module it's too small.
at the same time I did a general review and cleanup of the logging
statements.
|
|
|
|
|
|
the migration from the stdlib python's logger to twisted logger is
unable to format properly the failures unless the call is adapted
- Related: #8849
|
|
- Resolves: #8829
|
|
- Resolves: #8850
|
|
|
|
- Resolves: #8844
|
|
The icon it was introduced and then deleted by mistake on the recent
window refactor after pixelated integration.
- Resolves: #8826
|
|
- Resolves: #8845
|
|
|
|
|
|
|
|
|
|
|
