summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAge
* Copy mail back from mailtransportChristian Mollekopf2017-04-11
|
* Moved all preprocessing back into the pipelineChristian Mollekopf2017-04-11
|
* Move the preprocssing back out of entitystore into the pipeline.Christian Mollekopf2017-04-11
| | | | | This is where this really belongs, only the indexing is part of storage. This is necessary so preprocessors can move entities as well.
* We set the instance identifier in the base classChristian Mollekopf2017-04-11
|
* Less noiseChristian Mollekopf2017-04-10
|
* Don't continue processing the pipeline until we have appended theChristian Mollekopf2017-04-10
| | | | | | message. Otherwise the processor might think its done before it actually is.
* Added uid indexChristian Mollekopf2017-04-10
|
* Fixed readAllUids and readAllChristian Mollekopf2017-04-10
|
* Send an error status messagebefore crashing.Christian Mollekopf2017-04-07
|
* Avoid crashing if we fail to resolve the local id.Christian Mollekopf2017-04-07
|
* Detect maildir resource errorsChristian Mollekopf2017-04-07
|
* Better account status aggregation.Christian Mollekopf2017-04-07
| | | | | | | | | | | | | | | | | | | | | | | Only ever enter error state on non-recoverable errors. Otherwise: * Busy state while busy, then go back to online/offline/error. * If we failed connect during replay/sync we assume we're offline. * If we failed to login but could connect we have a known error condition. * If we succeeded to replay/sync something we are apprently online. At the core we have the problem that we have no way of telling wether we can connect to the server until we actually try (network is not enough: vpns, firewalls, ....). Further the status always reflects the latest status, so even if we were in an error state, once we retry we go out of the error state and either end up back in the error state or not. When aggregating states we have to similarly adjust the state to the most relevant among the resources. The states are ordered like this: * Error * Busy * Connected * Offline
* Be less verboseChristian Mollekopf2017-04-07
| | | | We already see the resource exiting.
* Fixed changereplay guardChristian Mollekopf2017-04-06
| | | | ...and improved debug output slightly.
* Bumped releaseChristian Mollekopf2017-04-05
|
* Mailtransport notificationsChristian Mollekopf2017-03-30
|
* We already print those warnings in the synchronizerChristian Mollekopf2017-03-30
|
* Print notification type namesChristian Mollekopf2017-03-29
|
* Emit dataChanged without rolesChristian Mollekopf2017-03-29
|
* CleanupChristian Mollekopf2017-03-28
|
* Added missing property mappersChristian Mollekopf2017-03-28
|
* Guard against destructionChristian Mollekopf2017-03-28
| | | | We really need to guard against this in kasync...
* Don't filter trash in the standard queryChristian Mollekopf2017-03-28
| | | | ...we selectively apply the filter in kube instead.
* Only send notifications about being connected if we did somethingChristian Mollekopf2017-03-28
| | | | | | against the source. We used to replay no changes and then claim the resource was online.
* Track the entities that this request applies to directly in theChristian Mollekopf2017-03-28
| | | | | | | | syncrequest That way we can do the notification emitting in the synchronizer and it keeps working even if the login already fails (so the synchronizing code would never be executed).
* Emit notifications while a folder is being syncedChristian Mollekopf2017-03-27
|
* Don't use 0 as error code and better error codesChristian Mollekopf2017-03-27
|
* Pass in days to downloadChristian Mollekopf2017-03-26
|
* SinkTraceCtxChristian Mollekopf2017-03-26
|
* Fixed notification queringChristian Mollekopf2017-03-26
|
* Ignore changereplay notifications in the notificationstestChristian Mollekopf2017-03-26
| | | | | They don't get through to the resource consistently, so we have to ignore them for now to make the test reliable.
* Don't filter notifications too early.Christian Mollekopf2017-03-26
| | | | | | With this it becomes difficult to test notifications, and notifications may contain more interesting information, so we don't want to drop them too early.
* Test the result of the write operation.Christian Mollekopf2017-03-26
|
* Don't store the lockfile inside the main resource folder.Christian Mollekopf2017-03-26
| | | | | | | | | We currently use the folder as the main db folder, meaning we remove the folder when removing the db. This results in the lockfile vanishing with the db, which then confuses QLockFile (resulting in a lot of warnings). We may want to start moving everything into a resource-instance folder, but then we have to do it properly across the board.
* Use the resourceaccessfactory for notifiers as well.Christian Mollekopf2017-03-26
| | | | | Otherwise we end up trying to start the resource from multiple places in notifiertest.
* Implemented notification support in the model.Christian Mollekopf2017-03-24
| | | | | | | | This will allow us to fold things like progress and sync status directly into the model. Usecases are mail download progress and folder sync progress. Ideally we would also solve the resource/account state through this.
* Fixed identity nameChristian Mollekopf2017-03-24
|
* DomainType::nameChristian Mollekopf2017-03-23
|
* New propertiesChristian Mollekopf2017-03-23
|
* Maintain the query state instead of using the offset.Christian Mollekopf2017-03-22
| | | | | | | | | | Instead of using the offset to skip over old results requires recalculating them, and resulted in some cases in results being added multiple times to the model. By just maintaining the state we can apply the offset directly to the base-set, and maintain the state in reduction etc. which is necessary to continue streaming results while making sure we don't report anything twice.
* Default domain adaptorChristian Mollekopf2017-03-21
|
* Move type implementations in one placeChristian Mollekopf2017-03-21
| | | | | | | Having them separated is rather pointless (since we need one for every type, and all types are the interface of sink, as one), and caused quite a bit of friction when adding new types. This will also make it easier to change things for all types.
* Removed unnecessary default implementationsChristian Mollekopf2017-03-21
|
* Better debugoutputChristian Mollekopf2017-03-21
|
* Translate login errorsChristian Mollekopf2017-03-20
|
* Make error codes part of the applicationdomain interfaceChristian Mollekopf2017-03-20
|
* We need the resource filter API also for SyncScopeChristian Mollekopf2017-03-19
|
* Better error messageChristian Mollekopf2017-03-19
|
* Excluded trash from threadleaders.Christian Mollekopf2017-03-19
|
* Fixed mailquery benchmark.Christian Mollekopf2017-03-19
|
generated by cgit v1.2.3 (git 2.25.1) at 2025-06-24 18:15:34 +0000