soledad.git - [soledad]

Age	Commit message (Collapse)	Author
2017-09-28	[doc] improve client doc	drebs

2017-09-28	[doc] move server db info to reference section	drebs

2017-09-28	[doc] improve server doc	drebs

2017-09-28	[doc] move auth to reference section	drebs

2017-09-28	[doc] add blobs doc	drebs

2017-09-28	[docs] update badges in README to point to unified package	Kali Kaneko

2017-09-28	[docs] add entry about packaging to changelog	Kali Kaneko

2017-09-28	[pkg] remove classifier, pypi is choking on that one	Kali Kaneko

2017-09-28	[pkg] update pypi upload command	Kali Kaneko

2017-09-28	[pkg] Add packages for debian buster	Varac
	Resolves: #8963
2017-09-20	[test] use swaks on e2e test	drebs

2017-09-20	[test] add swaks to docker image	drebs

2017-09-20	[test] use new Dockerfile location to update docker image	drebs

2017-09-20	[test] remove dependency on numpy	drebs

2017-09-20	[test] make conftest.py compatible with python3	drebs

2017-09-20	[bug] pin six version to avoid breaking pgpy	drebs
	New six version (1.11.0) breaks pgpy, so we pin to previous version (1.10.0). See: https://github.com/SecurityInnovation/PGPy/issues/217
2017-09-20	[test] add e2e test for incoming mail pipeline	drebs
	I had to include part of the bonafide source code because it was the easiest way to interact with the webapp. Closes: #8941
2017-09-20	[test] allow for custom user information on soledad_client fixture	drebs

2017-09-20	[docs] prettify changelog, bump it0.10.3	Kali Kaneko

2017-09-20	[tests] add back sqlcipher checks to tox setup	Victor Shyba

2017-09-17	[responsiveness] post seconds blocked to elasticsearch	drebs

2017-09-17	[test] split benchmarks in different ci jobs	drebs

2017-09-17	[refactor] move tests to root of repository	drebs
	Tests entrypoint was in a testing/ subfolder in the root of the repository. This was made mainly because we had some common files for tests and we didn't want to ship them (files in testing/test_soledad, which is itself a python package. This sometimes causes errors when loading tests (it seems setuptools is confused with having one python package in a subdirectory of another). This commit moves the tests entrypoint to the root of the repository. Closes: #8952
2017-09-15	[doc] move environment variables to reference section	drebs

2017-09-14	[pkg] add python-routes to soledad-common	Kali Kaneko
	- Resolves: #8944
2017-09-14	[refactor] improve instructions and fix small typos	Victor Shyba

2017-09-14	[test] add graph for sqlite blobs backend benchmark test	drebs

2017-09-14	[test] move legacy-vs-blobs graphing to benchmark scripts dir	drebs

2017-09-14	[test] add SQLiteBlobBackend benchmark tests	drebs

2017-09-14	[doc] update documentation on authentication	drebs
	- add server config file options for section [soledad-server] - fix services tokens file name - improve auth doc
2017-09-14	[pkg] use /var/lib/soledad as home directory for users	drebs
	The soledad-server debian package adds 2 users (soledad and soledad-admin), and was previously using /srv/leap as their home directories. As we are now using /var/lib/soledad for blobs, it also makes sense to have soledad users' home directories be set for /var/lib/soledad. This commit implements that.
2017-09-14	[pkg] standardize location of services tokens file	drebs
	Introduction of local services authentication added a configuration file containing the auth tokens for each service. There were different names for that file, and this commit standardizes all of them to the same value: /etc/soledad/services.tokens
2017-09-14	[pkg] use /var/lib/soledad/blobs to store blobs	drebs
	Soledad Server was previously using something in /srv to store blobs in the server side. Debian/lintian doesn't like that at all, so we are changing to /var/lib/soledad/blobs. Closes: #8948
2017-09-13	[refactor] remove dead code and improve naming	Victor Shyba
	From code review. -- Related: #8945
2017-09-11	[bug] use sql file handler from adbapi threadpool	Victor Shyba
	This commit makes all write calls happen inside the same thread that opened the blob handle. Doing it outside using FileBodyProducer will yield and run the writes across random reactor threads. This is an attempt to fix #8945 -- Resolves: #8945
2017-09-11	[bug] do not allow concurrent schema creation	Victor Shyba
	Moved schema creation and migrations to the pragma locked call, so we avoid it running concurrently on a thread pool. -- Resolves: #8945
2017-09-11	[pkg] update changelog	Victor Shyba

2017-09-11	[bug] close consumer on FileBodyProducer	Victor Shyba
	It isn't closed by Twisted like the producer is. -- Resolves: #8924 -- Related: #8932
2017-09-11	[tests] fix test_unarmored_blob_encrypt flakiness	Victor Shyba
	AES can generate base64 valid strings, making this test flaky. Try to decrypt using armor=False instead.
2017-09-11	[refactor] do not use unneeded lambda	drebs

2017-09-11	[test] print responsiveness results if no elastic url is given	drebs

2017-09-11	[test] selectivelly start events server on benchmarks	drebs
	Soledad's events server might be a pain for tests because if it is not properly initialized and shut down there might be parts of the server missing or leftover in the reactor after tests are run. With the recent changes to the way tests are invocated, there's the need to further isolate events server startup for benchmarks, otherwise it will conflict with other tests. This commit moves the events server setup to inside the pytest_collection_modifyitems() hook, where we can check if the benchmark subdir was selected and properly start the events server if needed.
2017-09-11	[test] add --subdir option and blacklist	drebs
	Use subdir path to select/deselect benchmark tests. Because of the way pytest and pytest benchamrk select/deselect tests, it makes more sense for this test suite to use a --subdir option to select only a subset of tests and a blacklist of subdirectories that should not be run unless explicitelly asked to. This commit adds a --subdir option, that will deselect all tests no in ./tests/<subdir> when the option is passed to pytest. Also, a blacklist is added so, unless explicitelly added as a --subdir, tests in blacklisted subdirectories will not be run. The reasons for this modification are: - pytest-benchmarks selects/deselects tests based on the type of their fixtures. This means that fixtures have to be instantiated previous to test selection/deselection, something that may cause side effects that we want to avoid. - the usual test suite is run for all benchmarks, while some tests should only be run in specific situations (as is the case of benchmarks and responsiveness tests). It is saner to implement subdir selection than marking all tests with pytest marks and using them to select/deselect.
2017-09-11	[benchmarks] post responsiveness tests to elasticsearch	drebs

2017-09-11	[benchmarks] add responsiveness test with watchdog	drebs

2017-09-11	[style] fixes from code review	Victor Shyba

2017-09-11	[tests] improve isolation on user uuid	Victor Shyba
	Hardcoded and repeated user uuids can lead to accidental concurrent operations between test cases, breaking isolation and creating random failures. This commit improves it a bit.
2017-09-11	[feature] save sync status on client side	Victor Shyba
	Adds two new columns for sync status and retries. Also some initial rough logic for upload retry limiting. -- Resolves: #8823 -- Related: #8822
2017-09-08	[test] improve legacy vs blobs image	drebs

2017-09-08	[bug] allow POST to blobs resource8938	drebs