summaryrefslogtreecommitdiffstats
path: root/common
Commit message (Collapse)AuthorAge
* Change the default for fullPayloadAvailableChristian Mollekopf2017-12-29
| | | | | | When creating new messages the default should be that the full payload is available. Not having the payload available is a specialcase used by the imap resource.
* Fixed removal of entityChristian Mollekopf2017-12-29
|
* Fixed incremental updates in folder queriesChristian Mollekopf2017-12-28
| | | | | | | | | Incremental additions of children in the tree were filtered due to the parent filter. This broke when we started to maintain state, thus causing the filter in datastorequery containing the parent filter to be carried over. Given that the incremental querying of children currently doesn't really add much value (we don't have trees that are large/deep enough), perhaps we're better off using a different approach.
* Fixed log pattern matchingChristian Mollekopf2017-12-28
|
* Print transaction spanChristian Mollekopf2017-11-21
|
* Storage debugging codeChristian Mollekopf2017-11-21
|
* Print key/value when put failsChristian Mollekopf2017-11-20
|
* Removed ResourceAccess::Private leak and resolved resulting memoryChristian Mollekopf2017-11-16
| | | | | | | | | corruption. It looks like the memory corruption (malloc started to crash) was coming QLocalSocket related signals. According to the docs it's not safe (whatever that means), to delete a QObject with pending signals, so we use deleteLater to schedule it's deletion. This resolved the crashes.
* Remove complete commands from the completeCommands hash againChristian Mollekopf2017-11-12
|
* Revert "Fixed warnings"Christian Mollekopf2017-11-12
| | | | | | Doesn't work with CATCH_ERRORS=ON This reverts commit 2bb2a10f5c4010d168b3d26e9937cf26365a0d0c.
* Fixed warningsChristian Mollekopf2017-11-10
|
* Revert "Fixed memoryleak"Christian Mollekopf2017-11-10
| | | | | | Fixing this introduces some crashes. I'll have to revisit this. This reverts commit 679f2d5d7d46b2f098e939883520b707f01b2a36.
* Fixed use after freeChristian Mollekopf2017-11-09
|
* Fixed memoryleakChristian Mollekopf2017-11-09
|
* Fixed memoryleakChristian Mollekopf2017-11-09
|
* Fixed warningChristian Mollekopf2017-11-03
|
* Ensure we get an appropriate exit code when a resource crashes.Christian Mollekopf2017-10-31
|
* Fixed parsing of larger headers.Christian Mollekopf2017-10-26
| | | | | | Just truncating the file is not a good idea. If the headers end up being larger (I just ran into that), then we just fail to parse the headers and miss important stuff like subjects. So let's not.
* Use LMDB_LIBRARIESChristian Mollekopf2017-10-20
|
* Debug outputChristian Mollekopf2017-10-10
|
* Ensure we copy all blobs when copying to another resourceChristian Mollekopf2017-10-09
|
* Error checking and debug outputChristian Mollekopf2017-10-09
|
* Optimized the incremental update case.Christian Mollekopf2017-10-08
| | | | | | | | | | | | This brings the incremental closer to a regular query (about 1.5 times as bad instead of 3.5 times). For a comparison look at MailQueryBenchmark::testIncremental() The optimization is built on the assumption that we i.e. get an update with 100 revisions, and thus the optimization applies to the case where we have multiple revisions within that batch that are part of the same reduction. In such a case we can avoid redoing the reduction lookup over and over.
* Fixed tests with secretstoreChristian Mollekopf2017-09-20
|
* Only processPendingCommandQueue once and send secret command after that.Christian Mollekopf2017-09-18
| | | | We run into a crash otherwise when creating the first account..
* Avoid storing the password in the configurationChristian Mollekopf2017-09-18
| | | | | | | The password (or any other secret), is now cached in the client process (in-memory only), and delivered to the resource via command. The resource avoids doing any operations against the source until the secret is available.
* commentsChristian Mollekopf2017-09-13
|
* Reduce the number of progress notifications for large sync sets.Christian Mollekopf2017-09-13
| | | | | We don't need an update for every mail if we download 50k mails. We just need enough to animate a progress bar.
* Simplified codeChristian Mollekopf2017-09-12
|
* Avoid reindexing the same threadChristian Mollekopf2017-09-12
|
* Clarified codeChristian Mollekopf2017-09-12
|
* Fixed getUids by type filtering.Christian Mollekopf2017-09-07
| | | | | We used to simply return all uids. Requires "sinksh upgrade"
* Avoid hiding the index() functionChristian Mollekopf2017-09-02
|
* Ensure we monitor resources for status changes that have been createdChristian Mollekopf2017-09-02
| | | | | | after the query. This fixes status monitoring when creating a new account.
* Use Q_GLOBAL_STATIC for threadsafety.Christian Mollekopf2017-08-31
| | | | | This resolves the following warning on shutdown it seems: "QObject::connect: No such signal QObject::aboutToClose() in ../../include/QtCore/5.9.1/QtCore/private/../../../../../src/corelib/io/qtextstream_p.h:75"
* Avoid non threadsafe initialization.Christian Mollekopf2017-08-31
| | | | | | local static initialization is only threadsafe if initialized on construction. The other codepath is not threadsafe, but is only used in testcode.
* Avoid use after destructionChristian Mollekopf2017-08-28
|
* use Q_GLOBAL_STATICChristian Mollekopf2017-08-28
| | | | In an attempt to resolve T6890.
* Detect connection lost so we can go to offline stateChristian Mollekopf2017-08-28
| | | | kimap should really have better error codes...
* Only return connected if there is any resource connected.Christian Mollekopf2017-08-26
|
* Default to NoStatus for resources until we know more.Christian Mollekopf2017-08-25
| | | | | | This allows the aggregation to ignore resources where we don't have any status information yet, so the account doesn't always end up being offline.
* Ensure the copied enum matchesChristian Mollekopf2017-08-22
|
* Implemented thread mergingChristian Mollekopf2017-08-18
| | | | | It can happen that thread messages are not delivered in order, which means we will have to merge threads once all messages are available.
* static members can apparently still lead to crashes...Christian Mollekopf2017-08-13
|
* Silence the compiler warningChristian Mollekopf2017-08-11
|
* CleanupChristian Mollekopf2017-08-11
|
* Avoid warningChristian Mollekopf2017-08-09
| | | | | | | setFuture can emit signals directly if the future is already stopped. This does not apply to our case but it fixes the warning. "QFutureWatcher::connect: connecting after calling setFuture() is likely to produce race"
* Use imported targets instead of qt5_use_modulesHeiko Becker2017-07-29
| | | | | | | | | | | | | | | | | | | From Qt's documentation: "This macro is obsolete. Use target_link_libraries with IMPORTED targets instead." It's only recommended with cmake >=2.8.9 & < 2.8.12. Sink already requires cmake 3.0. One advantage of using the imported targets is, that cmake complains if a target isn't found before it's used, like Qt5Concurrent missing from the find_package_call here. Reviewers: #sink, cmollekopf Reviewed By: #sink, cmollekopf Subscribers: #sink Tags: #sink Differential Revision: https://phabricator.kde.org/D6361
* Adjusted docs and test.Christian Mollekopf2017-07-27
|
* Empty resource id's are valid when we search for resources.Christian Mollekopf2017-07-27
|