| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
- 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 is an attempt to debug the failure of the vpn e2e test on the
works. if this commit makes the test pass, it means that we need to
capture the "no polkit authentication agent running" in a more
meaningful way.
|
|
|
|
|
|
|
|
|
|
As a couple of initial, example tests, Center and Confirmation were
refactored and tests were set up and added with mocha, enzyme and
chai. Spinner was also refactored.
|
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
|
|
Previously, if the active VPN was in the connecting state and the VPN
status component for another account was rendered the status for the
new account would show as connecting. This was because it didn't check
the domain returned from the status endpoint when parsing the returned
data and setting "connecting" as the status. We can safely assume that
a non active VPN is in the "down" state, so that's what this commit
does.
|
|
the BITMASK_INVITE_CODE variable must be set from within the CI
settings.
|
|
The version of webkit we're using doesn't understand display: flex,
instead it needs display: -webkit-flex.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This will enable forks to run jobs, without needing access to the
private token, or access to the docker-in-docker tagged runner
|
|
Allows to upload a key to providers that use a different api uri than
api.provider.net
- Resolves: #8868
|
|
|
|
I've removed the add_listener method because it's not used anywhere.
|
|
|
|
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
|
|
|
|
This adds a lock icon to the account list next to the account with the
currently active VPN. The icon is green if the VPN is connected,
yellow if the VPN is connectiong, and red in any other case.
- Resolves: #8853
|
|
|
|
|
|
- Resolves: #8884
|
|
|
|
- Resolves: #8886
|
|
- Resolves: #8887
|
|
|
|
Resolves: #8882
|
|
|
