summaryrefslogtreecommitdiffstats
path: root/common
Commit message (Collapse)AuthorAge
* Try to fix race condition causing us to loose initial updates.Christian Mollekopf2018-03-20
| | | | | The maillist sometimes misses updates, and this might be the root cause of it. Because it's difficult to test we'll just try this fix for now.
* The fallback on PATH was not implicit.Christian Mollekopf2018-03-20
|
* setInterval doesn't stickChristian Mollekopf2018-03-18
|
* On mac 1s is not enough, so give plenty of time on the first start.Christian Mollekopf2018-03-18
|
* Improved debug outputChristian Mollekopf2018-03-18
|
* Improved debug outputChristian Mollekopf2018-03-18
|
* Improved debugging outputChristian Mollekopf2018-03-18
|
* Use connectToServer instead of setServerName + openChristian Mollekopf2018-03-18
|
* Synchronization will fail without it, so warn.Christian Mollekopf2018-03-17
|
* QStandardPaths has a function to find executables.Christian Mollekopf2018-03-17
|
* Try starting the synchronizer with an absolute path, and fallback toChristian Mollekopf2018-03-17
| | | | | | PATH Otherwise we don't find the binary in a MacOS bundle.
* The path is not called "plugins" on macosx.Christian Mollekopf2018-03-16
|
* Ignore empty idsChristian Mollekopf2018-03-01
|
* Select all folders and emit notification if new mails are availableChristian Mollekopf2018-03-01
|
* Filtering for empty id's does not work, so detect and guard against it.Christian Mollekopf2018-03-01
|
* Fixed and tested the upgrade from a database without version.Christian Mollekopf2018-02-28
|
* Made the sync request struct public.Christian Mollekopf2018-02-27
| | | | Differential Revision: https://phabricator.kde.org/D6961
* Properly deal with filtered entities in reduced queries.Christian Mollekopf2018-02-22
| | | | Filtered entities would still end up in the entities list before.
* Some helper functions to avoid hardcoding collected property namesChristian Mollekopf2018-02-22
|
* We can't assess property changes for aggregates.Christian Mollekopf2018-02-22
|
* Handle the removal of the last item cleanlyChristian Mollekopf2018-02-22
|
* Removed unused parameterChristian Mollekopf2018-02-22
|
* Aggregation only becomes relevant when >1Christian Mollekopf2018-02-22
|
* Deal with removals in reduced queriesChristian Mollekopf2018-02-22
|
* Print aggregate idsChristian Mollekopf2018-02-21
|
* Fixed modificationsChristian Mollekopf2018-02-21
|
* Apply modifications to aggregate valuesChristian Mollekopf2018-02-21
|
* Remember aggregated idsChristian Mollekopf2018-02-21
|
* Support reductions in the list commandChristian Mollekopf2018-02-21
|
* Catch xapian exceptionsChristian Mollekopf2018-02-21
|
* If we have no store available, we also have no upgrade to execute.Christian Mollekopf2018-02-19
|
* Fixed crashes due to concurrently running queries.Christian Mollekopf2018-02-15
| | | | | | | | | | | | | | | | | | | | | | | | A single QueryRunner should never have multiple workers running at the same time. We did not properly enforce this in case of incremental updates coming in. The only way I managed to reproduce the crash: * Open a large folder with lots of unread mail in kube * Select a mail in the maillist and hold the down button * This will: * Repeatedly call fetch more * Trigger lot's of mark as read modifications that result in notifications. * Eventually it crashes somewhere in EntityStore, likely because of concurrent access of the filter structure which is shared through the state. We now ensure in the single threaded portion of the code that we only ever run one worker at a time. If we did receive an update during, we remember that change and fetch more once we're done. To be able to call fetch again that portion was also factored out into a separate function.
* Enable partial matchingChristian Mollekopf2018-02-13
|
* Improved debug messagesChristian Mollekopf2018-02-13
|
* Fixed date parsingChristian Mollekopf2018-02-13
|
* Xapian based fulltext indexingChristian Mollekopf2018-02-11
| | | | | This cuts into the sync performance by about 40%, but gives us fast fulltext searching for all local content.
* Return feedback on wether an upgrade has happened or not.Christian Mollekopf2018-02-11
|
* Support storage downgrading as wellChristian Mollekopf2018-02-11
|
* Fixed warningChristian Mollekopf2018-02-07
|
* Removed all traces of BLOB propertiesChristian Mollekopf2018-02-06
|
* Store all BLOB properties inline.Christian Mollekopf2018-02-06
| | | | | | | | | | | | | | | | | | | | | BLOB properties had a couple of intended purposes: * Allow large payloads to be streamed directly to disk, and then be handled by reference. * Allow zero-copy handling. * Keep the database values compact so we can avoid traversing large BLOBS. However, they came at the cost of code-complexity, and we lost all the benefits of our storage layer, such as transactions. Measurements showed, that for email (the intended primary usecase), the overhead is hardly measurable, with most parts performing better, or at least not worse. We additionally also gain file-system independence, which may help on other platforms. The biggest drawback is probably that large payloads need to be written to disk twice, because of the synchronizer queue (once for the queue, once for the actual data).
* Optional printing of transaction spanChristian Mollekopf2018-01-30
|
* Less hardcoded numbersChristian Mollekopf2018-01-30
|
* One central place to generate uidsChristian Mollekopf2018-01-30
|
* Include synchronization store in diskUsage calculationChristian Mollekopf2018-01-30
|
* Support for storage upgradesChristian Mollekopf2018-01-30
|
* Implemented removePrefixChristian Mollekopf2018-01-23
|
* The local variable might be gone already when the thread starts.Christian Mollekopf2018-01-08
|
* We need all parents available, not only oneChristian Mollekopf2018-01-03
|
* Use read-write locks for finer grained control to sDbi and sEnvironmentsChristian Mollekopf2018-01-03
| | | | | | | | | | There are only a few cases where have to access the list of dbis or environments, so we can normally get away with just read-locking. This seems to fix a segfault that was possibly caused be an environment being reused that has already been freed in another thread. The read-only lock when initially retrieving the environment seems to fix that.
generated by cgit v1.2.3 (git 2.25.1) at 2025-04-28 19:43:17 +0000