soledad.git/src/leap/soledad/client, branch 0.10.3 [soledad] [refactor] remove dead code and improve naming 2017-09-13T16:49:54+00:00 Victor Shyba victor1984@riseup.net 2017-09-13T16:49:54+00:00 c95f26dbb9315b94cf74747fa9c071b89331dd06 From code review. -- Related: #8945 
From code review.

-- Related: #8945
[bug] use sql file handler from adbapi threadpool 2017-09-12T01:18:38+00:00 Victor Shyba victor1984@riseup.net 2017-09-12T01:18:38+00:00 058d15265134db653987a6fff052cf81299bab51 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 
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
[bug] do not allow concurrent schema creation 2017-09-12T00:24:50+00:00 Victor Shyba victor1984@riseup.net 2017-09-12T00:24:50+00:00 969ab4ebeda2ac3abcb00d9beded5f013e074e4a Moved schema creation and migrations to the pragma locked call, so we avoid it running concurrently on a thread pool. -- Resolves: #8945 
Moved schema creation and migrations to the pragma locked call, so we
avoid it running concurrently on a thread pool.

-- Resolves: #8945
[bug] close consumer on FileBodyProducer 2017-09-11T21:24:06+00:00 Victor Shyba victor1984@riseup.net 2017-09-11T21:24:06+00:00 855ab772a800c522cca58e67140f833fa7815034 It isn't closed by Twisted like the producer is. -- Resolves: #8924 -- Related: #8932 
It isn't closed by Twisted like the producer is.

-- Resolves: #8924
-- Related: #8932
[style] fixes from code review 2017-09-11T14:22:59+00:00 Victor Shyba victor1984@riseup.net 2017-09-11T14:07:42+00:00 70aa789c94b0dcced535cee86243e2dd4113b28a 






[feature] save sync status on client side
2017-09-11T14:22:58+00:00

Victor Shyba
victor1984@riseup.net

2017-09-07T10:30:08+00:00

f0e069b9f7f0718263d96b3158c0c6a3de959d04

Adds two new columns for sync status and retries. Also some initial
rough logic for upload retry limiting.

-- Resolves: #8823
-- Related: #8822





Adds two new columns for sync status and retries. Also some initial
rough logic for upload retry limiting.

-- Resolves: #8823
-- Related: #8822







[feat] toggle http persistence depending on environment variable
2017-09-05T14:17:51+00:00

drebs
drebs@riseup.net

2017-09-04T23:30:01+00:00

e0a650d9ade2d028b9aaa4f0fb9fb07a371fbdfe












[feat] use a persistent connetion pool in http agent
2017-09-05T14:17:51+00:00

drebs
drebs@riseup.net

2017-09-02T05:38:57+00:00

e8cc3ca3d4ea868a971ae2479333a4e1807cf8be












[feat] use cookies in the client syncer
2017-09-05T14:17:51+00:00

drebs
drebs@riseup.net

2017-09-02T03:27:58+00:00

303a0cb452c4d252e0204449dd847dabc210e89b












[bug] ensure the number of threads in blobs thread pool
2017-09-05T14:17:46+00:00

drebs
drebs@riseup.net

2017-09-01T12:50:11+00:00

4d9fbf01b7fc9c0da8c2e267945d10af3837f161

The number of threads in the blobs databae thread pool can't be smaller
than the number of attemps to write concurrently to the database,
otherwise different kinds of concurrency problems may arise. By setting
the minimum and maximum number of threads to the same number, we make
sure there will always be that number of available threads for
interaction with the blobs db.





The number of threads in the blobs databae thread pool can't be smaller
than the number of attemps to write concurrently to the database,
otherwise different kinds of concurrency problems may arise. By setting
the minimum and maximum number of threads to the same number, we make
sure there will always be that number of available threads for
interaction with the blobs db.