| Age | Commit message (Collapse) | Author |
|---|
|
- skip ssl verification for this test
- use mail.bitmask as e2e provider for now
(ci.leap.se seems broken; cannot download smtp cert)
|
|
- Improve tests too: add entry in resolv.conf, not done without
resolvconf
|
|
- add invite code
|
|
- Resolves: #8874
|
|
|
|
- Resolves: #8881
|
|
|
|
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.
|
|
|
|
the BITMASK_INVITE_CODE variable must be set from within the CI
settings.
|
|
|
|
|
|
|
|
I've removed the add_listener method because it's not used anywhere.
|
|
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: #8882
|
|
When the tests/docker directory is changed, this CI job is triggered to
build the docker image and push it to the bitmask-dev container
registry.
This allows us to change the existing CI jobs to pull the image from our
registry, instead of from dockerhub.
|
|
are changed
|
|
mock a renamed method.
|
|
There was a test in the Keymanager refresher that was testing the
randomness of the refreshing intervals. It was producing a bunch of
intervals and checking that all of them where different. This test
(rarelly) fails some times, but this is not a sign of bad randomness.
- Resolves: #8813
|
|
In addition to the UnicodeError exception in _process_decrypted_doc
function, we have added ValueError to the exception list so that we can
catch any error in JSON parsing, specially a 'NODATA' error that we were
getting with some of the emails.
This is in reference to issues -
https://github.com/pixelated/pixelated-user-agent/issues/908 &
https://github.com/pixelated/pixelated-user-agent/issues/981 - to ignore
documents that have this problem and not have Soledad try to sync them
again and again.
with @deniscostadsc
|
|
with @deniscostadsc
|
|
Related with: https://github.com/pixelated/pixelated-user-agent/issues/924
with @aarni
Signed-off-by: Ruben Pollan <meskio@sindominio.net>
|
|
implements a global auth token for the app.
this token is written to .config/leap/authtoken, and passed to the
anchor part of the landing URI when opening the index resource by the
browser.
- Resolves: #8765
|
|
Active user is now only a concept of the cli. For it we add a
~/.config/leap/bitmaskctl.cfg file.
- Resolves: #8769
|
|
- Resolves: #8755
|
|
Check if a new fetched key was signed by a old key with the same address.
Please do not merge before: https://github.com/isislovecruft/python-gnupg/pull/150
- Resolves #8112
|
|
encode to ascii any parameter passed as unicode.
|
|
|
|
so that whitelisting doesn't have to peek into the data.
added more documentation and some tests stubs too.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
my goal here is also to start *real* unit tests for the keymanager, that
do not need an actual soledad implementation. this should make all the
coming tests much faster. I would like to have a common soledad stub
that follows the soledad api, but w/o actual disk persistance, and
migrate all the bulk of the keymanager tests to these unit tests.
|
|
- some pep8 problems
- some confusion with old and new code after merging
from old keymanager
|
|
disabled some tests that were failing, for some reason the twisted
logger doesn't want to be patched?
besides, I don't think it's a good idea to rely on log information for
tests. what is it really that we were trying to test there?
|
|
Port of the original commit:
8f1fe8dd4a54fd2bdda2fc78c339ce9b3d0fc331
by Zara Gebru that introduced updating keys in the background.
This was made in the legacy leapcode/keymanager repo, but was lost in
the merge to the unified bitmask-dev.
Original commit message follows:
--------------------------------
- refresh random key in random time
- add get key by fingerprint
- refactor nicknym methods to own file
- tests
- note this do not include a check for
revoked key, since that need some changes
in gnupg
- Related: #6089
|
|
This has been previously encapsulated in a dict, and the commands were
not modified accordingly.
I'm adding some very basic test for the KeymanagerService public api
contract.
- Resolves: #8577
|
|
in the variant that was merged, we call a failure method to get the
exception, so it's better to test a real failure initialized with an
exception.
besides, I'm starting to hate mocks.
|
|
This commit originall contained a fix for a wrong variable name that
avoided the outgoing service to be launched. This had been fixed in a
concurrent mr that got merged before this one. However, this MR
contained a couple of tests for the OutgoingService, and I'm merging
those tests now.
|
|
Missing yield from _insert_key_docs, which returns a Deferred, was
causing tests to fail.
|
|
Before we used to have content_doc.content_type = 'text/plain;
charset="utf-8"'.
Currently, we have content_doc.content_type = 'text/plain'.
This change will give us, on top of that: content_doc.charset = 'utf-8'.
One can reconstruct the original one using .content_type and .charset.
|
