| Age | Commit message (Collapse) | Author |
|---|
|
Intercept the creation of the protocol factory in the HTTP connection
pool to use twisted.protocols.policies.ThrottlingFactory and control the
incoming and outgoing bandwidth.
The factory only controls one connection, so when throttling we limit
the number of connections of the pool to one per host. This way,
throttling happens in a per-host basis.
Closes: #8931
|
|
|
|
Accessing _all_dbs slows down the test and open possibilites for
heisenbugs where some old leftover database can change code behavior.
-- Resolves: #9001
|
|
|
|
|
|
|
|
|
|
|
|
Closes: #9000
|
|
It was None for parallel tests and there is already a mechanism in place
for setting this URL, which avoids it being set in two different places.
|
|
twisted.internet.protocol.Factory
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Some errors during server startup could leave the server in a zombie
state (running, but not listening). This commit makes sure the server
stops if errors occur during deferreds created on server startup.
Closes #8997.
|
|
Our current use of sys.exit(20) to stop the server when startup checks
fail affects logging in a bad way. This commit uses a system event
trigger to exit with the desired status code when startup checks fail.
Closes: #8996
|
|
When starting up a Soledad Server through the use of a fixture in tests,
a config file is created with the options needed for that test. As the
config file was being created in /etc and not being removed, this was
influencing servers started by other tests that don't use that fixture.
By always using a temporary directory in the server fixture, we make
sure that the config file is used only for that test and is removed
after the test is finished.
Closes: #8995
|
|
|
|
|
|
After we fixed the server to wait for checks before listening on ports
(201ef7a9b979f8c8efaedbe542c631944d8956f4), the TAC test started failing
randomly in our CI, probably because sometimes the server takes more
than 1 second to startup in the CI setup (docker in a vm).
This commit adds a check with retry, and so the test will retry 10 times
with an interval of 1 second before failing.
|
|
elasticsearch-py 6.0.0 introduced a TLS cert verification bug:
https://github.com/elastic/elasticsearch-py/issues/669
That bug affects our benchmarks ci pipeline:
https://0xacab.org/leap/soledad/issues/8993#note_128667
This commit only pins the version of elasticsearch-py used by
benchamarks to avoid that bug. This pinning should probably be removed
when the next version of elasticsearch-py is released.
Closes #8993.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The Soledad python source currently makes use of versioneer to calculate
versions dynamically and hardcode versions upon creation of the python
package. Unfortunatlly, this procedure does not behave well with debian
packaging, and we need to manually generate/replace the _version.py file
so the code that ends up in the debian package reports the correct
version of the software.
This commit adds a script to replace the _version.py file with a static
one and rules during packaging to run that script during preparation
stage of debian helper.
|
|
|
|
|
|
|
|
Adds the ability to have document that wont be synced. This enables
applications to use soledad to store temporary blobs that should be
discarded later instead of unnecessarily keeping the sync loop busy.
-- Resolves: #8819
|
|
Sync method to propagate deletions in batch locally.
-- Resolves: #8961
|
|
-- Related: #8961
|
|
We were doing it for downloads, but not for uploads.
|
|
This commit creates a PENDING_DELETE sync status which can be used to
keep track of whats deleted locally in order to propagate to server
later.
-- Related: #8961
|
|
Closes: #8981.
|
|
Closes: #8895
|
|
|
|
|
|
|
|
|
|
|
|
|
